SuperOffice Outage History

Started Oct 21, 2026, 10:51 AM UTC· resolved Oct 22, 2026, 10:57 AM UTC

1. identified Oct 21, 2026, 10:51 AM UTC

   We are currently experiencing performance issues affecting some customers. The issue has been identified, and our team is working on a fix. We apologize for the inconvenience.

2. resolved Oct 22, 2026, 10:57 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 12, 2026, 07:00 PM UTC· resolved Oct 12, 2026, 08:32 PM UTC

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

Read the full incident report →

Started Sep 21, 2026, 09:10 AM UTC· resolved Sep 21, 2026, 10:42 AM UTC

1. investigating Sep 21, 2026, 09:10 AM UTC

   We are currently investigating the incident that is resulting in a diminished system performance for some of our customers.

2. monitoring Sep 21, 2026, 09:47 AM UTC

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

3. resolved Sep 21, 2026, 10:42 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 16, 2026, 10:34 AM UTC· resolved Sep 16, 2026, 11:33 AM UTC

1. investigating Sep 16, 2026, 10:34 AM UTC

   We are currently investigating an issue affecting logins to SuperOffice. Some customers may experience difficulties logging in to SuperOffice. Our team is actively investigating and we will share an update as soon as we have more information. We apologize for the inconvenience this may be causing.

2. monitoring Sep 16, 2026, 11:18 AM UTC

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

3. resolved Sep 16, 2026, 11:33 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 15, 2026, 10:17 AM UTC· resolved Sep 15, 2026, 01:25 PM UTC

1. investigating Sep 15, 2026, 10:17 AM UTC

   We are currently investigating an issue affecting logins to SuperOffice. Some customers may experience difficulties logging in to SuperOffice. Our team is actively investigating and we will share an update as soon as we have more information. We apologise for the inconvenience this may be causing.

2. monitoring Sep 15, 2026, 10:58 AM UTC

   A fix has been deployed for the issue affecting the login services and we are monitoring to confirm everything is back to normal. If you are still experiencing issues, please contact our support team and we will help you directly. Thank you for your patience.

3. resolved Sep 15, 2026, 01:25 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 04, 2026, 11:05 AM UTC· resolved Sep 04, 2026, 03:40 PM UTC

1. identified Sep 04, 2026, 11:05 AM UTC

   We're aware of delays affecting emails sent from SuperOffice - including login confirmation codes, account activation links, password reset emails, and CRM mailings - to recipients whose email is hosted on Microsoft 365 or Outlook.com (Outlook, Hotmail, Live addresses). This is caused by a known issue on Microsoft's side that is temporarily limiting how quickly they accept incoming mail from external senders, including us. It is affecting many senders across the internet, not just SuperOffice. What this means for you: Affected emails are delayed, not lost - our email provider automatically retries delivery over the following hours. If you're waiting on a confirmation code or activation email and it hasn't arrived after a few minutes, please wait and try again shortly rather than requesting a new one repeatedly, as this does not speed up delivery. No action is required on your end. We are actively monitoring the situation together with our email delivery provider and will update this page once Microsoft resolves the underlying issue.

2. identified Sep 04, 2026, 11:06 AM UTC

   We are continuing to monitor the scope of this issue.

3. identified Sep 04, 2026, 11:18 AM UTC

   We've identified the cause: this is a confirmed issue on Microsoft's side affecting delivery to Microsoft 365 / Outlook.com mailboxes, tracked internally by Microsoft as incident EX1467029. We've verified it affects multiple independent SuperOffice email systems (login/confirmation codes and Service/CRM emails) in the same way, confirming the cause is on Microsoft's end, not ours. Affected emails are delayed, not lost, and will be delivered automatically once Microsoft resolves EX1467029. No action is required on your end.

4. identified Sep 04, 2026, 01:11 PM UTC

   Microsoft has confirmed the cause: an anti-spam detection model in Exchange Online was incorrectly enforcing throttling against a subset of legitimate senders, including SuperOffice, causing "Server busy" delays for messages sent to and from external domains. Microsoft is rolling back the affected model and adding impacted sending IPs to an allow list as an interim mitigation. They estimate this rollout will complete within the next 30 minutes (as of their last update at 2:26 PM GMT+2), with their next update due by 4:30 PM GMT+2. We expect email delivery to Microsoft 365/Outlook.com recipients to recover as this rolls out. No action is required on your end — delayed emails will continue to be delivered automatically. We'll update this page once we see delivery return to normal or once Microsoft confirms resolution.

