SuperOffice incident
Login failures for some SuperOffice CRM Online customers
Resolved after 1 hour 32 minutes, on October 12, 2026.
Affected components: SuperOffice CRM Online – Sign-in Impact: Partial outage Start: 12 October 2026, 19:00 UTC (21:00 CEST) End: 12 October 2026, 20:32 UTC (22:32 CEST) Status: Resolved Resolved – 12 Oct 2026, 20:32 UTC From 19:00 to 20:32 UTC, a small number of customers hosted in our Sweden Central data center couldn't sign in to SuperOffice CRM Online. They saw the message "Sign-in could not be completed" with status 502. Users who were already signed in could keep working in most cases. Some background tasks that depend on the same service may have been delayed or failed during this time. What happened A supporting service that SuperOffice uses to complete sign-in runs on servers that scale up and down automatically. During a scheduled scaling in the evening, one of the servers failed to receive its configuration and couldn't take requests. As a result, sign-in requests for affected customers couldn't be complete How we fixed it Our operations team found that the affected server had not come into service correctly after it started. We restarted it, and sign-in has worked normally since 20:32 UTC (22:32 CEST). We have since added more capacity/redundancy to the affected service.
Update timeline
- resolved Oct 12, 2026, 09:08 PM UTC
Affected components: SuperOffice CRM Online – Sign-in Impact: Partial outage Start: 12 October 2026, 19:00 UTC (21:00 CEST) End: 12 October 2026, 20:32 UTC (22:32 CEST) Status: Resolved Resolved – 12 Oct 2026, 20:32 UTC From 19:00 to 20:32 UTC, a small number of customers hosted in our Sweden Central data center couldn't sign in to SuperOffice CRM Online. They saw the message "Sign-in could not be completed" with status 502. Users who were already signed in could keep working in most cases. Some background tasks that depend on the same service may have been delayed or failed during this time. What happened A supporting service that SuperOffice uses to complete sign-in runs on servers that scale up and down automatically. During a scheduled scaling in the evening, one of the servers failed to receive its configuration and couldn't take requests. As a result, sign-in requests for affected customers couldn't be complete How we fixed it Our operations team found that the affected server had not come into service correctly after it started. We restarted it, and sign-in has worked normally since 20:32 UTC (22:32 CEST). We have since added more capacity/redundancy to the affected service.
Your product runs on more than SuperOffice
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services