Satellite Internet for Oil and Gas Operations: Engineering Reference

The oil and gas industry operates across some of the most connectivity-challenged environments on Earth. Upstream production occurs in remote desert basins, offshore deepwater fields, arctic tundra, and equatorial jungle — locations where terrestrial fiber and cellular infrastructure is either nonexistent or prohibitively expensive to build. For these sites, satellite is not a convenience but the primary transport for production telemetry, safety systems, and personnel communications.

This is an engineering reference for satellite communications across oil and gas operations. It covers what each segment of the value chain actually needs from a network, the end-to-end architecture, how SCADA behaves over high-latency satellite links, hazardous-area certification of terminals, redundancy and availability design, and realistic cost structures. The goal is a vendor-neutral baseline that operators, OT/automation engineers, and procurement teams can use to specify and compare connectivity options. For the mining and remote-industrial equivalent, see Satellite Internet for Mining and Remote Industrial Sites. For offshore vessels and support fleets, see Maritime Satellite Internet.

Connectivity Requirements Across the Oil and Gas Value Chain

Connectivity requirements differ sharply between the three segments of the industry. Specifying a single "oil and gas" solution without distinguishing them leads to either over-provisioned cost or under-provisioned reliability.

Upstream (Exploration and Production)

Upstream sites — wellheads, drilling rigs, offshore platforms, and FPSOs — generate the most demanding requirements. A producing well site needs continuous SCADA telemetry (pressure, temperature, flow, choke position), safety and ESD (emergency shutdown) signalling, video for remote surveillance and well intervention support, voice for isolated crews, and increasingly real-time analytics for production optimization. Offshore platforms add crew welfare traffic for rotational personnel and high-bandwidth needs during drilling campaigns.

Midstream (Transport and Storage)

Midstream connectivity is dominated by pipeline monitoring across vast distances. Cathodic protection readings, pressure and flow at compressor and pump stations, leak-detection telemetry, and valve actuation commands must reach the control center reliably from stations that may be hundreds of kilometers apart with no local infrastructure. Bandwidth per site is modest, but the number of sites and the safety-critical nature of leak detection make availability the governing requirement.

Downstream (Refining and Distribution)

Downstream facilities — refineries, terminals, and distribution depots — are usually near infrastructure and use satellite mainly as backup to terrestrial links, or as primary connectivity for remote tank farms and loading terminals. The dominant requirement here is business continuity: an automatic failover path that keeps process control and enterprise systems online when the terrestrial link fails.

End-to-End Connectivity Architecture

A satellite deployment for an energy site follows a four-segment architecture, each layer engineered for the operational environment.

Field Instrumentation and RTUs

At the lowest layer, field instruments — pressure transmitters, flow meters, gas detectors, and valve actuators — interface with RTUs or PLCs that aggregate data and run local control logic. These devices speak industrial protocols (Modbus TCP/RTU, DNP3) and are the source and destination of the traffic the satellite link must carry. Local autonomy matters: well-designed RTUs continue safe local control during a link outage and buffer data for transmission on reconnection.

VSAT Terminal

The VSAT provides the satellite link between the field network and the wider network. A terminal comprises an outdoor unit (parabolic antenna 1.2–2.4 m for GEO, or a flat phased-array panel for LEO; plus the block upconverter and low-noise block) and an indoor unit (the satellite modem/router handling QoS, encryption, and acceleration). Power is supplied by AC mains where available or, more commonly upstream, by a solar-battery hybrid.

Space Segment

The satellite relays traffic between the terminal and the gateway. GEO satellites (operators such as Intelsat, SES, Arabsat, Yahsat, and Eutelsat) remain dominant for fixed energy sites because they provide continuous coverage of a fixed footprint with predictable link budgets and contractual CIR. LEO constellations (Starlink, Eutelsat OneWeb) add low latency and high throughput and are increasingly used as a complementary or failover path. See GEO vs LEO vs Hybrid below.

Gateway and SCADA Master

The gateway earth station connects the satellite network to terrestrial backbone, and from there traffic reaches the SCADA master, historian, and enterprise systems at the operations center. For multi-site operators, a managed network operations center (NOC) monitors terminal health, manages bandwidth allocation by operational priority, and provides the single pane of glass across all field sites. See End-to-End Architecture and Network Management and Control.

Engineering SCADA Over Satellite

The single most misunderstood aspect of energy satellite connectivity is how SCADA behaves over a high-latency link. Getting this right is the difference between a reliable system and one that times out constantly.

Protocol Behavior over High-Latency Links

