Skip to content

Outage tracker / Airbnb

Is Airbnb down?

I'm having a problem

Partially degradedchecked 4 minutes ago

Airbnb is answering our probes, but its API is running at least 3.9x its 7-day median from US-East. Everything else we check answered at its usual speed.

As of Oct 19, 2026, 9:22 PM UTC, RealUptime's checks of Airbnb passed in all 10 regions that returned a reading.

Front-door and live API checks

Our checks of Airbnb 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 Airbnb works for users.

Email me when our checks of Airbnb fail from two or more distant regions

One email when our checks of Airbnb 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 Airbnb's official status.

our check readinglive · checked Oct 19, 2026, 9:22 PM UTC
US-East1103 msDegraded
US-West661 msChecks passing
Europe612 msChecks passing
Asia-Pacific1011 msChecks passing
US-Central238 msChecks passing
Canada506 msChecks passing
UK203 msChecks passing
Southeast Asia1465 msChecks passing
Australia678 msChecks passing
South America1291 msChecks passing
their status pagetheir claim, not our reading

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

Airbnb 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 462ms2026-09-21 UTC: p95 701ms2026-09-22 UTC: p95 591ms2026-09-23 UTC: p95 681ms2026-09-24 UTC: p95 833ms2026-09-25 UTC: p95 1.3s2026-09-26 UTC: p95 962ms2026-09-27 UTC: p95 716ms2026-09-28 UTC: p95 811ms2026-09-29 UTC: p95 712ms2026-09-30 UTC: p95 764ms2026-10-01 UTC: p95 420ms2026-10-02 UTC: p95 437ms2026-10-03 UTC: p95 456ms2026-10-04 UTC: p95 466ms2026-10-05 UTC: p95 537ms2026-10-06 UTC: p95 686ms2026-10-07 UTC: p95 507ms2026-10-08 UTC: p95 667ms2026-10-09 UTC: p95 461ms2026-10-10 UTC: p95 743ms2026-10-11 UTC: p95 866ms2026-10-12 UTC: p95 394ms2026-10-13 UTC: p95 601ms2026-10-14 UTC: p95 428ms2026-10-15 UTC: p95 417ms2026-10-16 UTC: p95 1.0s2026-10-17 UTC: p95 602ms2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.4s
Sep 20Oct 4Oct 19
US-West
578msp95 · latest
2.5s1.3s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, 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 879ms2026-09-22 UTC: p95 1.5s2026-09-23 UTC: p95 1.1s2026-09-24 UTC: p95 791ms2026-09-25 UTC: p95 1.0s2026-09-26 UTC: p95 959ms2026-09-27 UTC: p95 1.7s2026-09-28 UTC: p95 1.0s2026-09-29 UTC: p95 805ms2026-09-30 UTC: p95 602ms2026-10-01 UTC: p95 944ms2026-10-02 UTC: p95 916ms2026-10-03 UTC: p95 506ms2026-10-04 UTC: p95 463ms2026-10-05 UTC: p95 808ms2026-10-06 UTC: p95 506ms2026-10-07 UTC: p95 692ms2026-10-08 UTC: p95 644ms2026-10-09 UTC: p95 568ms2026-10-10 UTC: p95 572ms2026-10-11 UTC: p95 771ms2026-10-12 UTC: p95 1.5s2026-10-13 UTC: p95 2.1s2026-10-14 UTC: p95 541ms2026-10-15 UTC: p95 821ms2026-10-16 UTC: p95 519ms2026-10-17 UTC: p95 615ms2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 578ms
Sep 20Oct 4Oct 19
Europe
1.2sp95 · latest
2.5s1.3s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 1.6s2026-09-21 UTC: p95 955ms2026-09-22 UTC: p95 800ms2026-09-23 UTC: p95 1.7s2026-09-24 UTC: p95 1.2s2026-09-25 UTC: p95 1.3s2026-09-26 UTC: p95 1.2s2026-09-27 UTC: p95 1.1s2026-09-28 UTC: p95 1.1s2026-09-29 UTC: p95 1.0s2026-09-30 UTC: p95 2.3s2026-10-01 UTC: p95 848ms2026-10-02 UTC: p95 793ms2026-10-03 UTC: p95 1.2s2026-10-04 UTC: p95 909ms2026-10-05 UTC: p95 640ms2026-10-06 UTC: p95 1.4s2026-10-07 UTC: p95 998ms2026-10-08 UTC: p95 814ms2026-10-09 UTC: p95 759ms2026-10-10 UTC: p95 1.9s2026-10-11 UTC: p95 1.2s2026-10-12 UTC: p95 758ms2026-10-13 UTC: p95 655ms2026-10-14 UTC: p95 937ms2026-10-15 UTC: p95 889ms2026-10-16 UTC: p95 786ms2026-10-17 UTC: p95 920ms2026-10-18 UTC: p95 815ms2026-10-19 UTC: p95 1.2s
Sep 20Oct 4Oct 19
Asia-Pacific
1.8sp95 · latest
5s2.5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 860ms2026-09-21 UTC: p95 1.4s2026-09-22 UTC: p95 1.4s2026-09-23 UTC: p95 2.3s2026-09-24 UTC: p95 996ms2026-09-25 UTC: p95 2.6s2026-09-26 UTC: p95 1.9s2026-09-27 UTC: p95 2.2s2026-09-28 UTC: p95 939ms2026-09-29 UTC: p95 2.5s2026-09-30 UTC: p95 1.3s2026-10-01 UTC: p95 2.4s2026-10-02 UTC: p95 2.4s2026-10-03 UTC: p95 809ms2026-10-04 UTC: p95 2.4s2026-10-05 UTC: p95 1.0s2026-10-06 UTC: p95 1.0s2026-10-07 UTC: p95 2.8s2026-10-08 UTC: p95 1.8s2026-10-09 UTC: p95 867ms2026-10-10 UTC: p95 2.1s2026-10-11 UTC: p95 1.8s2026-10-12 UTC: p95 3.1s2026-10-13 UTC: p95 1.6s2026-10-14 UTC: p95 648ms2026-10-15 UTC: p95 1.5s2026-10-16 UTC: p95 2.0s2026-10-17 UTC: p95 3.1s2026-10-18 UTC: p95 1.7s2026-10-19 UTC: p95 1.8s
Sep 20Oct 4Oct 19
US-Central
407msp95 · latest
5s2.5s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 303ms2026-09-21 UTC: p95 953ms2026-09-22 UTC: p95 1.1s2026-09-23 UTC: p95 678ms2026-09-24 UTC: p95 551ms2026-09-25 UTC: p95 517ms2026-09-26 UTC: p95 763ms2026-09-27 UTC: p95 1.5s2026-09-28 UTC: p95 802ms2026-09-29 UTC: p95 1.1s2026-09-30 UTC: p95 2.0s2026-10-01 UTC: p95 437ms2026-10-02 UTC: p95 833ms2026-10-03 UTC: p95 710ms2026-10-04 UTC: p95 1.1s2026-10-05 UTC: p95 343ms2026-10-06 UTC: p95 689ms2026-10-07 UTC: p95 889ms2026-10-08 UTC: p95 547ms2026-10-09 UTC: p95 446ms2026-10-10 UTC: p95 486ms2026-10-11 UTC: p95 333ms2026-10-12 UTC: p95 3.3s2026-10-13 UTC: p95 441ms2026-10-14 UTC: p95 485ms2026-10-15 UTC: p95 1.3s2026-10-16 UTC: p95 339ms2026-10-17 UTC: p95 892ms2026-10-18 UTC: p95 352ms2026-10-19 UTC: p95 407ms
Sep 20Oct 4Oct 19
Canada
1.3sp95 · latest
5s2.5s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 1.8s2026-09-21 UTC: p95 785ms2026-09-22 UTC: p95 1.2s2026-09-23 UTC: p95 950ms2026-09-24 UTC: p95 524ms2026-09-25 UTC: p95 1.2s2026-09-26 UTC: p95 761ms2026-09-27 UTC: p95 528ms2026-09-28 UTC: p95 1.7s2026-09-29 UTC: p95 2.9s2026-09-30 UTC: p95 614ms2026-10-01 UTC: p95 778ms2026-10-02 UTC: p95 839ms2026-10-03 UTC: p95 741ms2026-10-04 UTC: p95 749ms2026-10-05 UTC: p95 403ms2026-10-06 UTC: p95 1.1s2026-10-07 UTC: p95 668ms2026-10-08 UTC: p95 1.4s2026-10-09 UTC: p95 463ms2026-10-10 UTC: p95 599ms2026-10-11 UTC: p95 1.6s2026-10-12 UTC: p95 1.0s2026-10-13 UTC: p95 542ms2026-10-14 UTC: p95 719ms2026-10-15 UTC: p95 557ms2026-10-16 UTC: p95 694ms2026-10-17 UTC: p95 392ms2026-10-18 UTC: p95 1.0s2026-10-19 UTC: p95 1.3s
Sep 20Oct 4Oct 19
UK
828msp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 1s2026-09-21 UTC: p95 1.0s2026-09-22 UTC: p95 759ms2026-09-23 UTC: p95 892ms2026-09-24 UTC: p95 788ms2026-09-25 UTC: p95 930ms2026-09-26 UTC: p95 1.1s2026-09-27 UTC: p95 535ms2026-09-28 UTC: p95 709ms2026-09-29 UTC: p95 636ms2026-09-30 UTC: p95 724ms2026-10-01 UTC: p95 659ms2026-10-02 UTC: p95 509ms2026-10-03 UTC: p95 525ms2026-10-04 UTC: p95 657ms2026-10-05 UTC: p95 636ms2026-10-06 UTC: p95 431ms2026-10-07 UTC: p95 455ms2026-10-08 UTC: p95 512ms2026-10-09 UTC: p95 624ms2026-10-10 UTC: p95 571ms2026-10-11 UTC: p95 1.5s2026-10-12 UTC: p95 1.1s2026-10-13 UTC: p95 477ms2026-10-14 UTC: p95 897ms2026-10-15 UTC: p95 480ms2026-10-16 UTC: p95 687ms2026-10-17 UTC: p95 504ms2026-10-18 UTC: p95 608ms2026-10-19 UTC: p95 828ms
Sep 20Oct 4Oct 19
Southeast Asia
2.3sp95 · 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.0s2026-09-21 UTC: p95 1.5s2026-09-22 UTC: p95 1.5s2026-09-23 UTC: p95 2.3s2026-09-24 UTC: p95 1.5s2026-09-25 UTC: p95 1.4s2026-09-26 UTC: p95 1.5s2026-09-27 UTC: p95 1.6s2026-09-28 UTC: p95 1.8s2026-09-29 UTC: p95 1.5s2026-09-30 UTC: p95 1.8s2026-10-01 UTC: p95 1.3s2026-10-02 UTC: p95 1.3s2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 1.3s2026-10-05 UTC: p95 1.3s2026-10-06 UTC: p95 1.6s2026-10-07 UTC: p95 1.4s2026-10-08 UTC: p95 1.1s2026-10-09 UTC: p95 1.0s2026-10-10 UTC: p95 1.3s2026-10-11 UTC: p95 1.2s2026-10-12 UTC: p95 1.3s2026-10-13 UTC: p95 1.1s2026-10-14 UTC: p95 1.3s2026-10-15 UTC: p95 1.2s2026-10-16 UTC: p95 1.2s2026-10-17 UTC: p95 2.1s2026-10-18 UTC: p95 2.3s2026-10-19 UTC: p95 2.3s
Sep 20Oct 4Oct 19
Australia
2.9sp95 · 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 1.1s2026-09-21 UTC: p95 1.5s2026-09-22 UTC: p95 1.3s2026-09-23 UTC: p95 1.3s2026-09-24 UTC: p95 1.3s2026-09-25 UTC: p95 1.2s2026-09-26 UTC: p95 1.4s2026-09-27 UTC: p95 1.2s2026-09-28 UTC: p95 1.6s2026-09-29 UTC: p95 1.3s2026-09-30 UTC: p95 1.2s2026-10-01 UTC: p95 1.2s2026-10-02 UTC: p95 1.1s2026-10-03 UTC: p95 1.2s2026-10-04 UTC: p95 1.1s2026-10-05 UTC: p95 1.2s2026-10-06 UTC: p95 1.5s2026-10-07 UTC: p95 1.3s2026-10-08 UTC: p95 1.6s2026-10-09 UTC: p95 1.4s2026-10-10 UTC: p95 1.4s2026-10-11 UTC: p95 1.8s2026-10-12 UTC: p95 1.8s2026-10-13 UTC: p95 1.4s2026-10-14 UTC: p95 1.3s2026-10-15 UTC: p95 1.5s2026-10-16 UTC: p95 1.2s2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.7s2026-10-19 UTC: p95 2.9s
Sep 20Oct 4Oct 19
South America
1.3sp95 · latest
5s2.5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 1.7s2026-09-21 UTC: p95 1.4s2026-09-22 UTC: p95 1.6s2026-09-23 UTC: p95 1.3s2026-09-24 UTC: p95 1.3s2026-09-25 UTC: p95 1.7s2026-09-26 UTC: p95 2.1s2026-09-27 UTC: p95 1.7s2026-09-28 UTC: p95 1.8s2026-09-29 UTC: p95 1.7s2026-09-30 UTC: p95 1.8s2026-10-01 UTC: p95 1.5s2026-10-02 UTC: p95 1.1s2026-10-03 UTC: p95 1.6s2026-10-04 UTC: p95 1.6s2026-10-05 UTC: p95 1.2s2026-10-06 UTC: p95 1.2s2026-10-07 UTC: p95 1.5s2026-10-08 UTC: p95 1.7s2026-10-09 UTC: p95 2.1s2026-10-10 UTC: p95 1.7s2026-10-11 UTC: p95 1.4s2026-10-12 UTC: p95 2.9s2026-10-13 UTC: p95 1.6s2026-10-14 UTC: p95 1.4s2026-10-15 UTC: p95 4.6s2026-10-16 UTC: p95 1.5s2026-10-17 UTC: p95 2.5s2026-10-18 UTC: p95 1.4s2026-10-19 UTC: p95 1.3s
Sep 20Oct 4Oct 19

