Is Mews down?

We have noticed degraded performance of the system, user may experience long loading times and timeouts. We are investigating. Thank you for your patience.

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.

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.

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.

This incident has been resolved. If you still have trouble logging in or notice slow performance, please contact our support team.

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.

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.

The issue has been identified and a fix is being implemented.

The Mews team identified the issue and is working on a resolution. Further updates will follow as we make progress.

Guest Messenger is working normally for all properties.

The issue is now fully resolved. Mews is now operating as expected.

The team has resolved the issue, and we are closely monitoring the system to ensure stability.

The issue is now fully resolved. Mews is now operating as expected.

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.

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).

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.

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.

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

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.

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.

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.

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.