A GEO link adds roughly 600 ms of round-trip latency; a LEO link adds 30–60 ms. Legacy polling protocols were designed for low-latency serial or terrestrial networks, so default timeout and retry settings frequently fail over GEO. A SCADA master polling 200 RTUs sequentially with a 3-second timeout will accumulate failures simply because the round trip plus processing exceeds the window. Two adjustments solve most problems: extend poll timeouts to accommodate the satellite round trip (typically 5–10 seconds for GEO), and prefer report-by-exception or DNP3 unsolicited responses over constant polling so that field devices push changes rather than waiting to be asked.

TCP Acceleration and Bandwidth Sizing

Many satellite modems include TCP/protocol acceleration (PEP — performance enhancing proxies) that spoof acknowledgements locally to overcome the latency penalty on chatty protocols. Telemetry bandwidth itself is small: a poll-response cycle is typically 100–500 bytes, and even 200 RTUs at 10-second intervals aggregate to only 50–100 kbps. Video, file transfer, and crew welfare dominate the link budget, which is why traffic separation matters.

Addressing: Static IP and CGNAT

A recurring deployment pitfall — especially with LEO services — is addressing. Consumer-tier LEO accounts often place terminals behind carrier-grade NAT (CGNAT) with no public IP and no inbound port forwarding, which breaks SCADA polling that originates from the control center and breaks site-to-site VPNs. Energy deployments require a business-tier service with a static public IP, or a network architecture (overlay VPN / SD-WAN with a cloud concentrator) that does not depend on inbound reachability.

OT/IT Segmentation and Security

Control traffic and business/crew traffic must be logically separated. Standard practice places OT (SCADA) and IT (welfare, email, video) on separate VLANs with strict QoS prioritizing control traffic, and carries control over encrypted VPN tunnels for integrity. The relevant framework is IEC 62443 for industrial network security; satellite links should be treated as untrusted transport with encryption and segmentation enforced end to end. See QoS Over Satellite and Traffic Shaping.

GEO vs LEO vs Hybrid for Energy

There is no single correct orbit for energy connectivity — the right answer depends on the site's latency tolerance, the value of a contractual SLA, and the criticality of the link.

For safety-critical sites, the emerging standard is a hybrid: a GEO VSAT providing contractual CIR and a proven hazardous-area hardware path, with LEO carrying latency-sensitive and bulk traffic and providing an independent failover path. See Hybrid Multi-Orbit Satellite Networks and the Satellite Latency Comparison.

Hazardous-Area Compliance: ATEX and IECEx

This is the requirement most generic connectivity guides omit, yet it is mandatory for oil and gas. Upstream and many midstream facilities contain areas where flammable gas or vapor may be present, classified into zones, and any equipment installed there must be certified for that zone.

• Zone 0 — explosive atmosphere present continuously or for long periods.
• Zone 1 — explosive atmosphere likely in normal operation.
• Zone 2 — explosive atmosphere unlikely, and short-lived if it occurs.

ATEX (the European Directive) and IECEx (the international scheme) define the certification of equipment for these zones. Standard satellite modems and VSAT electronics are not intrinsically safe and must not be installed in a classified zone without protection.

The practical engineering approach is placement and protection: mount the antenna and outdoor unit on a mast or structure outside the classified area wherever line-of-sight allows; locate the indoor unit in a safe (non-classified) control room or instrument building; and where electronics must sit in a Zone 1 or Zone 2 area, house them in a certified enclosure — flameproof (Ex d), increased-safety (Ex e), or purged/pressurized (Ex p) — with appropriately rated cable glands and junction boxes. Hazardous-area classification drawings should be consulted at the design stage, not retrofitted after a terminal is specified. See Terminals and Remotes for terminal fundamentals.

Environmental and Power Constraints

Energy sites impose extremes that drive terminal selection.

• Temperature — desert fields can exceed 55 °C and arctic operations drop below −40 °C. Specify extended-temperature-range electronics, sun shields, or heated/cooled enclosures accordingly.
• Power — remote sites rarely have grid power. Low-power modems (30–60 W), correctly sized solar arrays, and battery banks rated for worst-case seasonal sunlight hours are essential; under-sizing the power system is a common cause of unreliable links.
• Dust, vibration, and corrosion — terminals near drilling, compression, or coastal/offshore environments need appropriate IP ratings, vibration tolerance, and corrosion-resistant hardware.
• Rain fade — Ku- and Ka-band links degrade in heavy rain; specify adequate link margin and adaptive coding and modulation (ACM). See Rain Fade in Satellite Communications and Ku-band vs Ka-band.