5. resolved Sep 04, 2026, 03:40 PM UTC

   Email delivery to Microsoft 365/Outlook.com recipients has returned to normal. We've confirmed no new "Server busy" (4.7.500) delivery failures for over an hour, and previously delayed emails are now being delivered successfully. This aligns with Microsoft's mitigation of the underlying anti-spam enforcement issue (EX1467029). We consider this incident resolved. If you continue to experience delivery delays to Microsoft 365/Outlook.com addresses, please contact support.

Read the full incident report →

Started Sep 04, 2026, 08:03 AM UTC· resolved Sep 04, 2026, 02:05 PM UTC

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

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

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

Read the full incident report →

Started Jul 24, 2026, 12:09 PM UTC· resolved Jul 24, 2026, 01:50 PM UTC

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

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

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

4. resolved Jul 24, 2026, 01:50 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 22, 2026, 08:42 AM UTC· resolved Jul 22, 2026, 09:41 AM UTC

1. investigating Jul 22, 2026, 08:42 AM UTC

   We are currently investigating availability issues with the SuperOffice CRM Cloud.

2. identified Jul 22, 2026, 09:05 AM UTC

   The issue has been identified and a fix is being implemented.

3. resolved Jul 22, 2026, 09:41 AM UTC

   This incident has been resolved.

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

Read the full incident report →

Started Jun 04, 2026, 09:08 AM UTC· resolved Jun 08, 2026, 01:42 PM UTC

1. investigating Jun 04, 2026, 09:08 AM UTC

   We are currently investigating an issue affecting authentication for Tryapp and Maillink (WebTools). Users may be unable to sign in or may experience interrupted sessions while using these services. Our team is actively working to identify the cause and restore normal service. We will provide an update as soon as we have more information. We apologies for any inconvenience this may cause.

2. identified Jun 04, 2026, 01:43 PM UTC

   We have identified an issue affecting authentication for Tryapp and Maillink (WebTools). Affected users may be unable to sign in or may experience interrupted sessions while using these services. What you can do: - Upgrade to WebTools 13, which resolves the issue. This is the recommended option for customers who are able to upgrade Our team is working on the hotfix. We will post a further update as soon as we have more information. We apologise for any inconvenience this may cause.

3. identified Jun 04, 2026, 05:48 PM UTC

   We are still working on the hotfix for the authentication issue affecting Tryapp and Maillink (WebTools). We will provide a new status update tomorrow. In the meantime, for customers who are able to upgrade, we continue to recommend upgrading to WebTools 13, which resolves the issue. (How To Update Webtools) Thank you for your patience. We apologise for any inconvenience this may cause.

4. identified Jun 05, 2026, 09:36 AM UTC

   We are still working on the fix for the authentication issue affecting Tryapp and Maillink (WebTools). Our team continues to investigate and is working toward a resolution. For customers who are able to upgrade, we continue to recommend upgrading to WebTools 13, which resolves the issue. (How To Update Webtools) We will share another update as soon as we have more information. Thank you for your patience.

5. identified Jun 05, 2026, 01:57 PM UTC

   We have good news on the authentication issue affecting Tryapp and Maillink (WebTools). Windows: We will roll out a fix tonight that resolves the issue for WebTools on Windows. MacLink: We need a little more time to resolve the issue for MacLink and are continuing to work on it. We will share another update as soon as we have more information. Thank you for your patience.

6. monitoring Jun 05, 2026, 09:34 PM UTC

   The fix for WebTools on Windows has been rolled out, and authentication for Tryapp and Maillink on Windows should now be working as expected. We are monitoring to confirm everything is stable. MacLink is still affected. A new version of MacLink will be released over the weekend, which resolves the issue. We will keep this incident open until the release is out and confirmed. If you are on Windows and still experience issues, please contact support. We will share another update once the new MacLink version is available. Thank you for your patience.

