TrekkSoft Outage History

TrekkSoft is up right now

TrekkSoft had 16 outages in the last 2 years totaling 241h 34m of downtime — averaging 0.7 incidents per month.

There were 16 TrekkSoft outages since June 11, 2024 totaling 241h 34m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.trekksoft.com

Major May 11, 2026

Service interruptions at TrekkSoft

Detected by Pingoru
May 11, 2026, 03:22 PM UTC
Resolved
May 11, 2026, 06:17 PM UTC
Duration
2h 55m
Affected: TrekkSoft BackofficeTrekkSoft APITrekkSoft Mobile App (mPOS)POS DeskTrekkSoft Website Builder
Timeline · 4 updates
  1. investigating May 11, 2026, 03:22 PM UTC

    We are currently experiencing global issues in several Trekksoft production functionalities (a.o. Backoffice, POS Desk) meaning that you can neither access the TrekkSoft backoffice nor accept bookings via the booking widget, channel manager or website builder. 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.

  2. monitoring May 11, 2026, 03:49 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved May 11, 2026, 06:17 PM UTC

    The incident has been fully resolved, and all systems are back to normal operation. We are currently conducting a thorough internal review and will publish a detailed post-mortem report tomorrow.

  4. postmortem May 12, 2026, 12:20 PM UTC

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

Read the full incident report →

Minor November 12, 2025

Disruption of online transactions via Saferpay/Worldline

Detected by Pingoru
Nov 12, 2025, 07:05 PM UTC
Resolved
Nov 12, 2025, 09:39 PM UTC
Duration
2h 33m
Affected: Payyo - Payment Gateway
Timeline · 5 updates
  1. investigating Nov 12, 2025, 07:05 PM UTC

    We are investigating an issue causing payment failures. We've traced the problem to our external payment gateway and are monitoring their investigation. We will update you as we learn more.

  2. identified Nov 12, 2025, 07:10 PM UTC

    We've received confirmation from Worldline that the following services are currently interrupted: - Processing of online transactions from Saferpay by American Express CH - Processing of online transactions from Saferpay by American Express DE - Processing of online transactions from Saferpay by Giropay - Processing of online transactions from Saferpay by Intercard - Processing of online transactions from Saferpay by Klarna - Processing of online transactions from Saferpay by Worldline CH - Processing of online transactions from Saferpay by Worldline EU - Processing of online transactions from Saferpay by American Express SafeKey - Processing of online transactions from Saferpay by Saferpay Backoffice - Processing of online transactions from Saferpay by Diners ProtectBuy - Processing of online transactions from Saferpay via Mastercard ID Check - Processing of online transactions from Saferpay via VISA Secure - Processing of TWINT online transactions from Saferpay (SATA)

  3. monitoring Nov 12, 2025, 08:24 PM UTC

    We've seen some improvements in payments handling, but are still observing issues related to SCA/3DS redirects back to Saferpay. Transactions without additional user authentication seem to be processed again.

  4. monitoring Nov 12, 2025, 09:16 PM UTC

    Processing has been stable for the last 20 minutes. We'll continue monitoring the situation.

  5. resolved Nov 12, 2025, 09:39 PM UTC

    Saferpay 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 disruption: Wednesday, November 12, 2025, 21:40 CET We apologize for any inconvenience this has caused you.

Read the full incident report →

Notice October 20, 2025

Service disruption warning

Detected by Pingoru
Oct 20, 2025, 09:52 AM UTC
Resolved
Oct 21, 2025, 07:49 AM UTC
Duration
21h 56m
Affected: TrekkSoft BackofficeTrekkSoft APITrekkSoft Mobile App (mPOS)POS DeskTrekkSoft Website BuilderTrekkSoft Knowledge BasePayyo - Payment GatewayExperienceBank - Channel Manager
Timeline · 4 updates
  1. monitoring Oct 20, 2025, 09:52 AM UTC

    Our Amazon cloud hosting service AWS is experiencing disruptions across the globe. At the moment hundreds of companies/services using AWS are not working. Currently all TrekkSoft and ExperienceBank services appear to be working correctly but we remain vigilant for a possible downtime because of the Amazon issues this morning. If you have upcoming tours we advise you to download guest manifests for today/tomorrow including pick up points. We will continue to update you as the situation evolves.

  2. monitoring Oct 20, 2025, 10:42 AM UTC

    We are continuing to monitor for any further issues.

  3. monitoring Oct 20, 2025, 03:03 PM UTC

    Our Amazon cloud hosting service Amazon Web Services (AWS) continues to experience global disruptions, which are impacting hundreds of companies. Currently, all TrekkSoft and ExperienceBank services appear to be working correctly. However, we remain highly vigilant and prepared for possible downtime due to the ongoing AWS instability. If you have upcoming tours we advise you to download guest manifests for today/tomorrow including pick up points. Due to the ongoing situation on AWS, we will be postponing our planned maintenance from Tuesday 21st to Wednesday 22nd of October between 6-8AM CEST. We will continue to monitor the ongoing situation with AWS in case it will force us to shift our maintenance plans yet again and, provide updates as they become available.

  4. resolved Oct 21, 2025, 07:49 AM UTC

    We are pleased to confirm that the Amazon Web Services (AWS) service disruptions have been fully resolved. All TrekkSoft and ExperienceBank services remained stable throughout the event. Thank you for your patience.

