Offshore Satellite Connectivity for Platforms and Remote Islands

Offshore satellite connectivity should be designed as fixed critical infrastructure, not purchased as a generic internet package. The right system connects a defined island or offshore site to named applications through an authorized satellite service, engineered power and mounting, secure local networks, shore-side operations, and a support contract that can be tested.

This guide covers fixed offshore platforms, remote islands, and archipelago networks. A moving ship has different terminal, blockage, route, authorization, and sea-trial requirements; use the dedicated maritime satellite internet guide for ships for that case.

Quick Answer

A dependable fixed-site design has six evidence sets:

accepted offshore link = site and application dossier
                        + authorized service and terminal
                        + reproducible availability design
                        + resilient power and physical installation
                        + segmented, monitored local network
                        + witnessed failure and application tests

Do not select a solution from an orbit name, frequency band, advertised speed, or coverage-map color alone. Those labels do not define the purchased capacity, gateway path, local authorization, rain performance, support boundary, or recovery behavior.

Start with the Site and Application Dossier

Issue every bidder the same dated input pack. At minimum, record:

• site coordinates, elevation, horizon mask, nearby structures, proposed antenna locations, and access restrictions;
• platform or island function, population or personnel level, operating calendar, and planned expansion;
• applications, endpoints, direction of initiation, busy-period demand, latency and loss sensitivity, and outage consequence;
• operational technology, enterprise IT, guest or welfare, voice, video, telemetry, cloud, and vendor-support traffic as separate classes;
• existing fiber, microwave, cellular, satellite, or radio paths and their known common dependencies;
• grid, generator, UPS, battery, renewable generation, earthing or bonding, surge protection, and heat-rejection conditions;
• wind, corrosion, salt spray, rainfall, lightning, temperature, flooding, vibration, and hazardous-area constraints;
• installation access, lifting, permits, spares, technician travel, weather windows, and recovery time expectations;
• responsible organizations for the terminal, LAN, security, applications, teleport, terrestrial handoff, and incident response.

Turn the application list into a traffic matrix instead of a single throughput number:

The matrix determines capacity, traffic policy, addressing, security, monitoring, and the minimum service that must remain during a failure. Average monthly consumption cannot replace it.

Map the End-to-End Architecture

An offshore connection normally contains more than the remote antenna and modem:

applications and field systems
        |
segmented LAN, firewall, routing, identity, and local services
        |
remote terminal and RF chain
        |
satellite or constellation
        |
gateway, network core, and terrestrial handoff
        |
enterprise, cloud, public internet, or control center

Name the owner, monitoring source, acceptance point, and recovery method for every segment. A provider may manage only part of the chain, while the contractual service level may be measured at a point that excludes the site LAN, power system, public internet, cloud application, or customer security overlay.

Use the end-to-end satellite architecture and ground segment guide to document those demarcations before comparing offers.

Fixed Island Network

An island program may include one aggregation site and many small remote sites. Do not force every location into one standard bill of materials. Classify sites by application consequence, available power, maintainability, and path options.

A hub island with fiber access may aggregate outer sites, but that creates a dependency on its landing station, local power, router, and operations team. A direct satellite path from each island may remove that aggregation dependency while creating more terminals to operate. Draw both architectures and test the real failure cases before deciding.

Offshore Platform

A platform adds marine exposure, constrained deck space, lifting and permit controls, possible hazardous-area boundaries, and strong separation requirements between operational and welfare networks. Determine whether the structure is fixed, floating, or subject to motion; a terminal suitable for a fixed installation is not automatically suitable for a moving or station-keeping asset.

The antenna position must be justified by a site-specific structural, RF, obstruction, access, corrosion, cable, power, lightning, and safety review. A sealed radome or a material label alone does not prove suitability for the environment.

Select a Service from Evidence, Not Labels

Ask each bidder to identify the exact service, terminal, network, and commercial policy. Capture:

The ITU Radio Regulations, 2024 edition define international spectrum allocations and radio-service frameworks. They do not replace the national authorization and site-specific obligations that apply to an earth station. Obtain written evidence for the actual country, coordinates, equipment, frequency assignment, and service arrangement.

