Is there an Sedna Systems outage?
Sedna Systems status: Systems Active
Last checked: 2 minutes ago
Get notified about any outages, downtime or incidents for Sedna Systems and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: 2 minutes ago
Get notified about any outages, downtime or incidents for Sedna Systems and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Sedna Systems.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowOutlogger tracks the status of these components for Xero:
| Component | Status |
|---|---|
| SEDNA - Private Hosting | Active |
| SEDNA - www.sednanetwork.com | Active |
View the latest incidents for Sedna Systems and check for official updates:
Description: Incident Report **SEDNA Incident** **09 Sep 2021** ## **Summary** On September 9th 2021 between 08:34 UTC and 09:59 UTC users were unable to login to or use SEDNA. This was due to a failure in our database storage layer which caused our database to failover and the application failed to re-connect gracefully. ## **Why this happened** There was an unforeseen failure in our storage layer and our redundancy setup meant that we should have seen minimal downtime however this was not the case. Our application server's DNS cache did not allow for our application instances to reconnect to our failover database until we manually intervened. **Actions and opportunities for improvement** We internally reviewed this incident and have agreed to the following action: 1. Ensure application instances can recover gracefully from a database failover. - **IN PROGRESS** 2. Improve reporting and alerting so we know about these issues earlier - **IN PROGRESS**
Status: Postmortem
Impact: Critical | Started At: Sept. 9, 2021, 8:34 a.m.
Description: Incident Report **SEDNA Inaccessible** **27 July 2021** ## **Summary** On July 27, 2021 SEDNA was inaccessible to most users or those who were already logged in could not perform actions between the hours of 12:11-13:16 UTC. ## **Why this happened** Our team deployed a change to our frontend monitoring system that affected the loading and redirection when using SEDNA. **Actions and opportunities for improvement** 1. Rolled back the change to the frontend monitoring - **COMPLETE** 2. Resolved issues with the logging update - **COMPLETE** 3. Continuous improvement to testing prior to deployment - **IN PROGRESS**
Status: Postmortem
Impact: None | Started At: July 27, 2021, 12:11 p.m.
Description: Incident Report **SEDNA Inaccessible** **27 July 2021** ## **Summary** On July 27, 2021 SEDNA was inaccessible to most users or those who were already logged in could not perform actions between the hours of 12:11-13:16 UTC. ## **Why this happened** Our team deployed a change to our frontend monitoring system that affected the loading and redirection when using SEDNA. **Actions and opportunities for improvement** 1. Rolled back the change to the frontend monitoring - **COMPLETE** 2. Resolved issues with the logging update - **COMPLETE** 3. Continuous improvement to testing prior to deployment - **IN PROGRESS**
Status: Postmortem
Impact: None | Started At: July 27, 2021, 12:11 p.m.
Description: #### **20 Apr 2021** ### **Summary** On April 20th at approximately 16:26UTC SEDNA customers were unable to log in to a new SEDNA session. This was due to an unforeseen issue with our 3rd party authentication layer, Auth0. Customers who were currently in an active SEDNA session, and did not log out, were not impacted. At approximately 19:47UTC Auth0 had resolved the issue and SEDNA customers were able to log in to SEDNA. For customers that remained logged in, no other areas of the SEDNA platform were affected. ### **Why this happened** In speaking with Auth0 on the result of the login outage, “This service disruption was due purely to performance degradation on our internal platform systems, was not the result of any third-party service, and did not result in any data leakage. After investigation, we are confident that the disruption was not caused by, and did not result in, a security compromise.” ### **Actions and opportunities for improvement** Internally we reviewed the Auth0 incident report and our current implementation of Auth0 as our authentication layer. Upon review of all of the information at our disposal, we have concluded that this was an isolated incident and Auth0 has taken all the necessary precautions in order to avoid this problem in the future.
Status: Postmortem
Impact: None | Started At: April 20, 2021, 4:37 p.m.
Description: Incident Report **SEDNA Incident** **19 Feb 2021** ## **Summary** Between 11:30 UTC and 13:30 UTC users on SEDNA were experiencing issues with loading the message list and search. ## **Why this happened** On February 19th 2021 SEDNA experienced an unforeseen increase in load on our platform. Our attempts to increase capacity to our search platform unintentionally added temporary strain on an already overloaded service, which then caused the search platform to temporarily go down. **Actions and opportunities for improvement** Short intro if necessary 1. Internally reviewed our capacity requirements and made the necessary upgrades to the search platform **- COMPLETE** 2. Enhance our capacity monitoring strategy **- IN PROGRESS** 3. Review our search platform scaling strategy **- IN PROGRESS**
Status: Postmortem
Impact: Minor | Started At: Feb. 19, 2021, 11:35 a.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.