Check your own site while you wait on Airbnb

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 Airbnb. It cannot diagnose Airbnb's own systems.

What we measured, function by function

Airbnb answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • APIprimaryUS-East: Degraded Answering, but 3.9x slower than its 7-day median.US-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
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
    DegradedUS-East, US-West, US-Central, Canada
    • US-East
      Degradedlatency: 1103msstatus code: 400checked: Oct 19, 2026, 9:13 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Airbnb normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 661msstatus code: 400checked: Oct 19, 2026, 9:22 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Airbnb normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Checks passinglatency: 238msstatus code: 400checked: Oct 19, 2026, 8:51 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Airbnb normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 506msstatus code: 400checked: Oct 19, 2026, 8:35 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Airbnb normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 1291msstatus code: 400checked: Oct 19, 2026, 8:31 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Airbnb normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 612msstatus code: 400checked: Oct 19, 2026, 9:19 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Airbnb normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Checks passinglatency: 203msstatus code: 400checked: Oct 19, 2026, 8:43 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Airbnb 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: 1011msstatus code: 400checked: Oct 19, 2026, 9:14 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Airbnb normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 1465msstatus code: 400checked: Oct 19, 2026, 8:38 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Airbnb normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 678msstatus code: 400checked: Oct 19, 2026, 8:40 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Airbnb 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 Airbnb, 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 Airbnb yet, which is not evidence that nothing is wrong.

