Live / Mews / Incident
Mews: Commander detail pages fail with a "Oops, something went wrong" error
Mews · mews.comMinor incidentResolved2026-11-12 17:52 UTC
Public — what happened
Summary
Mews reported a minor problem in which Commander detail pages showed an "Oops, something went wrong" error instead of loading. The company said it affected users with an enterprise profile who open a property other than their own, such as chain, group or sales staff. Mews listed the issue as starting at 16:00 UTC on 2026-11-12 and said at 17:05 UTC that it was investigating, then reported that a fix had been deployed and was being watched closely. The incident was marked resolved at 17:52 UTC.
Affected
Mews Operations
Timeline
- Started — 2026-11-12 16:00 UTC
- Identified — 2026-11-12 16:00 UTC
- Monitoring — 2026-11-12 17:05 UTC
- Resolved — 2026-11-12 17:52 UTC · 1h 52m 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 47, 2026, our weekly internet health report.