TrekkSoft Status Page

Jun 20, 2026 · resolved Jun 22

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

Jun 18, 2026 · resolved Jun 18

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

Jun 13, 2026 · resolved Jun 13

**Incident Description:** On June 13th at around 18:10 CEST, our platform experienced degraded performance caused by a DDoS attack targeting one of our merchant's domains. **Impact:** The incident caused slow load times across several customer-facing services, including AdminDesk, POS Desk, Website Builder, and TrekkSoft-hosted merchant websites. The degraded performance lasted approximately 1 hour 40 minutes, with full service restored by 19:50 CEST. No customer data was compromised. **Resolution:** Our engineering team identified the attack, set up traffic blocking rules to stop the affected domains, and rebooted the impacted infrastructure to fully restore service. **Preventive Measures and Recommendations:** We have begun work to strengthen our DDoS mitigation capabilities, so that attacks targeting a single merchant's domains can be detected and blocked more rapidly before they impact the broader platform.

Jun 12, 2026 · resolved Jun 12

**Incident Description:** On June 12th at around 14:30 CEST, our platform experienced a global incident caused by a DDoS attack targeting one of our merchant's domains. The attack overloaded shared infrastructure, making several of our services temporarily unreachable. **Impact:** The incident caused intermittent unavailability across several customer-facing services, including AdminDesk, POS Desk, Website Builder, and TrekkSoft-hosted merchant websites. The disruption lasted approximately 50 minutes, with full service restored by 15:20 CEST. No customer data was compromised. **Resolution:** Once our engineering team identified the source of the attack, they blocked the affected domains and rebooted the impacted infrastructure to restore service. **Preventive Measures and Recommendations:** We have begun work to strengthen our DDoS mitigation capabilities, so that attacks targeting a single merchant's domains can be detected and blocked more rapidly before they impact the broader platform.

May 11, 2026 · resolved May 11

**Overview:** Yesterday, between 17:02 and 17:43 CEST, TrekkSoft services \(including API, Backoffice, POS Desk, TrekkSoft Mobile App \(mPOS\), TrekkSoft Website Builder\) experienced a period of downtime. Our message queuing service \(CloudAMQP\) became unresponsive due to being overwhelmed by a volume of traffic that exceeded its capacity. **Timeline:** * 17:02 CEST: Start of outage. * 17:25 CEST: Engineering initiated an infrastructure upgrade. * 17:43 CEST: All services were fully restored and stabilized. **Next Steps & Prevention:** Infrastructure Scaling: We have permanently moved to a higher-tier service plan to provide a larger buffer for traffic spikes. We apologize for the interruption and appreciate your patience as we worked to restore service.

Is TrekkSoft down right now?

No — TrekkSoft is up. All systems operational as of Jul 13, 11:53 PM UTC.

What is TrekkSoft's current status?

TrekkSoft: All Systems Operational. Alert24 checks TrekkSoft's status page continuously and can notify you the moment it changes.

How do I get alerted when TrekkSoft goes down?

Alert24 monitors TrekkSoft and 3,700+ other cloud and SaaS providers. When an outage is detected it updates your status page automatically and pages your on-call team — no manual checks. Start free at alert24.net.