Starlink Outage History Log (Last 30 Days)
Archive of self-reported subscriber Starlink reports across global and regional hubs over a rolling 30-day observation window.
Monitoring Notices (30-day index)
Rolling 30-day archive of self-reported subscriber Starlink disruption filings grouped by severity and region.
30-Day Daily Subscriber Reports Calendar
Daily report cells are color-coded by UTC calendar day volume according to the four-tier threshold legend above.
Frequently Asked Questions About the 30-Day Log
Q1.What do the user reports in this 30-day window represent?
Answer: User reports do not equal network-level incidents. The Total Outage entries represent unilateral descriptions submitted by subscribers—frequently caused by local obstructions, loose proprietary cables, or premise power reboots—and are not verified against SpaceX telemetry.
Q2.How can I check operational status on days with zero or few reports?
Answer: You can switch to the "Complete 30-Day Daily Ledger" tab above. It lists every single day chronologically, marking baseline days with nominal operational status and a modelled baseline.
Q3.What typically drives clusters of disruption reports in this log?
Answer: Self-reported disruption clusters typically correspond to three operational or environmental factors: ① Regional teleport ground station Tier-1 fiber cuts or reroutes; ② NOAA G2+ solar geomagnetic storms causing high-latitude auroral absorption; ③ Severe convective squall lines causing significant Ku-band rain fade.
Q4.My dish is offline today, but there is no incident logged here?
Answer: If no central constellation incident is logged, your outage is most likely localized (e.g. tree/roof sky obstructions, loose proprietary cable connectors, dish thermal cutoff, or local power fluctuations). Use our troubleshooting guides on the homepage to diagnose local dish errors.
Understanding Historical Starlink Disruption Trends
Historical subscriber-reported disconnections across Starlink service cells typically fall into three primary categories: scheduled gateway firmware updates, severe weather precipitation attenuation (rain fade), and localized hardware or ground station fiber backhaul disruptions.
Reviewing past subscriber report logs helps users assess whether recent connection dropouts align with known maintenance windows or weather-related signal attenuation trends in their geographic zone.