Mews Outage History

Started Oct 21, 2026, 12:34 PM UTC· resolved Oct 21, 2026, 10:33 PM UTC

1. investigating Oct 21, 2026, 12:34 PM UTC

   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.

2. investigating Oct 21, 2026, 02:02 PM UTC

   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.

3. investigating Oct 21, 2026, 03:14 PM UTC

   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.

4. resolved Oct 21, 2026, 10:33 PM UTC

   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.

Read the full incident report →

Started Oct 19, 2026, 07:00 PM UTC· resolved Oct 19, 2026, 10:13 PM UTC

1. investigating Oct 19, 2026, 07:00 PM UTC

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

2. monitoring Oct 19, 2026, 07:40 PM UTC

   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.

3. resolved Oct 19, 2026, 10:13 PM UTC

   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.

Read the full incident report →

Started Oct 19, 2026, 09:10 AM UTC· resolved Oct 19, 2026, 07:31 PM UTC

1. identified Oct 19, 2026, 09:10 AM UTC

   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.

2. resolved Oct 19, 2026, 07:31 PM UTC

   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.

Read the full incident report →

Started Oct 18, 2026, 03:23 AM UTC· resolved Oct 18, 2026, 04:39 AM UTC

1. identified Oct 18, 2026, 03:23 AM UTC

   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.

2. resolved Oct 18, 2026, 04:39 AM UTC

   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.

Read the full incident report →

Started Oct 15, 2026, 12:03 PM UTC· resolved Oct 15, 2026, 06:51 PM UTC

1. identified Oct 15, 2026, 12:03 PM UTC

   Since around 11:30 UTC, new reservations, modifications and cancellations from Booking.com are not reaching Mews. This is caused by an outage of Booking.com’s Reservations API, which Booking.com has confirmed on their connectivity status page. Other channels and updates from Mews to Booking.com (availability, rates and restrictions) are not affected. Reservations are not lost. Booking.com will resend them once their service recovers, and they will be created in Mews automatically. Until then, please check the Booking.com Extranet for new bookings to avoid overbookings. We’ll post an update when Booking.com restores service.

2. identified Oct 15, 2026, 01:10 PM UTC

   Booking.com has reported a fix for their Reservations API, but we are not yet receiving Booking.com reservations reliably. Some reservations came through between 12:45 and 12:50 UTC, but most new, modified and cancelled bookings made since 11:15 UTC are still delayed. Reservations are not lost. They will be created in Mews automatically as soon as the connection is stable again. Until then, please continue to check the Booking.com Extranet for new bookings to avoid overbookings. We’re monitoring closely and will post another update within 30 minutes.

3. identified Oct 15, 2026, 02:14 PM UTC

   Booking.com is still experiencing an outage of their Reservations API. Since around 11:15 UTC, most new, modified and cancelled Booking.com reservations have not reached Mews; only small batches have come through intermittently. Other channels are not affected. Reservations are not lost. They will be created in Mews automatically once Booking.com’s service is stable. Until then, please check the Booking.com Extranet for new bookings and manage availability manually where needed to avoid overbookings. We are in contact with Booking.com and will post another update within 60 minutes.

4. identified Oct 15, 2026, 03:14 PM UTC

   Identified: Booking.com’s Reservations API is still experiencing an outage. Since around 11:15 UTC, most new, modified and cancelled Booking.com reservations have not reached Mews, and none have arrived since 13:42 UTC. Booking.com is working on a fix, but they have not given an estimated resolution time. Other channels are not affected. Reservations are not lost. They will be created in Mews automatically once Booking.com’s service is stable. Until then, please keep checking the Booking.com Extranet for new bookings and manage availability manually where needed to avoid overbookings. We’ll post another update within 60 minutes, or sooner if the situation changes.

5. monitoring Oct 15, 2026, 06:10 PM UTC

   Booking.com reservations have started reaching Mews again. Reservations delayed since around 11:15 UTC are now being delivered and created in Mews automatically. This may take some time to complete. Booking.com’s service is not yet fully stable, so some further delays are still possible. Please continue to check the Booking.com Extranet for recent bookings until this incident is resolved. We’ll post another update within 60 minutes.

6. resolved Oct 15, 2026, 06:51 PM UTC

   All Booking.com reservations delayed between 11:15 UTC and 17:55 UTC have been delivered to Mews, and the connection is operating normally. If you still notice a missing Booking.com reservation, please compare with the Booking.com Extranet and contact Mews Support.

