SEDNA Outage History

SEDNA is up right now

SEDNA had 18 outages in the last 2 years totaling 86h 25m of downtime — averaging 0.7 incidents per month.

There were 18 SEDNA outages since August 29, 2025 totaling 86h 25m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.sedna.com

Major June 3, 2026

Application Outage: Some Customers unable to access Sedna Multiple Clusters Affected

Detected by Pingoru
Jun 03, 2026, 03:47 PM UTC
Resolved
Jun 04, 2026, 01:13 PM UTC
Duration
21h 26m
Affected: SEDNA - www.sednanetwork.com
Timeline · 3 updates
  1. investigating Jun 03, 2026, 03:47 PM UTC

    An application outage has been identified and is affecting some Sedna customers across infrastructure clusters. Affected users are unable to log into or access the platform. The issue is under investigation by engineering as an emergency.

  2. investigating Jun 04, 2026, 08:54 AM UTC

    We are currently investigating reports of degraded performance affecting some users on the Sedna platform. Affected users may experience slowness when navigating Sedna. Users are still able to log in and access the platform. Our engineering team is actively investigating the root cause as a priority. We will provide further updates as our investigation progresses. We apologise for any inconvenience caused.

  3. resolved Jun 04, 2026, 01:13 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 3, 2026

Platform Performance issues: Some customers are experiencing platform slowness

Detected by Pingoru
Jun 03, 2026, 03:05 PM UTC
Resolved
Jun 04, 2026, 03:10 PM UTC
Duration
1d
Timeline · 6 updates
  1. investigating Jun 04, 2026, 01:22 PM UTC

    Platform performance issues have been identified and are affecting some Sedna customers across different clusters. Affected users may experience slowness when accessing the platform. The issue is under investigation by engineering as an emergency.

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

    We have identified the root cause of the issue and have implemented a fix.

  3. monitoring Jun 04, 2026, 01:25 PM UTC

    We are currently investigating reports of degraded performance affecting some users on the Sedna platform. Affected users may experience slowness when navigating Sedna. Users are still able to log in and access the platform. Our engineering team is actively investigating the root cause as a priority. We will provide further updates as our investigation progresses. We apologise for any inconvenience caused.

  4. identified Jun 04, 2026, 01:29 PM UTC

    The issue has been identified and a fix is currently being implemented. Sedna's Engineering team will continue to monitor the situation closely

  5. monitoring Jun 04, 2026, 01:31 PM UTC

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

  6. resolved Jun 05, 2026, 09:57 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 28, 2026

Application Outage: Customers are unable to access Sedna on Dublin 1 & 2

Detected by Pingoru
Apr 28, 2026, 10:30 AM UTC
Resolved
Apr 28, 2026, 06:09 PM UTC
Duration
7h 38m
Affected: SEDNA - www.sednanetwork.com
Timeline · 3 updates
  1. investigating Apr 28, 2026, 10:30 AM UTC

    An application outage was identified affecting some Sedna customers on our Dublin 1 and Dublin 2 clusters between 7:30am and 08:00 am UTC and 9:20am and 09:35 and UTC. During this time, impacted users were unable to log in or access the platform. The issue is being treated as an emergency by our engineering team while service is being restored. We are continuing to monitor the platform closely to ensure stability and will keep you updated as the investigation progresses.

  2. monitoring Apr 28, 2026, 01:53 PM UTC

    .

  3. resolved Apr 28, 2026, 06:09 PM UTC

    An initial investigation has been completed into the outage that affected some Sedna customers on our Dublin 1 and Dublin 2 clusters earlier today. The disruption was traced to a capacity issue that prevented impacted users from logging in or accessing the platform. As a precautionary measure, we have adjusted scaling policies on both clusters and temporarily disabled a non-essential feature to reduce load. Our engineering team is continuing the root cause analysis and will implement further improvements to prevent recurrence.

Read the full incident report →

Major April 27, 2026

Application Outage: Customers are unable to access Sedna on Dublin 1

Detected by Pingoru
Apr 27, 2026, 07:50 AM UTC
Resolved
Apr 27, 2026, 07:50 AM UTC
Duration
Timeline · 1 update
  1. resolved Apr 27, 2026, 08:29 AM UTC

    An application outage was identified affecting some Sedna customers on our Dublin 2 cluster. During this time, impacted users were unable to log in or access the platform. The issue was treated as an emergency by our engineering team and has now been resolved. A root cause analysis is currently underway, and Sedna’s engineering team is actively investigating to determine the underlying cause and prevent recurrence.

Read the full incident report →

Minor April 20, 2026