Orbit and Band Are Inputs, Not Outcomes

GEO, MEO, and LEO paths can all be valid candidates. Their usefulness depends on the purchased service and the applications:

• a fixed GEO path can offer stable geometry, but its service terms, capacity, gateway design, and application latency still require evidence;
• an NGSO service can reduce the space-path propagation component, but route variation, handovers, obstruction, gateway or point-of-presence routing, and traffic policy remain part of measured performance;
• a hybrid design can improve resilience only when the two paths do not share the failure that matters.

Likewise, C-, Ku-, and Ka-band labels do not establish availability. Frequency, elevation angle, local propagation, antenna performance, uplink and downlink budgets, coding and modulation, interference, and operator controls must be assessed together. Use ITU-R P.618-14 with the applicable companion recommendations and site inputs when predicting Earth-space propagation effects. Do not copy a generic rain margin or availability percentage from another location.

Engineer Availability from Failure Domains

List the events that can interrupt the required application, then show what remains:

Two terminals are not automatically two independent services. They may share the same mast, power board, cable tray, router, account, network core, gateway, DNS, or support organization. Document the common points explicitly.

For the underlying availability logic, see satellite diversity, gateway diversity, and satellite link availability.

Design Power and Physical Installation as Part of the Link

For a remote island or platform, loss of power and environmental control can dominate network availability. Build a measured load schedule that includes terminal startup, RF equipment, router, firewall, switching, monitoring, cooling or heating, and conversion losses. Then model normal, degraded, and recovery states against the site's real generation and storage profile.

Specify:

• primary and alternate energy sources, transfer logic, autonomy requirement, recharge case, maintenance bypass, and low-energy load shedding;
• protection, isolation, earthing or bonding, lightning and surge design, cable entry, connector sealing, and corrosion control;
• structural loads and fasteners, horizon and obstruction survey, RF exposure controls, safe access, fall protection, and lifting method;
• equipment temperature and ingress limits, enclosure heat rejection, salt and UV exposure, drainage, condensation, and inspection intervals;
• spare parts by failure consequence and lead time, storage conditions, test procedure, and configuration control.

Do not prescribe a universal antenna diameter, battery duration, material grade, enclosure rating, or maintenance interval. Those are outputs of the link budget, manufacturer limits, structural and electrical design, environmental evidence, applicable standards, and the operator's accepted risk.

Segment the Network and Control Remote Access

Treat the satellite link as an external network boundary. At minimum, separate operational technology, enterprise IT, guest or welfare, and management traffic. Define which flows are allowed, who approves them, how identities are verified, where logs are stored, and how vendor access is opened and closed.

The IMO guidelines on maritime cyber risk management address connected ship systems, dependencies, network segmentation, remote access, third parties, and continuous Govern, Identify, Protect, Detect, Respond, and Recover functions. An offshore facility should apply the relevant facility, safety, industrial-control, national, and company cybersecurity requirements as well; the IMO document alone is not a platform compliance standard.

Keep essential local functions safe when the WAN is unavailable. Control loops, protective systems, local name resolution, authentication dependencies, configuration access, alarm storage, and timekeeping should have an explicit degraded mode rather than silently depending on a remote cloud service.

If the site needs inbound maintenance, cameras, telemetry polling, or a site-to-site tunnel, define addressing before ordering. A provider-assigned public address, carrier-grade NAT, IPv6, and an outbound overlay VPN have different reachability and security properties. The dedicated static IP and maritime satellite guide explains the design and acceptance questions.

Procurement and Contract Checklist

Attach these schedules to the request for proposal and final contract:

1. Site, environmental, power, application, security, and traffic dossiers.
2. Exact service, hardware, software, authorization, installation, and support scope.
3. Capacity and performance definitions with measurement points and raw-data access.
4. Availability calculation, exclusions, planned maintenance, remedies, and chronic-failure rights.
5. Addressing, routing, DNS, VPN, monitoring, logging, data handling, and cybersecurity responsibilities.
6. Spares, field response, travel, access, weather-window, and restoration obligations.
7. Change control for price, plan, network, gateway, satellite, terminal, software, policy, and service area.
8. Ownership, warranty, renewal, suspension, termination, configuration handover, removal, and site restoration.