Read the full incident report →

Started Oct 09, 2026, 11:37 AM UTC· resolved Oct 09, 2026, 01:47 PM UTC

1. identified Oct 09, 2026, 11:37 AM UTC

   Customers in Italy can’t add a tax deducted payment to invoices in the new Billing screen. We’ve identified the cause and are preparing a fix. Workaround: on the burger button (the 3 dots in the billing screen) Switch to the old Billing page to close bills until the fix is live. We’ll post another update once the fix is deployed.

2. resolved Oct 09, 2026, 01:47 PM UTC

   The issue is now fully resolved. Mews is now operating as expected. Affected customers will be contacted with the process to fix affected invoices.

Read the full incident report →

Started Oct 08, 2026, 02:17 PM UTC· resolved Oct 08, 2026, 03:43 PM UTC

1. investigating Oct 08, 2026, 02:17 PM UTC

   They availability, price and restriction updates to channel managers are delayed. We are investigating the root cause.

2. monitoring Oct 08, 2026, 02:36 PM UTC

   We have identified problem of delay. The accumulated updates that caused slowing down the updates were removed. All the slowed updates will get processed soon. We are monitoring the recovery.

3. resolved Oct 08, 2026, 03:43 PM UTC

   Delayed updates were successfully synchronized to channel managers.

Read the full incident report →

Started Oct 06, 2026, 01:04 PM UTC· resolved Oct 06, 2026, 03:17 PM UTC

1. investigating Oct 06, 2026, 01:04 PM UTC

   Since about 09:55 UTC, some reservations from Choice EDGE CRS and SynXis are not showing up in Mews. This happens when a reservation includes a new loyalty membership. We found the cause and our engineers are fixing it. Please check your channel or CRS for missing bookings. We will post an update when it is fixed.

2. investigating Oct 06, 2026, 01:40 PM UTC

   Since around 09:55 UTC on October 6, some reservations for guests enrolling as new loyalty members at Strawberry hotels have not appeared in Mews; reservations that do not create a new membership are processing normally. We’re working on a fix, and affected properties should check their booking channels for missing reservations and any failure notifications.

3. resolved Oct 06, 2026, 03:17 PM UTC

   Between approximately 09:55 and 14:29 UTC on October 6, some reservations requiring a new loyalty membership failed to appear in Mews. This affected 62 properties. The issue is fixed and the bookings have been reprocessed. Please check your booking channels for any reservations still missing from Mews.

Read the full incident report →

Started Oct 05, 2026, 03:35 PM UTC· resolved Oct 05, 2026, 04:26 PM UTC

1. identified Oct 05, 2026, 03:35 PM UTC

   We're aware of a subset of Flexkeeping Customers who are experiencing issues accessing the Flexkeeping website. The team have identified the issue are are deploying a hot-fix presently.

2. monitoring Oct 05, 2026, 04:16 PM UTC

   A fix has been deployed to production and service should be restored. The team are monitoring recovery. No data loss was incurred.

3. resolved Oct 05, 2026, 04:26 PM UTC

   System access is restored.

Read the full incident report →

Started Oct 05, 2026, 03:12 PM UTC· resolved Oct 05, 2026, 07:00 PM UTC

1. investigating Oct 05, 2026, 03:12 PM UTC

   We're aware that availability, rate and restriction updates from Mews to some distribution channels are being delayed for a subset of properties. Reservations from channels into Mews are not affected. Affected properties may see updates reach their channels later than usual. Updates are not lost and will be delivered once processing catches up.

2. identified Oct 05, 2026, 04:23 PM UTC

   We've identified the cause of the delayed availability, rate and restriction updates to some distribution channels. An unusually high volume of updates from a single connected system was slowing the processing queue for a subset of properties. The inventory queue is now recovering and delays are reducing. Affected properties will see their updates reach their channels as the backlog clears. Updates are not lost. We're monitoring closely and will post again once processing is back to normal.

3. identified Oct 05, 2026, 04:51 PM UTC

   Reservation processing and inventory synchronization between Mews and distribution channels are currently not progressing. New reservations may not appear in Mews, and availability, rate and restriction updates may not reach channels. Nothing is lost, everything is queued and will be processed once the issue is resolved

4. identified Oct 05, 2026, 05:24 PM UTC

   Reservation processing was delayed by up to 40 minutes and is now fully operational. All delayed reservations have been processed. Inventory synchronization (availability, rate and restriction updates to channels) is still slower than usual, and some properties may see delays.

