Major incident

Mews: Mews POS unavailable

Current status of Mews: Operational — live Mews status

Timeline

1. Oct 2, 2026, 13:30 UTC
   resolved
   On 2 October 2026 between 15:14 and 15:41 CEST, Mews POS was slow or unavailable for all customers. Customers could not log in to POS or complete transactions. Our team identified the cause and reversed a configuration change within 20 minutes of the first alert. Service was fully restored at 15:41 CEST, and operations returned to normal shortly after.
2. Oct 8, 2026, 08:05 UTC
   postmortem
   **Problem** On 2 October 2026 at 15:14 CEST, POS became slow or unavailable for all customers for approximately 27 minutes. Customers could not log in or complete transactions. **Action** The team identified the cause and reversed a configuration change within 20 minutes of the first alert. Service was fully restored by 15:41 CEST, and operations returned to normal shortly after. **Causes** An unexpected increase in incoming payment notifications put excessive load on the POS database, which slowed down and then interrupted the service. **Solutions** The configuration change was immediately reversed to stop the notification flood. We are now improving the notification handler to filter out irrelevant messages before re-enabling the feature, with a staged rollout plan that includes database monitoring at each step.

Updates as published by Mews (original).