TrekkSoft incident

Global issues in Trekksoft production functionalities (e.g. Backoffice, POS Desk)

Critical Resolved View vendor source →

TrekkSoft experienced a critical incident on October 9, 2024 affecting TrekkSoft Backoffice and TrekkSoft Mobile App (mPOS) and 1 more component, lasting 2h 1m. The incident has been resolved; the full update timeline is below.

Started
Oct 09, 2024, 02:13 PM UTC
Resolved
Oct 09, 2024, 04:14 PM UTC
Duration
2h 1m
Detected by Pingoru
Oct 09, 2024, 02:13 PM UTC

Affected components

TrekkSoft BackofficeTrekkSoft Mobile App (mPOS)POS Desk

Update timeline

  1. investigating Oct 09, 2024, 02:13 PM UTC

    We are currently experiencing global issues in TrekkSoft's production functionalities (e.g. Backoffice, POS Desk). Our developers are already investigating on finding the root cause of the issue. We will keep you updated and apologize for the inconvenience caused.

  2. monitoring Oct 09, 2024, 03:20 PM UTC

    We are currently monitoring the issue.

  3. monitoring Oct 09, 2024, 03:28 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Oct 09, 2024, 04:14 PM UTC

    We registered a cyber attack towards our systems, that resulted in a brief downtime. We identified and quickly reacted to the issue by blocking the attackers. The incident has been resolved, and all Trekksoft functionalities are now operating normally. We will provide a postmortem of the incident in the coming days. We apologize once again for any inconvenience this may have caused.

  5. postmortem Oct 11, 2024, 07:02 AM UTC

    **Incident Date**: October 9th 2024 **Incident Duration**: Approximately 1 hour **Affected Services**: TrekkSoft Application, POS Desk, Backend Mobile Applications **Incident Description**: At approximately 03:30 PM CEST on October 9th, 2024, a prepared cyber attack was performed against our system. **Impact**: We experienced an attack that targeted parts of our system, causing our TrekkSoft Application, POS Desk, Backend Mobile Applications, be unavailable for about an hour. This happened because the attack was sending fake information to a specific parts of our system. **Resolution**: After identifying where the attack was coming from, we blocked it and restarted parts of our system that had stopped responding, which allowed us to get everything back up and running. **Preventive Measures:** We are taking further measurements to prevent similar incidents in the future.