Mews Incident History

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.

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.

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.

All updates were successfully processed.

Inventory processor stopped working. After restarting all the updates are being processed. No updates were missed, just delayed. We are monitoring the data recovery.

We're investigating the issue with inventory not being sent to channel managers.

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

The issue is now fully resolved. Us and customers confirmed they are now unblocked and can close bills.

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

The Mews team identified the issue and is working on a resolution. Further updates will follow as we make progress.

Missed reservations from SiteMinder are now being delivered to Mews, you should see any missing reservation to appear shortly.

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.

We are investigating issues with reservations delivery from SiteMinder