All Systems Operational

About This Site

Having trouble? Troubleshoot performance issues, check historical uptimes at uptime.mews.com.


In case of an emergency or system outage, Mews recommends scheduling report exports to ensure smooth operations in your property. Check the emergency report documentation for more information.

Mews Operations Operational
Mews Guest Experience Operational
Mews Business Intelligence Operational
Mews Payments Operational
Mews Open API Operational
Mews Marketplace Operational
Mews Events Operational
Mews POS Operational
Mews RMS (Atomize) Operational
Aircall Inbound calls Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Web throughput ?
Web response time ?
API throughput ?
API response time ?
Jan 7, 2026

No incidents reported today.

Jan 6, 2026

No incidents reported.

Jan 5, 2026

No incidents reported.

Jan 4, 2026

No incidents reported.

Jan 3, 2026
Resolved - The mitigation was successfully applied, and systems are now fully operational. During the process, there were two brief performance spikes, but these have been resolved. We will continue to monitor closely, but no further impact is expected.
Jan 3, 23:47 CET
Update - Microsoft Azure will be performing a restart of our database as part of a long-term fix to fully resolve the underlying issue. This restart is scheduled for 22:00 UTC and may cause brief downtime or slower performance during the maintenance window. We will continue to monitor closely and provide updates once the process is complete. Please see https://status.mews.com/incidents/1wqydcw6p47c for more details.
Jan 3, 17:38 CET
Update - Systems are stable and reporting features are working as expected. We continue to monitor closely and are actively working with Microsoft Azure on mitigating the root cause to prevent any recurrence.
Jan 3, 14:53 CET
Update - Systems have stabilized and reporting features are functioning normally. However, the underlying root cause has not yet been fully addressed, and the issue could potentially recur. We remain engaged with Microsoft on a detailed root cause analysis and long-term remediation. We will continue to monitor closely and share updates as we progress.
Jan 2, 18:12 CET
Update - We’re seeing the issue reoccur, affecting some reporting features. Customers may experience missing or delayed data in reports, errors when accessing certain pages, and general slowness.
We are actively working with Microsoft Azure to resolve it as quickly as possible.

Jan 2, 15:55 CET
Update - Performance remains stable. We are continuing to work closely with Microsoft on a detailed root cause analysis and deeper investigation.
Jan 2, 09:26 CET
Monitoring - The underlying issue was resolved and systems are recovering. Reporting features and page performance should be returning to normal, but we’re continuing to monitor closely to ensure everything is fully stable.
Jan 1, 22:53 CET
Investigating - We're investigating an issue affecting some reporting features. Some customers may see missing or delayed data in reports, but also errors when accessing some pages and general slowness.
We’ve traced the problem to an issue with our database systems and are working closely with our cloud provider, Microsoft Azure, to resolve it as quickly as possible.

Jan 1, 22:17 CET
Completed - The scheduled maintenance has been completed. The mitigation was successfully applied.
Jan 3, 23:35 CET
Verifying - The restart is completed and we are verifying that the application performance is recovered.
Jan 3, 23:22 CET
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 3, 23:00 CET
Scheduled - We have been addressing an issue that was causing peaks of missing or delayed data in reports, occasional errors when loading certain pages, and slower overall performance. The root cause was identified as a problem with our database systems.

To fully resolve this and ensure long-term stability, Microsoft Azure will perform a database restart as part of the permanent fix. This maintenance is scheduled for 22:00 UTC and may result in brief downtime or slower performance during the restart. We’ll monitor the process closely and provide updates once it’s complete.

If the issue reoccurs before the scheduled time, we will consider performing the restart sooner to minimize impact.

Jan 3, 17:36 CET
Jan 2, 2026
Jan 1, 2026
Dec 31, 2025
Resolved - This incident has been resolved.
Dec 31, 22:23 CET
Monitoring - Issue has been resolved and we are monitoring the delays in the queue processing
Dec 29, 00:51 CET
Identified - We have noticed a downgraded performance of webhook processing for public APIs.
We are currently looking into cleaning up the queue and bringing the queue wait time back down.
Thank you for your patience.

Dec 28, 23:16 CET
Resolved - The observed spike of responses affecting Kiosk clients stopped occurring after ~14:00 UTC. No new occurrences have been detected since.

Investigation confirmed the errors were caused by server-side transaction timeouts during bill retrieval, with no evidence of application logic failures.

As the issue has self-resolved and is no longer reproducible, the incident is being closed. The situation will continue to be monitored and followed up systematically.

Dec 31, 19:36 CET
Investigating - We are currently investigating reports of an issue affecting Mews Kiosk. The Mews team is actively working to identify the cause, and we will provide updates as soon as possible.
Dec 31, 15:30 CET
Resolved - All operations are now stable and processing at normal times.
Dec 31, 16:49 CET
Investigating - We have noticed a downgraded performance of the marketplace operations.
We are currently looking into it.

Dec 31, 15:53 CET
Dec 30, 2025

No incidents reported.

Dec 29, 2025
Dec 28, 2025
Dec 27, 2025

No incidents reported.

Dec 26, 2025

No incidents reported.

Dec 25, 2025

No incidents reported.

Dec 24, 2025

No incidents reported.