Airbnb Outage History

We are actively investigating intermittent connection issues where some API responses may be cut off before they are fully received. This began on September 29, 2026 at approximately 20:30 UTC and mainly affects larger responses, for example, from the reservations, listings, threads and resolutions endpoints. Our engineering teams are working to identify and resolve the issue, and we will update you with the latest information as soon as possible. In the meantime, we recommend retrying any requests that return incomplete responses, and using smaller page sizes (`_limit`) where possible.

We are currently investigating an issue affecting Partner Portal Sandbox V2 test applications. Affected apps are receiving 403 errors on write requests (for example, listing updates), while read requests continue to work normally. This issue is currently isolated to Sandbox V2 test apps; production listings are not affected. We will share more updates as soon as possible.

We are currently investigating an issue that is preventing `payout_notification` webhooks from being sent in some instances. The issue began on August 14, 2026, and has recurred on later dates. We recommend checking for gaps across all payout dates since then, not only August 14, 2026. In the meantime, partners can use the Transactions and Reservations API to retrieve relevant information about payouts. We are developing a fix and will update this page as work progresses.

We are investigating an incident impacting Airbnb and the API. This issue started around 2026-08-24 05:45 UTC and may result in 500 errors across our endpoints, mainly the pricing settings endpoint. We will share more updates as soon as possible.

We are currently investigating an issue that is causing delays in webhook notification deliveries. The delays started at approximately 2026-08-19 21:30 UTC and continue intermittently. We will provide further updates as soon as possible.

We are currently investigating an increased number of 500 Errors impacting the POST /v2/special_offers endpoint, which is used to send both special offers and pre-approvals. This started around 06:00 PDT and increased significantly from 09:15 PDT. Our engineering teams are working to identify and resolve the issue, and we will update you with the latest information as soon as possible.

We are actively investigating an increased number of 500 errors being served in response to PUT requests made to the Listings API. This issue began today, June 4, at approximately 9:00 UTC and spike between 9:30 and 10:45 UTC. These errors are persisting at a small scale, intermittently. We will provide more updates as they become available. We apologize for the inconvenience.

We had an issue that resulted in delayed processing of calendar and availability updates submitted through the calendar operations endpoint. Affected requests were either accepted successfully but took longer than usual to be reflected, with processing delays of approximately 45 minutes to 2 hours during the peak of the impact or failed altogether. The issue began on June 3, 2026 at approximately 02:00 UTC and was resolved on June 4, 2026 at approximately 05:30 UTC. This issue affected some partners submitting high volumes of calendar updates. Please retry any updates that did not take effect, and reach out to us via the Support Portal if you are still encountering the issue.

We are currently investigating an increased number of 500 Errors and high latency impacting requests to both Standard and LOS Record Calendar API endpoints. This pattern began today, June 2, at approximately 19:00 UTC. We recommend retrying any requests that are not processed successfully (as indicated by delivery of `async_request_failure_notification` webhooks). Our engineering teams are working to identify and resolve the issue, and we will update you with the latest information as soon as possible.

We are actively investigating intermittent 404 errors affecting the /v2/listing_photos endpoint. Some partners may experience failures when uploading, updating, or deleting listing photos. These errors are server-side and do not indicate that your listings or photos have been removed. To verify the actual state of a photo that returned a 404, call GET /v2/listing_photos?listing_id={listing_id} for all photos on a listing, or GET /v2/listing_photos/{photo_id} for a specific photo. Confirm whether the change took effect before retrying. Our engineering teams are working to identify and resolve the issue, and we will update you with the latest information as soon as possible.

We are currently investigating an increased number of 500 Errors impacting mainly the GET /v2/reservations/{confirmation_code} endpoint for some confirmations codes. This started around 19:30 PST. Our engineering teams are working to identify and resolve the issue, and we will update you with the latest information as soon as possible.

We are currently encountering an issue beginning at 05:00pm PST resulting in 500 errors across various endpoint. We will provide more updates as they become available. We apologize for the inconvenience.

We are continuing to investigate this issue.

We are investigating an incident impacting Airbnb and the API. This issue started around Oct 20 12:11 AM PDT and may result in 500 errors across our endpoints and the Airbnb website. We will share more updates as soon as possible.

We are currently investigating an issue that is preventing some partners from creating Support Tickets. For critical issues that require escalation, kindly contact your Airbnb Connectivity Partner Manager. Please see ticket priority guidelines - https://developer.airbnb.com/docs/create-and-manage-support-cases#ticket-priority We are looking into the matter and will update you with the latest information as soon as possible.

We are actively working to resolve an issue affecting access to the Partner Portal, and will post more updates as soon as possible.