Starlink Outage Map: Data Sources & Modelling Methodology
This document provides comprehensive technical transparency into the orbital ephemeris feeds, global ground station telemetry, and modelling methodology that power this platform.
Our Pledge: Transparent Modelling & Unverified User Submissions
User reports are stored in our PostgreSQL database and displayed as submitted. We do not verify them against SpaceX systems. When zero active disruptions are reported, regional health is calculated from transparent physical propagation baselines, never simulated outages.
01. Core Data Sources & Telemetry Feeds
How our backend aggregates satellite ephemeris, weather alerts, and subscriber telemetry
Celestrak LEO Satellite Ephemeris Catalog
We integrate with official General Perturbations (GP) NORAD ephemeris data provided by CelesTrak (celestrak.org/NORAD/elements (Starlink Group)). This feed monitors the orbital decay, altitude, and inclination of over 6,500 active Low Earth Orbit (LEO) Starlink satellites.
Crowdsourced Subscriber Reports
All subscriber outage and latency submissions are securely indexed in our cloud PostgreSQL database in structured cloud tables. Incoming filings increment global counters and regional timelines.
Global Gateway Downlink Monitoring
We reference operational telemetry across 43 primary regional monitoring hubs and gateway teleports worldwide. Baseline latency figures are modelled from local fibre backhaul distance and gateway load, calibrated against public measurement data.
NOAA Space Weather Prediction Center
Because severe geomagnetic storms (G3–G5) can cause atmospheric drag and temporary packet loss for LEO satellite constellations, we continuously cross-reference planetary K-index solar storm alerts from NOAA space weather feeds.
02. Ground Station & Gateway Reference Data
Modelled geographic latency baselines across regional gateway clusters
Each regional gateway operates with a geographic baseline latency corresponding to local fiber backhaul distances across our 9 primary gateway regions. Reports are aggregated from subscriber submissions and displayed after the page loads.
| Gateway Region | Operational Status | Modelled Latency |
|---|---|---|
| North America (East) | Modelled: Normal | ⚡ 29.0 ms |
| North America (West) | Modelled: Normal | ⚡ 21.5 ms |
| Western Europe | Modelled: Normal | ⚡ 21.1 ms |
| Eastern Europe | Modelled: Normal | ⚡ 34.5 ms |
| South America | Modelled: Normal | ⚡ 48.0 ms |
| Australia & NZ | Modelled: Normal | ⚡ 34.5 ms |
| East Asia & Japan | Modelled: Normal | ⚡ 33.8 ms |
| South Asia | Modelled: Normal | ⚡ 47.5 ms |
| Africa & Middle East | Modelled: Normal | ⚡ 53.6 ms |
03. Scientific Status Judging Criteria & Thresholds
Transparent rules governing automatic regional and global status classifications
< 3 Reports in Region
Ka-band ground station downlinks operate within modelled baseline thresholds, with standard modelled ping latency under 45ms.
3 – 4 Reports in Region
Triggered when a gateway region records moderate subscriber report volume, often associated with localized weather attenuation or peak-hour contention.
≥ 5 Reports in Region
Indicates elevated subscriber report activity within a gateway cluster (unverified against SpaceX telemetry; does not assert a network-level incident).
04. Subscriber Report Archive (30 Days)
Historical archive of subscriber filings and crowdsourced disruption reports
In accordance with our transparent reporting policy, crowdsourced subscriber disruption reports in the 30-day archive are cataloged in our PostgreSQL database and cross-correlated against NOAA solar space weather indices and regional teleport gateway telemetry. All archived entries reflect self-reported subscriber submissions grouped by UTC calendar day and are not verified against SpaceX systems.