Service interruptions at TrekkSoft
Timeline · 4 updates
- investigating Feb 19, 2026, 08:00 AM UTC
We are currently investigating technical issues affecting core Trekksoft services, including the Backoffice, POS Desk, Booking Widget, etc. You may experience difficulties processing bookings or accessing your account. 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.
- monitoring Feb 19, 2026, 08:14 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Feb 19, 2026, 10:18 AM UTC
This incident has been resolved and all Trekksoft functionalities are operating normally. We will provide a postmortem of the incident as soon as possible. We apologize once again for any inconvenience this may have caused.
- postmortem Feb 20, 2026, 01:44 PM UTC
**Incident Date: Feb 19, 2025** Incident Duration: Approx 2 hours Affected services: TrekkSoft API, TrekkSoft backoffice, POS Desk, TrekkSoft Mobile Applications \(mPOS\), TrekkSoft Website Builder **Incident Description:** On Feb 19th at around 06:30 AM CET, our system detected a cyber attack that degraded the system's performance. **Impact:** The incident degraded the functionality of most of our services, making it difficult for users to create new bookings or use the API as the database was too busy answering the bot’s fake requests \(the cyber attack\). The degraded performance lasted approximately 2 hours, with full service restored by 08:30 AM CET. **Resolution:** Once we identified the source of the attack, we blocked it to stop the issue. **Preventive Measures and Recommendations:** We remain deeply committed to the long-term strengthening of our security posture, with active work currently ongoing to sharpen our detection triggers and accelerate our response capabilities for any future incidents.