Read the full incident report →

Critical October 14, 2025

Scheduled maintenance notice: 14th October 6:00 AM to 8:00 AM (CEST)

Detected by Pingoru
Oct 14, 2025, 04:00 AM UTC
Resolved
Oct 14, 2025, 10:39 AM UTC
Duration
6h 39m
Affected: TrekkSoft BackofficeTrekkSoft APITrekkSoft Mobile App (mPOS)POS DeskTrekkSoft Website Builder
Timeline · 6 updates
  1. monitoring Oct 14, 2025, 04:00 AM UTC

    To continue improving our product’s performance and deliver an even better experience, we’ll be performing essential scheduled maintenance. During this time, there may be temporary downtime, though we expect any interruption to last no longer than two hours. When: Tuesday, October 14th, 6:00 – 8:00 am CEST We understand how important uninterrupted access is, and we truly appreciate your patience and understanding as we make this upgrade. If you have any questions or concerns, please don’t hesitate to reach out to our support team.

  2. monitoring Oct 14, 2025, 06:23 AM UTC

    Our scheduled maintenance is taking a bit longer than expected. The process is still ongoing, and some services may remain unavailable for a short while longer. We’re actively working to complete the update and verify everything is running smoothly. We’ll share another update as soon as maintenance is complete. Thank you for your continued patience and understanding.

  3. monitoring Oct 14, 2025, 08:21 AM UTC

    To accelerate the backup process required for our upcoming upgrade, we will temporarily disable HTTP traffic for both our web app and API. During this time, the system will be unavailable, and you may encounter a gateway error (e.g., 502) when attempting to access it. Once the backup is complete, our team will need an additional 30 minutes to finalize the upgrade before restoring full access. We sincerely apologize for the inconvenience and appreciate your understanding as we work to improve system performance and reliability.

  4. monitoring Oct 14, 2025, 08:21 AM UTC

    To accelerate the backup process required for our upcoming upgrade, we will temporarily disable HTTP traffic for both our web app and API. During this time, the system will be unavailable, and you may encounter a gateway error (e.g., 502) when attempting to access it. Once the backup is complete, our team will need an additional 30 minutes to finalize the upgrade before restoring full access. We sincerely apologize for the inconvenience and appreciate your understanding as we work to improve system performance and reliability.

  5. monitoring Oct 14, 2025, 08:45 AM UTC

    The upgrade has been successfully completed, and HTTP traffic has been re-enabled, restoring full access to the system. Our team continues to monitor performance to ensure everything is running smoothly. Thank you again for your patience and understanding during today’s upgrade.

  6. resolved Oct 14, 2025, 10:39 AM UTC

    The scheduled maintenance has been completed. All functionalities are operational. Thank you again for your continued patience and understanding.

Read the full incident report →

Minor June 30, 2025

Incident registered