5. resolved Oct 05, 2026, 07:00 PM UTC

   Reservation processing and inventory synchronization between Mews and distribution channels are now fully operational. All delayed updates have been processed.

Read the full incident report →

Started Oct 02, 2026, 01:14 PM UTC· resolved Oct 02, 2026, 01:41 PM UTC

1. resolved Oct 08, 2026, 08:04 AM UTC

   On 2 October 2026 between 15:14 and 15:41 CEST, Mews POS was slow or unavailable for all customers. Customers could not log in to POS or complete transactions. Our team identified the cause and reversed a configuration change within 20 minutes of the first alert. Service was fully restored at 15:41 CEST, and operations returned to normal shortly after.

2. postmortem Oct 08, 2026, 08:05 AM UTC

   **Problem** On 2 October 2026 at 15:14 CEST, POS became slow or unavailable for all customers for approximately 27 minutes. Customers could not log in or complete transactions. **Action** The team identified the cause and reversed a configuration change within 20 minutes of the first alert. Service was fully restored by 15:41 CEST, and operations returned to normal shortly after. **Causes** An unexpected increase in incoming payment notifications put excessive load on the POS database, which slowed down and then interrupted the service. **Solutions** The configuration change was immediately reversed to stop the notification flood. We are now improving the notification handler to filter out irrelevant messages before re-enabling the feature, with a staged rollout plan that includes database monitoring at each step.

Read the full incident report →

Started Oct 02, 2026, 12:48 PM UTC· resolved Oct 04, 2026, 06:22 PM UTC

1. investigating Oct 02, 2026, 12:48 PM UTC

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

2. resolved Oct 04, 2026, 06:22 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 02, 2026, 07:05 AM UTC· resolved Oct 02, 2026, 07:22 AM UTC

1. investigating Oct 02, 2026, 07:05 AM UTC

   We are currently investigating issues with provisioning new accounts for the Guest Messenger

2. resolved Oct 02, 2026, 07:22 AM UTC

   The new accounts were provisioned and the functionality is working.

Read the full incident report →

Started Sep 29, 2026, 03:02 PM UTC· resolved Sep 30, 2026, 08:06 AM UTC

1. monitoring Sep 29, 2026, 03:02 PM UTC

   We are aware of an issue affecting AI tooling. The cause is an outage at our AI provider and an Azure outage in the Sweden region. AI-powered features may be slow, return errors, or be unavailable. Core Mews functionality is not affected.

2. resolved Sep 30, 2026, 08:06 AM UTC

   The impact from the issue is over as of Tuesday 29th 8PM utc

3. postmortem Oct 07, 2026, 08:10 AM UTC

   **Problem** On 2026-09-29T14:30:06Z, AI-powered features in Mews — including AI guest messaging, AI property guidelines, and smart task suggestions — became intermittently unavailable or degraded. This was caused by an outage affecting Azure OpenAI and Azure AI Foundry services in the Sweden Central region, combined with a concurrent degradation of Anthropic's Claude service. Core Mews functionality was not affected. **Action** Our team detected the issue promptly and confirmed that AI features were unavailable due to the upstream outage. We published a status page update to inform customers, monitored the situation throughout the afternoon, and confirmed full recovery on 2026-09-29T19:06:00Z once Azure services returned to normal. **Causes** The outage was caused by infrastructure issues at Microsoft Azure affecting their OpenAI and AI Foundry services in the Sweden Central region. Azure reported that a backend service responsible for managing request metadata experienced timeouts when reading from dependent database and caching layers, resulting in intermittent failures and increased latency for customers in that region. Anthropic's Claude service also experienced concurrent degradation. **Solutions** The issue was resolved by Microsoft Azure restoring normal operations in the Sweden Central region. On our side, we are working on adding in-product indicators so customers are clearly informed when AI-powered features are temporarily unavailable, and we are reviewing our integration points to ensure features recover automatically once upstream services are restored.

Read the full incident report →

Started Sep 28, 2026, 04:06 PM UTC· resolved Sep 28, 2026, 05:52 PM UTC

1. identified Sep 28, 2026, 04:06 PM UTC

   The Mews team identified the issue and is working on a resolution. This issue affects most of the properties in Morocco region. It prevents users from creating new reservation and modifying them. To prevent this from happening use different browser that is not updated like edge/chrome.