Mail Ingress & Egress Delay : Dublin2, Dublin3 clusters

Detected by Pingoru
Apr 20, 2026, 12:06 PM UTC
Resolved
Apr 20, 2026, 12:06 PM UTC
Duration
Timeline · 1 update
  1. resolved Apr 20, 2026, 12:06 PM UTC

    This morning (between approximately 10:10 and 10:40 UTC), we experienced a performance degradation of email ingress and egress in our Dublin2 and Dublin3 clusters. This issue was brought to our attention by automated alerting built on our internal observability tooling. Application scaling policies increased capacity during this period, reducing its overall length. This was a repeated issue, seen previously on 16th March, caused by abnormally expensive processing of a set of malformed emails sent to a large number of recipients. Mitigation steps we have taken so far have unfortunately not been sufficient to avoid a recurrence, and as such, we will continue to investigate to improve resilience.

Read the full incident report →

Notice March 23, 2026

Dublin2 Performance Issues

Detected by Pingoru
Mar 23, 2026, 10:45 AM UTC
Resolved
Mar 23, 2026, 10:45 AM UTC
Duration
Affected: SEDNA - www.sednanetwork.com
Timeline · 1 update
  1. resolved Mar 23, 2026, 10:45 AM UTC

    The issue causing elevated CPU load in the Dublin2 cluster has been identified and mitigated. We have implemented measures to prevent recurrence. All services have resumed and should now be operating normally.

Read the full incident report →

Minor March 18, 2026

Mail Delay : Dublin 2

Detected by Pingoru
Mar 18, 2026, 10:48 AM UTC
Resolved
Mar 18, 2026, 01:09 PM UTC
Duration
2h 21m
Affected: SEDNA - www.sednanetwork.com
Timeline · 2 updates
  1. investigating Mar 18, 2026, 10:48 AM UTC

    We are investigating reports of delayed mail between 10:20 am and 10:35 am GMT. We have implemented a corrective measure and are seeing normal mail delivery. Our engineering team is actively investigating the cause. We will provide further updates as soon as more information becomes available.

  2. resolved Mar 18, 2026, 01:09 PM UTC

    Correct measures was put in place once delay was noted by our engineers. This has been monitored and we can confirm that service has been restored and is working as expected.

Read the full incident report →

Minor March 16, 2026

Mail Ingress & Egress Delay : Global

Detected by Pingoru
Mar 16, 2026, 12:37 PM UTC
Resolved
Mar 16, 2026, 01:16 PM UTC
Duration
38m
Affected: SEDNA - www.sednanetwork.com
Timeline · 3 updates
  1. investigating Mar 16, 2026, 12:37 PM UTC

    We are currently investigating an issue affecting mail ingress and egress globally. From 11:30 to 12:00 UTC some customers may have experienced delays or disruptions in email processing. Our engineering team is actively investigating the cause. We will provide further updates as soon as more information becomes available.

  2. monitoring Mar 16, 2026, 12:41 PM UTC

    System appears to be operational. Our engineering team will continue to monitor this from our end.

  3. resolved Mar 16, 2026, 01:16 PM UTC

    Earlier today (from 11:31 to 12:09 UTC) we experienced a performance degradation of email ingress and egress globally across tenants in our public clusters. This was caused by abnormally expensive processing of a set of malformed emails sent to a large number of recipients. We will continue to monitor and investigate how our systems can be updated to improve resilience.

Read the full incident report →

Major February 12, 2026

Mail Ingress & Egress Outage: Some Customers in EU Clusters unable to Send and Receive Mail

Detected by Pingoru
Feb 12, 2026, 06:48 PM UTC
Resolved
Feb 12, 2026, 08:38 PM UTC
Duration
1h 49m
Affected: SEDNA - www.sednanetwork.com
Timeline · 4 updates
  1. investigating Feb 12, 2026, 06:48 PM UTC

    An outage affecting Sedna’s mail egress and ingress services has been identified on specific infrastructure EU clusters. Affected users are unable to send and receive mail. The issue is under investigation by engineering as an emergency.

  2. investigating Feb 12, 2026, 07:51 PM UTC

    We are continuing to investigate this issue, and will update every hour until it is resolved.

  3. monitoring Feb 12, 2026, 08:18 PM UTC

    Clusters are now healthy, and the backlog is being processed, we estimate 30 minutes.

  4. resolved Feb 12, 2026, 08:38 PM UTC

    This incident has been resolved, and all back logged messages have been processed

Read the full incident report →

Major January 22, 2026

Microsoft Outage