Recent probe events

No probe events on record yet for Airbnb.

check entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Airbnb 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 Airbnb covering any window you pick, with our check readings and Airbnb's own claim at the time, side by side.

Full check history for Airbnb: 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

Airbnb uptime by RealUptime's checksLive, from this page's own readings.
[![Airbnb uptime by RealUptime's checks](https://realuptime.io/outages/airbnb/badge.svg?days=30)](https://realuptime.io/outages/airbnb)
<a href="https://realuptime.io/outages/airbnb"><img src="https://realuptime.io/outages/airbnb/badge.svg?days=30" alt="Airbnb 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 Airbnb down?", https://realuptime.io/outages/airbnb. 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 Airbnb's stated SLA

At or above your target

Our checks of Airbnb 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 Airbnb'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

primaryfunctional: live API
https://api.airbnb.com/v2/listings
secondary
https://www.airbnb.com/

What our check can and cannot see

A pass means the service's servers answered our request with the error they give a request that carries no account or valid input. It does not show that sign-in works or that any real request succeeds.

Host checked: api.airbnb.com

RealUptime is not affiliated with Airbnb; the name identifies what we checked, and nothing here speaks for Airbnb's own team. We send a single web request to Airbnb from 10 regions on our own schedule and time the response. We do not see inside Airbnb's systems, do not use an account or real transaction, and are not the same signal Airbnb's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Airbnb is a real functional API call (marked “functional” above), not just a landing page, so a passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.