Is Mews down?

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

We're investigating the issue.

We've been able to resolve the cause of the incident. The app had around 10-second response time or was unresponsive for the end users. The system is functional, we are working on containing the root cause. More updates soon.

We have narrowed the problem to be related to a maintenance event performed by our cloud provider Microsoft Azure on our production database. We are cooperating with them to address the root cause.

We've been able to identify the cause the performance issues out to be an unplanned migration work on the side of our cloud provider, Microsoft Azure.

There were issues with the release of the Mews Connector for the properties using the Italian fiscal printer. Version 185 will is currently being released with the fix.

Mews Connector version 1.1.185 is being rolled out automatically or can be downloaded from this site: https://store.mews.li/Package/Connector/InstallMewsConnector/Data After installing the 1.1.185 version of the Mews Connector, the errored device commands for the Italian fiscal printer can be retried.

Version 1.1.185 of the Mews Connector solved the issue. If you are on Mews Connector version 1.1.183 or 1.1.184 please update to 1.1.185. Once updated please retry the printer device commands.

**Problem** On Tue, 01 Sep 2026 11:59:00 UTC, a new version of the Mews Connector \(v1.1.183\) introduced an issue that prevented receipt printing on Italian fiscal printers. Properties using these printers saw their fiscal device commands enter an error state, meaning receipts could not be reported to the fiscal printer. **Action** Our team detected the issue within minutes of the first errors appearing and immediately began investigating. We initially attempted to restore the previous working version, but further testing revealed the issue required a targeted fix rather than a rollback. A corrected version \(v1.1.185\) was built, tested, and released on Tue, 01 Sep 2026 15:38:00 UTC. The update rolled out automatically to connected Connector instances and was also made available for manual download. By Tue, 01 Sep 2026 17:24:29 UTC, the fix had reached over 95% of instances and the issue was confirmed resolved. Properties were advised to retry any device commands that had entered an error state once the update was installed. **Causes** A software dependency used by the Connector's fiscal printer module was resolved incorrectly during the build process, resulting in a version mismatch that caused the application to fail when attempting to communicate with Italian fiscal printers. This was a build-environment issue rather than a deliberate code change, which is why rebuilding the previous version's code did not resolve the problem. **Solutions** * Released Mews Connector v1.1.185, which resolved the dependency mismatch and restored normal fiscal printer operation. * Affected device commands could be retried after the update was installed — no data was lost. * We are pinning all software dependencies to specific versions to prevent build-environment drift from causing similar issues in the future. * We are adding additional pre-release validation steps that specifically test fiscal printer functionality before new Mews Connector versions are released. * In Q4 2026 we will replace the current on-premise Italian fiscal printer integration with a cloud-based Italian fiscal integration, removing this class of dependency issue for Italian properties.

Updates to availability, rates and restrictions sent from Mews to Booking.com began to be delayed. We traced the cause to slow and failing responses from Booking.com's rates and availability service, and we have contacted Booking.com. Properties with a Booking.com connection may see recent changes take longer than usual to appear.

The queue is clearing slowly, but updates are still being sent with some delay. We’re monitoring the system closely and keeping an eye on the processing times.

Booking.com's rates and availability service has recovered and delivery of pending updates is now progressing quickly. We expect all outstanding availability, rate and restriction updates to be delivered within the hour. Availability and rates on Booking.com will then match Mews. We are monitoring the connection.

Booking.com's rates and availability service has recovered and updates are being delivered normally. Waiting updates are still being processed and will be delivered over the next few hours.

Updates to availability, rates and restrictions sent from Mews to Booking.com began to be delayed at 14:00 CEST today. We traced the cause to slow and failing responses from Booking.com's rates and availability service, and we have contacted Booking.com. Properties with a Booking.com connection may see recent changes take longer than usual to appear.

The queue is clearing slowly, but updates are still being sent with some delay. We’re monitoring the system closely and keeping an eye on the processing times.

We are still monitoring the pending queue items, but updates are still being sent with some delay. We’re monitoring the system closely and keeping an eye on the processing times.

Booking.com's rates and availability service has recovered and delivery of pending updates is now progressing quickly. We expect all outstanding availability, rate and restriction updates to be delivered within the hour. Availability and rates on Booking.com will then match Mews. We are monitoring the connection.

Booking.com's rates and availability service has recovered and updates are being delivered normally. Waiting updates are still being processed and will be delivered over the next few hours.

We identified an issue causing check-in failures at a limited number of properties. The issue has been mitigated and check-ins are operating normally. We are monitoring the situation while we finalize a permanent fix.

This incident has been resolved.