Migrating Open API traffic to new infrastructure

The mitigation steps and migration were completed.

The migration of Booking Engine API and Channel Manager API on the production environment has been completed. All Open APIs are now fully operational.

While we have taken steps to minimize timeout spikes, occasional timeouts may still occur. We are continuing to investigate the underlying causes.

The planned migration of Booking Engine API and Channel Manager API on the production environment will resume tomorrow (August 19) between 11:00 and 13:00 UTC.

During the migration window, you may experience increased response latency for the affected APIs.

The migration of Connector API on the production environment was successfully completed yesterday. Booking Engine API and Channel Manager API have also been migrated on the demo environment.

The planned migration of Booking Engine API and Channel Manager API on the production environment is postponed. We will provide the updated schedule next week.

Connector API migration on the demo environment was completed successfully yesterday.

Today (August 13), we will also migrate Booking Engine API and Channel Manager API on the demo environment between 12:00 and 13:00 UTC.

The migration of Connector API on the production environment will proceed as planned today between 13:00 and 16:00 UTC.

Tomorrow (August 14), Booking Engine API and Channel Manager API will be migrated on the production environment between 13:00 and 16:00 UTC.

During each migration window, you may experience increased response latency in the affected APIs in the respective environments.

We are migrating Connector API traffic to dedicated infrastructure.

Schedule:
- Demo environment: August 12, 13:00–16:00 UTC
- Production environment: August 13, 13:00–16:00 UTC

You may experience increased response latency for Connector API during these times in the respective environments.

We continue the investigation and talking to our cloud provider.
Our platform team is actively monitoring, and taking mitigation steps as needed.
Further updates will follow as more information becomes available.

We continue to investigate and are closely monitoring the system’s status. Periodic latency spikes may occasionally occur in short intervals on individual instances. Our platform team is actively working to identify the root cause, monitoring metrics, and taking mitigation steps as needed.

We have upscaled our compute infrastructure to reduce the load on affected instances, which should help minimize customer impact.

Further updates will follow as more information becomes available.

Correction, please disregard the previous update as it was related to another incident: https://status.mews.com/incidents/3q6n596dqzd9

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

We have resolved the issue, and we are closely monitoring the system to ensure stability.

We are currently investigating reports of increased latency across our public API. Initial indicators show periodically elevated response times and timeouts affecting most endpoints.

Thank you for your patience as we work to resolve the issue.