Oct <var data-var='date'> 9</var>, <var data-var='time'>15:47</var> CEST Resolved - The issue is now fully resolved. Mews is now operating as expected. Affected customers will be contacted with the process to fix affected invoices. Oct <var data-var='date'> 9</var>, <var data-var='time'>13:37</var> CEST Identified - 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.

Italy: unable to add tax deducted payment in the new Billing screen

Oct <var data-var='date'> 8</var>, <var data-var='time'>17:43</var> CEST Resolved - Delayed updates were successfully synchronized to channel managers. Oct <var data-var='date'> 8</var>, <var data-var='time'>16:36</var> CEST Monitoring - 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. Oct <var data-var='date'> 8</var>, <var data-var='time'>16:17</var> CEST Investigating - They availability, price and restriction updates to channel managers are delayed. We are investigating the root cause.

Updates to channel managers are delayed.

Oct <var data-var='date'> 6</var>, <var data-var='time'>17:17</var> CEST Resolved - 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. Oct <var data-var='date'> 6</var>, <var data-var='time'>15:40</var> CEST Update - 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. Oct <var data-var='date'> 6</var>, <var data-var='time'>15:04</var> CEST Investigating - 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.

Some channel reservations with loyalty memberships are not being created

Oct <var data-var='date'> 5</var>, <var data-var='time'>21:00</var> CEST Resolved - Reservation processing and inventory synchronization between Mews and distribution channels are now fully operational. All delayed updates have been processed. Oct <var data-var='date'> 5</var>, <var data-var='time'>19:24</var> CEST Update - 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. Oct <var data-var='date'> 5</var>, <var data-var='time'>18:51</var> CEST Update - 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 Oct <var data-var='date'> 5</var>, <var data-var='time'>18:23</var> CEST Identified - 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. Oct <var data-var='date'> 5</var>, <var data-var='time'>17:12</var> CEST Investigating - 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.

Delays in reservations and channel updates

Oct <var data-var='date'> 5</var>, <var data-var='time'>18:26</var> CEST Resolved - System access is restored. Oct <var data-var='date'> 5</var>, <var data-var='time'>18:16</var> CEST Monitoring - A fix has been deployed to production and service should be restored. The team are monitoring recovery. No data loss was incurred. Oct <var data-var='date'> 5</var>, <var data-var='time'>17:35</var> CEST Identified - 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.

Errors accessing Flexkeeping

Oct <var data-var='date'> 4</var>, <var data-var='time'>20:22</var> CEST Resolved - This incident has been resolved. Oct <var data-var='date'> 2</var>, <var data-var='time'>14:48</var> CEST Investigating - We have noticed a downgraded performance of the system. We are currently looking into it. Thank you for your patience.

Downgraded Performance - Connector API - kiosks, printers, integrations are affected

Oct <var data-var='date'> 2</var>, <var data-var='time'>15:30</var> CEST Resolved - 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.

Mews POS unavailable

Oct <var data-var='date'> 2</var>, <var data-var='time'>09:22</var> CEST Resolved - The new accounts were provisioned and the functionality is working. Oct <var data-var='date'> 2</var>, <var data-var='time'>09:05</var> CEST Investigating - We are currently investigating issues with provisioning new accounts for the Guest Messenger

Investigating issues with the provisioning of the Guest Messenger

Sep <var data-var='date'>30</var>, <var data-var='time'>14:43</var> CEST Resolved - The issue causing slowness and timeouts in Mews, which began on September 25, has been resolved. All affected properties can now work normally. Sep <var data-var='date'>29</var>, <var data-var='time'>10:28</var> CEST Monitoring - 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. Sep <var data-var='date'>28</var>, <var data-var='time'>18:03</var> CEST Identified - 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. NOTE: this update was intended for a separate incident https://status.mews.com/incidents/jsp79g3qvh42 and was posted here by accident. Apologies for any confusion. Sep <var data-var='date'>25</var>, <var data-var='time'>16:53</var> CEST Update - 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. Sep <var data-var='date'>25</var>, <var data-var='time'>16:13</var> CEST Update - 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. Sep <var data-var='date'>25</var>, <var data-var='time'>14:10</var> CEST Monitoring - We see that the performance of the platform across all connections is back to normal. We will keep monitoring the incident. Sep <var data-var='date'>25</var>, <var data-var='time'>12:59</var> CEST Investigating - We have noticed a downgraded performance of the system. We are currently looking into it. Thank you for your patience.

Downgraded Performance

