- 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
-
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.
-
monitoring Apr 28, 2026, 01:53 PM UTC
.
-
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 →
- Detected by Pingoru
- Apr 27, 2026, 07:50 AM UTC
- Resolved
- Apr 27, 2026, 07:50 AM UTC
- Duration
- —
Timeline · 1 update
-
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 →
- Detected by Pingoru
- Apr 20, 2026, 12:06 PM UTC
- Resolved
- Apr 20, 2026, 12:06 PM UTC
- Duration
- —
Timeline · 1 update
-
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 →
- 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
-
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 →
- 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
-
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.
-
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 →
- 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
-
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.
-
monitoring Mar 16, 2026, 12:41 PM UTC
System appears to be operational. Our engineering team will continue to monitor this from our end.
-
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 →
- 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
-
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.
-
investigating Feb 12, 2026, 07:51 PM UTC
We are continuing to investigate this issue, and will update every hour until it is resolved.
-
monitoring Feb 12, 2026, 08:18 PM UTC
Clusters are now healthy, and the backlog is being processed, we estimate 30 minutes.
-
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 →
- 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
-
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
-
investigating Jan 23, 2026, 04:37 AM UTC
We are continuing to investigate this issue.
-
resolved Jan 23, 2026, 07:01 AM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
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.
-
resolved Jan 16, 2026, 03:19 AM UTC
This incident has been resolved.
Read the full incident report →
Critical January 15, 2026 - 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
-
investigating Jan 15, 2026, 08:55 PM UTC
We are currently investigating this issue.
-
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.
-
resolved Jan 15, 2026, 09:30 PM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
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.
-
resolved Dec 10, 2025, 09:47 AM UTC
This incident has been resolved.
Read the full incident report →
Critical October 27, 2025 - 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
-
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
-
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 →
- 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
-
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.
-
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 - 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
-
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.
-
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.
-
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.
-
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.
-
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 →
Critical October 17, 2025 - Detected by Pingoru
- Oct 17, 2025, 07:44 AM UTC
- Resolved
- Oct 17, 2025, 12:32 PM UTC
- Duration
- 4h 48m
Affected: SEDNA - www.sednanetwork.com
Timeline · 9 updates
Read the full incident report →
- Detected by Pingoru
- Aug 29, 2025, 01:36 PM UTC
- Resolved
- Aug 29, 2025, 04:13 PM UTC
- Duration
- 2h 36m
Timeline · 4 updates
-
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
-
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
-
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
-
resolved Aug 29, 2025, 04:13 PM UTC
This incident has now been resolved
Read the full incident report →
- Detected by Pingoru
- May 15, 2025, 08:10 AM UTC
- Resolved
- May 16, 2025, 09:30 PM UTC
- Duration
- 1d 13h
Affected: SEDNA - www.sednanetwork.com
Timeline · 3 updates
-
investigating May 15, 2025, 08:54 AM UTC
We are currently investigating an issue impacting automatic mail forwarding in Exchange Online: Issue ID EX1072592. Affected users may experience delays or failures in receiving forwarded mail due to a fault within the Exchange system. Our Engineering team is actively investigating and closely monitoring the situation. We will provide further updates as more information becomes available
-
monitoring May 16, 2025, 09:26 AM UTC
Microsoft Exchange Online has completed the deployment of a code fix to address the underlying regression, which has resolved the issue for newly sent messages. They are now initiating a targeted recovery process for messages affected during the impacted timeframe and are actively working on a scalable solution to ensure full remediation: Issue ID EX1072592 As a result, some previously unforwarded emails may now begin to be delivered. Sedna customers may notice the arrival of older messages - potentially up to a few days old - as part of this recovery effort. We will continue to monitor the situation and provide updates as new information becomes available
-
resolved May 20, 2025, 10:29 AM UTC
Final Update on Exchange Online Forwarding Issue — Issue ID: EX1072592 Microsoft has confirmed that messages users attempted to forward between 2:04 PM UTC on May 11, 2025, and 5:00 AM UTC on May 16, 2025, will not be automatically replayed. Sedna users who wish to have emails from this period re-forwarded should contact Microsoft Support directly and reference Issue ID EX1072592. This will allow Microsoft to initiate a manual recovery of the affected messages.
Read the full incident report →
- Detected by Pingoru
- Apr 23, 2025, 11:58 AM UTC
- Resolved
- Apr 23, 2025, 12:13 PM UTC
- Duration
- 14m
Affected: SEDNA - www.sednanetwork.com
Timeline · 4 updates
-
investigating Apr 23, 2025, 11:58 AM UTC
An application outage has been identified and is affecting customers on Dublin 1 infrastructure. Affected users are unable to log into or access the platform. The issue is under investigation by engineering as an emergency.
-
identified Apr 23, 2025, 12:06 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Apr 23, 2025, 12:13 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Apr 23, 2025, 12:18 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 18, 2025, 07:40 AM UTC
- Resolved
- Apr 18, 2025, 09:20 AM UTC
- Duration
- 1h 39m
Affected: SEDNA - www.sednanetwork.com
Timeline · 3 updates
-
investigating Apr 18, 2025, 09:03 AM UTC
We are currently investigating this issue.
-
monitoring Apr 18, 2025, 09:05 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Apr 18, 2025, 09:27 AM UTC
This incident has been resolved and our Engineers are continuing to monitor the situation.
Read the full incident report →
- Detected by Pingoru
- Mar 03, 2025, 05:22 PM UTC
- Resolved
- Mar 03, 2025, 06:26 PM UTC
- Duration
- 1h 4m
Affected: SEDNA - www.sednanetwork.comSEDNA - Private Hosting
Timeline · 2 updates
-
investigating Mar 03, 2025, 05:35 PM UTC
An application outage has been identified and is affecting all customers on Dublin 3. Affected users are unable to log into or access the platform. The issue is under investigation by engineering as an emergency.
-
resolved Mar 03, 2025, 06:38 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 03, 2025, 01:34 PM UTC
- Resolved
- Mar 03, 2025, 06:38 PM UTC
- Duration
- 5h 3m
Affected: SEDNA - www.sednanetwork.comSEDNA - Private Hosting
Timeline · 3 updates
-
investigating Mar 03, 2025, 01:42 PM UTC
Customers on our Dublin 3 cluster are experiencing a temporary delay in receiving mail. The issue is under investigation by engineering as an emergency.
-
monitoring Mar 03, 2025, 01:53 PM UTC
A fix has been implemented, and mail ingest has been resolved. We are currently monitoring the delayed auto-tagging of the affected messages.
-
resolved Mar 03, 2025, 06:38 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 24, 2025, 12:40 PM UTC
- Resolved
- Feb 24, 2025, 12:40 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Feb 24, 2025, 01:12 PM UTC
All customers may have experienced a temporary delay in receiving mail between 12:15pm to 12:40pm UTC. The issue has now been fully resolved. We sincerely apologize for any inconvenience and appreciate your patience.
Read the full incident report →
- Detected by Pingoru
- Oct 28, 2024, 08:37 AM UTC
- Resolved
- Oct 28, 2024, 08:47 AM UTC
- Duration
- 10m
Timeline · 2 updates
-
identified Oct 28, 2024, 08:08 AM UTC
The issue has been identified and a fix is being implemented.
-
resolved Oct 28, 2024, 09:51 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 01, 2024, 12:47 AM UTC
- Resolved
- Oct 01, 2024, 01:37 AM UTC
- Duration
- 50m
Affected: SEDNA - www.sednanetwork.com
Timeline · 2 updates
-
identified Oct 01, 2024, 12:47 AM UTC
Users on our Virginia-1 cluster are currently experiencing slowness issues on Sedna. This includes some delays in outbound and inbound messages. Our Engineering Team is investigating this with the highest priority.
-
resolved Oct 01, 2024, 01:37 AM UTC
Our team has confirmed the issue is now resolved. Users should now be able to access Sedna without any performance issues.
Read the full incident report →
Notice September 26, 2024 - Detected by Pingoru
- Sep 26, 2024, 10:43 AM UTC
- Resolved
- Sep 27, 2024, 04:51 AM UTC
- Duration
- 18h 7m
Timeline · 4 updates
-
investigating Sep 26, 2024, 10:43 AM UTC
users may experience issues with connecting their calendars in Sedna.
-
identified Sep 26, 2024, 02:03 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Sep 26, 2024, 02:57 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Sep 27, 2024, 04:51 AM UTC
This incident has been resolved.
Read the full incident report →