Skip to content

Outage tracker / Booking.com

Is Booking.com down?

I'm having a problem

Partially degradedchecked 2 minutes ago

Booking.com is answering our probes, but running at least 4.5x its 7-day median from Europe. The rest of the regions we check answered at their usual speed.

As of Oct 19, 2026, 8:51 PM UTC, RealUptime's checks of Booking.com passed in all 10 regions that returned a reading.

Front-door checks

Our checks of Booking.com did not fail from two or more distant regions in the 60 days we have checked it (since Aug 20, 2026). This does not show Booking.com works for users.

Email me when our checks of Booking.com fail from two or more distant regions

One email when our checks of Booking.com fail from two or more distant regions, and one when they pass, after you confirm the address. No account, no card.

This is our own reading from outside. It is not Booking.com's official status.

our check readinglive · checked Oct 19, 2026, 8:51 PM UTC
US-East1251 msChecks passing
US-West1304 msChecks passing
Europe527 msDegraded
Asia-Pacific1637 msChecks passing
US-Central453 msChecks passing
Canada397 msChecks passing
UK341 msChecks passing
Southeast Asia1621 msChecks passing
Australia3582 msChecks passing
South America1754 msChecks passing
their status pagetheir claim, not our reading

Booking.com publishes no status feed we can read, so the only reading here is our check reading on the left.

Booking.com response time, by region

