Mews experienced a major incident on January 15, 2026 affecting Mews Operations, lasting 4h 15m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jan 15, 2026, 08:22 AM UTC
We are currently investigating an issue affecting ledger updates. Ledger data has not been updated since approximately 16:00 CET on January 14th. Our team is actively working to identify the root cause and restore normal operations. We will provide updates as we learn more.
- monitoring Jan 15, 2026, 09:08 AM UTC
The team has resolved the issue. We started syncing the accounting data to ledgers now and we will provide an update when the ledgers are fully up to date. We are closely monitoring the system to ensure stability.
- resolved Jan 15, 2026, 12:38 PM UTC
The issue is now fully resolved. All missing data have been synced to the accounting ledgers and they are operating as expected.
- postmortem Jan 23, 2026, 08:55 AM UTC
### Problem On **14 Jan 2026 at 1:57 PM UTC**, updates from the Mews Platform to the Accounting service \(Ledgers\) stopped being processed. During this period, **ledger balances and trial balances were not updated** with the latest activity, while day‑to‑day hotel operations continued to work normally. ### Action On **15 Jan 2026 at 8:44 AM UTC**, the Mews Engineering team restored the flow of updates to Accounting and temporarily increased system capacity to process the backlog. By **15 Jan 2026 at 2:23 PM UTC**, all ledgers were fully up to date and the system was operating normally again. ### Causes A change in our internal messaging system unintentionally interrupted the service that forwards updates from the Mews Platform to Accounting. The service appeared healthy but had stopped passing new events through, so new accounting activity was not reflected until the issue was identified and resolved. ### Solutions The team resolved the issue by restarting the affected service and briefly increasing Accounting system capacity to safely process all pending updates. All accounting data for the affected period has been reconciled. To reduce the chance of recurrence, Mews has strengthened safeguards around how changes are made to our systems and improved internal processes for managing them safely. These guardrails directly address the root cause of this incident and prevent this specific issue from happening again. We are also enhancing monitoring across our platform so that any similar issues can be detected and addressed even more quickly in the future.