Aug <var data-var='date'>18</var>, <var data-var='time'>19:27</var> BST Resolved - This incident has been resolved. Any messages that bounced during the incident can continue to be resent. Aug <var data-var='date'>18</var>, <var data-var='time'>19:00</var> BST Identified - The issue has been identified and a fix is being implemented. Aug <var data-var='date'>18</var>, <var data-var='time'>18:20</var> BST Investigating - An outage affecting Sedna’s mail egress services has been identified on our Virginia 1 clusters. Affected users are experiencing delays with sending or are unable to send mail. The issue is under investigation by engineering as an emergency.

Mail Delivery Outage: Some Customers in our Virginia 1 Cluster are Unable to Send Mail

Aug <var data-var='date'>17</var>, <var data-var='time'>20:38</var> BST Resolved - Any mail delayed during the outage has now been processed, and mail flow is operating normally. Aug <var data-var='date'>17</var>, <var data-var='time'>20:36</var> BST Monitoring - All queued messages have been redriven. Aug <var data-var='date'>17</var>, <var data-var='time'>20:10</var> BST Identified - The issue has been identified and a fix is being implemented. Aug <var data-var='date'>17</var>, <var data-var='time'>19:40</var> BST Investigating - An outage affecting Sedna’s mail egress and ingress services has been identified across multiple clusters. Affected users are experiencing delays in sending and receiving mail. The issue is under investigation by our Engineering team as an emergency.

Some Sedna users are experiencing delays in mail flow

Aug <var data-var='date'>16</var>, <var data-var='time'>10:00</var> BST Resolved - This incident has been resolved. Any messages that bounced during the incident can continue to be resent. Aug <var data-var='date'>16</var>, <var data-var='time'>08:00</var> BST Monitoring - Some customers are experiencing SPF bounces, this is a side effect of the mitigation and not a continuation of the issue. We are continuing to monitor closely before confirming full resolution. Any messages that bounced during the incident can continue to be resent. Aug <var data-var='date'>16</var>, <var data-var='time'>01:30</var> BST Investigating - The anti-spam filtering issue has been mitigated. Any messages that bounced during the incident can now be resent. Aug <var data-var='date'>15</var>, <var data-var='time'>23:30</var> BST Monitoring - The issue has been mitigated. We are monitoring closely and continuing to work with Microsoft. Any messages that bounced during the incident can now be resent. Aug <var data-var='date'>15</var>, <var data-var='time'>08:30</var> BST Investigating - We are seeing further reports of outbound emails to Microsoft 365 and Outlook recipients being rejected. The issue is ongoing and our engineering team is continuing to work with Microsoft and our email delivery provider on a resolution. Inbound mail remains unaffected. Bounced messages were not lost and can be resent once delivery is restored. Aug <var data-var='date'>15</var>, <var data-var='time'>01:30</var> BST Monitoring - The issue has been mitigated. We are monitoring closely and continuing to work with Microsoft. Any messages that bounced during the incident can now be resent. Aug <var data-var='date'>14</var>, <var data-var='time'>00:00</var> BST Investigating - We are investigating an issue affecting outbound email from Sedna to recipients hosted on Microsoft 365 and Outlook. Microsoft's anti-spam filtering is rejecting messages sent from a number of our outbound IP addresses, and senders are receiving bounce-back notifications (NDRs) for affected messages. Inbound mail is not affected, and delivery to recipients outside of Microsoft 365 / Outlook is unaffected. We will provide further updates as our investigation progresses.

Outbound Mail Delivery: Rejections for Some Microsoft 365 / Outlook Recipients

Jul <var data-var='date'>23</var>, <var data-var='time'>13:50</var> BST Resolved - An issue affecting Sedna’s mail ingress services in the Dublin 2 cluster has been resolved. During the incident, affected users were unable to receive incoming emails. Our engineering team identified and fixed the root cause, and mail flow has fully stabilized.

Mail Ingress Outage: Some Customers were Unable to Receive Mail

Jul <var data-var='date'>19</var>, <var data-var='time'>13:08</var> BST Resolved - Earlier today, some customers hosted on our European clusters experienced delays to email processing due to an infrastructure issue. This has been resolved, and all queued mail from this incident has now been processed. Jul <var data-var='date'>19</var>, <var data-var='time'>12:22</var> BST Identified - An outage affecting Sedna’s mail egress and ingress services has been identified on a specific infrastructure cluster (eu-west-1). Affected users are unable to send and receive mail. The issue is under investigation by engineering as an emergency.

Mail Ingress & Egress Outage: Some Unable to Send and Receive Mail (eu-west-1)