Detected by Pingoru
Jan 22, 2026, 09:00 PM UTC
Resolved
Jan 23, 2026, 07:01 AM UTC
Duration
10h
Affected: SEDNA - www.sednanetwork.com
Timeline · 3 updates
  1. investigating Jan 23, 2026, 04:36 AM UTC

    Microsoft Outage: Degraded Service Microsoft is currently experiencing degraded service functionality. As a result, recipients using Microsoft mailboxes may not receive emails, and messages sent from Sedna may result in NDRs. Updates on Microsoft’s Service Health Status can be found here: https://status.cloud.microsoft/m365

  2. investigating Jan 23, 2026, 04:37 AM UTC

    We are continuing to investigate this issue.

  3. resolved Jan 23, 2026, 07:01 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice January 15, 2026

Mail Flow Delay: Virginia1 Cluster

Detected by Pingoru
Jan 15, 2026, 10:45 PM UTC
Resolved
Jan 16, 2026, 12:15 AM UTC
Duration
1h 29m
Affected: SEDNA - www.sednanetwork.com
Timeline · 2 updates
  1. investigating Jan 16, 2026, 03:16 AM UTC

    An outage affecting Sedna’s mail egress and egress services has been identified across our Virginia1 Cluster. Affected users may experience delays with sending and receiving mail. The issue is under investigation by Sedna's Engineering team as an emergency.

  2. resolved Jan 16, 2026, 03:19 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical January 15, 2026

Mail Ingress & Egress Outage: Customers in EU Clusters unable to Send and Receive Mail

Detected by Pingoru
Jan 15, 2026, 08:55 PM UTC
Resolved
Jan 15, 2026, 09:30 PM UTC
Duration
35m
Affected: SEDNA - www.sednanetwork.com
Timeline · 3 updates
  1. investigating Jan 15, 2026, 08:55 PM UTC

    We are currently investigating this issue.

  2. investigating Jan 15, 2026, 08:56 PM UTC

    An outage affecting Sedna’s mail egress and ingress services has been identified on specific infrastructure EU clusters. Affected users are unable to send and receive mail. The issue is under investigation by engineering as an emergency.

  3. resolved Jan 15, 2026, 09:30 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 10, 2025

Mail Ingress & Egress Outage: Customers in our EU Cluster unable to Send and Receive Mail

Detected by Pingoru
Dec 10, 2025, 09:39 AM UTC
Resolved
Dec 10, 2025, 09:47 AM UTC
Duration
7m
Affected: SEDNA - www.sednanetwork.com
Timeline · 2 updates
  1. monitoring Dec 10, 2025, 09:39 AM UTC

    Estimated impact window: 08:40–09:05 UTC During this time, mail could not be sent or received in our EU cluster. Service has since fully recovered, and the system is currently healthy. All incoming mail from the affected window has been successfully reprocessed and no messages were lost. Any outbound messages that could not be delivered would have generated an NDR; if you received one, please resend the message. We are investigating the root cause and will provide further updates. In the interim, if you notice any mail delivery failures or unexpected behaviour, please let us know.

  2. resolved Dec 10, 2025, 09:47 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical October 27, 2025

Mail Creation and Delivery Issues on Dublin2 cluster

Detected by Pingoru
Oct 27, 2025, 10:38 AM UTC
Resolved
Oct 27, 2025, 10:41 AM UTC
Duration
2m
Affected: SEDNA - www.sednanetwork.com
Timeline · 2 updates
  1. identified Oct 27, 2025, 10:38 AM UTC

    Dear Customers, We’re aware that some may currently be experiencing issues creating and receiving new mail. Our engineering team is actively investigating and working to resolve the issue as quickly as possible. We’ll provide updates as the engineering team progress on resolving the issue. Next update estimated in 15 mins

  2. resolved Oct 27, 2025, 10:41 AM UTC

    Dear Customers, Mail delivery services have now been restored, and new mail is flowing as expected. Thank you for your patience

Read the full incident report →

Minor October 20, 2025

Platform performance issues: Customers experiencing autotagging slowness in Virginia1 and default clusters

Detected by Pingoru
Oct 20, 2025, 04:44 PM UTC
Resolved
Oct 20, 2025, 09:00 PM UTC
Duration
4h 16m
Affected: SEDNA - www.sednanetwork.com
Timeline · 2 updates
  1. monitoring Oct 20, 2025, 04:44 PM UTC

    Platform performance issues have been identified and are affecting some Sedna customers across infrastructure clusters (virginia1 and default). Affected users may see slowness and/or spinners intermittently when accessing the platform, specifically impacting auto-tagging functionality. The issue is under investigation by engineering as an emergency and is related to the AWS incident from earlier today.

  2. resolved Oct 21, 2025, 07:09 AM UTC

    Dear Customer, We're pleased to inform you that the latest update from AWS is that the issue has now been completely resolved. https://health.aws.amazon.com/health/status All systems are working as expected and all services should be back to full operational efficiency. Thank you for your patience and understanding

