Live  /  Mews  /  Incident

Mews: Performance Degredation Resolved

Mews · mews.comMinor incidentResolved2026-11-05 18:34 UTC
Public — what happened

Summary

Mews reported slower performance for customers connecting from Norway, starting around 07:35 UTC on November 4, with pages like the reservation timeline and reports loading slowly. The company said its own systems were working normally and pointed to a network connection problem at a third-party provider's Oslo location, which later also touched some customers in Sweden. On November 5 Mews reported slow loading again for some properties in several Nordic countries and Spain, which could slow front-desk work at check-in. Mews said the team resolved the slowdown for Norway customers and was monitoring, and the incident was marked resolved at 18:34 on November 5.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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.

The full archive is on the Mews status & history page.

Related: Mews status & history. SquidGrid is not affiliated with Mews.