Jul <var data-var='date'>15</var>, <var data-var='time'>13:14</var> BST Resolved - This incident has been resolved. Jul <var data-var='date'>15</var>, <var data-var='time'>13:10</var> BST Investigating - Logins were temporarily disrupted for about an hour while we accelerated planned security maintenance. Service has been fully restored, and we have found no evidence of any impact to customer data

Auth Disruption: Accelerated Credential Upgrade

Jun <var data-var='date'> 4</var>, <var data-var='time'>16:10</var> BST Resolved - This incident has been resolved. Jun <var data-var='date'> 4</var>, <var data-var='time'>14:31</var> BST Monitoring - A fix has been implemented and we are monitoring the results. Jun <var data-var='date'> 4</var>, <var data-var='time'>12:05</var> BST Identified - The issue has been identified and a fix is currently being implemented. Sedna's Engineering team will continue to monitor the situation closely Jun <var data-var='date'> 4</var>, <var data-var='time'>09:45</var> BST Monitoring - 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. Jun <var data-var='date'> 3</var>, <var data-var='time'>16:50</var> BST Identified - We have identified the root cause of the issue and have implemented a fix. Jun <var data-var='date'> 3</var>, <var data-var='time'>16:05</var> BST Investigating - 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.

Platform Performance issues: Some customers are experiencing platform slowness

Jun <var data-var='date'> 3</var>, <var data-var='time'>16:45</var> BST Resolved - This incident has been resolved. Jun <var data-var='date'> 3</var>, <var data-var='time'>16:07</var> BST Investigating - 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.

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

May <var data-var='date'>20</var>, <var data-var='time'>08:10</var> BST Completed - The scheduled maintenance has been completed. May <var data-var='date'>20</var>, <var data-var='time'>07:10</var> BST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. May <var data-var='date'>11</var>, <var data-var='time'>13:29</var> BST Scheduled - We wanted to give you advance notice of a short period of scheduled maintenance affecting your Sedna environment on Wednesday, 20 May, beginning at 06:10 UTC. We've timed this for when your cluster is at its quietest to keep the impact as small as possible. Here's what to expect: At the start of the window, there will be a brief period of complete downtime – up to 4 minutes, though likely shorter. During those few minutes, Sedna will be unavailable, and users will see loading spinners rather than the usual interface. Following that, there may be a further period of up to 20 minutes where you notice some reduced performance or minor service disruption before everything is fully back to normal. No mail will be lost. Anything coming in during the window will be safely queued and delivered automatically once the maintenance is complete. No action is needed on your side. If you have any questions ahead of Wednesday, please don't hesitate to reach out.

Essential Maintenance on Virginia1

May <var data-var='date'> 7</var>, <var data-var='time'>01:30</var> BST Completed - The scheduled maintenance has been completed. May <var data-var='date'> 7</var>, <var data-var='time'>00:30</var> BST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. May <var data-var='date'> 1</var>, <var data-var='time'>21:32</var> BST Scheduled - To ensure continued performance and reliability, our Engineering team will be carrying out essential maintenance on the Exxon cluster on 6th May 2026 between 23:30 and 00:30 UCT. As part of this work, the actual downtime will be brief - a matter of minutes - and is most likely to occur towards the start of that window. During this time, users may experience difficulties accessing Sedna. Services will automatically recover once the maintenance is complete, and no data loss or configuration changes are expected. This maintenance is part of routine platform updates to improve performance, stability, and reliability. We appreciate your understanding and patience as we complete this work and continue to maintain our strong service standards.

Essential Maintenance on the Exxon cluster

May <var data-var='date'> 7</var>, <var data-var='time'>01:00</var> BST Completed - The scheduled maintenance has been completed. May <var data-var='date'> 7</var>, <var data-var='time'>00:00</var> BST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. May <var data-var='date'> 1</var>, <var data-var='time'>21:29</var> BST Scheduled - To ensure continued performance and reliability, our Engineering team will be carrying out essential maintenance on the ST cluster on 6th May 2026 between 23:00 and 00:00 UCT. As part of this work, the actual downtime will be brief - a matter of minutes - and is most likely to occur towards the start of that window. During this time, users may experience difficulties accessing Sedna. Services will automatically recover once the maintenance is complete, and no data loss or configuration changes are expected. This maintenance is part of routine platform updates to improve performance, stability, and reliability. We appreciate your understanding and patience as we complete this work and continue to maintain our strong service standards.

Essential Maintenance on the ST cluster

