We are notifying you of a recent, high-priority outage that temporarily disrupted communication on the Booking.com Reservations API. This issue has now been fully resolved.
Incident timeframe: - Start time: 04 November 2026, 10:50:57 AM UTC - End time: 04 November 2026, 01:51:10 PM UTC - Status: Resolved
Impact level: - High - Reservation communication through the Booking.com API was disrupted during the outage. - As an immediate mitigation, Booking.com applied a global hold to prevent reservation timeouts, and this hold will be lifted once the issue is resolved.
Action required: Partners are advised to review and retry any failed reservation requests during the affected timeframe.
All services are now operating normally and reservations are being communicated as expected. Booking.com will continue monitoring the system and take additional actions to mitigate any impact.
Thank you for your understanding.
Posted Nov 05, 2026 - 02:16 UTC
Identified
We would like to inform you about a technical issue from Booking.com causing a token retrieval error is currently ongoing.
Incident timeframe: - Start time: 4 November 2026, 5:06 PM (GMT+7) - End time: Ongoing
Impact level: - High - The connection with Booking.com is currently disrupted due to an issue with token retrieval. - Hotels may not receive new bookings from Booking.com and cannot push data updates to Booking.com. - The Product team is working with Booking.com to resolve this issue.
Action required: Hotels are advised to monitor their Booking.com accounts and make manual adjustments (e.g., updating room availability directly on Booking.com) to avoid overbooking.
We will keep you informed of any updates.
Thank you for your understanding.
Posted Nov 04, 2026 - 12:48 UTC
This incident affected: API and Channel Distribution.