Mews Status

Identified: We identified an issue with a recently introduced feature in Rate Management that impacted override pricing. This caused incorrect VAT/Tax rates to be applied to items with overrides.

The feature has now been disabled, and we are deploying a fix to prevent any new reservations from being created with incorrect VAT/Tax rates.

We are also identifying existing reservations that were affected. Further updates will be shared here as we progress.

Resolved: We believe the impact from the issue is over.

Monitoring: We have redeployed a fix and we are closely monitoring the system.

Identified: We have noticed a regression with the deployed fix and are working on new release.

Monitoring: Mews support chat was facing an issue where it was inaccessible to most users. We've have implemented a solution and are currently monitoring.

Identified: We have identified the problem with opening up Mews support chat and are rolling out a solution. Expected in the next hour.

Investigating: We are currently experiencing an issue with our chat & chatbot support functionality. In case of critical incidents, do not hesitate to contact us over the phone - contact Mews through https://www.mews.com/en/contact-us

Investigating: We are currently experiencing an issue with our chat & chatbot support functionality. In case of critical incidents, do not hesitate to contact us over the phone - Contact Mews | Get in touch with us

Investigating: We are currently investigating reports of an issue affecting Mews Messaging. The Mews team is actively working to identify the cause, and we will provide updates as soon as possible.

Resolved: We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.

Monitoring: During a new feature rollout we spotted some performance issues related to that feature. We've rolled it back and are monitoring this closely

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

Investigating: We observe elevated amount of timeouts on Connector API as well. We are continuing with investigation.

Investigating: We have noticed a downgraded performance of the system. We are currently looking into it. Thank you for your patience.

Resolved: We are pleased to report that the service issue identified earlier today has been fully resolved. Our engineering team has been closely monitoring system performance for the past two hours, and all metrics have returned to normal levels.

All services are operating normally. We have seen no recurrence of the issue during our extended monitoring period.

We apologize for any inconvenience this may have caused and appreciate your patience as we worked to resolve this matter.

Thank you for your understanding.

Monitoring: We experienced an elevated error rate across the API and web application, resulting in widespread operation failures. The root cause was an expired certificate in an internal service. The issue has been resolved and all services are now fully restored. We apologize for any inconvenience this may have caused.

Identified: We're currently investigating an elevated level of API errors. Customers may experience issues when performing actions in the web app, making API calls, or completing reservations and other operations, which may be delayed. We've identified the root cause and are actively working on mitigation.

Resolved: We have successfully implemented a fix for all future reservations that were impacted. The issue has been resolved and all new reservations are functioning correctly.

Properties that were affected during the incident will receive direct communications from our team with detailed information about what occurred and any potential next steps that may be required.

If you have not received any communications from us, your property was not impacted by this incident and no action is required on your part.

We appreciate your patience while we worked to resolve this issue. If you have any questions or concerns, please don't hesitate to reach out to our support team.

Identified: We have released a fix so that all new reservations have their intended products included as defined by the product rules. The affected reservations are those that were created via either the Booking engine and the Guest portal between 24.09.2025 13:20 UTC till 25.09.2025 13:05 UTC. Simultaneously, we are working on fixing future reservations that were affected to ensure products are correctly assigned.

We recommend reviewing today’s reservations created within that the impacted timeframe, scheduled for check-in today as the check-in process re-applies all products and the price may differ from what the guest saw in their confirmation email.

We’ll share further updates soon with the next steps.

Identified: We are releasing a change to ensure that all new reservations correctly include products defined by product rules. At the same time, we are working on fixing reservations created since yesterday that are missing products.

We recommend reviewing today’s reservations scheduled for check-in, as the check-in process re-applies all products and the price may differ from what the guest saw in their confirmation email.

We’ll share further updates soon with the next steps.

Identified: We identified an issue introduced yesterday at 3 PM (GMT+2) affecting reservations with product rules. Products added by rules were not being included in reservations, except for those created through a Channel Manager.

We are actively working on a fix, which we expect to deliver within the next 2 hours. Once resolved, we will correct future reservations to ensure the missing products are properly included.

Identified: The Mews team identified the issue and is working on a resolution. We are working on it, we expect the situation to be fixed in ~2 hours.

We'll provide another update soon.

Investigating: We are currently investigating reports of an issue affecting Booking Engine and the reservations made through it. The Mews team is actively working to identify the cause, and we will provide updates as soon as possible.

Resolved: We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.

Monitoring: During a new feature rollout we spotted some performance issues related to that feature. We've rolled it back and are monitoring this closely

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

Investigating: We observe elevated amount of timeouts on Connector API as well. We are continuing with investigation.

Investigating: We have noticed a downgraded performance of the system. We are currently looking into it. Thank you for your patience.

Resolved: We are pleased to report that the service issue identified earlier today has been fully resolved. Our engineering team has been closely monitoring system performance for the past two hours, and all metrics have returned to normal levels.

All services are operating normally. We have seen no recurrence of the issue during our extended monitoring period.

We apologize for any inconvenience this may have caused and appreciate your patience as we worked to resolve this matter.

Thank you for your understanding.

Monitoring: We experienced an elevated error rate across the API and web application, resulting in widespread operation failures. The root cause was an expired certificate in an internal service. The issue has been resolved and all services are now fully restored. We apologize for any inconvenience this may have caused.

Identified: We're currently investigating an elevated level of API errors. Customers may experience issues when performing actions in the web app, making API calls, or completing reservations and other operations, which may be delayed. We've identified the root cause and are actively working on mitigation.