Detected by Pingoru
Jun 30, 2025, 08:06 PM UTC
Resolved
Jul 01, 2025, 07:07 AM UTC
Duration
11h
Affected: TrekkSoft BackofficeTrekkSoft APITrekkSoft Mobile App (mPOS)POS DeskTrekkSoft Website Builder
Timeline · 4 updates
  1. investigating Jun 30, 2025, 08:06 PM UTC

    We are currently experiencing intermittent system failures due to a database overload. As a result, you may encounter issues accessing the backoffice or receiving bookings online. Our team is actively working to resolve the issue, and we apologize for any inconvenience this may cause

  2. monitoring Jul 01, 2025, 05:55 AM UTC

    The system has been stable and fully operational since 10:15 PM CEST on June 30. We will continue to monitor the situation closely and provide a more detailed update later today.

  3. resolved Jul 01, 2025, 07:07 AM UTC

    The incident has been resolved, and all TrekkSoft functionalities are operating as expected. The intermittent failure was due to a database overload. A more detailed explanation of the incident will be shared as soon as possible. We sincerely apologize once again for any inconvenience caused.

  4. postmortem Jul 02, 2025, 01:19 PM UTC

    **Incident Date**: June 30th 2025 **Incident Duration**: Approximately 45 min **Affected Services**: TrekkSoft Backoffice ‌ **Incident Description:** On June 30th, around 20:00 CEST, our system went unresponsive, causing an intermittent downtime of approximately 45 min. This was due to a node’s failure that led to a boost in database connections which crashed the system. **Impact**: The unresponsiveness of approx 45 minutes resulted in issues accessing the Backoffice or receiving online bookings. **Resolution:** Once we identified the faulty part, the node was rebooted and this fixed the issue. **Preventive Measures:** We will be working on improving how quickly we can detect node failures and reviewing whether there is a need to add additional nodes.

Read the full incident report →

Major June 19, 2025

Registered issue: Booking notifications failure

Detected by Pingoru
Jun 19, 2025, 11:40 AM UTC
Resolved
Jun 19, 2025, 03:02 PM UTC
Duration
3h 22m
Affected: TrekkSoft API
Timeline · 3 updates
  1. investigating Jun 19, 2025, 11:40 AM UTC

    We are currently experiencing an issue with bookings notifications delivery. Notifications look delivered on our end but actually not received. Our developers are already investigating the root cause of the issue. We're sorry for any inconvenience this has caused and appreciate your patience as we work to fix it. We'll keep you updated on our progress.

  2. monitoring Jun 19, 2025, 12:42 PM UTC

    The notification emails that where not sent are being sent. The root cause of the issue was a problem with one of our systems. We will keep monitoring the situation

  3. resolved Jun 19, 2025, 03:02 PM UTC

    The incident has been resolved and booking notifications are being delivered as expected. As mentioned, the root cause seemed to be related to an issue in one of our systems. We sincerely apologize once again for any inconvenience caused.

Read the full incident report →

Notice June 12, 2025

Incident Summary – June 11th 2025

Detected by Pingoru
Jun 12, 2025, 08:06 AM UTC
Resolved
Jun 12, 2025, 08:06 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Jun 12, 2025, 08:06 AM UTC

    On June 11th, between 8:30 PM and 9:20 PM, our company experienced a targeted attack on several subdomains. During this time, key applications—including Admin Desk, POS Desk, Booking Widget, and Website Builder—were partially or fully unavailable. As a result, bookings were not being processed successfully. After an analysis by the engineering team, patterns for the attack as well as the source was identified and the IP address successfully blocked. Bookings originating from OTAs were subsequently reprocessed and delivered later that evening. As improvement steps, we plan to change our proxies used for subdomains and move them to a web application firewall. We apologize for any inconvenience this may have caused.

Read the full incident report →

Major April 16, 2025

Registered issue: Custom Domains not accessible

Detected by Pingoru
Apr 16, 2025, 07:09 PM UTC
Resolved
Apr 17, 2025, 07:08 AM UTC
Duration
11h 59m
Affected: TrekkSoft BackofficeTrekkSoft Website Builder
Timeline · 4 updates
  1. investigating Apr 16, 2025, 07:09 PM UTC

    We are currently experiencing issues with custom domains not being accessible. Therefore the option to book might be limited. 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.

  2. monitoring Apr 16, 2025, 08:36 PM UTC

    Custom domains are now accessible again. The root cause of the issue was an attack, which was now successfully being blocked. We will keep monitoring the situation.

  3. resolved Apr 17, 2025, 07:08 AM UTC

    The incident has been resolved, and all TrekkSoft functionalities are operating as expected since Wednesday, 22:16pm CEST. Our investigation revealed that an attack happened affecting custom domains. We aim to publish a detailed post-mortem later today. We sincerely apologize once again for any inconvenience caused.

  4. postmortem Apr 23, 2025, 03:10 PM UTC

    **Incident Date**: April 16th 2025 **Incident Duration**: Approximately 4 hours **Affected Services**: TrekkSoft Backoffice, TrekkSoft Website Builder ‌ **Incident Description:** On April 16th, around 18:00 CEST, our system was hit by an attack that caused unusually high network traffic. This led to about 4 hours of downtime, during which the system was unusable for those using a custom domain. **Impact**: The outage of approximately 4h affected the Backoffice and Website Builder sections of the system. **Resolution:** Once we identified the source of the attack, we blocked it to stop the issue. **Preventive Measures:** We are now working on strengthening our protection and improving how quickly we can detect and respond to similar problems in the future.