US-East
1.4sp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 556ms2026-09-21 UTC: p95 568ms2026-09-22 UTC: p95 684ms2026-09-23 UTC: p95 647ms2026-09-24 UTC: p95 688ms2026-09-25 UTC: p95 697ms2026-09-26 UTC: p95 632ms2026-09-27 UTC: p95 651ms2026-09-28 UTC: p95 600ms2026-09-29 UTC: p95 651ms2026-09-30 UTC: p95 683ms2026-10-01 UTC: p95 652ms2026-10-02 UTC: p95 598ms2026-10-03 UTC: p95 625ms2026-10-04 UTC: p95 665ms2026-10-05 UTC: p95 664ms2026-10-06 UTC: p95 632ms2026-10-07 UTC: p95 501ms2026-10-08 UTC: p95 727ms2026-10-09 UTC: p95 504ms2026-10-10 UTC: p95 602ms2026-10-11 UTC: p95 625ms2026-10-12 UTC: p95 601ms2026-10-13 UTC: p95 546ms2026-10-14 UTC: p95 566ms2026-10-15 UTC: p95 518ms2026-10-16 UTC: p95 772ms2026-10-17 UTC: p95 768ms2026-10-18 UTC: p95 1.4s2026-10-19 UTC: p95 1.4s
Sep 20Oct 4Oct 19
US-West
1.5sp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 765ms2026-09-21 UTC: p95 617ms2026-09-22 UTC: p95 635ms2026-09-23 UTC: p95 544ms2026-09-24 UTC: p95 733ms2026-09-25 UTC: p95 714ms2026-09-26 UTC: p95 777ms2026-09-27 UTC: p95 501ms2026-09-28 UTC: p95 605ms2026-09-29 UTC: p95 576ms2026-09-30 UTC: p95 728ms2026-10-01 UTC: p95 977ms2026-10-02 UTC: p95 1.0s2026-10-03 UTC: p95 1.0s2026-10-04 UTC: p95 1.1s2026-10-05 UTC: p95 1.1s2026-10-06 UTC: p95 1.2s2026-10-07 UTC: p95 1.0s2026-10-08 UTC: p95 948ms2026-10-09 UTC: p95 915ms2026-10-10 UTC: p95 1.0s2026-10-11 UTC: p95 898ms2026-10-12 UTC: p95 957ms2026-10-13 UTC: p95 1.1s2026-10-14 UTC: p95 902ms2026-10-15 UTC: p95 969ms2026-10-16 UTC: p95 991ms2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.6s2026-10-19 UTC: p95 1.5s
Sep 20Oct 4Oct 19
Europe
968msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 388ms2026-09-21 UTC: p95 290ms2026-09-22 UTC: p95 351ms2026-09-23 UTC: p95 380ms2026-09-24 UTC: p95 376ms2026-09-25 UTC: p95 311ms2026-09-26 UTC: p95 397ms2026-09-27 UTC: p95 393ms2026-09-28 UTC: p95 310ms2026-09-29 UTC: p95 323ms2026-09-30 UTC: p95 316ms2026-10-01 UTC: p95 702ms2026-10-02 UTC: p95 561ms2026-10-03 UTC: p95 575ms2026-10-04 UTC: p95 327ms2026-10-05 UTC: p95 284ms2026-10-06 UTC: p95 289ms2026-10-07 UTC: p95 322ms2026-10-08 UTC: p95 207ms2026-10-09 UTC: p95 496ms2026-10-10 UTC: p95 409ms2026-10-11 UTC: p95 251ms2026-10-12 UTC: p95 493ms2026-10-13 UTC: p95 264ms2026-10-14 UTC: p95 156ms2026-10-15 UTC: p95 732ms2026-10-16 UTC: p95 225ms2026-10-17 UTC: p95 608ms2026-10-18 UTC: p95 751ms2026-10-19 UTC: p95 968ms
Sep 20Oct 4Oct 19
Asia-Pacific
2.4sp95 · latest
2.5s1.3s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 1.3s2026-09-21 UTC: p95 1.4s2026-09-22 UTC: p95 1.2s2026-09-23 UTC: p95 1.2s2026-09-24 UTC: p95 1.2s2026-09-25 UTC: p95 1.0s2026-09-26 UTC: p95 976ms2026-09-27 UTC: p95 1.1s2026-09-28 UTC: p95 1.4s2026-09-29 UTC: p95 1.3s2026-09-30 UTC: p95 1.1s2026-10-01 UTC: p95 1.4s2026-10-02 UTC: p95 1.4s2026-10-03 UTC: p95 1.8s2026-10-04 UTC: p95 1.3s2026-10-05 UTC: p95 1.5s2026-10-06 UTC: p95 1.4s2026-10-07 UTC: p95 1.7s2026-10-08 UTC: p95 1.3s2026-10-09 UTC: p95 1.2s2026-10-10 UTC: p95 937ms2026-10-11 UTC: p95 1.6s2026-10-12 UTC: p95 1.2s2026-10-13 UTC: p95 1.4s2026-10-14 UTC: p95 1.5s2026-10-15 UTC: p95 1.8s2026-10-16 UTC: p95 1.6s2026-10-17 UTC: p95 1.8s2026-10-18 UTC: p95 2.3s2026-10-19 UTC: p95 2.4s
Sep 20Oct 4Oct 19
US-Central
817msp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 519ms2026-09-21 UTC: p95 672ms2026-09-22 UTC: p95 708ms2026-09-23 UTC: p95 523ms2026-09-24 UTC: p95 649ms2026-09-25 UTC: p95 652ms2026-09-26 UTC: p95 502ms2026-09-27 UTC: p95 627ms2026-09-28 UTC: p95 663ms2026-09-29 UTC: p95 559ms2026-09-30 UTC: p95 1.0s2026-10-01 UTC: p95 585ms2026-10-02 UTC: p95 682ms2026-10-03 UTC: p95 639ms2026-10-04 UTC: p95 734ms2026-10-05 UTC: p95 566ms2026-10-06 UTC: p95 522ms2026-10-07 UTC: p95 608ms2026-10-08 UTC: p95 640ms2026-10-09 UTC: p95 778ms2026-10-10 UTC: p95 475ms2026-10-11 UTC: p95 489ms2026-10-12 UTC: p95 617ms2026-10-13 UTC: p95 769ms2026-10-14 UTC: p95 655ms2026-10-15 UTC: p95 624ms2026-10-16 UTC: p95 656ms2026-10-17 UTC: p95 654ms2026-10-18 UTC: p95 757ms2026-10-19 UTC: p95 817ms
Sep 20Oct 4Oct 19
Canada
539msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 556ms2026-09-21 UTC: p95 634ms2026-09-22 UTC: p95 641ms2026-09-23 UTC: p95 632ms2026-09-24 UTC: p95 726ms2026-09-25 UTC: p95 819ms2026-09-26 UTC: p95 791ms2026-09-27 UTC: p95 698ms2026-09-28 UTC: p95 715ms2026-09-29 UTC: p95 684ms2026-09-30 UTC: p95 754ms2026-10-01 UTC: p95 649ms2026-10-02 UTC: p95 815ms2026-10-03 UTC: p95 566ms2026-10-04 UTC: p95 683ms2026-10-05 UTC: p95 616ms2026-10-06 UTC: p95 885ms2026-10-07 UTC: p95 795ms2026-10-08 UTC: p95 893ms2026-10-09 UTC: p95 608ms2026-10-10 UTC: p95 709ms2026-10-11 UTC: p95 911ms2026-10-12 UTC: p95 584ms2026-10-13 UTC: p95 680ms2026-10-14 UTC: p95 653ms2026-10-15 UTC: p95 570ms2026-10-16 UTC: p95 574ms2026-10-17 UTC: p95 692ms2026-10-18 UTC: p95 547ms2026-10-19 UTC: p95 539ms
Sep 20Oct 4Oct 19
UK
338msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 212ms2026-09-21 UTC: p95 264ms2026-09-22 UTC: p95 348ms2026-09-23 UTC: p95 390ms2026-09-24 UTC: p95 387ms2026-09-25 UTC: p95 622ms2026-09-26 UTC: p95 548ms2026-09-27 UTC: p95 544ms2026-09-28 UTC: p95 420ms2026-09-29 UTC: p95 325ms2026-09-30 UTC: p95 412ms2026-10-01 UTC: p95 361ms2026-10-02 UTC: p95 555ms2026-10-03 UTC: p95 285ms2026-10-04 UTC: p95 282ms2026-10-05 UTC: p95 380ms2026-10-06 UTC: p95 485ms2026-10-07 UTC: p95 260ms2026-10-08 UTC: p95 382ms2026-10-09 UTC: p95 369ms2026-10-10 UTC: p95 355ms2026-10-11 UTC: p95 420ms2026-10-12 UTC: p95 321ms2026-10-13 UTC: p95 325ms2026-10-14 UTC: p95 352ms2026-10-15 UTC: p95 297ms2026-10-16 UTC: p95 227ms2026-10-17 UTC: p95 226ms2026-10-18 UTC: p95 922ms2026-10-19 UTC: p95 338ms
Sep 20Oct 4Oct 19
Southeast Asia
2.1sp95 · latest
2.5s1.3s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 1.3s2026-09-21 UTC: p95 1.4s2026-09-22 UTC: p95 1.5s2026-09-23 UTC: p95 1.4s2026-09-24 UTC: p95 932ms2026-09-25 UTC: p95 1.2s2026-09-26 UTC: p95 1.4s2026-09-27 UTC: p95 917ms2026-09-28 UTC: p95 1.1s2026-09-29 UTC: p95 1.0s2026-09-30 UTC: p95 885ms2026-10-01 UTC: p95 753ms2026-10-02 UTC: p95 1.4s2026-10-03 UTC: p95 1.4s2026-10-04 UTC: p95 1.1s2026-10-05 UTC: p95 1.1s2026-10-06 UTC: p95 1.0s2026-10-07 UTC: p95 856ms2026-10-08 UTC: p95 909ms2026-10-09 UTC: p95 813ms2026-10-10 UTC: p95 1.1s2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 727ms2026-10-13 UTC: p95 1.2s2026-10-14 UTC: p95 912ms2026-10-15 UTC: p95 848ms2026-10-16 UTC: p95 800ms2026-10-17 UTC: p95 1.9s2026-10-18 UTC: p95 2.1s2026-10-19 UTC: p95 2.1s
Sep 20Oct 4Oct 19
Australia
2.5sp95 · latest
5s2.5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 915ms2026-09-21 UTC: p95 1.0s2026-09-22 UTC: p95 934ms2026-09-23 UTC: p95 976ms2026-09-24 UTC: p95 1.4s2026-09-25 UTC: p95 1.1s2026-09-26 UTC: p95 857ms2026-09-27 UTC: p95 1.4s2026-09-28 UTC: p95 1.1s2026-09-29 UTC: p95 976ms2026-09-30 UTC: p95 1.5s2026-10-01 UTC: p95 2.5s2026-10-02 UTC: p95 2.4s2026-10-03 UTC: p95 1.9s2026-10-04 UTC: p95 1.9s2026-10-05 UTC: p95 1.9s2026-10-06 UTC: p95 1.7s2026-10-07 UTC: p95 1.8s2026-10-08 UTC: p95 1.8s2026-10-09 UTC: p95 1.9s2026-10-10 UTC: p95 2.0s2026-10-11 UTC: p95 2.1s2026-10-12 UTC: p95 2.0s2026-10-13 UTC: p95 2.1s2026-10-14 UTC: p95 2.2s2026-10-15 UTC: p95 1.8s2026-10-16 UTC: p95 2.2s2026-10-17 UTC: p95 2.6s2026-10-18 UTC: p95 2.5s2026-10-19 UTC: p95 2.5s
Sep 20Oct 4Oct 19
South America
2.3sp95 · latest
2.5s1.3s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 1.0s2026-09-21 UTC: p95 696ms2026-09-22 UTC: p95 966ms2026-09-23 UTC: p95 865ms2026-09-24 UTC: p95 1.1s2026-09-25 UTC: p95 1.1s2026-09-26 UTC: p95 807ms2026-09-27 UTC: p95 963ms2026-09-28 UTC: p95 920ms2026-09-29 UTC: p95 1.4s2026-09-30 UTC: p95 1.2s2026-10-01 UTC: p95 1.6s2026-10-02 UTC: p95 2.1s2026-10-03 UTC: p95 1.4s2026-10-04 UTC: p95 1.7s2026-10-05 UTC: p95 1.4s2026-10-06 UTC: p95 1.4s2026-10-07 UTC: p95 1.8s2026-10-08 UTC: p95 1.7s2026-10-09 UTC: p95 1.6s2026-10-10 UTC: p95 1.7s2026-10-11 UTC: p95 1.4s2026-10-12 UTC: p95 1.3s2026-10-13 UTC: p95 1.8s2026-10-14 UTC: p95 2.3s2026-10-15 UTC: p95 1.8s2026-10-16 UTC: p95 1.5s2026-10-17 UTC: p95 2.4s2026-10-18 UTC: p95 2.4s2026-10-19 UTC: p95 2.3s
Sep 20Oct 4Oct 19