Sep <var data-var='date'>30</var>, <var data-var='time'>10:06</var> CEST Resolved - The impact from the issue is over as of Tuesday 29th 8PM utc Sep <var data-var='date'>29</var>, <var data-var='time'>17:02</var> CEST Monitoring - 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.

AI tooling degraded due to Claude and Azure Foundry outage

Sep <var data-var='date'>28</var>, <var data-var='time'>19:52</var> CEST Resolved - 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. Sep <var data-var='date'>28</var>, <var data-var='time'>18:06</var> CEST Identified - 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.

Reservation creation issues in Morocco

Sep <var data-var='date'>20</var>, <var data-var='time'>12:41</var> CEST Resolved - 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. Sep <var data-var='date'>20</var>, <var data-var='time'>12:03</var> CEST Monitoring - 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. Sep <var data-var='date'>20</var>, <var data-var='time'>11:21</var> CEST Update - 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. Sep <var data-var='date'>20</var>, <var data-var='time'>11:20</var> CEST Update - 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. Sep <var data-var='date'>20</var>, <var data-var='time'>10:20</var> CEST Update - 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. Sep <var data-var='date'>20</var>, <var data-var='time'>08:34</var> CEST Update - 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. Sep <var data-var='date'>20</var>, <var data-var='time'>07:28</var> CEST Identified - 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.

Synxis & BestWestern Outage

Sep <var data-var='date'>17</var>, <var data-var='time'>14:31</var> CEST Resolved - This incident has been resolved. Sep <var data-var='date'>16</var>, <var data-var='time'>11:48</var> CEST Identified - 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. Sep <var data-var='date'>16</var>, <var data-var='time'>11:14</var> CEST Investigating - 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.

Live Chat Disruption

Sep <var data-var='date'> 9</var>, <var data-var='time'>22:54</var> CEST Resolved - 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. Sep <var data-var='date'> 9</var>, <var data-var='time'>22:19</var> CEST Update - 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. Sep <var data-var='date'> 9</var>, <var data-var='time'>21:42</var> CEST Update - 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. Sep <var data-var='date'> 9</var>, <var data-var='time'>21:38</var> CEST Monitoring - We're investigating the issue. Sep <var data-var='date'> 9</var>, <var data-var='time'>21:30</var> CEST Investigating - We have noticed a downgraded performance of the system. We are currently looking into it. Thank you for your patience.

Sep <var data-var='date'> 1</var>, <var data-var='time'>19:14</var> CEST Resolved - 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. Sep <var data-var='date'> 1</var>, <var data-var='time'>18:26</var> CEST Update - Mews Connector version 1.1.185, which includes the fix, is being rolled out automatically. It can also be downloaded and installed manually. https://store.mews.li/Package/Connector/InstallMewsConnector/Data After updating, properties can retry any Italian fiscal printer device commands that are in an Error state. Sep <var data-var='date'> 1</var>, <var data-var='time'>17:38</var> CEST Monitoring - We identified an issue in Mews Connector versions 1.1.183 and 1.1.184 that caused device commands sent to Italian fiscal printers to fail. A fix is currently being released in Mews Connector version 1.1.185. Apologies for the inconvenience.

Italian Fiscal Printer Commands Failing in Mews Connector (Windows)

Aug <var data-var='date'>23</var>, <var data-var='time'>12:05</var> CEST Resolved - 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. Aug <var data-var='date'>23</var>, <var data-var='time'>09:53</var> CEST Update - 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. Aug <var data-var='date'>23</var>, <var data-var='time'>08:19</var> CEST Monitoring - 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. Aug <var data-var='date'>23</var>, <var data-var='time'>06:24</var> CEST Identified - 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.

Delays sending availability and rate updates to Booking.com

Aug <var data-var='date'>22</var>, <var data-var='time'>23:45</var> CEST Resolved - 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. Aug <var data-var='date'>22</var>, <var data-var='time'>22:36</var> CEST Update - 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. Aug <var data-var='date'>22</var>, <var data-var='time'>21:41</var> CEST Update - 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. Aug <var data-var='date'>22</var>, <var data-var='time'>20:27</var> CEST Monitoring - 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. Aug <var data-var='date'>22</var>, <var data-var='time'>19:18</var> CEST Identified - 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.

Aug <var data-var='date'>21</var>, <var data-var='time'>17:50</var> CEST Resolved - This incident has been resolved. Aug <var data-var='date'>21</var>, <var data-var='time'>15:50</var> CEST Monitoring - 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.

Check-in failures at a limited number of properties

