SuperOffice Outage History
SuperOffice is up right nowSuperOffice had 11 outages in the last 2 years totaling 128h 41m of downtime — averaging 0.5 incidents per month.
There were 11 SuperOffice outages since October 22, 2025 totaling 128h 41m of downtime. Each is summarised below — incident details, duration, and resolution information.
SuperOffice for Outlook Loading Issues
Timeline · 3 updates
- investigating Sep 04, 2026, 08:03 AM UTC
Microsoft has confirmed that their Microsoft 365 service degradation has been resolved. However, we have continued to receive reports of SuperOffice for Outlook remaining in a loading state in Microsoft Outlook and Outlook on the web, including new reports this morning. Our investigation now points to a brief, intermittent issue on SuperOffice's own infrastructure serving the add-in, rather than the previously suspected Microsoft service degradation. The issue appears to have resolved itself for affected users, but we are continuing to investigate the exact root cause. If you are still experiencing a loading screen, closing and reopening the SuperOffice for Outlook add-in should resolve it as a temporary workaround. We will provide a further update once we have confirmed the root cause.
- monitoring Sep 04, 2026, 10:00 AM UTC
We have identified the cause of SuperOffice for Outlook remaining in a loading state and have taken corrective action. The service has been stable for the past hour and we are continuing to monitor closely. We will provide a further update once we are confident the issue is fully resolved, or if the situation changes.
- resolved Sep 04, 2026, 02:05 PM UTC
We have seen no new occurrences of SuperOffice for Outlook remaining in a loading state since corrective action was taken, and feedback received from customers has been positive. Based on this, we consider this incident resolved. If you are still experiencing this issue, please contact SuperOffice Support so we can assist you directly.
A diminished system performance has been detected
Timeline · 3 updates
- investigating Sep 01, 2026, 11:33 AM UTC
We are currently investigating the incident that resulted in a diminished system performance.
- monitoring Sep 01, 2026, 12:18 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Sep 01, 2026, 12:37 PM UTC
This incident has been resolved.
Delayed email delivery (Mailgun → Service)
Timeline · 4 updates
- investigating Jul 24, 2026, 12:09 PM UTC
We're investigating a delay in email delivery from Mailgun to Service. Emails are not lost, just delayed. Update to follow.
- identified Jul 24, 2026, 12:50 PM UTC
Mailgun has identified the root cause of the delay affecting email delivery into Service and is now working on a fix. Emails are not lost delivery will resume normally once the fix is deployed on their end. We are monitoring the situation closely and will post another update once service is fully restored.
- monitoring Jul 24, 2026, 01:20 PM UTC
A fix has been implemented by Mailgun and is being monitored. Delayed messages are now being processed and should catch up shortly.
- resolved Jul 24, 2026, 01:50 PM UTC
This incident has been resolved.
Service unavailable
Timeline · 4 updates
- investigating Jul 22, 2026, 08:42 AM UTC
We are currently investigating availability issues with the SuperOffice CRM Cloud.
- identified Jul 22, 2026, 09:05 AM UTC
The issue has been identified and a fix is being implemented.
- resolved Jul 22, 2026, 09:41 AM UTC
This incident has been resolved.
- postmortem Jul 24, 2026, 10:58 AM UTC
On Wednesday 22 July 2026, between 10:25 and 11:31 CEST, SuperOffice CRM Online was unavailable for many customers: it was not possible to log in, and customers hosted on our old cloud platform could not reach the service at all. Users who were already logged in on our new cloud platform could continue working. The cause was an error made during routine cleanup at our old cloud platform's hosting provider: the DNS \(internet name resolution\) entries for SuperOffice's services on that platform were deleted by mistake, after being incorrectly assessed as no longer in use. The entries were restored within about 30 minutes of the cause being identified, and service recovered progressively as DNS caches refreshed - for most customers within the hour, for some up to an hour longer depending on their internet provider. No data was lost, no data was at risk, no personal data was affected, and the incident was not related to any SuperOffice software change
Authentication issues with Tryapp and Maillink (WebTools)
Timeline · 8 updates
Network disruption
Timeline · 1 update
- resolved Apr 14, 2026, 02:28 PM UTC
Network disruption that was causing intermittent availability issues with the SuperOffice CRM Cloud for some customers
CRM Script Customer Experience Issues Identified
Timeline · 3 updates
- investigating Feb 20, 2026, 11:31 AM UTC
We’ve identified a handful of customer‑experience issues related to CRM scripts. Investigation is in progress.
- identified Feb 20, 2026, 11:52 AM UTC
The issue has been identified and a fix is scheduled to roll out later today.
- resolved Feb 20, 2026, 06:39 PM UTC
This incident has been resolved.
Temporary Login Issue
Timeline · 2 updates
- investigating Jan 24, 2026, 10:33 AM UTC
Login via online.superoffice.com is temporarily unavailable. Please use id.superoffice.com to login.
- resolved Jan 24, 2026, 01:56 PM UTC
This incident has been resolved.
Email Delivery Issues via Mailgun
Timeline · 3 updates
- investigating Nov 13, 2025, 03:52 PM UTC
We are currently investigating an issue that may prevent some emails from being delivered to inboxes via Mailgun. Our provider is aware of the problem and is working to identify the cause
- monitoring Nov 13, 2025, 04:05 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Nov 13, 2025, 06:06 PM UTC
This incident has been resolved.
Degredation of sending and receiving e-mails.
Timeline · 4 updates
- investigating Oct 22, 2025, 11:27 AM UTC
We're currently investigating a degradation of our mail service.
- investigating Oct 22, 2025, 12:26 PM UTC
We are continuing to investigate the issue
- identified Oct 22, 2025, 12:51 PM UTC
The issue has been identified and a fix is being implemented.
- resolved Oct 22, 2025, 05:03 PM UTC
This incident has been resolved.