Live / Mews / Incident
Mews: Booking.com reservations delayed
Mews · mews.comMinor incidentResolved2026-10-15 18:51 UTC
Public — what happened
Summary
Mews said that new bookings, changes and cancellations made through Booking.com were not arriving in its system, starting around 11:15 to 11:30 UTC on 2026-10-15; other sales channels and the information Mews sends to Booking.com, such as rates and availability, kept working. Mews attributed the problem to an outage of Booking.com's Reservations API, which it said Booking.com had confirmed, and it advised hotels to check the Booking.com Extranet for new bookings in the meantime. Mews stressed that no reservations were lost. Only small batches arrived during the afternoon, until deliveries resumed by 18:10 UTC, when the backlog began syncing automatically, and the incident was marked resolved at 18:51.
Timeline
- Started — 2026-10-15 12:03 UTC
- Identified — 2026-10-15 12:03 UTC (4 updates)
- Monitoring — 2026-10-15 18:10 UTC
- Resolved — 2026-10-15 18:51 UTC · 6h 48m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Mews against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Mews: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Mews report →
More from Mews
Covered in The Squid’s Ink, Week 43, 2026, our weekly internet health report.