Why your VSAT uptime report is not telling you the truth

The uptime figure in your SLA report measures whether the satellite terminal had a signal. It does not measure whether that signal was capable of doing useful work. These are different things, and the distinction is costing fleet operators real money in renegotiation leverage they never use because they cannot see the evidence.

How vendors calculate "99.5% uptime"

A VSAT terminal is typically considered "up" when it maintains a valid signal lock to the satellite. By this definition, a vessel can log 99.5% uptime while experiencing throughput so degraded by beam contention that ECDIS updates time out, crew messaging fails, and engineering data transfer queues for hours.

The measurement is binary: signal or no signal. The experience is a spectrum. Vendor reporting is built around the binary because it is easier to defend and harder to dispute.

Scheduled maintenance windows are usually excluded from uptime calculations entirely. A four-hour maintenance window at 0200 vessel time does not appear in the headline figure. Neither does a graceful degradation event where the terminal stays locked but usable bandwidth drops to near zero.

What beam contention does in practice

GEO VSAT operates on shared capacity. Vessels in high-traffic regions — the Strait of Malacca, the Gulf of Aden transit corridor, port approach zones near Singapore, Rotterdam, and Houston — share beam capacity with every other vessel and coastal installation on the same footprint.

During peak traffic periods, a vessel with a committed information rate (CIR) of 1 Mbps may find its actual throughput well below that. The CIR is the floor the provider commits to delivering; what you actually see depends on contention across the beam. Providers rarely publish beam utilisation data. There is no industry-standard format for reporting it. You will not find it in your monthly SLA pack.

A vessel in the Singapore Strait during the morning peak may log technically compliant uptime while experiencing conditions operationally equivalent to an outage.

Weather events and the accountability gap

Force majeure clauses in most VSAT contracts explicitly exclude weather-related degradation from SLA liability. This is standard. The problem is how broadly "weather" is applied.

A tropical cyclone 800 km away from a vessel's position can degrade GEO VSAT performance through rain fade on the ground segment uplink, without triggering any formal outage event and without appearing anywhere in the vendor's report. The vessel logs a degraded transit. The vendor logs compliant uptime. Nobody is technically lying. Nobody is accountable.

What your vendor report is not showing you

The five data points that would make your SLA enforceable are absent from most standard reports.

If your monthly pack contains none of these, you are not receiving a performance report. You are receiving a compliance document written to satisfy the vendor's contractual obligations, not yours.

What to do with this

Start with your last three months of SLA reports. If you cannot find throughput windows, latency percentiles, or zone-level breakdowns, you do not have enough data to hold your provider accountable — or to renegotiate intelligently.

Request supplementary data exports. Most providers have backend telemetry that is not surfaced in the standard report. They will provide it if you ask specifically, cite your contract, and make clear you are tracking it going forward.

When you have the data, define your own thresholds. What does "useful" connectivity mean for your vessels — not what does "technically up" mean. Build your next contract negotiation around those thresholds, not around a headline uptime figure that was always designed to be easy to meet.

The 99.5% number is not a lie. It is just not what you need to know.