2. resolved Sep 28, 2026, 05:52 PM UTC

   A fix has been deployed for the issues affecting reservation creation and modification for properties in the Morocco region. The issue should now be resolved and normal functionality restored. No further actions required as a result of the fix.

3. postmortem Oct 08, 2026, 04:08 PM UTC

   # Moroccan properties unable to create reservations \(28 September 2026\) ## What happened On 28 September 2026, for about four hours, staff at most of our properties in Morocco, and guests booking online with them, saw errors when creating or changing reservations. Pricing and availability could not be loaded, so new bookings could not be completed. ## Why it happened Morocco moved to a permanent UTC\+0 time zone on 20 September 2026. Web browsers and devices received this change at different times, but the time zone data used by our servers was not updated. The two disagreed about when each day starts, so our system rejected the requests. ## What we did Once the issue was reported, our engineering team identified the cause within about an hour and prepared a targeted fix. It was live by 17:37 UTC and verified in production by 17:58 UTC. Reservations, pricing and availability have worked normally since then. Reservation times created during the affected period may display one hour off in some views. Our support team can help with any questions. ## What we're doing to prevent it * Upgrading our time zone database to the current version, which already includes Morocco's change. * Monitoring for this type of error, so we catch it within a day. * Tracking upcoming time zone rule changes in the countries where our customers operate. We apologise for the disruption this caused to you and your guests.

Read the full incident report →

Started Sep 25, 2026, 10:59 AM UTC· resolved Sep 30, 2026, 12:43 PM UTC

1. investigating Sep 25, 2026, 10:59 AM UTC

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

2. monitoring Sep 25, 2026, 12:10 PM UTC

   We see that the performance of the platform across all connections is back to normal. We will keep monitoring the incident.

3. monitoring Sep 25, 2026, 02:13 PM UTC

   We have identified the source of the degraded performance and applied a mitigation that isolates it from the rest of the system. The system should now be responding normally. Some users may still experience slowness when generating the Manager Report. We continue to investigate and monitor the situation.

4. monitoring Sep 25, 2026, 02:53 PM UTC

   The system continues to operate normally, and we are monitoring it closely. Some reports may occasionally load slowly or fail to load while we work on a permanent fix.

5. identified Sep 28, 2026, 04:03 PM UTC

   The Mews team identified the issue and is working on a resolution. This issue affects most of the properties in Morocco region. It prevents users from creating new reservation and modifying them. To prevent this from happening use different browser that is not updated like edge/chrome.

6. monitoring Sep 29, 2026, 08:28 AM UTC

   The problematic reports remain isolated to a separate component, reducing their impact on the rest of the system. The platform is operating normally, and we continue to monitor the situation while working on a permanent solution.

7. resolved Sep 30, 2026, 12:43 PM UTC

   The issue causing slowness and timeouts in Mews, which began on September 25, has been resolved. All affected properties can now work normally.

Read the full incident report →

Started Sep 20, 2026, 05:28 AM UTC· resolved Sep 20, 2026, 10:41 AM UTC

1. identified Sep 20, 2026, 05:28 AM UTC

   Properties connected to SynXis (Sabre) are currently affected. Since approximately 04:20 UTC, availability, rate and restriction updates are not reaching SynXis. The cause is an outage on the SynXis side, their service is currently rejecting our requests. We are in contact with Sabre. Queued updates will retry automatically once SynXis is reachable. Properties not connected to SynXis are unaffected. Next update within 60 minutes.

2. identified Sep 20, 2026, 06:34 AM UTC

   Properties connected to SynXis (Sabre) remain affected. The scope is broader than our previous update stated. Since approximately 04:20 UTC: - Availability, rate and restriction updates are not reaching SynXis. - New reservations from SynXis are not reaching Mews. - Reservation updates are not synchronising back to SynXis. SynXis is still rejecting our requests. Error levels have fallen from their peak but have been stable for the past hour, and we have not yet seen any recovery. We remain in contact with Sabre. Correcting our earlier update: not all queued updates will resend on their own. A portion have exceeded their automatic retry limit during the outage. We have identified these and will reprocess them ourselves once SynXis is reachable — no action is required from you. If you use SynXis, please continue to treat your channel data as out of date and check SynXis directly for new bookings. Next update within 60 minutes.