Check your own site while you wait on Booking.com

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 are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 1251msstatus code: 401checked: Oct 19, 2026, 8:43 PM UTC
      0 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-West
      Checks passinglatency: 1304msstatus code: 401checked: Oct 19, 2026, 8:50 PM UTC
      0 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.
    • US-Central
      Checks passinglatency: 453msstatus code: 401checked: Oct 19, 2026, 8:51 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Booking.com normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 397msstatus code: 401checked: Oct 19, 2026, 8:38 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Booking.com normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 1754msstatus code: 401checked: Oct 19, 2026, 8:44 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Booking.com normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    DegradedEurope, UK
    • Europe
      Degradedlatency: 527msstatus code: 401checked: Oct 19, 2026, 8:49 PM UTC
      0 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.
    • UK
      Checks passinglatency: 341msstatus code: 401checked: Oct 19, 2026, 8:45 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Booking.com normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 1637msstatus code: 401checked: Oct 19, 2026, 8:44 PM UTC
      0 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.
    • Southeast Asia
      Checks passinglatency: 1621msstatus code: 401checked: Oct 19, 2026, 8:38 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Booking.com normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 3582msstatus code: 401checked: Oct 19, 2026, 8:08 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Booking.com normally. We do not have enough reports from Australia to say anything about what people there are seeing.

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 probe events

