pingoru pingoru FlightAware had 16 outages in the last 2 years totaling 249h 26m of downtime, averaging 0.7 incidents per month.
There were 16 FlightAware outages since May 19, 2026 totaling 249h 26m of downtime. Each is summarised below. Incident details, duration, and resolution information.
We had brief issues logging in to to FlightAware, which should be resolved at this time. The issues occurred between approximately 11:19 - 11:28 CT. If you have persistent issues, it may be necessary to refresh your browser or restart the FlightAware application.
Our upstream provider of space-based ADS-B data is having issues and it is affecting the availability of space-based ADS-B data and Global Beacon.
We are working with our upstream provider of space-based ADS-B to restore service. At this time the upstream issue continues to affect the availability of space-based ADS-B data and Global Beacon.
Our upstream space-based ADS-B provider has restored service and we are operating normally at this time. This will be the final update for this issue.
We have detected an issue with an upstream space-based ADS-B provider, resulting in intermittent feed volume. This may affect Global Beacon tracking and alerting as well as downstream availability of space-based ADS-B data.
Our upstream provider has implemented a solution and we are seeing stable output from them. At this time, space-based ADS-B and Global Beacon services are operating normally, and this will be the final update for this incident.
Our upstream provider of Space-Based ADS-B has identified an issue with their data delivery. This is resulting in fluctuations in feed volume. This may affect Global Beacon tracking and alerting as well as downstream availability of space-based ADS-B data.
This incident is now resolved.
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.
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.
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.
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.
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.
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...
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...
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...
We have detected an issue causing a loss of redundancy for FlightAware services. All services are available and we are investigating now.
We are continuing to investigate the issue. All services remain available with a loss of redundancy.
We have resolved the connectivity issue and are now transitioning to scheduled maintenance.
We are continuing with scheduled maintenance. All services remain available with a loss of redundancy.
All service redundancy has been restored and maintenance is concluded.
We are investigating issues signing in to Global Beacon.
A root cause has been identified and initial steps have been taken to address the issue. Error rates are trending down. We are monitoring the situation closely.
A root cause has been identified, and we are diligently working to restore the redundant capacity; error rates are trending down. We continue to monitor the situation closely.
Remediation was a success and all Global Beacon instances are healthy and serving traffic with nominal error rates.
We are currently experiencing delays in flight tracking data. The team is actively investigating the issue and working to restore back to real time.
Flight tracking data is now processing normally and is up to date. Thank you for your patience while we worked to resolve this issue.
The issue has been identified and a fix is in progress.
Expected recovery is in 20 minutes.
This incident is now resolved.
We are aware of a problem causing a loss of redunancy of some FlightAware services. We are investigating the issue to determine if there is any other impact.
We have identified the issue, and the redundant services have recovered. We will continue to investigate the matter and provide further updates as needed.
Redundancy has been restored to FlightAware services.
We are investigating an issue currently affecting firehose/surface movement.
We have taken steps to correct these issues and are currently monitoring the recovery.
Everything is back to normal.
From about 19:24 UTC to 19:39 UTC, some customers may have observed elevated error rates when accessing AeroAPI or using certain portions of the Flight Aware Mobile applications. The issue would present as intermittent 500 failures affecting API requests. Internal monitoring detected this...
Firehose is currently operating with a loss of redundancy. IP range is limited and rejected connections are expected at this time.
Firehose redundancy has been restored.
Investigation is ongoing.
We are still investigating the reason for outage and will be working towards a resolution.
We are still determining the reason for outage, but recovery of affected services has started. Expect additional updates shortly.
We have determined the reason for outage and all services are operational. We are resolving this incident.
We have identified and are investigating a connectivity issue in one of our facilities.
We are working on resolving a connectivity issue in one of our facilities. Some Flight alerts/notifications may not be delivered and there may be a degradation of ADS-B data.
We have mitigated the issue and are working on restoring full operation at the affected facility.
We have mitigated the issue and are still working on full resolution. All services appear to be operating normally with the exception of alerts to Android devices.
Android alerts/notifications have been restored. Mitigation remains in place and we are still working on full resolution,
All services are operating normally.