Read the full incident report →

Major January 31, 2025

Payment gateway issue

Detected by Pingoru
Jan 31, 2025, 08:40 AM UTC
Resolved
Jan 31, 2025, 09:21 AM UTC
Duration
41m
Affected: Payyo - Payment Gateway
Timeline · 2 updates
  1. investigating Jan 31, 2025, 08:40 AM UTC

    We want to inform you about an ongoing issue with the Payyo payment gateway. Currently, multiple errors are occurring when customers attempt to make payments on our hosted payment page (HPP), which may prevent transactions from being completed. We are in close contact with Payyo and will keep you updated on the situation. You can also check for real-time updates at http://status.payyo.ch/. We apologize for any inconvenience and appreciate your patience as we work to resolve this. If you have any questions or concerns, please don’t hesitate to reach out.

  2. resolved Jan 31, 2025, 09:21 AM UTC

    We're happy to inform you that the incident has been resolved. Payyo's platform is now stable, and customers can successfully proceed with payments again. We sincerely apologize for any inconvenience this may have caused.

Read the full incident report →

Minor December 2, 2024

Registered system slowdown December the 2nd 2024

Detected by Pingoru
Dec 02, 2024, 11:40 AM UTC
Resolved
Dec 03, 2024, 12:52 PM UTC
Duration
1d 1h
Affected: TrekkSoft BackofficeTrekkSoft Mobile App (mPOS)POS Desk
Timeline · 6 updates
  1. investigating Dec 02, 2024, 11:40 AM UTC

    We are currently experiencing a system delay that is causing a general slowdown of the system, this might result in error messages being shown and also might prevent some bookings from being placed. The affected areas include the booking widget, PoS desk and the mPoS mobile app. Our developers are actively investigating the root cause of this issue. We sincerely apologize for any inconvenience this may have caused and appreciate your patience as we work toward a resolution. If you have any questions or concerns, please feel free to reach out to us. We will keep you informed of any updates through our https://status.trekksoft.com page. If you haven't subscribed yet, we encourage you to do so to stay updated.

  2. investigating Dec 02, 2024, 12:37 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Dec 02, 2024, 12:39 PM UTC

    We have identified the root cause, applied a fix, and are currently monitoring the results.

  4. monitoring Dec 02, 2024, 05:27 PM UTC

    We are continuing to monitor for any further issues.

  5. resolved Dec 03, 2024, 12:52 PM UTC

    The incident has been resolved, and all TrekkSoft functionalities are operating as expected. Our investigation revealed that the system slowdown, which caused error messages during booking attempts and prevented some bookings from being processed, was triggered by an unexpected increase in system requests (e.g. a high volume of reporting requests). We have implemented a fix that appears to have resolved the issue and are actively exploring measures to prevent similar issues in the future. A detailed postmortem of the incident will be shared in the coming days. We sincerely apologize once again for any inconvenience caused.

  6. postmortem Dec 09, 2024, 02:14 PM UTC

    **Incident Date**: December 2nd 2024 **Incident Duration**: Approximately 5 hours \(intermittently\) **Affected Services**: TrekkSoft Backoffice, POS Desk, TrekkSoft Mobile App \(mPOS\) **Incident Description**: On Monday, Dec 2nd, at 12:13 PM CET, system slowness was reported, leading to an inability to process bookings. Earlier that morning, an alert indicated web response times exceeding 1.0 seconds for over 10 minutes. **Impact**: Investigation revealed it was caused by resource-heavy queries, making the system unresponsive. **Resolution**: This issue coincided with increased demand for year-end reports, likely contributing to the slowdown. Queues for reporting and scheduling were overloaded, with pending messages being gradually consumed after being moved to temporary queues. **Preventive Measures:** Further monitoring and optimization are ongoing to prevent similar issues.

Read the full incident report →

Critical October 9, 2024

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

Detected by Pingoru
Oct 09, 2024, 02:13 PM UTC
Resolved
Oct 09, 2024, 04:14 PM UTC
Duration
2h 1m
Affected: TrekkSoft BackofficeTrekkSoft Mobile App (mPOS)POS Desk
Timeline · 5 updates
  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.

Read the full incident report →