Starlink Outage History Log (Last 30 Days)
Historical record of global and regional Starlink satellite service disruptions, telemetry incidents, and network recoveries across a rolling 30-day observation window.
Incidents Log (30-day index)
Comprehensive 30-day rolling record of global Starlink constellation availability, gateway telemetry anomalies, atmospheric attenuation, and restoration logs from 2026-09-29 to 2026-10-28.
Why are only a few incidents logged across the 30 days?
Operational Context: Unlike a daily journal, this page is an Incident Log monitoring the rolling 30-day window (2026-09-28 to 2026-10-27). Starlink's satellite constellation maintains a ~99.8% baseline uptime globally. Incident entries are generated only when anomalous events occur (such as Tier-1 teleport fiber disruptions, NOAA solar geomagnetic storms, or severe convective rain fade).
Days without an incident entry operated at 100% capacity with 0 disruptions. If you wish to review day-by-day operational health for all 30 days, simply switch to the "Complete 30-Day Daily Ledger" tab below to inspect every single calendar day.
Routine orbital plane constellation station-keeping and optical laser crosslink alignment caused momentary 10-15s beam handoff delays for maritime and coastal terminals.
Scheduled upstream Tier-1 fiber transport maintenance across regional teleport gateways required dynamic Ka-band feeder link failover, causing temporary 8-15% packet drops for ~18 minutes before full convergence.
Moderate coronal mass ejection (CME) shockwave triggered temporary high-latitude ionospheric scintillation. Polar orbit laser crosslink (ISL) handoffs experienced elevated jitter (up to 65ms) in Alaska and Northern Scandinavia.
Automated software rollout to European ground teleport border gateways caused transient route re-advertisements. Residential dishes experienced brief 30-to-60 second DNS lookup delays during peering reconvergence.
Intense mesoscale convective thunderstorm front with heavy hail density caused acute Ku-band atmospheric signal attenuation across parts of Missouri, Illinois, and Indiana. Disconnection self-recovered as storm cells shifted eastward.
SpaceX constellation operations performed orbital phase adjustment and optical link re-pointing across 24 Gen2 satellites over the South Pacific, resulting in brief maritime terminal handoff re-syncs.
Frequently Asked Questions About the 30-Day Log
Q1.Why are there only a few incident logs in the 30-day window?
Answer: The "30-Day Log" specifies a monitoring observation window covering the last 30 calendar days, not a requirement that disruptions occur daily. Starlink operates with over 99.8% fleet uptime. On nominal days with zero network anomalies, no incident ticket is generated.
Q2.How can I verify operational health on days with no incidents?
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 verified zero-disruption telemetry.
Q3.What qualifies as a logged disruption incident?
Answer: Incidents are recorded for verified systemic events: ① 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 Uptime Trends
As satellite constellation density expands globally, Starlink network availability consistently exceeds 99.4% uptime in most developed service cells. Historical disconnections typically fall into three primary categories: scheduled gateway firmware updates, severe weather precipitation attenuation (rain fade), and rare ground station fiber backhaul disruptions.
Reviewing past outage logs helps users assess whether recent connection dropouts align with known maintenance windows or signal attenuation trends in their geographic zone.