Degraded system performance
Last updatepostmortemOct 12 · 08:40 UTC
Service disruption on 11th October 2026 — Postmortem
Status: Resolved
What happened
On 11 October, between approximately 17:50–18:55 and 19:45–22:40 CEST (about 4 hours), our platform had degraded performance. During this timespan, the majority of bookings and other actions across the Booking Widget, API, and POS could not be completed.
Initial monitoring metrics resembled patterns consistent with a malicious traffic burst caused by a cyberattack, prompting our engineering team to investigate that vector first.
After investigation it was identified the issue was not a cyber attack. There was no security breach, and no customer or payment data was affected.
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 22:40 CEST.
What caused it
The disruption was triggered by an unusually high volume of bookings that overloaded our booking API, then our database.
What we're doing about it
To ensure high resilience against unexpected traffic spikes moving forward, we are implementing the following measures:
- Automated API Autoscaling for bookings handled via our API
- We are improving our monitoring alerts so our team can immediately tell the difference between a high-volume sale and a security threat, saving valuable diagnostic time.
- Direct guidelines and communication channels with our customers about high traffic events, to prepare system resources in advance
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.
Reported by TrekkSoft on their status page.