FlightAware incident

Degraded performance in GlobalBeacon.

Minor Resolved View vendor source →

FlightAware experienced a minor incident on September 28, 2026 affecting Global Beacon (Global Beacon) and Space-Based ADS-B (Space-Based ADS-B), lasting 7h 10m. The incident has been resolved; the full update timeline is below.

Started
Sep 28, 2026, 12:30 PM UTC
Resolved
Sep 28, 2026, 07:40 PM UTC
Duration
7h 10m
Detected by Pingoru
Sep 28, 2026, 12:30 PM UTC

Affected components

Global Beacon (Global Beacon)Space-Based ADS-B (Space-Based ADS-B)

Update timeline

  1. identified Sep 28, 2026, 12:30 PM UTC

    title: Degraded performance in GlobalBeacon. Internal monitoring has detected that some 3rd party data sources have deviated from normal quality levels. As a result, space-Based ADSB data is delayed. This primarily impacts GlobalBeacon which is functional but displaying delayed...

  2. investigating Sep 28, 2026, 04:25 PM UTC

    We continue to work with upstream providers to address the issue; the volume of space-Based ADSB data is below nominal levels and unusually delayed. GlobalBeacon is impacted; some flight positions will be slow to update or missing all together. Unfortunately we do not yet have an estimated...

  3. resolved Sep 28, 2026, 07:40 PM UTC

    For the 80 minutes we have seen nominal data throughput and quality from upstream sources. GlobalBeacon functionalty has been restoerd and we are closing the incident. We apologize for any inconvenience this may cause and appreciate your patience while working towards this...