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.
Apr 28, 2026 - 11:30 BST
SEDNA - www.sednanetwork.com
Operational
90 days ago
99.99
% uptime
Today
SEDNA - Private Hosting
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Related
No incidents or maintenance related to this downtime.
Past Incidents
Apr 28, 2026
Unresolved incident: Application Outage: Customers are unable to access Sedna on Dublin 1 & 2.
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.
Apr 27, 08:50 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.
Apr 20, 13:06 BST