Live / Mews / Incident
Mews: Errors accessing Flexkeeping
Mews · mews.comMajor incidentResolved2026-10-05 16:26 UTC
Public — what happened
Summary
Mews reported a major incident on October 5, 2026, beginning at 15:35 UTC, in which some Flexkeeping customers had trouble reaching the Flexkeeping website. The company said its team had pinpointed the problem at that point and was rolling out an urgent fix, though it did not describe the cause. By 16:16 UTC Mews said the fix was live, service should be working again, and no data had been lost. After a period of monitoring, the incident was marked resolved at 16:26.
Timeline
- Started — 2026-10-05 15:35 UTC
- Identified — 2026-10-05 15:35 UTC
- Monitoring — 2026-10-05 16:16 UTC
- Resolved — 2026-10-05 16:26 UTC · 51 min 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 42, 2026, our weekly internet health report.