May <var data-var='date'> 7</var>, <var data-var='time'>00:30</var> BST Completed - The scheduled maintenance has been completed. May <var data-var='date'> 6</var>, <var data-var='time'>23:30</var> BST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. May <var data-var='date'> 1</var>, <var data-var='time'>21:28</var> BST Scheduled - To ensure continued performance and reliability, our Engineering team will be carrying out essential maintenance on the BP cluster on 6th May 2026 between 22:30 and 23:30 UCT. As part of this work, the actual downtime will be brief - a matter of minutes - and is most likely to occur towards the start of that window. During this time, users may experience difficulties accessing Sedna. Services will automatically recover once the maintenance is complete, and no data loss or configuration changes are expected. This maintenance is part of routine platform updates to improve performance, stability, and reliability. We appreciate your understanding and patience as we complete this work and continue to maintain our strong service standards.

Essential Maintenance on the BP cluster

May <var data-var='date'> 7</var>, <var data-var='time'>00:00</var> BST Completed - The scheduled maintenance has been completed. May <var data-var='date'> 6</var>, <var data-var='time'>23:00</var> BST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. May <var data-var='date'> 1</var>, <var data-var='time'>21:25</var> BST Scheduled - To ensure continued performance and reliability, our Engineering team will carry out essential maintenance on the Gunvor cluster on 6th May 2026 between 22:00 and 23:00 UCT. As part of this work, the actual downtime will be brief - a matter of minutes - and is most likely to occur towards the start of that window. During this time, users may experience difficulties accessing Sedna. Services will automatically recover once the maintenance is complete, and no data loss or configuration changes are expected. This maintenance is part of routine platform updates to improve performance, stability, and reliability. We appreciate your understanding and patience as we complete this work and continue to maintain our strong service standards.

Essential Maintenance on the Gunvor cluster

May <var data-var='date'> 6</var>, <var data-var='time'>23:30</var> BST Completed - The scheduled maintenance has been completed. May <var data-var='date'> 6</var>, <var data-var='time'>22:30</var> BST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. May <var data-var='date'> 1</var>, <var data-var='time'>21:23</var> BST Scheduled - To ensure continued performance and reliability, our Engineering team will carry out essential maintenance on the Oldendorff cluster on 6th May 2026 between 21:30 and 22:30 UCT. As part of this work, the actual downtime will be brief - a matter of minutes - and is most likely to occur towards the start of that window. During this time, users may experience difficulties accessing Sedna. Services will automatically recover once the maintenance is complete, and no data loss or configuration changes are expected. This maintenance is part of routine platform updates to improve performance, stability, and reliability. We appreciate your understanding and patience as we complete this work and continue to maintain our strong service standards.

Essential Maintenance on the Oldendorff cluster

May <var data-var='date'> 6</var>, <var data-var='time'>23:00</var> BST Completed - The scheduled maintenance has been completed. May <var data-var='date'> 6</var>, <var data-var='time'>22:00</var> BST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. May <var data-var='date'> 1</var>, <var data-var='time'>21:17</var> BST Scheduled - To ensure continued performance and reliability, our Engineering team will carry out essential maintenance on the Inchcape cluster on 6th May 2026, between 21:00 and 22:00 UCT. As part of this work, the actual downtime will be brief - a matter of minutes - and is most likely to occur towards the start of that window. During this time, users may experience difficulties accessing Sedna. Services will automatically recover once the maintenance is complete, and no data loss or configuration changes are expected. This maintenance is part of routine platform updates to improve performance, stability, and reliability. We appreciate your understanding and patience as we complete this work and continue to maintain our strong service standards.

Essential Maintenance on the Inchcape cluster

May <var data-var='date'> 6</var>, <var data-var='time'>22:30</var> BST Completed - The scheduled maintenance has been completed. May <var data-var='date'> 6</var>, <var data-var='time'>21:30</var> BST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. May <var data-var='date'> 1</var>, <var data-var='time'>21:14</var> BST Scheduled - To ensure continued performance and reliability, our Engineering team will carry out essential maintenance on the SaturnV cluster on 6th May 2026, between 2030 and 2130 UCT. As part of this work, the actual downtime will be brief - a matter of minutes - and is most likely to occur towards the start of that window. During this time, users may experience difficulties accessing Sedna. Services will automatically recover once the maintenance is complete, and no data loss or configuration changes are expected. This maintenance is part of routine platform updates to improve performance, stability, and reliability. We appreciate your understanding and patience as we complete this work and continue to maintain our strong service standards.

Essential Maintenance on SaturnV

