TrekkSoft Outage History

13 incidents recorded over the last 365 days, 9 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live TrekkSoft status100.00% uptime history

Every Recorded TrekkSoft Incident

TrekkSoft incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 20, 2026Scheduled maintenance notice: 20th OctoberOur scheduled maintenance is taking a bit longer than expected. The process is still ongoing, and our services may continue to be affected for a short while longer. We’re actively working to complete the update and…2h 0mScheduled
Oct 11, 2026Degraded system performance**Service disruption on 11th October 2026 — Postmortem** **Status: Resolved** **What happened** On 11 October, between approximately 17:50–18:55 and 19:45–22:40 CEST \(about 4 hours\), our platform had degraded…4h 2mResolved
Sep 30, 2026Scheduled maintenance notice: 30th SeptemberThe scheduled maintenance has been completed. All functionalities are operational. Thank you again for your continued patience and understanding2h 0mScheduled
Sep 1, 2026Scheduled maintenance noticeThe scheduled maintenance has been completed. All functionalities are operational. Thank you again for your continued patience and understanding1h 0mScheduled
Aug 6, 2026Global issue affecting all/ majority of TrekkSoft’s functionalities**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…2h 40mResolved
Jun 20, 2026Issues accessing TrekkSoft Backoffice and POS Desk**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…48h 11mResolved
Jun 18, 2026Global issue affecting all/majority of TrekkSoft’s functionalities**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…3h 9mResolved
Jun 13, 2026Resolved - Performance Issues Mitigated**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…-215 minResolved
Jun 12, 2026Global issue affecting all/majority of TrekkSoft’s functionalities**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…1h 41mResolved
May 11, 2026Service interruptions at TrekkSoft**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…2h 55mResolved
Apr 15, 2026Scheduled maintenance notice: 15th April 2026The scheduled maintenance has been successfully completed.2h 0mScheduled
Feb 19, 2026Service interruptions at TrekkSoft**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…2h 18mResolved
Nov 12, 2025Disruption of online transactions via Saferpay/WorldlineSaferpay has confirmed that the incident is resolved. At the current time we do not have further information about the cause of the incident. Start of disruption: Wednesday, November 12, 2025, 19:07 CET End of…2h 33mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next TrekkSoft incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This TrekkSoft Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before TrekkSoft acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single TrekkSoft outage in this window ran 2d, against a mean recovery of 6h 12m. If you depend on TrekkSoft in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.