Live / Mews / Incident
Mews: Issues with login and slow performance
Mews · mews.comCritical outageResolved2026-10-29 17:16 UTC
Public — what happened
Summary
Mews reported a critical incident on 2026-10-29 in which its system ran slowly, with some users facing long loading times, timeouts, forced logouts and failed logins. The company said the login problems occurred between 15:25 and 15:40 UTC, and it began investigating at 15:39 UTC. By 16:02 UTC Mews said performance was back to normal and people could log in again, and it said it had traced the problem to one of its database replicas and was working with its cloud provider on the root cause. The incident was marked resolved at 17:16 UTC.
Affected
Mews Operations, Mews Guest Experience, Mews Open API
Timeline
- Started — 2026-10-29 15:39 UTC
- Investigating — 2026-10-29 15:39 UTC (2 updates)
- Monitoring — 2026-10-29 16:02 UTC
- Resolved — 2026-10-29 17:16 UTC · 1h 38m 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.