May <var data-var='date'> 6</var>, <var data-var='time'>21:00</var> BST Completed - The scheduled maintenance has been completed. May <var data-var='date'> 6</var>, <var data-var='time'>20:00</var> BST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. May <var data-var='date'> 1</var>, <var data-var='time'>21:09</var> BST Scheduled - To ensure continued performance and reliability, our Engineering team will be carrying out essential maintenance on the Jera cluster on 6th May 2026 between 19:00 and 20:00 UCT. As part of this work, the actual downtime will be brief - a matter of minutes - and is most likely to occur towards the start of that window. During this time, users may experience difficulties accessing Sedna. Services will automatically recover once the maintenance is complete, and no data loss or configuration changes are expected. This maintenance is part of routine platform updates to improve performance, stability, and reliability. We appreciate your understanding and patience as we complete this work and continue to maintain our strong service standards.

Essential Maintenance on the Jera cluster

May <var data-var='date'> 6</var>, <var data-var='time'>18:00</var> BST Completed - The scheduled maintenance has been completed. May <var data-var='date'> 6</var>, <var data-var='time'>17:00</var> BST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. May <var data-var='date'> 1</var>, <var data-var='time'>20:54</var> BST Scheduled - To ensure continued performance and reliability, our Engineering team will carry out essential maintenance on the Rio Tinto cluster on 6th May 2026, between 1600 and 1700 UCT. As part of this work, the actual downtime will be brief - a matter of minutes - and is most likely to occur towards the start of that window. During this time, users may experience difficulties accessing Sedna. Services will automatically recover once the maintenance is complete, and no data loss or configuration changes are expected. This maintenance is part of routine platform updates to improve performance, stability, and reliability. We appreciate your understanding and patience as we complete this work and continue to maintain our strong service standards.

Essential Maintenance on Rio Tinto

Apr <var data-var='date'>28</var>, <var data-var='time'>19:09</var> BST Resolved - 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, with the application unavailable for a 15-minute period on Dublin 1 and two 15-minute periods on Dublin 2. In both cases, our resiliency measures ensured the application recovered automatically. 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. Apr <var data-var='date'>28</var>, <var data-var='time'>12:30</var> BST Monitoring - . Apr <var data-var='date'>28</var>, <var data-var='time'>11:30</var> BST Investigating - 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.

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

Apr <var data-var='date'>27</var>, <var data-var='time'>08:50</var> BST Resolved - 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.

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

Apr <var data-var='date'>20</var>, <var data-var='time'>13:06</var> BST Resolved - 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.

Mail Ingress & Egress Delay : Dublin2, Dublin3 clusters

Mar <var data-var='date'>23</var>, <var data-var='time'>10:45</var> GMT Resolved - 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.

Dublin2 Performance Issues

Mar <var data-var='date'>18</var>, <var data-var='time'>13:09</var> GMT Resolved - 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. Mar <var data-var='date'>18</var>, <var data-var='time'>10:48</var> GMT Investigating - 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.

Mail Delay : Dublin 2

Mar <var data-var='date'>16</var>, <var data-var='time'>13:16</var> GMT Resolved - 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. Mar <var data-var='date'>16</var>, <var data-var='time'>12:41</var> GMT Monitoring - System appears to be operational. Our engineering team will continue to monitor this from our end. Mar <var data-var='date'>16</var>, <var data-var='time'>12:37</var> GMT Investigating - 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.

Mail Ingress & Egress Delay : Global

Feb <var data-var='date'>12</var>, <var data-var='time'>20:38</var> GMT Resolved - This incident has been resolved, and all back logged messages have been processed Feb <var data-var='date'>12</var>, <var data-var='time'>20:18</var> GMT Monitoring - Clusters are now healthy, and the backlog is being processed, we estimate 30 minutes. Feb <var data-var='date'>12</var>, <var data-var='time'>19:51</var> GMT Update - We are continuing to investigate this issue, and will update every hour until it is resolved. Feb <var data-var='date'>12</var>, <var data-var='time'>18:48</var> GMT Investigating - 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.

Is Sedna Systems down?

Sedna Systems status is UP

Lastest published events

Mail Delivery Outage: Some Customers in our Virginia 1 Cluster are Unable to Send Mail

Some Sedna users are experiencing delays in mail flow

Outbound Mail Delivery: Rejections for Some Microsoft 365 / Outlook Recipients

Sedna Systems Services, Components and Regions

Recent Sedna Systems events

Mail Delivery Outage: Some Customers in our Virginia 1 Cluster are Unable to Send Mail

Some Sedna users are experiencing delays in mail flow

Outbound Mail Delivery: Rejections for Some Microsoft 365 / Outlook Recipients

Mail Ingress Outage: Some Customers were Unable to Receive Mail

Mail Ingress & Egress Outage: Some Unable to Send and Receive Mail (eu-west-1)

Auth Disruption: Accelerated Credential Upgrade