Airbnb status

How we check Airbnb

We watch www.airbnb.com from all five of our probe regions, every 2 minutes. A region that sees a failure does not make this page say "down" on its own: a second region has to agree first, the same confirmation rule every YoPingMe monitor uses.

Airbnb's web app is how the large majority of searching, booking, and host management actually happens, unlike some marketplaces built primarily as native apps, so we watch the web host directly and pin the response an anonymous request receives rather than assuming a 2xx.

What is Airbnb?

Airbnb operates as a marketplace connecting guests with hosts renting out homes and rooms, and unlike some delivery and ride-hailing apps built primarily around a mobile experience, a large share of searching, booking, and host management genuinely happens through the website. That makes the web host a meaningful, direct signal for the platform rather than a proxy for an app people rarely open a browser for instead.

Listing availability is the most common source of trouble mistaken for a platform issue. Each host controls their own calendar, pricing, and booking rules independently, and a listing that appears blocked or unavailable for specific dates is very often reflecting a real constraint the host set, a booking already made by someone else, or a minimum-stay rule, rather than a search feature malfunctioning. Airbnb's systems are accurately reporting what the host configured, even when the result is frustrating for a guest with specific dates in mind.

Host responsiveness is a separate axis from platform availability that is easy to conflate. Hosts are individuals or small operators replying on their own schedule rather than an automated system, so a message that sits unanswered for hours or longer reflects a person's availability, not a failure of the messaging system to deliver it. Checking whether a message shows as delivered or read is a more direct way to confirm the platform did its job than assuming an outage.

Reservations already confirmed do not depend on the platform staying continuously reachable to remain valid. A booking made before an incident stays booked, and the practical concern during any real disruption is whether new searches, messages, or bookings are affected going forward, not whether an existing trip is at risk. Guests with an imminent check-in during a reported issue are usually better served contacting their host directly through whatever channel exists outside the platform.

Price variation between searches for the same listing is a pricing-logic detail rather than a sign of anything wrong. Length-of-stay discounts, demand-based pricing a host has opted into, and fees that depend on party size or exact dates can all produce different totals for what looks like the same search, and none of it reflects instability in the platform showing the numbers.

Frequently asked questions

Is Airbnb down right now?

Check the board above; it reflects our own probes against Airbnb's web infrastructure from all five of our regions, refreshed every couple of minutes and confirmed across two regions before this page would call it down.

A listing shows as unavailable for my dates but this page says Airbnb is up. What does that mean?

That reflects the host's actual calendar, not a platform problem. Hosts control their own availability, pricing, and minimum-stay rules per listing, and a date range genuinely being blocked or already booked looks identical to a search glitch while Airbnb's systems are reporting the listing's real state accurately.

My message to a host has not been answered. Is that an outage?

Almost never. Hosts are individuals or small teams responding on their own schedule, not an automated system, so a delayed reply is a person not having checked messages yet rather than a platform failure to deliver anything. Checking the message thread for a delivered or read indicator confirms whether it reached the host.

Does an Airbnb outage cancel or affect an existing reservation?

No. An outage affects the ability to search, message, or book going forward, not the record of a reservation already confirmed. If a check-in coincides with a reported incident, the reservation itself remains valid; contacting the host directly through means outside the platform is the practical fallback if messaging is affected.

I am seeing different prices for the same listing on different searches. Is that a bug?

Usually not. Pricing can include dynamic adjustments for length of stay, demand-based pricing the host has enabled, and fees calculated per search context, so the same listing can legitimately show different totals depending on the exact dates and party size entered. This is pricing logic working as intended, not inconsistent platform behavior.