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.

We are currently experiencing issues in some Trekksoft production functionalities (a.o. Backoffice, POS Desk). This might result in you not being able to access the Backoffice or POS Desk. 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 statuspage for any further information. If you haven’t subscribed to it yet, we encourage you to do it.

The ongoing technical issue is also impacting booking functionality for certain accounts, preventing new bookings from being received. Our development team is actively working on a fix. Thank you for your patience as we work to resolve this completely. We will keep you updated here.

Certain domains and subdomains were inaccessible this mornig, which caused the temporary disruptions to TrekkSoft production functionalities (including the Backoffice, POS Desk, and Booking Widgets). All systems and services are now fully operational and working as expected. Next Steps: Our engineering team is closely monitoring performance and stability to ensure everything remains running smoothly. We appreciate your patience while we brought services back online. Another update will be provided once we formally close the incident.

This incident has been resolved.

**Incident Description:** On June 20th, between 04:41 and 08:45 CEST, several of our customer-facing services, including Admin Desk, POS Desk, and TrekkSoft-hosted websites, experienced slow load times and intermittent unavailability. **Cause and Resolution** The disruption was caused by a sustained DDoS attack on our shared infrastructure. Our engineering team successfully identified and blocked the source of the traffic, restoring full service within approximately 4 hours. No customer data was compromised during this incident. **Preventive Measures and Recommendations:** 1. Increasing infrastructure capacity and automatic traffic protections. 2. Implementing stricter isolation boundaries so an issue with one account cannot affect others. 3. Deploying advanced bot-management tools to block malicious traffic proactively. We apologize for the disruption to your operations and appreciate your understanding.

We are currently experiencing global issues in several Trekksoft production functionalities (a.o. Backoffice, POS Desk) that could potentially be affecting access to the TrekkSoft backoffice and 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 statuspage for any further information. If you haven’t subscribed to it yet, we encourage you to do it.

For a short period of time, certain domains and subdomains were inaccessible, which caused the temporary disruptions to TrekkSoft production functionalities (including the Backoffice, POS Desk, and Booking Widgets). Current Status: System Recovery: All systems and services are now fully operational and working as expected. Next Steps: Our engineering team is closely monitoring performance and stability to ensure everything remains running smoothly. We appreciate your patience while we brought services back online. Another update will be provided once we formally close the incident.

We have successfully resolved the recent performance issues, and all platform functions have returned to normal operations. No customer or system data was compromised during this incident. We will continue to closely monitor all systems to ensure ongoing stability and performance. Thank you for your patience and understanding.

**Incident Date: June 18th, 2026** Incident Duration: Approximate 20 minutes **Incident Description:** On June 18th at around 17:15 CEST, our infrastructure experienced a sudden surge of abnormal automated traffic directed at one of our merchant sites, which degraded performance across the platform. **Impact:** The incident caused slow load times and intermittent unavailability across several of our customer-facing services, including the AdminDesk, POS Desk, Booking Widget, and TrekkSoft-hosted merchant websites. Because the traffic surge overloaded a shared infrastructure layer, the impact extended beyond the targeted merchant to other customers on the same infrastructure. The degraded performance lasted approximately 20 minutes, with full service restored by 17:35 CEST. **No customer data was affected.** **Resolution:** Once our engineering team identified the source of the abnormal traffic, they blocked it to stop the issue. Systems recovered as the traffic was cut off, and we monitored stability through the rest of the day to confirm full recovery. **Preventive Measures and Recommendations:** We remain committed to strengthening the resilience of our platform. We have already begun work to add infrastructure capacity and improve our automatic traffic protections, so that a single source of abnormal traffic can no longer impact other customers sharing the same infrastructure.