3. identified Sep 20, 2026, 08:20 AM UTC

   Properties connected to SynXis (Sabre) remain affected. There is no change to the impact described in our previous update, and we have not yet seen recovery. SynXis continues to reject our requests. Error levels have not improved over the past two hours. We are still in contact with Sabre and do not have an estimated time to resolution from them. The volume of updates requiring manual reprocessing continues to grow while the outage is ongoing. This means full resynchronisation will take some time after SynXis becomes reachable again — availability, rates and restrictions will not all be correct the moment their service returns. We will confirm here when resynchronisation is complete. If you use SynXis, please continue to treat your channel data as out of date and check SynXis directly for new bookings. Next update within 60 minutes.

4. identified Sep 20, 2026, 09:20 AM UTC

   SynXis has begun responding again as of approximately 08:40 UTC, and queued updates are now processing. Availability, rate and restriction updates, and reservation synchronisation, are flowing again. We are now working through the backlog. Updates that exceeded their automatic retry limit during the outage are being reprocessed by us — this is in progress and will take some time. Your channel data may remain out of date until it completes. We will confirm here once reprocessing is finished and data is fully resynchronised. Next update within 60 minutes.

5. identified Sep 20, 2026, 09:21 AM UTC

   We are seeing elevated errors on connections to BWH | Best Western CRS since approximately 06:00 UTC. Updates are still being processed, but a portion are failing and retrying, so some changes may be delayed reaching the channel. This is unrelated to the SynXis incident. We are investigating. Next update within 60 minutes.

6. monitoring Sep 20, 2026, 10:03 AM UTC

   SynXis has fully recovered and reprocessing is complete. All updates that exceeded their retry limit during the outage have been reprocessed — availability, rates, restrictions and reservations are resynchronised for SynXis-connected properties. No further action is needed. BWH | Best Western CRS has confirmed an unplanned outage on their side, caused by scheduled maintenance overrunning its window. We have been seeing normal error levels on BWH connections since approximately 09:10 UTC and updates are processing again. We are monitoring and awaiting their confirmation that the outage is fully resolved. Next update within 60 minutes, or sooner if anything changes.

7. resolved Sep 20, 2026, 10:41 AM UTC

   This incident is resolved. SynXis (Sabre) was unavailable between approximately 04:20 and 08:40 UTC. BWH | Best Western CRS experienced a separate unplanned outage on their side, caused by maintenance overrunning its window, between approximately 06:00 and 09:10 UTC. Both connections have been operating normally since. All updates affected during both outages — availability, rates, restrictions, and reservations — have been reprocessed and resynchronised. No action is required from you.

Read the full incident report →

Started Sep 16, 2026, 09:14 AM UTC· resolved Sep 17, 2026, 12:31 PM UTC

1. investigating Sep 16, 2026, 09:14 AM UTC

   We are currently experiencing intermittent disruptions to our live chat service due to an issue with a third party system provider. This is affecting agent availability for chat support. While this is being resolved, please submit your query as a case instead of live chat, so our team can respond as soon as possible. We will update this page once the issue is resolved.

2. identified Sep 16, 2026, 09:48 AM UTC

   Salesforce, our case management system provider, is experiencing a service disruption affecting multiple regions. This is causing severe delays, intermittent errors, and inability to access some services, including live chat and support case creation. Salesforce has identified the cause as an internal login service issue and is working on a fix, including a rolling restart on one of the affected instances. You can find more details here >> https://status.salesforce.com/incidents/20004433 << While this is ongoing, please expect delays if you submit a case, and live chat agents may be temporarily unavailable. We will update this page as soon as we have more information.

3. resolved Sep 17, 2026, 12:31 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 01, 2026, 03:38 PM UTC· resolved Sep 01, 2026, 05:14 PM UTC

1. monitoring Sep 01, 2026, 03:52 PM UTC

   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.

2. monitoring Sep 01, 2026, 04:26 PM UTC

   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.

3. resolved Sep 01, 2026, 05:14 PM UTC

   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.

4. postmortem Sep 10, 2026, 12:47 PM UTC

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

Read the full incident report →

Started Aug 23, 2026, 04:24 AM UTC· resolved Aug 23, 2026, 10:05 AM UTC

1. identified Aug 23, 2026, 04:24 AM UTC

   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.

2. monitoring Aug 23, 2026, 06:19 AM UTC

   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.

3. monitoring Aug 23, 2026, 07:53 AM UTC

   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.

4. resolved Aug 23, 2026, 10:05 AM UTC

   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.

Read the full incident report →

