A satellite link carries information between equipment on Earth through a spacecraft. A dependable service also needs a usable view of the sky, an active service plan, ground-network connectivity and power at the places where people work. Start with the task—sending a report, joining a call or connecting a remote office—then check the entire path.
Follow one packet from the user to the application
For a typical internet connection, a laptop sends data through a local router to the satellite terminal. The terminal transmits toward a spacecraft; the traffic reaches a gateway on Earth and continues through terrestrial networks to its destination. Some networks also route traffic between satellites before returning it to Earth. The response makes a corresponding return journey.
A terminal is the user's satellite equipment. A gateway connects the space network with networks on the ground. A beam is a coverage region served by an antenna pattern; capacity within it may be shared. ESA's telecommunications explanation describes the space relay and its ground endpoints.
This path explains a common diagnostic trap: a strong Wi-Fi signal establishes a local radio connection, while the satellite service or destination application may still be unavailable. Check the router, terminal and application as separate stages.
Choose the orbit for the job
Scroll the table horizontally on small screens. Keyboard users can focus the table region and use the arrow keys.
| Orbit | What it means for a link | What to ask |
|---|---|---|
| Geostationary (GEO) | A satellite appears fixed above the equator; a fixed installation can point toward one location. | Is that direction unobstructed? Can the application tolerate the propagation delay? |
| Low Earth orbit (LEO) | Satellites move across the sky; a constellation and handovers support continuing service. | How much open sky does this terminal need? What happens during obstructions or handovers? |
| Medium Earth orbit (MEO) | Between LEO and GEO; service architecture determines tracking and coverage. | Which terminal, coverage area and handover arrangements are included? |
ESA's orbit guide places geostationary satellites about 35,786 kilometers above the equator. Lower orbits shorten the radio journey, but actual performance also includes scheduling, processing, gateways and internet routing. Use the orbit label to form testable expectations, then measure the applications that matter.
Measure the experience the task needs
Throughput measures useful data delivered per second. Latency measures travel time; record whether a test reports one-way or round-trip delay. Jitter describes variation in delay, and packet loss records missing packets. A fast bulk download can coexist with pauses in an interactive call.
Test the actual work application at the hours it matters. Record upload and download results separately, connection method, server or destination, local traffic and weather. Run a wired local test when practical to separate Wi-Fi trouble from the wide-area link. Provider engineering, such as Starlink's latency discussion, shows why delay has several contributors beyond orbital altitude.
For a remote interview, test a sustained call and an attachment upload together. For overnight reporting, test transfer completion and retries. Choose acceptance criteria before the trial and judge the complete set of representative measurements.
Write a site brief before choosing equipment
- Identify the place and use. Record coordinates, country, fixed or mobile operation, essential applications and working hours.
- Document the sky view. Use the selected provider's survey method at the proposed terminal location. Include seasonal tree growth and nearby structures.
- List every powered component. Terminal, router, switch and local access points may need separate backup arrangements.
- Describe network integration. Ask about address assignment, VPN compatibility, inbound access, filtering and who administers the router.
- Assign recovery responsibility. Keep provider contacts, site access instructions, approved spares and configuration backups available offline.
Have the installer resolve mounting, cable routing, weather exposure and equipment-specific requirements. A clear-sky photograph helps discussion; the equipment manual and site assessment determine the installation.
Test the backup as a working path
Two internet subscriptions can still depend on the same router, power supply or building entry. Draw the shared components and decide which failures the backup must survive. During an agreed test window, withdraw the primary connection using the approved procedure and measure when the essential application works again.
Record existing sessions that drop, login or multifactor steps that fail, DNS behavior and the return to the primary link. A backup that restores web browsing may still fail to restore a business VPN. Keep one short recovery sheet accessible without the internet.
Use the satellite link planning checklist to turn this guide into a site brief and test record. For buying an individual service, continue with satellite broadband selection; for contracted reliability, use the enterprise service guide.
Sources and further reading
Source links reviewed September 28, 2026. Check current service terms, equipment documents and operational notices when applying the guide.