Availability and Redundancy Design

Availability is the governing metric for oil and gas connectivity because the cost of a control-system outage — deferred production, a missed leak alarm, an HSE incident — dwarfs the cost of the link.

Link Budget and Margin

A site link budget should carry margin for rain fade appropriate to the ITU-R rain zone, with ACM configured to trade throughput for availability during fades rather than dropping the link. Critical sites should validate the worst-case availability the chosen band and margin actually deliver, not the clear-sky figure.

Redundancy Architectures

Safety-critical sites use independent failure modes: dual antenna and modem, two satellites or two orbits (GEO + LEO), and automatic failover so a single satellite, gateway, or modem failure does not isolate the site. See Satellite Link Availability, Satellite Gateway Diversity, and Satellite Backhaul.

SLA Targets

Typical targets are 99.7%+ availability for safety-critical control and 99.5% for non-critical IT and welfare traffic. Note that 99.7% still permits roughly 26 hours of downtime per year — for ESD and leak detection, the redundancy architecture, not the headline SLA number, is what delivers real resilience.

Recommended Configurations by Site Type

Cost Structure and Total Cost of Ownership

Connectivity cost has three components: capital (terminal $2,500–$50,000+ depending on orbit and hardening; installation and commissioning $5,000–$25,000 depending on site access), recurring airtime ($500–$10,000+/month depending on CIR, coverage, and orbit), and operations (managed NOC monitoring, typically $200–$1,000/month per site). Across a multi-year field lifecycle, connectivity is a small fraction of total operating cost — which is why availability and redundancy, not the lowest monthly rate, should drive the decision for production-critical sites.

Frequently Asked Questions

Can LEO (Starlink) replace GEO VSAT for oil and gas SCADA? For latency-sensitive and bulk traffic, LEO is compelling. For safety-critical SCADA it is increasingly used, but two conditions must be met: a business-tier service with a static public IP (not CGNAT), and an honest assessment of the SLA — most LEO tiers do not yet offer the contractual availability guarantees that GEO VSAT does. The common pattern is hybrid: LEO for performance, GEO for the contractual floor and hazardous-area hardware path.

How is SCADA polling affected by satellite latency? A GEO round trip is ~600 ms, so poll timeouts tuned for terrestrial networks will fail. Extend timeouts to 5–10 seconds for GEO, enable TCP/protocol acceleration on the modem, and prefer report-by-exception or DNP3 unsolicited reporting over constant polling.

Do satellite terminals need ATEX or IECEx certification? Standard terminals are not intrinsically safe. Place the antenna and electronics outside classified zones where possible; where equipment must sit in a Zone 1 or Zone 2 area, use a certified enclosure (Ex d, Ex e, or Ex p) with rated glands and junction boxes, guided by the site's hazardous-area classification drawings.

What availability SLA should an upstream site require? Target 99.7%+ for safety-critical control and 99.5% for IT/welfare traffic — but treat the redundancy architecture (dual orbit, dual modem, automatic failover) as the real driver of resilience, since 99.7% still allows ~26 hours of annual downtime.

Which frequency band is best for oil and gas? C-band offers the most rain resilience and is favored for offshore and tropical critical links; Ku-band balances availability and terminal cost for most onshore sites; Ka-band and LEO offer higher throughput where rain margin and coverage permit. See Ku-band vs Ka-band.

How much bandwidth does a remote well site actually need? SCADA telemetry alone is small — 50–100 kbps aggregates a large RTU count. Real bandwidth is driven by video surveillance, remote-support sessions, and crew welfare, which is why traffic separation and QoS prioritizing control traffic are essential.

Related Reading

• Satellite Internet for Mining and Remote Industrial Sites
• Maritime Satellite Internet: VSAT vs Starlink for Ships
• QoS Over Satellite and Traffic Shaping
• Hybrid Multi-Orbit Satellite Networks
• Satellite Link Availability
• Desert Infrastructure Solutions
• Terminals and Remotes

Conclusion

Satellite is the foundational connectivity layer for oil and gas operations beyond the reach of fiber and cellular. The engineering decisions that matter most are not which vendor, but which orbit and redundancy model fits the site's criticality, how SCADA is tuned for satellite latency and addressing, and how terminals are placed and certified for hazardous areas. GEO VSAT with committed CIR remains the standard for mission-critical control; LEO adds latency and throughput; and hybrid multi-orbit architectures, designed around independent failure modes and honest availability targets, represent the resilient standard for production-critical energy infrastructure.