Started Aug 21, 2026, 01:50 PM UTC· resolved Aug 21, 2026, 03:50 PM UTC

1. monitoring Aug 21, 2026, 01:50 PM UTC

   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.

2. resolved Aug 21, 2026, 03:50 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 18, 2026, 11:58 AM UTC· resolved Aug 18, 2026, 01:29 PM UTC

1. identified Aug 18, 2026, 11:58 AM UTC

   Our data processing infrastructure is running behind which is delaying fresh data for Mews Business Intelligence. No data has been lost.

2. resolved Aug 18, 2026, 01:29 PM UTC

   Our data processing infrastructure is now fully operational. No data has been lost and the data within Mews Business Intelligence is now refreshed.

Read the full incident report →

Started Aug 11, 2026, 03:45 PM UTC· resolved Aug 11, 2026, 07:04 PM UTC

1. investigating Aug 11, 2026, 03:45 PM UTC

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

2. identified Aug 11, 2026, 04:12 PM UTC

   The Mews team identified a minor visual issue affecting Atomize customers and is working on a resolution. Further updates will follow as we make progress.

3. resolved Aug 11, 2026, 07:04 PM UTC

   The issue has been resolved.

Read the full incident report →

Started Aug 08, 2026, 02:23 PM UTC· resolved Aug 08, 2026, 10:09 PM UTC

1. investigating Aug 08, 2026, 02:23 PM UTC

   We are currently investigating reports of an issue affecting verification email. The Mews team is actively working to identify the cause, and we will provide updates as soon as possible. Emails delivery can be delayed up to 40 minutes.

2. monitoring Aug 08, 2026, 02:31 PM UTC

   We are again sending the authentication verification emails in a timely manner. We keep monitoring the situation.

3. resolved Aug 08, 2026, 10:09 PM UTC

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

Read the full incident report →

Started Aug 01, 2026, 06:47 AM UTC· resolved Aug 01, 2026, 09:05 AM UTC

1. investigating Aug 01, 2026, 06:47 AM UTC

   Austria — bills cannot be closed for some properties We are investigating an issue affecting some properties in Austria where bills cannot be closed. The issue is related to the fiscal registry integration and does not affect reservations, payments, or any other part of the system. Affected properties will see an error when attempting to close a bill. We are working to identify the full scope of impact and will post an update shortly.

2. monitoring Aug 01, 2026, 07:57 AM UTC

   We identified an issue affecting some properties in Austria that prevented bills from being closed. The issue has been resolved, and we are closely monitoring the system to ensure continued stability. We apologize for any inconvenience this may have caused.

3. resolved Aug 01, 2026, 09:05 AM UTC

   Between 00:00 and 09:15 CEST on 1 August, properties in Austria were unable to close bills and check out guests due to an issue with the Austrian fiscal registry integration. The issue has been identified and resolved, and bill closing and check-outs are working normally again. No data was lost, and any bills affected during this period can now be closed as usual — no further action is needed. We apologize for the disruption this caused during morning check-outs.

4. postmortem Aug 07, 2026, 01:13 PM UTC

   **Problem** On 1 August 2026 at 00:00 Central European Summer Time, properties in Austria using the Chaining fiscal registry integration could not close bills or complete guest check-outs. Affected properties saw the message "Cannot close bills because of fiscal registry constraints" when closing any bill that included a cash or card payment. The issue affected at least 181 properties and blocked 1,621 bills. **Action** Austrian properties and our Support team raised the issue at 07:49 Central European Summer Time. We identified the cause and applied a fix at 10:00 Central European Summer Time, which immediately restored bill closing and guest check-outs. **Causes** A background process prepares the monthly fiscal records that Austrian properties need in order to close bills. One property's account status changed twice, from active to deactivated and back again, and this left that property's fiscal records incomplete. The process handled every Austrian property in a single batch, so this one property stopped it from preparing records for all the others. The failure became visible at the start of August, when properties needed the new month's records. **Solutions** We restored fiscal record generation for all active Austrian properties at 10:00 Central European Summer Time and confirmed full recovery at 11:01 Central European Summer Time. The system is fully operational, properties can now close every bill affected during the incident, and we did not lose any data. We are adding dedicated monitoring and alerting to this process, introducing health checks at each month boundary, and redesigning it so one property can no longer block the others. We know that blocked check-outs during the morning departure wave put front desks under real pressure, and we are sorry for the disruption this caused you and your guests.

Read the full incident report →