Mews Outage History
Mews is up right nowPingoru has recorded 108 incidents for Mews: 108 in the last 12 months and 28 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 11 | 314 of 720 (44%) |
| May 2026 | 8 | 166 of 744 (22%) |
| June 2026 | 13 | 42 of 720 (6%) |
| July 2026 | 5 | 45 of 744 (6%) |
| August 2026 | 7 | 27 of 744 (4%) |
| September 2026 | 7 | 157 of 720 (22%) |
| October 2026 | 14 | 98 of 591 (17%) |
Incidents, newest first
Major August 1, 2026 Bill closing and check-out issues for properties in Austria using the Chaining fiscal registry integration 2h 17m Mews Operations
Started Aug 01, 2026, 06:47 AM UTC· resolved Aug 01, 2026, 09:05 AM UTC
- 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.
- 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.
- 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.
- 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.
Minor July 23, 2026 Identity document scanning in Mews Operations is failing intermittently 20h 3m Mews Operations
Started Jul 23, 2026, 12:33 PM UTC· resolved Jul 24, 2026, 08:37 AM UTC
- investigating Jul 23, 2026, 12:33 PM UTC
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.
- investigating Jul 23, 2026, 01:58 PM UTC
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.
- resolved Jul 24, 2026, 08:37 AM UTC
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.
- postmortem Jul 29, 2026, 10:07 AM UTC
**Problem** On 2026-07-23T10:53:00Z, identity document scanning in Mews Operations began failing intermittently. Approximately half of scan attempts returned an error, while the other half succeeded normally. The issue affected hotel staff scanning guest identity documents \(passports, IDs\) during check-in. **Action** We immediately investigated the issue and identified that the third-party service processing document images was rejecting some of our requests. We published a Statuspage update within 20 minutes advising customers that retrying a failed scan would typically succeed after one or two attempts, and that manual entry of document details remained available throughout. Our team worked to diagnose the root cause, confirming the issue was not related to any Mews code release or configuration change. The service recovered fully by 2026-07-23T16:35:00Z. **Causes** The third-party service that processes document images intermittently blocked requests from our infrastructure, treating them as automated traffic. This was not caused by exceeding any usage limits — our usage was well within normal thresholds. The blocking occurred at the provider's network edge layer rather than at the API service level, which is why it affected only a portion of requests. **Solutions** The issue resolved on its own after approximately five and a half hours. No customer data was lost, and the vast majority of affected users \(93%\) were able to complete their scans successfully by retrying. To prevent recurrence, we are taking the following steps: 1. Establishing a direct support relationship with the provider so we can escalate issues more quickly in the future 2. Evaluating alternative document processing providers to reduce our dependency on a single third party We apologise for the inconvenience caused to hotel staff who had to retry document scans during the affected period.
Major July 17, 2026 Updates to channel managers are not sent. 11m Mews Marketplace
Started Jul 17, 2026, 02:42 AM UTC· resolved Jul 17, 2026, 02:53 AM UTC
- investigating Jul 17, 2026, 02:42 AM UTC
We're investigating the issue with inventory not being sent to channel managers.
- monitoring Jul 17, 2026, 02:49 AM UTC
Inventory processor stopped working. After restarting all the updates are being processed. No updates were missed, just delayed. We are monitoring the data recovery.
- resolved Jul 17, 2026, 02:53 AM UTC
All updates were successfully processed.
Major July 14, 2026 SiteMinder reservation delivery issues 1h 16m Mews Marketplace
Started Jul 14, 2026, 05:11 PM UTC· resolved Jul 14, 2026, 06:28 PM UTC
- investigating Jul 14, 2026, 05:11 PM UTC
We are investigating issues with reservations delivery from SiteMinder
- identified Jul 14, 2026, 05:54 PM UTC
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.
- resolved Jul 14, 2026, 06:28 PM UTC
Missed reservations from SiteMinder are now being delivered to Mews, you should see any missing reservation to appear shortly.
Major July 9, 2026 Bills can only contain up to 0 items 14m
Started Jul 09, 2026, 02:10 PM UTC· resolved Jul 09, 2026, 02:24 PM UTC
- identified Jul 09, 2026, 02:10 PM UTC
The Mews team identified the issue and is working on a resolution. Further updates will follow as we make progress.
- monitoring Jul 09, 2026, 02:14 PM UTC
We have resolved the issue, customer are confirming that bills can be closed again. We are monitoring the systems now before we close this incident
- resolved Jul 09, 2026, 02:24 PM UTC
The issue is now fully resolved. Us and customers confirmed they are now unblocked and can close bills.
- postmortem Jul 16, 2026, 03:33 PM UTC
**Problem** On 2026-07-09T13:37:00Z, a deployment introduced a configuration change that inadvertently set the maximum number of items allowed on a bill to zero. As a result, all customers across the production environment were unable to close bills. Users saw the error message: "Bills can only contain up to 0 items.". **Action** Our team identified the root cause within minutes of the incident being reported and corrected the configuration at 2026-07-09T14:05:34Z. Bill closing was restored immediately. **Causes** A newly configuration defaulted to 0 instead to the correct number.
Notice July 6, 2026 Issue with Accounting report (Order item report) 23h 10m Mews Operations
Started Jul 06, 2026, 12:38 PM UTC· resolved Jul 07, 2026, 11:48 AM UTC
- investigating Jul 06, 2026, 12:38 PM UTC
We've been made aware of issues with the accounting report and are looking into it
- identified Jul 06, 2026, 01:30 PM UTC
We have identified the issue with the accounting report, this issue is localized to viewing the report in Detailed mode only. We are releasing a fix right now.
- monitoring Jul 06, 2026, 02:05 PM UTC
A patch resolving the issue affecting the Order Items report in Detailed mode has been deployed to production. The report is loading normally again on the sites we were aware of. We are continuing to monitor to confirm the issue is fully resolved, and will post a final update once we're confident it is.
- resolved Jul 07, 2026, 11:48 AM UTC
We deployed the patch to production yesterday and having monitored for 24 hours we believe the issue is resolved and users should be able to filter Order item report in Detailed mode without issue.
Minor June 30, 2026 Booking.com outage 49m Mews Marketplace
Started Jun 30, 2026, 08:27 PM UTC· resolved Jun 30, 2026, 09:17 PM UTC
- monitoring Jun 30, 2026, 08:27 PM UTC
We are aware of an issue affecting the delivery of Booking.com reservations into Mews. New and updated reservations from Booking.com may be delayed in appearing in your Mews account.
- resolved Jun 30, 2026, 09:17 PM UTC
This issue originated with Booking.com and has been resolved on their side. We are now processing queued reservations.
Minor June 30, 2026 Reservations show inflated totals 38m Mews Operations, Mews Marketplace
Started Jun 30, 2026, 05:25 PM UTC· resolved Jun 30, 2026, 06:04 PM UTC
- identified Jun 30, 2026, 05:25 PM UTC
We have identified an issue where, for some reservations imported from connected Channel Managers, products that should be included in the rate (for example breakfast) were added on top of the reservation total instead. This inflated the reservation total and the assigned night cost for the affected bookings. The cause has been identified and the faulty behavior has been stopped, so no new reservations are affected. We are currently reprocessing the affected reservations to correct their totals. No action is required from your side. We will post a further update once reprocessing is complete.
- resolved Jun 30, 2026, 06:04 PM UTC
This incident has been resolved.
Minor June 25, 2026 Return icon showing on all reservations on the timeline 8m Mews Operations, Mews Guest Experience
Started Jun 25, 2026, 11:49 AM UTC· resolved Jun 25, 2026, 11:58 AM UTC
- identified Jun 25, 2026, 11:49 AM UTC
We are aware that customers are seeing the return icon on all reservations on the timeline. The Mews team identified the issue and is working on a resolution. Further updates will follow as we make progress.
- resolved Jun 25, 2026, 11:58 AM UTC
We've verified that the return icon is no longer showing incorrectly for all reservations on the timeline. We think the impact from the issue is over.
Major June 25, 2026 All inventory updates from Expedia are failing. 1h 39m Mews Operations, Mews Marketplace
Started Jun 25, 2026, 09:44 AM UTC· resolved Jun 25, 2026, 11:24 AM UTC
- monitoring Jun 25, 2026, 09:44 AM UTC
Expedia is currently experiencing an outage. Inventory updates from Mews to Expedia are failing, but reservation flows are unaffected. We are actively monitoring and will provide updates as the situation develops.
- resolved Jun 25, 2026, 11:24 AM UTC
Expedia has resolved their outage. Inventory updates from Mews to Expedia are back to normal.
Minor June 24, 2026 Issue with Mews Kiosk and OCI Generating Registration Cards 1h 30m
Started Jun 24, 2026, 09:29 AM UTC· resolved Jun 24, 2026, 11:00 AM UTC
- identified Jun 24, 2026, 09:29 AM UTC
The Mews team identified the issue and is working on a resolution. Further updates will follow as we make progress.
- resolved Jun 24, 2026, 11:00 AM UTC
We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.
Major June 22, 2026 Reservations from booking.com are missing. 31m Mews Marketplace
Started Jun 22, 2026, 08:17 PM UTC· resolved Jun 22, 2026, 08:49 PM UTC
- monitoring Jun 22, 2026, 08:17 PM UTC
Booking.com is experiencing an outage. https://connect.booking.com/status/incident/732 We are monitoring situation.
- resolved Jun 22, 2026, 08:49 PM UTC
Booking.com has resolved the outage. All missed reservations were retried by booking.com
Minor June 20, 2026 Synxis CRS updates are failing due to Synxis internal maintanance. 1d 1h Mews Marketplace
Started Jun 20, 2026, 04:00 AM UTC· resolved Jun 21, 2026, 05:29 AM UTC
- monitoring Jun 20, 2026, 04:00 AM UTC
Synxis is doing internal maintanance, which resulted as unavailable services. This prevent us to deliver inventory updates about availability, prices and restrictions. We are monitoring situation. Once maintanance is resolved all updates will be automatically retried.
- monitoring Jun 20, 2026, 11:57 AM UTC
Synxis CRS maintenance was finished. All missed updates are being retried. We keep monitoring situation.
- resolved Jun 21, 2026, 05:29 AM UTC
Missed updates were retried
Minor June 11, 2026 Digital keys not working due to outage on 3rd party end (Assa Abloy) 35m Mews Guest Experience
Started Jun 11, 2026, 08:18 AM UTC· resolved Jun 11, 2026, 08:53 AM UTC
- investigating Jun 11, 2026, 08:18 AM UTC
Our observability tools have detected errors indicating a potential outage with a third-party provider (Assa Abloy/Vostio API), which may impact digital key creation and management for Mews customers and their guests. We are currently investigating the issue and have contacted the third party and will provide an update soon.
- monitoring Jun 11, 2026, 08:32 AM UTC
Technical contacts at Assa Abloy have confirmed an issue on their end, which was resolved at 10:10 AM CEST. We are continuing to monitor systems on the Mews side, but the issue should now be fully resolved.
- resolved Jun 11, 2026, 08:53 AM UTC
Technical contacts at Assa Abloy have confirmed an issue on their side, which has now been resolved. Mews observability monitoring no longer indicates any ongoing problems. Support for both digital and physical key creation via Mews has been fully restored.
- postmortem Jun 30, 2026, 08:24 AM UTC
**Problem** On 2026-06-11 at about 9am BST, a technical issue on our third-party partner Assa Abloy's \(Vostio\) side caused their API to become temporarily unavailable. This impacted digital key services for some Mews customers and their guests, meaning some key creation and key management operations may have failed during the outage window. **Action** Our team detected the issue through internal monitoring tools and immediately began investigating. We contacted Assa Abloy's technical team, who confirmed the issue was on their side. While waiting for their resolution, we monitored our systems and published a status update to keep customers informed. Assa Abloy deployed a fix at approx 9.10am BST, and we continued monitoring to confirm that services had returned to normal. The incident was fully resolved on 9:38am BST. **Causes** A technical issue occurred within Assa Abloy's infrastructure that affected their Vostio API. Since Mews relies on this API for digital key operations, the outage caused some key cutting requests to fail and prevented some reservation updates from being processed on the Vostio side. Assa Abloy has indicated they will publish a root cause analysis with further details. **Solutions** Assa Abloy's R&D team identified and deployed a fix for the underlying issue. On the Mews side, we are taking steps to improve our response to similar third-party outages in the future, including enhancing our monitoring to detect these failures faster and working with Assa Abloy to improve our visibility into the status of their services.
Minor June 10, 2026 Reserved spaces not marked as dirty overnight 4h 34m Mews Operations
Started Jun 10, 2026, 07:00 AM UTC· resolved Jun 10, 2026, 11:34 AM UTC
- identified Jun 10, 2026, 07:00 AM UTC
Some reserved spaces were not automatically marked as dirty according to the housekeeping interval. We are fixing the background job responsible for the automatic updates and preparing a one-time correction to update the affected spaces. In the meanwhile, if you don't have the "Check-out makes space dirty" option enabled, check that recently checked-out spaces are correctly marked as dirty.
- resolved Jun 10, 2026, 11:34 AM UTC
We have resolved the root cause responsible for the missing updates. Future updates will be applied correctly. We apologize for the disruption to your operations.
Minor June 4, 2026 Expedia reservation delays 33m Mews Marketplace
Started Jun 04, 2026, 11:42 AM UTC· resolved Jun 04, 2026, 12:16 PM UTC
- identified Jun 04, 2026, 11:42 AM UTC
We identified an issue with Expedia reservations that is causing delays, and are currently applying the fix. All reservations should be processed shortly
- resolved Jun 04, 2026, 12:16 PM UTC
This incident has been resolved.
Minor June 3, 2026 Investigating issues with Guest Portal 34m Mews Guest Experience
Started Jun 03, 2026, 03:43 PM UTC· resolved Jun 03, 2026, 04:18 PM UTC
- investigating Jun 03, 2026, 03:43 PM UTC
We are currently investigating reports of an issue affecting Mews Guest Portal. The Mews team is actively working to identify the cause, and we will provide updates as soon as possible.
- monitoring Jun 03, 2026, 03:53 PM UTC
We've identified the issue and deployed a fix. Please refresh the page to restore the functionality.
- resolved Jun 03, 2026, 04:18 PM UTC
The issue is now fully resolved. Mews Guest Portal is now operating as expected.
- postmortem Jun 15, 2026, 11:44 AM UTC
### Problem On June 3rd at 00:00 UTC, the Mews Guest Portal homepage became unresponsive for guests. Guests who attempted to access the Guest Portal homepage — for example after completing Online Check-in or via an email link — were unable to load the page. Other Guest Portal functions, including Online Check-in itself, continued to operate normally. The main impact was that guests could not view their stay dashboard or download digital keys from the homepage. The issue persisted until June 3rd 15:50 UTC, when a fix was deployed and the Guest Portal homepage was fully restored. ### Action Once the issue was reported, the Mews engineering team immediately began investigating. Within minutes, the team identified the source of the problem and deployed a fix. The Guest Portal homepage was fully restored, and the team monitored the system for an additional 30 minutes to confirm stability before marking the incident as resolved. A status page update was published to keep customers informed throughout the process. ### Causes The issue was caused by a service configuration mismatch during a routine deployment. This mismatch caused errors when loading the Guest Portal homepage, resulting in the page becoming unresponsive. Importantly, the underlying check-in functionality was not affected — guests were still able to complete Online Check-in during this period. ### Solutions The immediate fix was a service deployment that corrected the mismatch and restored normal functionality. Going forward, Mews is reviewing its deployment and monitoring processes to prevent similar mismatches from occurring and to ensure faster detection of issues like this in the future.
Major June 2, 2026 Some customers are experiencing an issue where their guests are unable to check in via Kiosk v4.51 3h 53m
Started Jun 02, 2026, 11:38 AM UTC· resolved Jun 02, 2026, 03:32 PM UTC
- investigating Jun 02, 2026, 11:38 AM UTC
We are currently investigating reports of an issue affecting Mews Kiosk with error message "Invalid AccountId Error". The Mews team is actively working to identify the cause, and we will provide updates as soon as possible.
- identified Jun 02, 2026, 12:11 PM UTC
Some customers running the latest Kiosk v4.51 are impacted, particularly those who have 100+ active reservations. The team is working on the fix that will be available shortly.
- resolved Jun 02, 2026, 03:32 PM UTC
The issue has been resolved and Kiosk operations have been fully restored.
- postmortem Jun 18, 2026, 02:10 PM UTC
**Problem** On Tue, 02 Jun 2026, guests at some properties using Mews Kiosk v4.51.0 were unable to complete check-in. The issue affected properties with a high number of arrivals on the same day, causing an error during the check-in process. Approximately 29 properties were impacted. ### Action Our team identified the issue and began working on a fix immediately. A backend change was deployed to production on Tue, 02 Jun 2026 15:07:00 UTC, restoring check-in functionality for all affected properties. In parallel, an updated version of the Kiosk app was prepared and submitted to app stores. The Android version became available the same afternoon, and the iOS version followed later that evening. The issue was fully resolved and confirmed working by affected customers by Tue, 02 Jun 2026 15:27:34 UTC. ### Causes The Kiosk v4.51.0 was over-fetching data, requesting data for all active customers at a property instead of only the customers relevant to the reservation being checked in. This caused the request to exceed an API limit when a property had more than 100 customers arriving on the same day, resulting in an error that blocked the check-in process. ### Solutions * A backend fix was deployed to increase the API limit, immediately restoring check-in functionality for all affected properties. * A new Kiosk app version \(4.51.1\) was released that corrects the data request to only fetch information relevant to the matched reservation, resolving the root cause. * Follow-up improvements to our deployment pipeline, testing strategy, and documentation have been identified and are being implemented to reduce the likelihood of similar issues in the future.
Minor June 1, 2026 Issue with Mews 1h 5m
Started Jun 01, 2026, 11:30 AM UTC· resolved Jun 01, 2026, 12:36 PM UTC
- monitoring Jun 01, 2026, 11:30 AM UTC
We identified a brief period of increased response times affecting some Mews customers. Our team has addressed the underlying cause and we are monitoring the system to confirm stability. We will provide a further update shortly.
- monitoring Jun 01, 2026, 11:59 AM UTC
Between approximately 11:40am and 11:56am UTC, some customers may have experienced slow responses or intermittent errors when using Mews. Performance has recovered and we’re continuing to monitor; if you’re still seeing issues, please retry your request and contact Support if it persists.
- resolved Jun 01, 2026, 12:36 PM UTC
The issue is now fully resolved. Mews is now operating as expected.
Notice May 29, 2026 Intermittent errors and access issues in Mews 3h 51m
Started May 29, 2026, 12:25 PM UTC· resolved May 29, 2026, 04:17 PM UTC
- investigating May 29, 2026, 12:25 PM UTC
We are currently investigating reports of intermittent errors and "no access" messages affecting some users when loading pages within Mews. Our engineering team is actively looking into the issue.
- identified May 29, 2026, 02:01 PM UTC
Intermittent access and page-loading errors in Mews have now stabilized. We've identified and remediated the issue, and are addressing the underlying root cause.
- resolved May 29, 2026, 04:17 PM UTC
We confirmed our analysis of the root cause was correct. We fully remediated the issue and validated the solution successfully by thorough testing.
Minor May 27, 2026 Investigating issues with permissions 1h 30m Mews Operations, Mews Guest Experience, Mews Open API, Mews Marketplace
Started May 27, 2026, 02:59 PM UTC· resolved May 27, 2026, 04:30 PM UTC
- investigating May 27, 2026, 02:59 PM UTC
We are aware of an issue with our authorization service. Some customers are seeing access errors on pages they should be able to reach. We are actively investigating and will share an update as soon as we know more.
- monitoring May 27, 2026, 03:40 PM UTC
The team have scaled out our authorization service and switched to a healthy replica. We are monitoring to confirm there are no further issues. Customers should no longer see unexpected access errors. If you are still affected, please reach out to our support team.
- monitoring May 27, 2026, 04:07 PM UTC
We are continuing to monitor for any further issues.
- resolved May 27, 2026, 04:30 PM UTC
We're happy the remediation work has now resolved this
Minor May 25, 2026 Reservation delivery issues 3h 31m Mews Marketplace
Started May 25, 2026, 12:36 PM UTC· resolved May 25, 2026, 04:08 PM UTC
- investigating May 25, 2026, 12:36 PM UTC
We are currently investigating an issue affecting reservation delivery through channel manager integrations. Some reservations are not being processed as expected, and we are working to resolve this as quickly as possible.
- identified May 25, 2026, 01:24 PM UTC
We have identified a problem with a malformed reservation payload that is holding up a partition of our reservations processing, causing delay in 1.6% of reservations for about 24 hours. We are implementing a fix. Missing reservations are delayed but will be processed. There is a chance of overbooking.
- monitoring May 25, 2026, 02:02 PM UTC
The fix has been deployed and we have confirmed that reservations are flowing again. It can take several minutes for the delayed reservations to be processed, with an increased risk of overbooking.
- resolved May 25, 2026, 04:08 PM UTC
The issue is now fully resolved. All delayed reservations were confirmed to be processed by 15:00 UTC.
Minor May 24, 2026 German Fiscalization Is Having Issues due to Fiskaly Maintenance 1d 2h Mews Operations
Started May 24, 2026, 12:45 PM UTC· resolved May 25, 2026, 03:37 PM UTC
- investigating May 24, 2026, 12:45 PM UTC
We are currently investigating this issue.
- identified May 24, 2026, 12:46 PM UTC
We are monitoring the situation and we will keep you posted when Fiskaly is done with the maintenance. You might experience delayed bill printing if you have the German fiscalization enabled.
- identified May 24, 2026, 12:47 PM UTC
We are actively monitoring the ongoing Fiskaly maintenance and will provide an update once it has been completed. Customers with German fiscalization enabled may experience delays in bill printing during this period.
- identified May 24, 2026, 01:07 PM UTC
We are actively monitoring the ongoing Fiskaly maintenance and will provide an update once it has been completed. Customers with German fiscalization enabled may experience delays in bill printing during this period.
- monitoring May 24, 2026, 01:37 PM UTC
We are seeing improvements in the transmission of fiscal records to Fiskaly. We will continue monitoring the situation and share a further update once the service is fully restored.
- resolved May 25, 2026, 03:37 PM UTC
Everything is working as expected on the Mews side. While Fiskaly continues to work on restoring full performance of their TSS service, you may still see fiscal records marked with "Connection to TSS is not possible." on receipts — this is the expected fallback behavior.
Minor May 21, 2026 Booking.com reservations outage. 2h 50m Mews Marketplace
Started May 21, 2026, 10:57 AM UTC· resolved May 21, 2026, 01:48 PM UTC
- monitoring May 21, 2026, 10:57 AM UTC
Booking.com is experiencing outage for reservations delivery. No reservations for booking.com direct integration are currently created in Mews. We are monitoring the situation.
- resolved May 21, 2026, 01:48 PM UTC
Booking.com has resolved the outage. Reservations are now successfully being created in Mews.
Minor May 13, 2026 RoomCloud Updates Failing 1d 21h Mews Marketplace
Started May 13, 2026, 03:48 PM UTC· resolved May 15, 2026, 01:18 PM UTC
- monitoring May 13, 2026, 03:48 PM UTC
RoomCloud Channel Manager is currently experiencing API issues. As a result, inventory pushes and reservation confirmations are failing. We are monitoring the situation closely, and once the issue is resolved, the affected inventory will be re-pushed.
- resolved May 15, 2026, 01:18 PM UTC
Issue is resolved and failed messages were successfully retried.