Travel status
Airlines, booking platforms and the operational IT behind them. All 5 are checked every 20 minutes; the status beside each one is the result of its most recent check.
Travel technology is the oldest infrastructure in this directory, and its outages are the only ones with physical consequences that persist for days after the systems come back.
How reliable travel has been, last 30 days
Measured by our own checks, run every 20 minutes, not taken from any provider’s status page. 5 of 5 services have enough history to report.
| Service | Now | Uptime 30d | Downtime | Response |
|---|---|---|---|---|
| Airbnb | Up | 100.0% | none | 398 ms |
| Booking.com | Up | 100.0% | none | 305 ms |
| Delta Air Lines | Up | 100.0% | none | 384 ms |
| Southwest Airlines | Up | 100.0% | none | 260 ms |
| Uber | Up | 100.0% | none | 294 ms |
Southwest Airlines has been the steadiest here over the last 30 days. Uptime is observed uptime: The share of measured time our checks got a usable answer. It excludes nothing, including announced maintenance.
Why travel services go down
Airline reservation and departure control systems are decades old, deeply interconnected, and cannot be taken offline for gradual modernisation. Booking, check-in, crew scheduling and baggage all read from the same core. A failure in one therefore grounds aircraft rather than merely breaking a website, and the recovery is physical: Crews and aircraft end the day in the wrong cities.
That is the property no other category shares. A social network that recovers after two hours has fully recovered. An airline that recovers after two hours has a schedule to rebuild, and the disruption continues for two or three days after the technology is fixed.
What an outage here looks like
Check-in fails, the app cannot retrieve a booking, airport screens stop updating. Existing bookings usually still exist - retrieval is what broke - though that is no comfort at a gate.
When these services are under most strain
Early morning departure banks, public holidays, and severe weather, which triggers exactly the rebooking volume the systems handle worst.
At a glance
- Typical duration
- 2 to 8 hours of systems, days of knock-on disruption
- Usual cause
- Reservation or departure control core systems
- Tell-tale sign
- Booking exists but cannot be retrieved
- Recovery
- The only category with physical recovery after the fix
What to do when travel is down
- Screenshot your boarding pass now, before you need it. A saved pass keeps working when retrieval does not. This is the single most useful precaution in this category.
- Go to the airport unless told otherwise. Systems recover faster than schedules. Being present matters more than being rebooked online.
- Your booking almost certainly still exists. Retrieval failing is not cancellation, though the error rarely makes that clear.
Still not sure whether it is them or you? Check the site from our servers - We are on a different network, a different resolver and a different route from you.