Is there an Sedna Systems outage?
Sedna Systems status: Systems Active
Last checked: 6 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: 6 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** **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.
Description: **SEDNA Incident** **27 Jan 2021** ### **Summary** On January 27th, 2021 at approximately 1648 PST \(0048 UTC\) outbound messages from SEDNA were halted and sent messages were being returned with a non delivery report stating an issue with the SMTP API header. Our Engineering team deployed an update as a hotfix for the issue which restored service at approximately 1723 PST \(0123 UTC\) resulting in a ~35 minute period of dropped messages. ### **Why this happened** Our third-party mail delivery service experienced an issue with how they handle a specific string in the SMTP API that handles bounce and blocked email suppression lists. This resulted in outbound messages from SEDNA being dropped until our team deployed the hotfix. Once our third-party provider resolved the issue, we reverted our hotfix to restore our previous suppression list management via the SMTP API. ### **Actions and opportunities for improvement** A key takeaway from this issue is that our delivery pipeline prevented us from deploying our hotfix sooner. 1. Review delivery pipeline to improve deployment speeds - **IN PROGRESS**
Status: Postmortem
Impact: Critical | Started At: Jan. 28, 2021, 12:39 a.m.
Description: **SEDNA Incident** **27 Jan 2021** ### **Summary** On January 27th, 2021 at approximately 1648 PST \(0048 UTC\) outbound messages from SEDNA were halted and sent messages were being returned with a non delivery report stating an issue with the SMTP API header. Our Engineering team deployed an update as a hotfix for the issue which restored service at approximately 1723 PST \(0123 UTC\) resulting in a ~35 minute period of dropped messages. ### **Why this happened** Our third-party mail delivery service experienced an issue with how they handle a specific string in the SMTP API that handles bounce and blocked email suppression lists. This resulted in outbound messages from SEDNA being dropped until our team deployed the hotfix. Once our third-party provider resolved the issue, we reverted our hotfix to restore our previous suppression list management via the SMTP API. ### **Actions and opportunities for improvement** A key takeaway from this issue is that our delivery pipeline prevented us from deploying our hotfix sooner. 1. Review delivery pipeline to improve deployment speeds - **IN PROGRESS**
Status: Postmortem
Impact: Critical | Started At: Jan. 28, 2021, 12:39 a.m.
Description: **24 November 2020** ## **Summary** On November 24th 2020 between the hours 8am GMT and 10am GMT SEDNA was inaccessible to some users and some users were experiencing degraded services. ## **Why this happened** SEDNA relies on a cloud provider for our search functionality and they began experiencing difficulties which in turn had an impact on SEDNA’s ability to load messages and function as expected. One node in a regional search cluster became inaccessible in a way that led to inconsistent and delayed responses. We worked with AWS to resolve the problem and in the mean-time initiated a redeployment of the search cluster - that redeployment succeeded and service was fully restored. **Actions and opportunities for improvement** 1. Investigate root cause with AWS - **IN PROGRESS** 2. Improve degraded search mode to mitigate reliance on the search service - **IN PROGRESS** 3. Enhanced alarms around search service - **COMPLETED**
Status: Postmortem
Impact: Critical | Started At: Nov. 24, 2020, 8:25 a.m.
Description: **24 November 2020** ## **Summary** On November 24th 2020 between the hours 8am GMT and 10am GMT SEDNA was inaccessible to some users and some users were experiencing degraded services. ## **Why this happened** SEDNA relies on a cloud provider for our search functionality and they began experiencing difficulties which in turn had an impact on SEDNA’s ability to load messages and function as expected. One node in a regional search cluster became inaccessible in a way that led to inconsistent and delayed responses. We worked with AWS to resolve the problem and in the mean-time initiated a redeployment of the search cluster - that redeployment succeeded and service was fully restored. **Actions and opportunities for improvement** 1. Investigate root cause with AWS - **IN PROGRESS** 2. Improve degraded search mode to mitigate reliance on the search service - **IN PROGRESS** 3. Enhanced alarms around search service - **COMPLETED**
Status: Postmortem
Impact: Critical | Started At: Nov. 24, 2020, 8:25 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.
