Booking.com reservations delayed

All Booking.com reservations delayed between 11:15 UTC and 17:55 UTC have been delivered to Mews, and the connection is operating normally. If you still notice a missing Booking.com reservation, please compare with the Booking.com Extranet and contact Mews Support.

Booking.com reservations have started reaching Mews again. Reservations delayed since around 11:15 UTC are now being delivered and created in Mews automatically. This may take some time to complete.

Booking.com’s service is not yet fully stable, so some further delays are still possible. Please continue to check the Booking.com Extranet for recent bookings until this incident is resolved. We’ll post another update within 60 minutes.

Identified: Booking.com’s Reservations API is still experiencing an outage. Since around 11:15 UTC, most new, modified and cancelled Booking.com reservations have not reached Mews, and none have arrived since 13:42 UTC. Booking.com is working on a fix, but they have not given an estimated resolution time. Other channels are not affected.

Reservations are not lost. They will be created in Mews automatically once Booking.com’s service is stable. Until then, please keep checking the Booking.com Extranet for new bookings and manage availability manually where needed to avoid overbookings. We’ll post another update within 60 minutes, or sooner if the situation changes.

Booking.com is still experiencing an outage of their Reservations API. Since around 11:15 UTC, most new, modified and cancelled Booking.com reservations have not reached Mews; only small batches have come through intermittently. Other channels are not affected.

Reservations are not lost. They will be created in Mews automatically once Booking.com’s service is stable. Until then, please check the Booking.com Extranet for new bookings and manage availability manually where needed to avoid overbookings. We are in contact with Booking.com and will post another update within 60 minutes.

Booking.com has reported a fix for their Reservations API, but we are not yet receiving Booking.com reservations reliably. Some reservations came through between 12:45 and 12:50 UTC, but most new, modified and cancelled bookings made since 11:15 UTC are still delayed.

Reservations are not lost. They will be created in Mews automatically as soon as the connection is stable again. Until then, please continue to check the Booking.com Extranet for new bookings to avoid overbookings. We’re monitoring closely and will post another update within 30 minutes.

Since around 11:30 UTC, new reservations, modifications and cancellations from Booking.com are not reaching Mews. This is caused by an outage of Booking.com’s Reservations API, which Booking.com has confirmed on their connectivity status page. Other channels and updates from Mews to Booking.com (availability, rates and restrictions) are not affected.

Reservations are not lost. Booking.com will resend them once their service recovers, and they will be created in Mews automatically. Until then, please check the Booking.com Extranet for new bookings to avoid overbookings. We’ll post an update when Booking.com restores service.