Read the full incident report →

Critical October 20, 2025

Mail Flow Issue related to AWS outage - US-EAST-1

Detected by Pingoru
Oct 20, 2025, 07:39 AM UTC
Resolved
Oct 20, 2025, 12:06 PM UTC
Duration
4h 27m
Affected: SEDNA - www.sednanetwork.com
Timeline · 5 updates
  1. investigating Oct 20, 2025, 07:39 AM UTC

    Dear Customers, We’re currently experiencing a mail flow issue, which is causing emails to queue and may also impact incoming mail delivery. Our engineering team is actively investigating and working to resolve the issue as quickly as possible. We’ll provide updates as more information becomes available. Thank you for your patience and understanding.

  2. identified Oct 20, 2025, 08:11 AM UTC

    Dear Customers, We've identified that the widespread mail flow issue affecting some customers is related to an ongoing AWS outage impacting our infrastructure. As a result, mail delivery and processing may be delayed. Our engineering team is closely monitoring the situation and working with AWS to restore normal service as soon as possible. We’ll share further updates as more information becomes available.

  3. identified Oct 20, 2025, 09:14 AM UTC

    Dear Customers, The mail flow issue affecting some customers remains ongoing and is linked to a wider AWS outage impacting multiple services. Our engineers continue to monitor the situation closely and are working to restore full functionality when AWS systems recover. For more information, you can track updates directly from AWS via their status page: https://health.aws.amazon.com/health/status We’ll continue to provide updates as they become available. Thank you for your continued patience and understanding.

  4. monitoring Oct 20, 2025, 10:47 AM UTC

    Dear Customers, AWS has confirmed that the underlying issue has been mitigated, and most services are operating normally again. Some throttling and backlogs are still being cleared, particularly affecting the US-EAST-1 region, which may cause intermittent delays or errors. Our team continues to monitor the situation closely and will provide further updates as AWS progresses toward full resolution. Thank you for your patience and understanding.

  5. resolved Oct 20, 2025, 12:06 PM UTC

    Dear Customers, We’re pleased to confirm that all services are now operating normally. The earlier disruption, which was linked to an AWS outage in the has been fully resolved. Our systems are stable, and mail flow and processing have returned to normal. We’ll continue to monitor closely to ensure everything remains stable. Thank you for your patience and understanding throughout this incident.

Read the full incident report →

Minor August 29, 2025

Microsoft Incident - Users may experience delays sending and receiving email messages

Detected by Pingoru
Aug 29, 2025, 01:36 PM UTC
Resolved
Aug 29, 2025, 04:13 PM UTC
Duration
2h 36m
Timeline · 4 updates
  1. investigating Aug 29, 2025, 01:36 PM UTC

    As per Microsoft: ID: EX1144276 Issue type: Incident Status: Service Degradation Impacted services: Exchange Online Details: Title: Users may experience delays sending and receiving email messages User impact: Users may experience delays sending and receiving email messages. Current status: We're reviewing service monitoring telemetry to isolate the source of the issue and establish a fix. Scope of impact: Some users who are located in Europe attempting to send or receive Exchange Online email messages may be impacted. Next update by: Friday, August 29, 2025, at 2:30 PM UTC

  2. investigating Aug 29, 2025, 01:38 PM UTC

    Aug 29, 2025, 4:38 PM GMT+2 The new throttling rule has successfully been deployed. We’ve received confirmation from some of the previously affected users that they can now send and receive email. Additionally, our telemetry shows that the new throttling rule is having the desired effect and providing relief. Next update by: Friday, August 29, 2025 at 6:00 PM GMT+2

  3. investigating Aug 29, 2025, 04:12 PM UTC

    Aug 29, 2025, 5:38 PM GMT+2 After monitoring the service and receiving confirmation from previously affected users, we’ve confirmed that impact has been remediated. The service will now resume periodic attempts to deliver emails that were sent during the impacted period. Issue details Issue ID: EX1144276 Affected services: Exchange Online Status: Service restored Start time: Aug 29, 2025, 12:36 PM GMT+2 End time: Aug 29, 2025, 5:10 PM GMT+2 Issue type: Incident

  4. resolved Aug 29, 2025, 04:13 PM UTC

    This incident has now been resolved

Read the full incident report →