Is TrekkSoft down?

We are currently experiencing global issues in several Trekksoft production functionalities (a.o. Backoffice, POS Desk) meaning that you can neither access the TrekkSoft backoffice nor accept bookings via the booking widget, channel manager or website builder. Our developers are already investigating the root cause of the issue. We apologize for any inconvenience this may have caused and appreciate your patience as we work to resolve the issue. If you have any questions or concerns, please don't hesitate to contact us. We will make sure to keep you updated on the progress of this issue. We will keep you updated through our https://status.trekksoft.com/ for any further information. If you haven’t subscribed to it yet, we encourage you to do it.

We are currently monitoring the platform. Service has remained stable since the incident, and we continue to observe the system while our investigation remains ongoing.

The platform is operating normally, and this incident is now considered resolved. We will continue investigating the circumstances surrounding the disruption as part of our post-incident review. A post-mortem with additional details will be shared once the investigation has been completed.

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