Issues accessing TrekkSoft Backoffice and POS Desk
Timeline · 5 updates
- investigating Jun 20, 2026, 06:13 AM UTC
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.
- investigating Jun 20, 2026, 06:41 AM UTC
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.
- monitoring Jun 20, 2026, 08:22 AM UTC
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.
- resolved Jun 22, 2026, 06:25 AM UTC
This incident has been resolved.
- postmortem Jun 25, 2026, 06:45 AM UTC
**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.