oneclick™ System status - Notice history

All systems operational

Notice history

View current status

May 2026

Apr 2026

No notices reported this month

Mar 2026

de.oneclick.services OTC Cluster service issues
ResolvedPartial outage70 hours 23 minutes
  • ResolvedUTC

    This incident has been resolved.

    We will follow with a a post mortem once we have competed our analysis.

  • MonitoringUTC

    We implemented a fix and are all services are up and running again.

    Customers might still experience occasional disconnects in the next couple of hours, if some services are restarted.

    We are continuing to monitor our systems and will post a post mortem of the incident here on our status page.

  • UpdateUTC

    We implemented a fix for de.oneclick.services (core services) - Login at de.oneclick.services is possible again. Due to work in progress customers might still experience disconnects.

    We are are still working on a fix for our streaming cluster (delivery services / datacenter) Germany - Magdeburg.

  • IdentifiedUTC

    We identified a problem with OTC ressources and are continuing to work on a fix for this incident.

  • InvestigatingUTC

    Currently OTC services are down which impact login and usage of our OTC Cluster de.oneclick.services.

    We are currently investigating this incident.

MAR23
Migration Streaming Cluster Switzerland - Zürich (23.03. - 27.03.2026)
CompletedMaintenance79 hours 29 minutes
Login issues on oneclick core international: Connection Error (Step 8 and 9)
ResolvedDegraded performance7 hours 46 minutes
  • PostmortemUTC

    Incident Report: Connection Error During App Launch

    Some users encountered an error in step 9 of the app launch process, which prevented the application from opening.

    Cause:

    The error was triggered by a brief unavailability of the underlying infrastructure components. As a result, an internal control service of the oneclick platform received incorrect status information about ongoing sessions and, based on this, made an incorrect decision that interrupted the affected connection. In the background, the affected connection requests were incorrectly redirected, which was only noticeable to the user as an error during app launch—without any visible redirection to the login page.

    Impact:

    Affected users were temporarily unable to launch their application and saw an error message in step 9. No data or sessions were compromised.

    Action taken:

    The error was not caused by a change resulting from a software update. We have thoroughly analysed the cause and are working on improving error handling at the affected location to ensure that such infrastructure errors do not impact ongoing user sessions in the future.

    We apologise for the inconvenience and are available to answer any questions you may have.

  • ResolvedUTC

    This incident has been resolved.

  • MonitoringUTC

    We have identified and resolved the issue. We are currently monitoring our systems to verify full functionality.

  • InvestigatingUTC

    Some users are experiencing login issues. We are currently investigating this incident.

Previous

Mar 2026 to May 2026

Next