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
Past Incidents
Oct 30, 2026
No incidents reported today.
Oct 29, 2026
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
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
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
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
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
We are investigating.
Thank you for your patience.
Oct 29, 16:39 CET
Oct 28, 2026
Resolved -
The issue is now fully resolved. Mews is now operating as expected.
Oct 28, 11:25 CET
Oct 28, 11:25 CET
Monitoring -
Guest Messenger is working normally for all properties.
Oct 28, 11:19 CET
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
Oct 28, 10:53 CET
Identified -
The issue has been identified and a fix is being implemented.
Oct 28, 10:28 CET
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
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 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
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, 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
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
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
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
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
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
Oct 22, 13:58 CEST
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
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
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
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
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
Oct 20, 2026
Resolved -
Between approximately 16:50 and 19:20 UTC, outgoing emails from Mews were delayed by up to 45 minutes. This affected all email types, including two-factor authentication and sign-in emails, booking confirmations, invoices, and guest communications. As a result, some users were unable to sign in to Mews during this period.
The cause was a progressive slowdown in the background service that processes the email queue. We restored full processing capacity at 19:20 UTC, after which the backlog of delayed emails was sent and delivery returned to normal. We have monitored the service since then and confirmed that it remains stable.
We apologize for the disruption.
Oct 20, 00:13 CEST
The cause was a progressive slowdown in the background service that processes the email queue. We restored full processing capacity at 19:20 UTC, after which the backlog of delayed emails was sent and delivery returned to normal. We have monitored the service since then and confirmed that it remains stable.
We apologize for the disruption.
Oct 20, 00:13 CEST
Monitoring -
Email delivery has recovered and has been running normally since approximately 21:20 CEST. The backlog of delayed emails has been sent.
The cause was a slowdown in the service that processes the email queue. We have restored full capacity and are monitoring closely to confirm it remains stable.
Oct 19, 21:40 CEST
The cause was a slowdown in the service that processes the email queue. We have restored full capacity and are monitoring closely to confirm it remains stable.
Oct 19, 21:40 CEST
Investigating -
We have noticed a downgraded performance of the system.
We are currently looking into it.
Thank you for your patience.
Oct 19, 21:00 CEST
We are currently looking into it.
Thank you for your patience.
Oct 19, 21:00 CEST
Oct 19, 2026
Resolved -
This issue is resolved. All accounting ledger data has been processed, and accounting ledgers are now up to date for all properties. All pending trial balances have been generated, and new ones are being generated without delay.
No data was lost. We apologise for the inconvenience and thank you for your patience.
Oct 19, 21:31 CEST
No data was lost. We apologise for the inconvenience and thank you for your patience.
Oct 19, 21:31 CEST
Identified -
We’re aware that accounting ledger data is being processed with a delay. Because of this, accounting ledgers may not show the latest transactions, and generated trial balances may take longer than usual to produce.
No data has been lost. All pending transactions will appear in the ledgers once processing catches up.
Our team is working on a fix, and we’ll post another update as soon as we have more information. We apologise for the inconvenience.
Oct 19, 11:10 CEST
No data has been lost. All pending transactions will appear in the ledgers once processing catches up.
Our team is working on a fix, and we’ll post another update as soon as we have more information. We apologise for the inconvenience.
Oct 19, 11:10 CEST
Oct 18, 2026
Resolved -
This issue is now resolved, some properties saw slow responses and errors in Mews when checking in guests or making changes to reservations. This included changing dates, adding products, cancelling and locking reservations. Some actions took around 30 seconds and then failed. Viewing reservations and checking out guests were not affected.
We are sorry for the disruption to your front desk. We’re reviewing what happened so we can catch this kind of issue sooner in future.
Oct 18, 06:39 CEST
We are sorry for the disruption to your front desk. We’re reviewing what happened so we can catch this kind of issue sooner in future.
Oct 18, 06:39 CEST
Identified -
The Mews team identified an issue with the chekcing flow in selected properties and we are working on a resolution. Further updates will follow as we make progress.
Oct 18, 05:23 CEST
Oct 18, 05:23 CEST
Oct 17, 2026
No incidents reported.
Oct 16, 2026
No incidents reported.