Service disruption on 6 August 2026 — Postmortem

Status: Resolved

What happened

On 6 August, between approximately 12:00 and 12:22 CEST, our platform was unavailable for around 19 minutes. During this window, bookings and other actions across the Booking Widget, API, Admin Desk, Website Builder, and POS could not be completed.

Impact

For the duration of the disruption, requests to our systems did not complete as expected. Merchants and their customers would have seen errors or unresponsive pages when trying to book or manage activities. Service returned to normal at around 12:22 CEST.

What caused it

The disruption was triggered by a routine update to our database as part of a scheduled deployment. A change that is normally quick and low-impact interacted with one of the most heavily used parts of our system, which caused requests to queue up rather than complete. This built up quickly and made the platform unresponsive until the condition cleared and traffic drained back to normal.

What we're doing about it

We've identified the specific cause and the conditions that allowed a routine change to have this effect. We're putting several improvements in place, including changes to how these database updates are applied so they can't build up this kind of backlog again, and additional monitoring so we detect this type of issue ourselves before it affects service, rather than relying on error reports.

We understand disruptions like this affect your business and your own customers, and we're sorry for the impact. If you have any questions or believe you're still seeing related issues, please contact our support team.