No probe events on record yet for Booking.com.

check 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 check readings and Booking.com's own claim at the time, side by side.

Full check history for Booking.com: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Put this badge in your README

Booking.com uptime by RealUptime's checksLive, from this page's own readings.
[![Booking.com uptime by RealUptime's checks](https://realuptime.io/outages/booking-com/badge.svg?days=30)](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 by RealUptime's checks" height="20"></a>

The badge shows the share of our checks that passed over the last 30 days. 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 and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

To cite this page: RealUptime, "Is Booking.com down?", https://realuptime.io/outages/booking-com. The readings change with every check, so give the date you read them.

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

How our checks compare with Booking.com's stated SLA

At or above your target

Our checks of Booking.com failed for none over the last 30 days, which is 100% uptime by our checks. A 99.9% target allows 43 minutes over that period.

Our checks show no gap in this period. That does not rule out one you saw.

These figures come from our own checks of one public endpoint per service. They are not the service's real uptime. This is computed from our own checks, 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.

What we check

secondary
https://www.booking.com/
primary
https://distribution-xml.booking.com/2.0/

What our check can and cannot see

A pass means the service's servers answered with the sign-in refusal they give any request that is not signed in. It does not show that sign-in works or that anything behind the sign-in wall responds.

Host checked: distribution-xml.booking.com

RealUptime is not affiliated with Booking.com; the name identifies what we checked, and nothing here speaks for Booking.com's own team. We send a single web request to Booking.com from 10 regions on our own schedule and time the response. We do not see inside Booking.com's systems, do not use an account or real transaction, and are not the same signal Booking.com's own team has access to. Treat this as one external data point, not a verdict. What we check for Booking.com is its front door only: a passing check means the endpoints above answered, not that the underlying product or account features work. Read the full methodology.