FlightAware experienced a minor incident on September 28, 2026 affecting Global Beacon (Global Beacon) and Space-Based ADS-B (Space-Based ADS-B), lasting 4h 16m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Sep 28, 2026, 11:44 PM UTC
We have detected an issue with an upstream space-based ADS-B provider, resulting in intermittent feed volume and latency. This may affect Global Beacon tracking and alerting as well as downstream availability of space-based ADS-B data.
- identified Sep 29, 2026, 12:45 AM UTC
We are continuing to monitor the issue with an upstream space-based ADS-B provider, which is resulting in intermittent feed volume and latency. This may affect Global Beacon tracking and alerting as well as downstream availability of space-based ADS-B data.
- identified Sep 29, 2026, 01:52 AM UTC
We are continuing to monitor the issue with an upstream space-based ADS-B provider, which has been resulting in intermittent feed volume and latency. While the feed appears to have stabilized, we do not yet have an all-clear from the provider.
- identified Sep 29, 2026, 03:00 AM UTC
We are continuing to monitor the issue with an upstream space-based ADS-B provider. The data feed has remained stable for the last hour, but we still do not have an all-clear from the provider.
- resolved Sep 29, 2026, 04:01 AM UTC
We have received a message from our upstream provider that data is flowing at nominal levels, and have verified that it continues to be stable this will be the last update for this issue. Thank you for your patience.