7. monitoring Jun 06, 2026, 05:45 PM UTC

   The authentication issue affecting Tryapp and Maillink (WebTools) has been fixed, and services are now operational on both Windows and MacLink. A new version of MacLink is now available in production and resolves the issue. All MacLink users need to upgrade to this version. MacLink will prompt you to update automatically and provide a download for you to install. If you continue to experience any issues after upgrading, please contact support. Thank you for your patience.

8. resolved Jun 08, 2026, 01:42 PM UTC

   Following the monitoring period, the authentication issue affecting Tryapp and Maillink (WebTools) is now fully resolved on both Windows and MacLink. All services are operating normally. Reminder: all MacLink users should be on the latest version released in production. If you have not yet upgraded, MacLink will prompt you to update and provide a download to install. A incident report will follow later this month. If you experience any further issues, please contact support. Thank you for your patience.

Read the full incident report →

Started Apr 13, 2026, 11:30 PM UTC· resolved Apr 13, 2026, 11:30 PM UTC

1. resolved Apr 14, 2026, 02:28 PM UTC

   Network disruption that was causing intermittent availability issues with the SuperOffice CRM Cloud for some customers

Read the full incident report →

Started Feb 20, 2026, 11:31 AM UTC· resolved Feb 20, 2026, 06:39 PM UTC

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

2. identified Feb 20, 2026, 11:52 AM UTC

   The issue has been identified and a fix is scheduled to roll out later today.

3. resolved Feb 20, 2026, 06:39 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 24, 2026, 10:33 AM UTC· resolved Jan 24, 2026, 01:56 PM UTC

1. investigating Jan 24, 2026, 10:33 AM UTC

   Login via online.superoffice.com is temporarily unavailable. Please use id.superoffice.com to login.

2. resolved Jan 24, 2026, 01:56 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 13, 2025, 03:52 PM UTC· resolved Nov 13, 2025, 06:06 PM UTC

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

2. monitoring Nov 13, 2025, 04:05 PM UTC

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

3. resolved Nov 13, 2025, 06:06 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 22, 2025, 11:27 AM UTC· resolved Oct 22, 2025, 05:03 PM UTC

1. investigating Oct 22, 2025, 11:27 AM UTC

   We're currently investigating a degradation of our mail service.

2. investigating Oct 22, 2025, 12:26 PM UTC

   We are continuing to investigate the issue

3. identified Oct 22, 2025, 12:51 PM UTC

   The issue has been identified and a fix is being implemented.

4. resolved Oct 22, 2025, 05:03 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 03, 2025, 08:39 AM UTC· resolved Sep 04, 2025, 08:16 AM UTC

1. investigating Sep 03, 2025, 08:39 AM UTC

   We are currently investigating this issue.

2. investigating Sep 03, 2025, 08:40 AM UTC

   We are continuing to investigate this issue.

3. identified Sep 03, 2025, 09:25 AM UTC

   We’ve identified the cause of the login issue affecting a small number of users. These users experience a problem where the login page appears to be stuck loading. A workaround has been found and is being implemented for affected users when our monitors detect it or by contacting support. A permanent fix will be rolled out during the evening.

4. monitoring Sep 03, 2025, 03:07 PM UTC

   Workaround has been implemented. A permanent fix will be rolled out tonight.

5. monitoring Sep 03, 2025, 09:33 PM UTC

   A fix has been implemented tonight. Login services are back to normal for all affected users.

6. resolved Sep 04, 2025, 08:16 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 27, 2025, 06:30 AM UTC· resolved Aug 27, 2025, 07:40 AM UTC

1. resolved Aug 27, 2025, 07:42 AM UTC

   Between 08:26–08:40 CET, users experienced degraded performance during login. Service began to recover at 08:36 CET and was fully back to normal by 08:40 CET. We apologize for the inconvenience caused.

Read the full incident report →

Started Aug 25, 2025, 08:29 AM UTC· resolved Aug 26, 2025, 07:38 AM UTC