Compare total cost over one common service period:

TCO = surveys, design, and approvals
    + terminal, RF, network, power, and civil works
    + freight, lifting, travel, installation, and commissioning
    + recurring capacity, support, licences, and data
    + spares, maintenance, repairs, and site visits
    + overage, changes, renewal, and escalation
    + removal, restoration, and exit obligations

This prevents a low monthly access price from hiding the cost of power work, logistics, field support, or an unusable addressing model.

Acceptance Test Plan

Write pass/fail thresholds and remedies before installation. Retain timestamps, configurations, logs, screenshots, photographs, raw measurements, incidents, exceptions, and witness sign-off.

1. Documentation and Installation

• verify equipment model and revision, licences, authorization, drawings, structural records, cable and connector inspection, protection, earthing or bonding, labels, and inventory;
• confirm approved antenna horizon, obstruction, RF safety, environmental, power, network, and cybersecurity records;
• test monitoring access, alarm destinations, support contacts, spares, manuals, and recovery instructions.

2. Network and Application Baseline

• verify addressing, routing, DNS, time, VPN, identity, segmentation, firewall policy, QoS, logging, and management access;
• measure both directions between named endpoints with the agreed method;
• run real application transactions for telemetry, voice, enterprise systems, bulk transfer, and remote support as applicable.

3. Failure and Recovery

• remove each approved dependency in turn: WAN path, terminal, router interface, power feed, VPN endpoint, DNS service, or management path;
• measure detection, policy decision, traffic restoration, application recovery, failback, alarm, and ticket behavior separately;
• prove that restricted traffic remains restricted and that critical local functions continue during isolation.

4. Operating-Period Trial

Collect a representative period of synchronized RF, network, power, weather, traffic, and application data. Record what conditions were not observed; a short clear-weather test cannot prove an annual availability objective.

FAQ

What is the best satellite internet for an offshore platform?

There is no universal best service. The right offer passes the platform's authorization, structural, environmental, power, application, security, failure, support, and commercial gates. Compare exact plans and paths, not provider categories.

Is GEO or LEO better for remote islands?

Neither orbit is inherently better for every island. Measure application performance, confirm capacity and service policy, model propagation and obstructions, verify support and authorization, and test the purchased service. Some sites use one path; higher-consequence sites may justify independent paths.

Does an offshore platform need two satellite links?

Only the outage-consequence and failure analysis can answer that. If a second link is required, prove independence across antenna view, power, terminal, local routing, space path, gateway, terrestrial handoff, provider operations, and authorization.

What availability percentage should the contract require?

Derive the target from allowed application downtime and the site's safe degraded mode. Then define measurement points, sampling, aggregation, exclusions, maintenance treatment, evidence, and remedy. A percentage without those terms is not a complete requirement.

Can a fixed satellite terminal be used on a floating platform?

Do not assume so. Motion, pointing, mounting, structural loads, operating authorization, equipment certification, and service terms can change the terminal class and installation design. Obtain asset-specific approval.

Related Guides

• Maritime Satellite Internet for Ships — moving-vessel design, contracts, and sea-trial acceptance
• Oil and Gas Satellite Communications — energy-asset applications, OT boundaries, hazardous areas, procurement, and lifecycle evidence
• Oil Rig Satellite Internet — drilling-rig and production-platform design and acceptance
• Satellite Failover for Ships — multi-WAN health checks, traffic policy, and switchover testing
• Satellite Terminal Architecture — antenna, RF, modem, and network interfaces
• QoS over Satellite — classification and shaping under constrained capacity
• Remote Site Network Monitoring — NOC telemetry, alarm design, and fault isolation
• Satellite Provider Evaluation — SLA measurement boundaries, exclusions, and remedies