Resolved after 22 hours 33 minutes, on June 23, 2025.
A fix has been implemented and we are monitoring the results. As a result of this issue, there would have been some reservation webhook notifications that were delivered without the thread_id parameter. These have been backfilled and you should be able to retrieve them using the GET reservations API. We apologize for the inconvenience caused.
Update timeline
- investigating Jun 23, 2025, 10:09 AM UTC
We are currently investigating an issue that had begun on 2025-06-18, affecting a subset of reservation webhook notifications where the thread_id is not populated in the reservation object. As a result, some webhook notifications may experience delivery delays. Please note that this issue does not impact all reservation webhook notifications but is limited to a small subset. We recommend utilizing the GET reservations API to retrieve the necessary data for your system. Further updates will be provided as we progress in resolving this issue.
- monitoring Jun 24, 2025, 02:48 AM UTC
A fix has been implemented and we are monitoring the results. As a result of this issue, there would have been some reservation webhook notifications that were delivered without the thread_id parameter. These have been backfilled and you should be able to retrieve them using the GET reservations API. We apologize for the inconvenience caused.
- resolved Jun 24, 2025, 08:42 AM UTC
This incident has been resolved.
Your product runs on more than Airbnb
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services