Aug <var data-var='date'>18</var>, <var data-var='time'>15:29</var> CEST Resolved - Our data processing infrastructure is now fully operational. No data has been lost and the data within Mews Business Intelligence is now refreshed. Aug <var data-var='date'>18</var>, <var data-var='time'>13:58</var> CEST Identified - Our data processing infrastructure is running behind which is delaying fresh data for Mews Business Intelligence. No data has been lost.

Data Processing Delays - Mews Business Intelligence Affected

Aug <var data-var='date'>11</var>, <var data-var='time'>21:04</var> CEST Resolved - The issue has been resolved. Aug <var data-var='date'>11</var>, <var data-var='time'>18:12</var> CEST Identified - 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. Aug <var data-var='date'>11</var>, <var data-var='time'>17:45</var> CEST Investigating - 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.

Investigating issues with Mews RMS and Atomize

Aug <var data-var='date'> 9</var>, <var data-var='time'>00:09</var> CEST Resolved - The issue is now fully resolved. Mews is now operating as expected. Aug <var data-var='date'> 8</var>, <var data-var='time'>16:31</var> CEST Monitoring - We are again sending the authentication verification emails in a timely manner. We keep monitoring the situation. Aug <var data-var='date'> 8</var>, <var data-var='time'>16:23</var> CEST Investigating - 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.

Investigating issues causing delayed verification emails

Aug <var data-var='date'> 1</var>, <var data-var='time'>11:05</var> CEST Resolved - 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. Aug <var data-var='date'> 1</var>, <var data-var='time'>09:57</var> CEST Monitoring - 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. Aug <var data-var='date'> 1</var>, <var data-var='time'>08:47</var> CEST Investigating - 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.

Bill closing and check-out issues for properties in Austria using the Chaining fiscal registry integration

Jul <var data-var='date'>24</var>, <var data-var='time'>10:37</var> CEST Resolved - Identity document scanning has been fully operational since 16:35 UTC. Between 10:53 and 16:35 UTC on 23 July, roughly half of document scan attempts in guest profiles failed due to rate limiting at the third-party service that processes document images. Retrying a scan or entering document details manually worked throughout the incident, and no data was lost. We apologize for the disruption and are taking steps to prevent a recurrence. Jul <var data-var='date'>23</var>, <var data-var='time'>15:58</var> CEST Update - Since 23 July, 10:53 UTC, scanning identity documents in guest profiles is failing intermittentlyl roughly half of scan attempts return an error. This is caused by rate limiting at the third-party service that processes document images; we have confirmed the issue is not related to any Mews release and are working on restoring full service. Workaround: retrying the scan usually succeeds after one or two attempts. Jul <var data-var='date'>23</var>, <var data-var='time'>14:33</var> CEST Investigating - We are currently investigating reports of an Mews identity scanner malfunction. The Mews team is actively working to identify the cause, and we will provide updates as soon as possible.

Identity document scanning in Mews Operations is failing intermittently

Jul <var data-var='date'>17</var>, <var data-var='time'>04:53</var> CEST Resolved - All updates were successfully processed. Jul <var data-var='date'>17</var>, <var data-var='time'>04:49</var> CEST Monitoring - Inventory processor stopped working. After restarting all the updates are being processed. No updates were missed, just delayed. We are monitoring the data recovery. Jul <var data-var='date'>17</var>, <var data-var='time'>04:42</var> CEST Investigating - We're investigating the issue with inventory not being sent to channel managers.

Updates to channel managers are not sent.

Jul <var data-var='date'>14</var>, <var data-var='time'>20:28</var> CEST Resolved - Missed reservations from SiteMinder are now being delivered to Mews, you should see any missing reservation to appear shortly. Jul <var data-var='date'>14</var>, <var data-var='time'>19:54</var> CEST Identified - We’re investigating an issue where some reservations from SiteMinder have been delayed or may not appear in Mews, impacting customers since around 2:10pm UTC. Even though we have started receiving reservations normally we are working on recovering missed reservations. Jul <var data-var='date'>14</var>, <var data-var='time'>19:11</var> CEST Investigating - We are investigating issues with reservations delivery from SiteMinder

Is Mews down?

Mews status is UP

Lastest published events

Italy: unable to add tax deducted payment in the new Billing screen

Updates to channel managers are delayed.

Some channel reservations with loyalty memberships are not being created

Mews Services, Components and Regions

Recent Mews events

Italy: unable to add tax deducted payment in the new Billing screen

Updates to channel managers are delayed.

Some channel reservations with loyalty memberships are not being created

Delays in reservations and channel updates

Errors accessing Flexkeeping

Downgraded Performance - Connector API - kiosks, printers, integrations are affected