Live / Mews / Incident
Mews: Guest Messenger unavailable for some properties
Mews · mews.comMinor incidentResolved2026-10-28 10:25 UTC
Public — what happened
Summary
Mews said Guest Messenger in Mews Operations was unavailable for some properties that had already been using it, showing a "Guest messaging is being set up" notice instead of the inbox. The company said staff at affected properties could not read or reply to guest messages and guests did not receive replies, while other parts of Mews Operations were not affected. Mews said the problem began on 27 October at 15:34 CET, and that it later found the cause and rolled out a fix. By 10:19 UTC on 28 October it reported Guest Messenger working normally for all properties, and the incident was marked resolved at 10:25.
Affected
Mews Guest Experience
Timeline
- Started — 2026-10-28 09:13 UTC
- Investigating — 2026-10-28 09:13 UTC (2 updates)
- Identified — 2026-10-28 09:28 UTC (2 updates)
- Monitoring — 2026-10-28 10:19 UTC
- Resolved — 2026-10-28 10:25 UTC · 1h 12m 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 45, 2026, our weekly internet health report.