Incident History for Mews

The login and slow performance incident has been resolved; contact support if issues persist.

System stable since recovery; root cause of the database replica issue is still being investigated with the cloud provider.

Login failures and slow performance between 15:25-15:40 UTC have recovered; the issue was traced to a database replica and is being monitored.

Some users experienced login failures and logouts between 15:25-15:40 UTC; recovery is underway and investigation continues.

The Guest Messenger issue is fully resolved and Mews is operating as expected.

Guest Messenger is working normally for all properties after the incident was resolved.

The Mews team identified the issue causing Guest Messenger unavailability and is working on a resolution; further updates will follow.

Cause of Guest Messenger inbox unavailability found and a fix is being rolled out; no action needed from properties.

Booking.com resolved its issue; delayed inventory updates are being recovered and reservations are flowing while Mews continues monitoring.

Booking.com's issue remains unresolved; inventory updates and reservation delivery are still affected while Mews monitors and prepares recovery.

Booking.com is fixing a major disruption; reservation delivery is now also affected and the incident is reclassified as critical.

Mews identified the cause on Booking.com's side and is contacting them; inventory updates are affected while reservations still arrive.

The accounting ledger delay is resolved; all ledger data is processed, ledgers are up to date, and trial balances generate without delay.

Accounting ledger processing is delayed, so ledgers may lack recent transactions and trial balances take longer; no data has been lost.

The check-in flow issue in Mews Operations is now resolved after causing slow responses and errors for some properties.

The Mews team has identified an issue affecting the check-in flow in selected properties and is working on a resolution.

The Italy tax deducted payment issue in the new Billing screen is fully resolved and Mews is operating as expected.

Delayed updates were successfully synchronized to channel managers and the incident is resolved.

Delayed channel manager updates are being processed after removing accumulated updates; recovery is being monitored.

Availability, price and restriction updates to channel managers are delayed while the root cause is investigated.

A postmortem has been published for the AI tooling degradation caused by the Claude and Azure Foundry outage.

Reservations requiring new loyalty memberships failed to appear in Mews; the issue is fixed and bookings reprocessed.

Some Strawberry channel reservations with new loyalty memberships are not appearing in Mews; engineers are working on a fix.

Some Choice EDGE CRS and SynXis reservations with new loyalty memberships are not appearing in Mews; engineers are fixing the identified cause.

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

Reservation processing is fully operational again, but inventory synchronization to channels remains slower than usual with possible delays.

Reservation processing and inventory synchronization between Mews and distribution channels are not progressing; updates are queued and will process once resolved.

Inventory queue recovering after high update volume; delays reducing as backlog clears, updates not lost, monitoring closely.

The Connector API incident affecting kiosks, printers, and integrations has been resolved.

Mews is investigating degraded performance of the Connector API affecting kiosks, printers, and integrations.

The Guest Messenger provisioning issue is resolved; new accounts were provisioned and functionality is working.

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

The issue causing slowness and timeouts in Mews Operations has been resolved and all affected properties can work normally.

The AI tooling outage caused by Claude and Azure Foundry is resolved as of September 29, 8PM UTC.

AI tooling is degraded due to Claude and Azure Foundry outages, while core Mews functionality remains unaffected.

Mews is monitoring the situation after isolating problematic reports to a separate component, with the platform operating normally while a permanent solution is developed.

SynXis and Best Western CRS outages have been resolved; both connections operate normally and all affected updates were reprocessed.

SynXis fully recovered and reprocessed; Best Western CRS error levels normal since 09:10 UTC, monitoring while awaiting their confirmation of full resolution.

Elevated errors on Best Western CRS connections since 06:00 UTC; some updates failing and retrying, investigation ongoing.

SynXis is responding again and queued updates are processing, but backlog reprocessing continues and channel data may remain out of date.

SynXis continues rejecting requests with no recovery; properties remain affected and resynchronisation will take time once service returns.