All Systems Operational

Uptime over the past 90 days. View historical uptime.
SuperOffice CRM Cloud Operational
Login services Operational
Sales & Marketing Client Operational
Service Client Operational
WebTools Operational
API and Apps Operational
SuperOffice CRM Cloud Mail Service Operational
mailgun Outbound Delivery Operational
mailgun Inbound email processing Operational
mailgun Events & Logs Operational
Central Services Operational
Support Portal Operational
Community Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Scheduled Maintenance

SuperOffice CRM Cloud software update. Oct 13, 2026 04:00-05:00 CEST

We are updating the SuperOffice CRM Cloud.
This release is a scheduled maintenance release of SuperOffice 12.

Release details :
Detailed information on the release including release notes, can be found here: (see link for details)

This is the first group of two to be upgraded. Expected downtime is up to 5 minutes between 04:00 and 05:00 cest.
The next group will be upgraded this upcoming Friday.
Posted on Oct 12, 2026 - 00:11 CEST

Oct 12, 2026

Login failures for some SuperOffice CRM Online customers
Resolved - 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.
Oct 12, 21:00 CEST

Oct 11, 2026

No incidents reported.

Oct 10, 2026

No incidents reported.

Oct 9, 2026

No incidents reported.

Oct 8, 2026

No incidents reported.

Oct 7, 2026

Applying the latest system updates.
Completed - The scheduled maintenance has been completed.
Oct 7, 23:00 CEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 7, 22:00 CEST
Scheduled - Applying the latest system updates is a crucial step in maintaining the security and performance of the service. During the update process, it's common for services to experience instability.
Oct 6, 16:33 CEST

Oct 6, 2026

No incidents reported.

Oct 5, 2026

No incidents reported.

Oct 4, 2026

No incidents reported.

Oct 3, 2026

No incidents reported.

Oct 2, 2026

No incidents reported.

Oct 1, 2026

No incidents reported.

Sep 30, 2026

No incidents reported.

Sep 29, 2026

No incidents reported.

Sep 28, 2026

No incidents reported.

Incident History Powered by Atlassian Statuspage