← Back to Booking.com's live status
We started measuring Booking.com on August 20, 2026, which is 15 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Booking.com's own status page declared. Below it, any public chatter we saw about Booking.com and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Booking.com's own status page declared. Three records side by side; none of them changes another.
Each probe cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused probe is not an outage. Report bars count unverified reports, not people we verified; they never change our reading. The status-page lane is Booking.com's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention Booking.com next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
Availability by region
Availability is measured probes that succeeded, divided by every probe we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
| Region | Availability | Probes recorded |
|---|---|---|
| US-East | 99.84% | 634 |
| US-West | 99.84% | 633 |
| Europe | 99.52% | 631 |
| Asia-Pacific | 99.84% | 613 |
Monthly summary
Tracking Booking.com since Aug 20, 2026. In that time our probes detected 1 outage, 1h 1m in total. Months before that date are not tracked and carry no figure.
| Month | Uptime | Outages | Downtime |
|---|---|---|---|
| Oct 2025 | not tracked | ||
| Nov 2025 | not tracked | ||
| Dec 2025 | not tracked | ||
| Jan 2026 | not tracked | ||
| Feb 2026 | not tracked | ||
| Mar 2026 | not tracked | ||
| Apr 2026 | not tracked | ||
| May 2026 | not tracked | ||
| Jun 2026 | not tracked | ||
| Jul 2026 | not tracked | ||
| Aug 2026 from Aug 20, 2026 | 99.65% | 1 | 1h 1m |
| Sep 2026 | 100% | 0 | 0 min |
Uptime here is the share of each month in which our probes had no outage open for Booking.com: two consecutive failed readings from a region opens one, the first clean reading closes it. Any detected outage counts, including one seen from a single region, and an outage that crosses midnight on the first of a month is counted in both months with its minutes split. User reports, public posts and Booking.com's own status page contribute nothing to these figures.
Our incident log
Every outage our own probes detected for Booking.com in the last 90 days, or since we started measuring it if that is more recent. This list is probe-only: Booking.com's own declared incidents appear further down this page in their own attributed section, never merged with what we measured here. User reports live on the live page, in their own labeled block.
Permanent incident records
Every closed Booking.com incident RealUptime has ever detected gets its own permanent, citable page: the region-by-region timeline, exactly as measured, that stays up even after the incident log above ages out of this 90-day window.
Full detail on what a probe does and does not prove is in the methodology page.