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
Support Service Operational
Support Chat Service Operational
Support Inbound Calls Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance

Nov 6, 2026

No incidents reported today.

Nov 5, 2026

Resolved - This incident has been resolved.
Nov 5, 19:34 CET
Monitoring - The team has resolved the performance degredation for our customers in Norway, and we are closely monitoring the system to ensure stability.
Nov 5, 17:08 CET
Update - Today, November 5, some properties in Norway, Sweden, Finland, Denmark and Spain are experiencing slow loading in Mews, which may delay front-desk work during check-in, although completing the check-in itself is unaffected. We’re working to restore normal performance and will share another update; no customer workaround is currently confirmed.
Nov 5, 14:08 CET
Investigating - We have noticed a downgraded performance of the system.
We are currently looking into it. There is a slowness reported from Nordic properties.
Thank you for your patience.

Nov 5, 13:52 CET
Update - We are continuing to investigate slower performance in Mews for customers connecting from Norway, and some customers in Sweden. Mews remains available, but some pages, such as the reservation timeline and reports, may still load more slowly than usual.

Mews systems themselves are working normally. The provider has escalated the issue to its engineering team, and we have also raised it with our hosting provider. We are continuing to work with them to resolve it.

We will post another update if anything changes. Thank you for your patience.

Nov 4, 17:07 CET
Monitoring - We have identified the cause of the slower performance affecting customers connecting from Norway, and some customers in Sweden. The issue is in the network connection between our internet provider's Oslo location and our servers. Mews systems themselves are working normally.

Performance has improved over the last hour but is not yet fully back to normal. Some pages, such as the reservation timeline and reports, may still load more slowly than usual. We are working with the provider, who is actively investigating.

We will post another update if anything changes. Thank you for your patience.

Nov 4, 13:24 CET
Update - We are continuing to investigate slower performance in Mews for customers connecting from Norway, which started at 08:35 CET (07:35 UTC). Mews remains available, but some pages may load slowly, especially those that load more data, such as the reservation timeline and reports. Customers in other regions are not affected.

Our systems are operating normally. The issue appears to be with the network connection between our internet provider's Oslo location and our servers. We have escalated the issue with the provider and are working on ways to reduce the impact.

Thank you for your patience.

Nov 4, 11:25 CET
Investigating - We are seeing slower performance in Mews for customers connecting from Norway and Germany since 08:35 CET (07:35 UTC). Pages such as the reservation timeline and reports may take longer than usual to load. Customers in other regions are not affected.

Our investigation points to a connectivity issue at a third-party network provider's Oslo location, not to Mews systems. We are working to resolve it.

We will post another update within 30 minutes. Thank you for your patience.

Nov 4, 10:49 CET
Postmortem - Read details
Nov 5, 17:05 CET
Resolved - This incident has been resolved.
Nov 5, 16:44 CET
Monitoring - The issue was pinpointed to a specific race condition and the mitigation has started. All impacted properties will be back to normal within 30 minutes.
Nov 5, 15:53 CET
Identified - The Mews team identified the issue and is working on a resolution. Further updates will follow as we make progress.
Nov 5, 13:50 CET

Nov 4, 2026

Resolved - All the failed updates were successfully resend to booking.com
Nov 4, 13:58 CET
Monitoring - The outage on booking.com side has been resolved.
The retry of all the failed price, restriction and availability updates is in the progress.
Missing reservations will shortly appear in Mews.

Nov 4, 12:58 CET
Identified - Booking.com is experiencing an outage.
https://connectivity-status.booking.com/
We are monitoring situation from our side.
Once the outage is resolved all the updates will be automatically sent to booking.com

Nov 4, 12:15 CET
Investigating - We are unable to reach booking.com APIs. We are investigating the issue.
Currently no updates are automatically sent to booking.com nor any reservations are retrieved from booking.com

Nov 4, 12:02 CET

Nov 3, 2026

No incidents reported.

Nov 2, 2026

No incidents reported.

Nov 1, 2026

No incidents reported.

Oct 31, 2026

No incidents reported.

Oct 30, 2026

No incidents reported.

Oct 29, 2026

Postmortem - Read details
Nov 5, 20:05 CET
Resolved - This incident has been resolved. If you still have trouble logging in or notice slow performance, please contact our support team.
Oct 29, 18:16 CET
Update - The system has been stable and performing normally since recovery.

We are still working with our cloud provider to find the root cause of the database replica issue, and we will take steps to prevent it from happening again. We apologize for the disruption and thank you for your patience.

Oct 29, 18:02 CET
Monitoring - Between 15:25 and 15:40 UTC, some users of the mews monolith were logged out or couldn’t log in, and the system was slower than usual. Performance has since returned to normal and users can log in again. We traced the issue to one of our database replicas and are working with our cloud provider to investigate the root cause. We are monitoring the situation closely.
Oct 29, 17:02 CET
Update - Some users were getting logged out and encountered login failures between 15:25-15:40 UTC. We are seeing signs of recovery and continue investigating.
Oct 29, 16:46 CET
Investigating - We have noticed degraded performance of the system, user may experience long loading times and timeouts.
We are investigating.
Thank you for your patience.

Oct 29, 16:39 CET

Oct 28, 2026

Postmortem - Read details
Nov 5, 12:40 CET
Resolved - The issue is now fully resolved. Mews is now operating as expected.
Oct 28, 11:25 CET
Monitoring - Guest Messenger is working normally for all properties.
Oct 28, 11:19 CET
Update - The Mews team identified the issue and is working on a resolution. Further updates will follow as we make progress.
Oct 28, 10:53 CET
Identified - The issue has been identified and a fix is being implemented.
Oct 28, 10:28 CET
Update - Since 27 October, 15:34 CET, Guest Messenger shows “Guest messaging is being set up” instead of the inbox for some properties, and guests aren’t getting replies. We found the cause and are rolling out a fix. You don’t need to do anything.
Oct 28, 10:26 CET
Investigating - Since 27 October at 15:34 CET, Guest Messenger in Mews Operations shows “Guest messaging is being set up” instead of the inbox for many properties that were already using it. Staff at affected properties can’t read or reply to guest messages, and guests don’t receive replies. Other parts of Mews Operations aren’t affected. We’re investigating the cause and will post an update within 30 minutes.
Oct 28, 10:13 CET

Oct 27, 2026

Resolved - The issue is now fully resolved. Mews is now operating as expected.
Oct 27, 11:09 CET
Monitoring - The team has resolved the issue, and we are closely monitoring the system to ensure stability.
Oct 26, 20:05 CET

Oct 26, 2026

Oct 25, 2026

No incidents reported.

Oct 24, 2026

No incidents reported.

Oct 23, 2026

No incidents reported.