Is FlightAware Down?

No — FlightAware is up

Reachable from all 8 checked regions

Average response time: 225ms

Last checked 1 hour ago · checks run every 6 hours

Official status page: https://status.flightaware.com

FlightAware uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

267ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 25 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

25-day clean streak

Jul 25 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

gru

274ms

DNS 0ms TCP 3ms TLS 9ms TTFB 218ms

iad

152ms

DNS 0ms TCP 2ms TLS 7ms TTFB 116ms

jnb

431ms

DNS 0ms TCP 0ms TLS 7ms TTFB 396ms

lax

158ms

DNS 0ms TCP 1ms TLS 6ms TTFB 120ms

lhr

187ms

DNS 1ms TCP 3ms TLS 14ms TTFB 176ms

nrt

251ms

DNS 0ms TCP 1ms TLS 6ms TTFB 218ms

ord

194ms

DNS 0ms TCP 2ms TLS 8ms TTFB 154ms

sin

259ms

DNS 0ms TCP 1ms TLS 5ms TTFB 253ms

sjc

174ms

DNS 0ms TCP 2ms TLS 8ms TTFB 134ms

What FlightAware does

FlightAware tracks flights worldwide, combining a network of ADS-B receivers, satellite reception and official air traffic feeds into live maps and arrival predictions. Passengers and the people meeting them use the website and app, while airlines, airports and logistics companies consume the same data through APIs, so an outage hits casual tracking and operational systems together.

What an outage looks like

Maps load with no aircraft on them, or planes freeze at a position from several minutes earlier while the timestamp keeps advancing. Flight pages show gaps in the track log, arrival estimates stop moving, and alerts for a followed flight never arrive. Integrations built on AeroAPI return errors or empty result sets, which leaves downstream dashboards showing no flights rather than an obvious failure.

What to do about it

Check status.flightaware.com, which reports ADS-B, AeroAPI, Alerts, Global Beacon, Firehose, Foresight, Space-Based ADS-B, Integrated Maps, Data Availability, and Web and Mobile as separate components, so a data-feed fault is distinguishable from a website one. For one specific flight, the airline's own app and the destination airport's arrivals board are independent sources and usually stay accurate.

Is it down for everyone, or just you?

If this page says FlightAware is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

AccuWeather

AWS

Cloudflare

Wikipedia

FlightAware outage FAQ

Is FlightAware down or has my flight stopped transmitting?

Open a second flight on a busy route. If that one updates normally, the platform is fine and the aircraft you are following has simply moved out of receiver coverage, which happens routinely over oceans and remote terrain. If every flight is frozen or the map is empty, the problem is FlightAware rather than the aircraft.

Does an outage mean flights are not being tracked at all?

No. Air traffic control tracking is entirely separate from FlightAware and keeps running regardless. FlightAware aggregates ADS-B and official feeds for public display, so an outage removes your view of the data rather than the data itself. Positions recorded by receivers during the gap generally appear in the track log once the platform recovers.

Will my flight alerts arrive late or not at all?

Alerts are listed as their own component, so they can fail while the maps work. When the alerting pipeline recovers, notifications for events that already happened may arrive in a burst or be dropped as stale, which is why a departure alert can land after the aircraft is airborne. Do not rely on an alert as the only prompt to leave for the airport during an incident.

What can I use instead while FlightAware is down?

The airline's own app and website carry the operational status of their own flights and do not depend on FlightAware. The departure and arrival boards published by the airports at each end are another independent source. Other tracking sites run their own receiver networks, so they are usually unaffected by a FlightAware incident.

Does an outage affect AeroAPI and the website together?

Not necessarily. The status page tracks Web and Mobile separately from AeroAPI, Firehose and the underlying ADS-B and satellite feeds, and a fault in one layer need not touch the others. A working website with a failing API points at the delivery layer, while empty maps and empty API responses together point at the data pipeline feeding both.

How we measure this

We request FlightAware's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where FlightAware publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when FlightAware goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required