A ground station is an Earth-based facility with large antennas and radio equipment that communicates with satellites and connects them to terrestrial networks. In satellite internet, ground stations, often called gateways, are where traffic from user terminals leaves the space segment and enters the internet backbone, and where commands and telemetry for the satellites are exchanged.
Every satellite internet system has three parts: the space segment of satellites, the user segment of dishes and terminals, and the ground segment of ground stations, network operations centers and fiber links. The ground segment is less visible than the satellites, yet it largely determines capacity, latency and regulatory reach.
What a ground station does in satellite internet
A ground station performs two broad roles. As a gateway, it carries user data: traffic from a subscriber’s terminal travels up to a satellite and down to the gateway, which routes it onto the internet, and the reply takes the reverse path. As a telemetry, tracking and command (TT&C) station, it monitors satellite health and sends maneuver and configuration commands.
| Station type | Main function | Typical antennas |
|---|---|---|
| Gateway | User traffic between satellites and internet | Several tracking dishes or one large fixed dish |
| TT&C station | Satellite health, orbit control, commands | Tracking dishes, often in S band |
| Point of presence site | Interconnection with internet exchanges | No antennas, colocated network equipment |
| Teleport | Shared facility serving several operators | Many dishes for different satellites |
The gateway also hosts network functions such as IP routing, traffic shaping, encryption endpoints and, in many designs, the core network that authenticates subscribers. In regenerative systems that process data on board, some of these functions move into the satellite.
Ground stations in GEO and LEO systems
The orbit of the constellation changes the ground segment dramatically. A geostationary satellite appears fixed in the sky, so its gateway uses a large fixed dish, commonly 7 to 13 meters in diameter, pointed permanently at one satellite. A small number of gateways can serve a whole continent.
In LEO constellations at altitudes of roughly 500 to 1,200 km, each satellite crosses the sky in minutes and sees only a region a few thousand kilometers across. Gateways therefore need multiple tracking antennas, usually 1.5 to 3.5 meters in diameter under radomes, so they can hand over from a setting satellite to a rising one without interruption. Operators need many gateways spread across the service area, often dozens per continent, unless satellites relay traffic among themselves.
| Property | GEO system | LEO system |
|---|---|---|
| Antenna type | Large fixed parabolic dish | Several small tracking dishes |
| Number of gateways | Few per region | Many, close to users |
| Handover need | None in normal operation | Continuous, every few minutes |
| Round-trip latency contribution | About 480 ms or more | Typically 20 to 60 ms total |
| Placement constraint | View of one satellite | Within reach of user cells |
Optical inter-satellite links reduce this dependence. When satellites can pass data among themselves by laser, traffic can reach a gateway far from the user, which allows service over oceans and remote regions where no gateway is within view. MEO systems fall in between, with tracking antennas but fewer handovers than LEO.
Frequency bands and key engineering parameters
Gateways usually operate in higher frequency bands than user links, because they need very large bandwidth and can afford bigger, more precise antennas. The Ka band, around 17 to 30 GHz, is the workhorse for modern gateways, and Q and V bands at roughly 37 to 52 GHz are increasingly used to free Ka spectrum for users.
| Parameter | Typical range | Effect |
|---|---|---|
| Antenna diameter | 1.5 to 13 m | Gain, beam width, rain margin |
| Feeder link bandwidth | Hundreds of MHz to several GHz | Total capacity per satellite |
| Uplink transmit power | Hundreds of watts to kilowatts | Link margin under fading |
| Backhaul capacity | 10 to several hundred Gbit/s | Throughput into the internet |
| Site availability target | Often 99.9 percent or higher | Need for redundancy and diversity |
Higher bands suffer from rain fade, strong attenuation during heavy precipitation. Operators counter it with adaptive coding and modulation, uplink power control and site diversity, where a second gateway a few tens of kilometers away takes over when a storm hits the first.
Siting, licensing and connectivity
Choosing a gateway site is a trade-off between radio, network and regulatory needs. The site needs a clear view of the sky above a minimum elevation angle, low radio interference, resilient power and, above all, high-capacity fiber backhaul to an internet exchange or data center.
- Licensing: each gateway requires national spectrum and earth station authorization, often with coordination to protect terrestrial links.
- Market access: regulators may require local gateways to keep domestic traffic and lawful interception within the country.
- Physical security: gateways are critical infrastructure and need protection against tampering and outages.
- Climate: rain-heavy regions require more margin or diversity sites.
Ground station capacity is increasingly offered as a service. Shared teleports and cloud-hosted ground networks let smaller satellite operators rent antenna time instead of building their own sites, a model popular for Earth observation satellites.
Common misconceptions and failure modes
A frequent misconception is that satellite internet bypasses terrestrial infrastructure entirely. In reality, almost all traffic still ends up on fiber networks via a ground station, so the ground segment is a potential bottleneck. If a region lacks gateways and the constellation has no inter-satellite links, service quality there suffers or is unavailable.
Typical failure modes include fiber cuts at the gateway, power outages, heavy weather beyond the designed margin and misconfigured routing that sends traffic to a distant point of presence, adding latency. Users may also notice that their apparent internet location matches the gateway or point of presence rather than their home, which affects content localization and geoblocking.
A non-technical view
A satellite dish on your roof talks to a satellite in space, but the satellite itself is not the internet. The data has to come back down somewhere, and that place is a ground station: a fenced site with several big antennas connected to fast fiber cables.
You can think of it as a harbor for internet traffic. Ships, the satellites, carry goods between the open sea and the harbor, and from there everything continues by road, the fiber network. Without enough harbors in the right places, even the best fleet of ships cannot deliver much cargo.
A concrete example
A LEO satellite internet operator wants to launch service in a mountainous country. Its satellites lack inter-satellite links in that region, so every user beam must be within view of a gateway. Engineers place three gateway sites, each with eight tracking antennas of about 2 meters, near major fiber routes and at least 50 km apart.
One site sits in a valley prone to summer thunderstorms, so a fourth site is added as a diversity backup. During the first heavy storm, Ka band attenuation at the valley site rises sharply, traffic shifts automatically to the backup and customers notice only a brief speed reduction. The design keeps typical latency under 40 ms because traffic enters the national fiber network close to the users.