Skip to content

Outage tracker / Booking.com

Is Booking.com down?

I'm having a problem

Operationalchecked 2 minutes ago

We reached Booking.com from all 10 regions we check.

As of Oct 6, 2026, 9:56 PM UTC, Booking.com answered RealUptime's probes in all 10 regions that returned a reading.

Reachability verified

Last outage: 1h 1m on Aug 31, 2026 (web surface, from Europe).

Email me the next time we see Booking.com go down

Measured by our own probes from ten regions, not Booking.com's status page. One email when a measured outage opens and one when it closes, after you confirm the address. No account, no card.

our independent probeslive · checked Oct 6, 2026, 9:56 PM UTC
US-East479 msOperational
US-West715 msOperational
Europe189 msOperational
Asia-Pacific874 msOperational
US-Central479 msOperational
Canada404 msOperational
UK437 msOperational
Southeast Asia952 msOperational
Australia1571 msOperational
South America1073 msOperational
their status pagetheir claim, not our reading

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

US-East
643msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-07 UTC: p95 642ms2026-09-08 UTC: p95 575ms2026-09-09 UTC: p95 565ms2026-09-10 UTC: p95 629ms2026-09-11 UTC: p95 555ms2026-09-12 UTC: p95 509ms2026-09-13 UTC: p95 562ms2026-09-14 UTC: p95 555ms2026-09-15 UTC: p95 603ms2026-09-16 UTC: p95 666ms2026-09-17 UTC: p95 647ms2026-09-18 UTC: p95 579ms2026-09-19 UTC: p95 584ms2026-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 643ms
Sep 7Sep 21Oct 6
US-West
1.2sp95 · 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-07 UTC: p95 612ms2026-09-08 UTC: p95 594ms2026-09-09 UTC: p95 402ms2026-09-10 UTC: p95 419ms2026-09-11 UTC: p95 577ms2026-09-12 UTC: p95 524ms2026-09-13 UTC: p95 530ms2026-09-14 UTC: p95 627ms2026-09-15 UTC: p95 695ms2026-09-16 UTC: p95 642ms2026-09-17 UTC: p95 680ms2026-09-18 UTC: p95 590ms2026-09-19 UTC: p95 647ms2026-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.2s
Sep 7Sep 21Oct 6
Europe
212msp95 · 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-07 UTC: p95 305ms2026-09-08 UTC: p95 305ms2026-09-09 UTC: p95 246ms2026-09-10 UTC: p95 335ms2026-09-11 UTC: p95 263ms2026-09-12 UTC: p95 357ms2026-09-13 UTC: p95 266ms2026-09-14 UTC: p95 240ms2026-09-15 UTC: p95 326ms2026-09-16 UTC: p95 359ms2026-09-17 UTC: p95 386ms2026-09-18 UTC: p95 382ms2026-09-19 UTC: p95 359ms2026-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 212ms
Sep 7Sep 21Oct 6
Asia-Pacific
1.4sp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-07 UTC: p95 845ms2026-09-08 UTC: p95 986ms2026-09-09 UTC: p95 856ms2026-09-10 UTC: p95 933ms2026-09-11 UTC: p95 832ms2026-09-12 UTC: p95 719ms2026-09-13 UTC: p95 1.2s2026-09-14 UTC: p95 951ms2026-09-15 UTC: p95 783ms2026-09-16 UTC: p95 1.0s2026-09-17 UTC: p95 996ms2026-09-18 UTC: p95 969ms2026-09-19 UTC: p95 1.5s2026-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.4s
Sep 7Sep 21Oct 6
US-Central
497msp95 · 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-07 UTC: p95 837ms2026-09-08 UTC: p95 611ms2026-09-09 UTC: p95 600ms2026-09-10 UTC: p95 530ms2026-09-11 UTC: p95 667ms2026-09-12 UTC: p95 629ms2026-09-13 UTC: p95 633ms2026-09-14 UTC: p95 607ms2026-09-15 UTC: p95 609ms2026-09-16 UTC: p95 607ms2026-09-17 UTC: p95 573ms2026-09-18 UTC: p95 539ms2026-09-19 UTC: p95 584ms2026-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 497ms
Sep 7Sep 21Oct 6
Canada
890msp95 · 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-07 UTC: p95 634ms2026-09-08 UTC: p95 588ms2026-09-09 UTC: p95 735ms2026-09-10 UTC: p95 648ms2026-09-11 UTC: p95 696ms2026-09-12 UTC: p95 680ms2026-09-13 UTC: p95 805ms2026-09-14 UTC: p95 691ms2026-09-15 UTC: p95 827ms2026-09-16 UTC: p95 690ms2026-09-17 UTC: p95 692ms2026-09-18 UTC: p95 557ms2026-09-19 UTC: p95 636ms2026-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 890ms
Sep 7Sep 21Oct 6
UK
486msp95 · 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-07 UTC: p95 244ms2026-09-08 UTC: p95 196ms2026-09-09 UTC: p95 186ms2026-09-10 UTC: p95 217ms2026-09-11 UTC: p95 218ms2026-09-12 UTC: p95 359ms2026-09-13 UTC: p95 369ms2026-09-14 UTC: p95 338ms2026-09-15 UTC: p95 378ms2026-09-16 UTC: p95 231ms2026-09-17 UTC: p95 238ms2026-09-18 UTC: p95 366ms2026-09-19 UTC: p95 200ms2026-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 486ms
Sep 7Sep 21Oct 6
Southeast Asia
1.0sp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-07 UTC: p95 931ms2026-09-08 UTC: p95 867ms2026-09-09 UTC: p95 763ms2026-09-10 UTC: p95 944ms2026-09-11 UTC: p95 1.0s2026-09-12 UTC: p95 752ms2026-09-13 UTC: p95 926ms2026-09-14 UTC: p95 963ms2026-09-15 UTC: p95 791ms2026-09-16 UTC: p95 792ms2026-09-17 UTC: p95 1.1s2026-09-18 UTC: p95 1.7s2026-09-19 UTC: p95 1.2s2026-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.0s
Sep 7Sep 21Oct 6
Australia
1.7sp95 · 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-07 UTC: p95 959ms2026-09-08 UTC: p95 1.1s2026-09-09 UTC: p95 942ms2026-09-10 UTC: p95 1.1s2026-09-11 UTC: p95 961ms2026-09-12 UTC: p95 1.2s2026-09-13 UTC: p95 1.1s2026-09-14 UTC: p95 1.4s2026-09-15 UTC: p95 1.3s2026-09-16 UTC: p95 771ms2026-09-17 UTC: p95 671ms2026-09-18 UTC: p95 660ms2026-09-19 UTC: p95 711ms2026-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.7s
Sep 7Sep 21Oct 6
South America
1.4sp95 · 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-07 UTC: p95 1.1s2026-09-08 UTC: p95 994ms2026-09-09 UTC: p95 997ms2026-09-10 UTC: p95 1.5s2026-09-11 UTC: p95 847ms2026-09-12 UTC: p95 875ms2026-09-13 UTC: p95 890ms2026-09-14 UTC: p95 1.1s2026-09-15 UTC: p95 1.0s2026-09-16 UTC: p95 998ms2026-09-17 UTC: p95 1.0s2026-09-18 UTC: p95 817ms2026-09-19 UTC: p95 886ms2026-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.4s
Sep 7Sep 21Oct 6

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 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 we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 479msstatus code: 401checked: Oct 6, 2026, 9:37 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
      Operationallatency: 715msstatus code: 401checked: Oct 6, 2026, 9:48 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
      Operationallatency: 479msstatus code: 401checked: Oct 6, 2026, 9:24 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
      Operationallatency: 404msstatus code: 401checked: Oct 6, 2026, 9:30 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
    Operationallatency: 1073msstatus code: 401checked: Oct 6, 2026, 9:25 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
    OperationalEurope, UK
    • Europe
      Operationallatency: 189msstatus code: 401checked: Oct 6, 2026, 9:55 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
      Operationallatency: 437msstatus code: 401checked: Oct 6, 2026, 9:25 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
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 874msstatus code: 401checked: Oct 6, 2026, 9:52 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
      Operationallatency: 952msstatus code: 401checked: Oct 6, 2026, 9:24 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
      Operationallatency: 1571msstatus code: 401checked: Oct 6, 2026, 9:56 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 outages

Partial outage, 1h 1mmeasured by our probes · Europe2026-08-31

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.

Put this badge in your README

Booking.com uptime measured by RealUptimeLive, from this page's own readings.
[![Booking.com uptime measured by RealUptime](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 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 last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 minutes over that period.

By our measurement there is no shortfall to claim for this period.

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.

What we check

secondary
https://www.booking.com/
primary
https://distribution-xml.booking.com/2.0/
RealUptime is not affiliated with Booking.com; the name identifies what we measured, 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 proves reachability only: the endpoints above answer, but that does not confirm the underlying product or account features work. Read the full methodology.