Live / Mews / Incident
Mews: Reservation from booking.com are delayed and updates are failing
Mews · mews.comMajor incidentResolved2026-11-04 12:58 UTC
Public — what happened
Summary
Mews reported a major incident beginning at 11:02 UTC on 2026-11-04 in which it could not reach booking.com's systems, so reservations from booking.com were not arriving and updates from Mews were not being sent. By 11:15 UTC Mews said the problem was an outage on booking.com's side and that it was monitoring, with queued updates to be sent automatically once service returned. At 11:58 UTC Mews said booking.com had resolved its outage, that failed price, restriction and availability updates were being retried, and that missing reservations would soon appear. Mews marked the incident resolved at 12:58 UTC.
Affected
Mews Marketplace
Timeline
- Started — 2026-11-04 11:02 UTC
- Investigating — 2026-11-04 11:02 UTC
- Identified — 2026-11-04 11:15 UTC
- Monitoring — 2026-11-04 11:58 UTC
- Resolved — 2026-11-04 12:58 UTC · 1h 56m 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 46, 2026, our weekly internet health report.