Is Booking.com down?
Operationalchecked 1 minute ago
We reached Booking.com from all 4 regions we check.
Last outage: 1h 1m on Aug 31, 2026 (web surface, from Europe).
Booking.com publishes no status feed we can read, so the only independent reading here is ours on the left.
Booking.com response time, by region
Is it Booking.com, or is it you?
Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Booking.com -- it cannot diagnose Booking.com's own systems.
What we measured, and what people reported
- US-EastOperationallatency: 589msstatus code: 202checked: Sep 3, 2026, 12:43 AM UTC0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Booking.com normally. We do not have enough reports from US-East to say anything about what people there are seeing.
- US-WestOperationallatency: 767msstatus code: 202checked: Sep 3, 2026, 12:57 AM UTC0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Booking.com normally. We do not have enough reports from US-West to say anything about what people there are seeing.
- EuropeOperationallatency: 270msstatus code: 202checked: Sep 3, 2026, 1:28 AM UTC0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Booking.com normally. We do not have enough reports from Europe to say anything about what people there are seeing.
- Asia-PacificOperationallatency: 751msstatus code: 202checked: Sep 3, 2026, 1:04 AM UTC0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Booking.com normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
- US-CentralNot monitored from this regionBooking.com is not monitored from this region.0 people in the last 5 minutesNot enough reports to say
- CanadaNot monitored from this regionBooking.com is not monitored from this region.0 people in the last 5 minutesNot enough reports to say
- UKNot monitored from this regionBooking.com is not monitored from this region.0 people in the last 5 minutesNot enough reports to say
- Southeast AsiaNot monitored from this regionBooking.com is not monitored from this region.0 people in the last 5 minutesNot enough reports to say
- AustraliaNot monitored from this regionBooking.com is not monitored from this region.0 people in the last 5 minutesNot enough reports to say
- South AmericaNot monitored from this regionBooking.com is not monitored from this region.0 people in the last 5 minutesNot enough reports to say
Somewhere else or not sure: 0 people in the last 5 minutes
These are unverified reports from people using Booking.com, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Booking.com yet, which is not evidence that nothing is wrong.
Recent outages
measured entries are our own probes' readings; declared entries are the vendor's. How this check works
We have been measuring Booking.com since August 20, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.
Need this in writing? Generate an SLA evidence report for Booking.com covering any window you pick, with our measurements and Booking.com's own claim at the time, side by side.
Full availability history for Booking.com: 90-day availability by region, month-by-month uptime, and every incident on record.
Monitor your own site the same way
This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.
Start monitoring your own serversTell me when this goes down
Get told when we measure this
We will tell you when our probes stop reaching Booking.com, and again when they can reach it again. That is our own measurement from ten regions, not Booking.com's status page. No account, no card.
Put this badge in your README
Live, from this page's own readings.[](https://realuptime.io/outages/booking-com)<a href="https://realuptime.io/outages/booking-com"><img src="https://realuptime.io/outages/booking-com/badge.svg?days=30" alt="Booking.com uptime measured by RealUptime"></a>The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.
What Booking.com's SLA implies, from our measurement
At or above your target
We measured none of downtime for Booking.com over the 337h 29m since we started watching it on 2026-08-20, which is 100% uptime by our reading. A 99.9% target allows 20 minutes over that period.
By our measurement there is no shortfall to claim for this period.
Separately, we measured 1h 1m where only one of our regions was affected. It is excluded above because most SLAs would not credit it, and it is the kind of outage a single-vantage monitor never sees at all.
This is computed from our own probe measurements, not from Booking.com's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.