1. identified Aug 25, 2025, 08:29 AM UTC

   We’ve identified a bottleneck in a network component within the datacenter that is causing periodic performance issues. A fix is scheduled for 22:00 tonight, which may result in up to 15 minutes of downtime. We apologize for the inconvenience and appreciate you're understanding as we work to improve system performance.

2. monitoring Aug 25, 2025, 08:21 PM UTC

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

3. resolved Aug 26, 2025, 07:38 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 05, 2025, 05:38 AM UTC· resolved Jul 05, 2025, 07:11 AM UTC

1. investigating Jul 05, 2025, 05:38 AM UTC

   We're currently experiencing issues with user logins. Our team is actively investigating and working to resolve the problem as quickly as possible. We’ll share updates as soon as we have more information.

2. identified Jul 05, 2025, 05:56 AM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring Jul 05, 2025, 05:56 AM UTC

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

4. monitoring Jul 05, 2025, 06:23 AM UTC

   To implement an additional fix, we will need to take the system offline temporarily. This will cause some downtime. We’re working to minimize the impact and will update once everything is back online

5. monitoring Jul 05, 2025, 06:41 AM UTC

   We are continuing to monitor for any further issues.

6. resolved Jul 05, 2025, 07:11 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 17, 2025, 09:32 AM UTC· resolved Mar 17, 2025, 05:11 PM UTC

1. investigating Mar 17, 2025, 09:32 AM UTC

   We are currently experiencing mail delivery issues in our solution, we are investigating the issue

2. investigating Mar 17, 2025, 10:12 AM UTC

   Our mail provider is still investigating the ongoing issue, : (https://status.mailgun.com)

3. identified Mar 17, 2025, 11:59 AM UTC

   The issue has been identified and a fix is being implemented. (https://status.mailgun.com)

4. monitoring Mar 17, 2025, 03:05 PM UTC

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

5. resolved Mar 17, 2025, 05:11 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 05, 2025, 09:51 AM UTC· resolved Mar 06, 2025, 11:18 AM UTC

1. investigating Mar 05, 2025, 09:51 AM UTC

   We are currently investigating this issue.

2. identified Mar 05, 2025, 09:58 AM UTC

   We are actively working with ISPs to resolve the current issues We also encourage our customers to contact their ISPs, as this appears to be an ISP-specific issue. Our investigation shows that superoffice.com domains can be resolved using Google or Cloudflare DNS resolvers, such as 1.1.1.1 and 8.8.8.8.

3. monitoring Mar 05, 2025, 01:04 PM UTC

   Several ISPs are keeping this issue open, but many users have found a workaround to access SuperOffice websites. We will continue monitoring the situation and will provide updates as they become available.

4. resolved Mar 06, 2025, 11:18 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 20, 2025, 10:29 AM UTC· resolved Feb 20, 2025, 03:34 PM UTC

1. investigating Feb 20, 2025, 10:29 AM UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

2. investigating Feb 20, 2025, 10:48 AM UTC

   There is currently an incident in Azure affecting document storage. We are actively monitoring the situation and will provide updates as more information becomes available.

3. identified Feb 20, 2025, 11:08 AM UTC

   The ongoing Azure incident is impacting the storage of documents and attachments, the retrieval of existing documents and attachments, and the sending of emails from the service for some customers. We are actively monitoring the situation and will provide updates as soon as more information becomes available.

4. monitoring Feb 20, 2025, 12:25 PM UTC

   Our monitoring indicates that the situation is gradually normalizing. However, Microsoft has not yet updated their status. We will continue to closely monitor the situation and provide further updates as needed.

5. monitoring Feb 20, 2025, 02:35 PM UTC

   We are continuing to monitor for any further issues.

6. resolved Feb 20, 2025, 03:34 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 14, 2025, 07:13 AM UTC· resolved Feb 14, 2025, 08:14 AM UTC

1. investigating Feb 14, 2025, 07:13 AM UTC

   Currently, we are in the process of investigating login issues. Should you encounter this problem, we kindly ask you to reach out to our support team for assistance.

2. monitoring Feb 14, 2025, 07:18 AM UTC

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

3. resolved Feb 14, 2025, 08:14 AM UTC

   The incident has been resolved. We will continue monitoring the solution and provide a postmortem at a later stage.

Read the full incident report →