Downgraded Performance
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 04, 2026 - 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 04, 2026 - 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 04, 2026 - 10:49 CET

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 4, 2026

Reservation from booking.com are delayed and updates are failing
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

Issues with login and slow performance
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

Guest Messenger unavailable for some properties
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

Issue with Mews
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.

Oct 22, 2026

An issue with sending inventory updates to Booking.com
Resolved - Booking.com has resolved the issue!

We are staring the recovery process of inventory updates. The changes made between created between 11:00am UTC and 15:00 UTC today were delivered to booking.com with a delay.

We can also confirm that we see reservations coming in from Booking.com. We expect Booking.com to send us all reservations (created or modified) during the outage interval.

We are still monitoring the recovery process
Oct 22, 17:27 CEST
Update - The issue on Booking.com's side remains unresolved, and inventory updates and reservation delivery are still affected.

We are continuing to monitor the situation and preparing the recovery process so we can start processing queued inventory updates and recover affected reservations as soon as Booking.com restores its services.

We will provide another update as soon as there is meaningful progress.
Oct 22, 16:45 CEST
Update - Booking.com is actively working on fixing the issue. It is classified as Major disruption of their service.

The incident can be observed here - https://connectivity-status.booking.com/

Unfortunately, the issue has also started affecting reservation delivery, so we can confirm the are no reservations delivered. Therefore we decided to reclassify the incident as critical.

Once the issue will be resolved on Booking.com side, we will handle the recovery of reservations, as well as missed inventory updates.
Oct 22, 15:03 CEST
Identified - We have identified the cause to be on Booking.com side. We are reaching out to them to resolve the issue as soon as possible.

Reservations are still coming in, the issue affects only sending inventory updates (i.e. availability, prices and restrictions).
Oct 22, 14:15 CEST
Investigating - We are currently investigating an issue with delivering inventory updates to Booking.com. All requests are queued and waiting on our side for booking.com to accept them. Once the issue will be resolved, we will push all the queued data.
Oct 22, 13:58 CEST
Critical 0 day PHP vulnerability
Resolved - In response to the Critical PHP Vulnerability announced today, all potentially impacted instances were patched. We continue to monitor the situation diligently. No customer impact was observed.

Thank you for your understanding.
Oct 22, 00:33 CEST
Update - Updated security packages for the recent PHP vulnerabilities are starting to become available. We're preparing to apply them to the affected parts of our environment once they've been tested. Our protective measures stay in place and we're monitoring our systems closely. So far we've found no evidence that customer data or Mews services have been affected.

You don't need to do anything at this time. We'll post another update when remediation is under way.
Oct 21, 17:14 CEST
Update - We're continuing to respond to the recently disclosed critical vulnerabilities in PHP. The PHP maintainers have now released security fixes, and our teams are reviewing them and preparing to roll them out safely.

We have also added protective measures to reduce exposure while this work is under way, and we're watching our systems closely. So far we have found no evidence that customer data or Mews services have been affected.

What this means for you:
You don't need to do anything at this time. If that changes, we'll contact you directly.

We'll post another update as our work progresses or if anything changes. If you have questions, please contact our support team.
Oct 21, 16:02 CEST
Investigating - Dear customer,

We are aware of reports of a newly disclosed critical (zero-day) vulnerability affecting PHP 5.4+. We want you to know that we’re aware of it and our Security team is actively monitoring the situation.

What we’re doing

We’re assessing our environment to understand any potential exposure across our systems.
We’ve deployed extra monitoring and detection tools to spot and respond to any activity linked to this vulnerability.
We’re following guidance from the PHP maintainers and security researchers closely, and we’ll apply mitigations and patches as soon as they’re available and validated.


What this means for you
At this time, you don’t need to take any action. Protecting your data and keeping our services available are our top priorities, and we’ll contact you directly if anything changes or if you need to do something.
We’ll share further updates as the situation develops. If you have any questions, please contact our support team.

Thank you for your continued trust.
Oct 21, 14:34 CEST

Oct 21, 2026

Incident History Powered by Atlassian Statuspage