Is Sedna Systems Down Right Now? Check if there is a current outage ongoing.

The scheduled maintenance has been completed.

We will be undergoing scheduled maintenance on 21 May at 20:00 BST, leading to a brief downtime of approximately 60 seconds.

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.

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

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

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

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.

This incident has been resolved and our Engineers are continuing to monitor the situation.

A fix has been implemented and we are monitoring the results.

We are currently investigating this issue.

This incident has been resolved.

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.

This incident has been resolved.

A fix has been implemented, and mail ingest has been resolved. We are currently monitoring the delayed auto-tagging of the affected messages.

Customers on our Dublin 3 cluster are experiencing a temporary delay in receiving mail. The issue is under investigation by engineering as an emergency.

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.

This incident has been resolved.

The issue has been identified and a fix is being implemented.

Our team has confirmed the issue is now resolved. Users should now be able to access Sedna without any performance issues.

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.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

users may experience issues with connecting their calendars in Sedna.

On 21 August from approximately 3 pm BST, a small proportion of emails were incorrectly bounced across all clusters on Sedna. On 22 August at approximately 12 pm BST, Sedna's Engineering team implemented a fix to resolve this issue going forward and are currently investigating how to recover any missing emails. Further updates to follow

The issue has been identified and a fix is being implemented.

The issue has been identified and a fix is being implemented.

Sedna users across all clusters may experience interruptions in sending and receiving emails. Our Engineering Team is investigating this with the highest priority.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We have received some reports of Sedna being down for some of our customers. We are actively investigating this with uttermost priority.

This incident has been resolved.

A fix has been implemented and we are now monitoring the results.

Users on our Dublin-3 cluster may experience interruptions in receiving emails. Our Engineering Team is investigating this with the highest priority.

Our team has confirmed the issue is now resolved. Users should now be able to access Sedna without any performance issues.

Our Engineering team has completed deployment for the fix raised to address the slowness issues in Sedna. We continue to monitor our logs and performance. No components were marked as affected by this incident.

Users on our Virginia-1 cluster are currently experiencing slowness issues on Sedna. This includes spinners when the list not loading or slowness in search amongst others. Our Engineering Team is investigating this with the highest priority.

Our team has resolved the issue and we are currently monitoring the system. Users should now be able to access Sedna without any performance issues.

The team has resolved the immediate issue. We are continuing to investigate the root cause. Customers should now have access to Sedna.

An issue has been detected for the customer tenants affected in Singapore 1. The team has resolved the immediate issue. We are continuing to investigate the root cause. Customers should now have access to Sedna

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are aware of an issue affecting a number of customers on a specific infrastructure cluster (Singapore 1). Affected end users are unable to log into Sedna. We are investigating this as an emergency.

`Post Incident Report` `Dublin 3 Cluster Application Incident` ‌ Date of Issue 23 April 2024 Incident Reference INC-20240423-1418 ‌ # `01 `Summary ‌ On the 23rd April 2024 , the Sedna Platform experienced a partial loss of service. A small number of customers were affected by an application outage and were therefore unable to send or receive emails for a period of approximately 15 minutes. This is not the level of quality and reliability we strive to offer you, and we are taking immediate steps to improve the platform’s availability. We have conducted an internal investigation and are taking steps to improve our service. ‌ ‌ # `02 `Detailed description ‌ At approximately 14:08 UTC on 23 April 2024 Sedna incurred a restart of one of its primary applications \(Node\). The restart was an automated action triggered by the system as a result of an unhealthy state, and resulted in a period of 15 minutes of downtime while the restart completed.  ‌ The reason for the restart was related to a memory issue with the service, combined with an extraordinarily high workload on the system. The workload caused a backup in requests, which eventually exhausted the system memory and triggered a restart. The restart itself is an automated action that allows the system to respond to such an event and recover quickly, however during the restart process systems can be unavailable. ‌ The first customer case surfacing symptoms of an application outage was raised with Customer Support at 14:13 UTC, at which point the Sedna Support team triggered a major incident with the engineering team to urgently investigate the issue. The Sedna team deployed a Status Page notification at 14:21 UTC notifying all Status Page followers of the incident under investigation.  ‌ The service was fully operational at 14:23 UTC and all customers who reported an incident were informed of the incident closure on the same day. ‌ # `03 `Remediation and Prevention An incident of this nature receives Sedna’s highest level of scrutiny to ensure we can provide our customers with full confidence in the system. Following the incident the team conducted a retrospective to review the remediation taken and to detail next steps to ensure prevention of similar issues occurring in the future. See below the Remediation and Prevention details: ‌ * Remediation: * As of this report the issue itself has been fully resolved * Engineering has conducted a full review of related code - logs and telemetry data, to reduce the likelihood of follow on issues. ‌ * Prevention:  We have put the following changes in effect to reduce the likelihood of the issue from recurring: * Engineering has provisioned additional instances of the impacted application to help handle similar unexpected spikes in the future * Engineering has increased the memory size of the Node Application to add additional coverage for similar unexpected spikes in the future ‌ # `04 `What you can expect from SEDNA ‌ ‌ We understand the critical nature of the services SEDNA provides your business. We will continue to communicate with customers to answer any questions and ensure we do our best to provide a seamless customer experience. We apologize for any issues these events may have caused.  ‌ Please reach out directly to SEDNA Support \([support@sedna.com](mailto:support@sedna.com)\) with any questions.

This incident has been marked as resolved. For more details on this incident, see the linked Postmortem.

We are continuing to monitor for any further issues.

We are continuing to monitor for any further issues.

An issue has been detected in the database layer for the customer tenants affected in Dublin 3. The team has resolved the immediate issue. We are continuing to investigate the root cause. Customers should now have access to Sedna.

We are aware of an issue affecting a number of customers on a specific infrastructure cluster (Dublin 3). Affected end users are unable to log into Sedna. We are investigating this as an emergency.

This incident has been resolved and the platform is running normally. We apologise for any inconvenienced caused by this temporary interruption to service.

Service has been restored to the Dublin cluster and we are monitoring carefully to ensure that no further incidents occur.

We are continuing to investigate this issue.

We are currently investigating this issue.

Service has been restored and affected end users are now able to log into Sedna. The root cause was related to a configuration item in the Database layer and this has been rectified. Please accept our sincere apologies for any inconvenience caused.

An issue has been detected in the database layer for the customer tenants affected. A rollback of the recent deployment is being made and we will report back shortly. This should resolve the incident. Apologies for any inconvenience caused.

We are aware of an issue affecting a number of customers on a specific Infrastructure cluster (Dublin). Affected end users are unable to log into Sedna. We are investigating this as an emergency.

Our team has resolved the issue and users should now see Sedna working as expected

Our team has made a fix for this issue and we are currently monitoring the system, users should now be able to access Sedna without any performance issues.

Users accessing Sedna from www.sednanetwork.com experiencing slowness in Sedna loading content, our Engineering team are actively investigating this and we will be providing regular updates.

# Summary On the 28th June, 2023, the SEDNA Platform experienced a partial loss of service. A number of customers served by the North American server infrastructure were not able to view their recently sent messages or see new messages in their Inbox. We deeply regret the inconvenience caused during the five-hour and four-minute duration of this issue. ‌ We want to assure you that no messages were lost during this incident. However, there was a delay in processing both inbound and outbound messages as some sent messages were temporarily held in a staging queue, which were then delivered correctly at the end of the incident window. ‌ # Remediation and Prevention ‌ An incident of this nature receives Sedna’s highest level of scrutiny to ensure we can provide our customers with full confidence in the system. Following the incident the team conducted a series of follow ups: ‌ * Engineering Retro - documentation of the specific actions which caused the incident, the remediation, and the alerts through out to identify where / how improvements are needed * Engineering / CS Coordination Retro - confirmation of coordination between Support and Engineering to ensure we were providing the best possible support to our customers given the difficult situation * Leadership Team Retro - review with Sedna leadership on the issue, and specific actions which will be taken to ensure it is not repeated ‌ As a result of the reto’s listed above. SEDNA has taken specific action to ensure we reduce the likelihood of incidents like this in the future, and has developed a full plan of action  Those actions include: ‌ * A full detailed code review of the issue in question to identify the offending sections, how the code was developed, and what requirements were being targeted which produced such an error * A full detailed review of the QA process for the offending code to determine if additional measures could / should have been taken to ensure such a bug cannot be introduced in the future * A full review of the queueing and alerting systems used to identify similar issues  * A review of potential rollback procedures to include analysis of queue impacts so that we might faster resolve any similar issues in the future * A scheduled review of our autotagging specific development process to reduce the risk of inappropriate tagging and improved testing procedures * Consideration of enhancements to improve the queue processing approach that impacts this area of service ‌ This is only an initial list of actions taken. As we work through the above we expect additional specific actions to be identified and remedied.  ‌ # What you can expect from SEDNA ‌ We understand the critical nature of the services SEDNA provides your business. We will continue to communicate with customers to answer any questions and ensure we do our best to provide a seamless customer experience. We apologize for any issues these events may have caused.  ‌ Please reach out directly to SEDNA Support \([support@sedna.com](mailto:support@sedna.com)\) with any questions.

This incident has been resolved. A post-incident report will be shared in due course.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is in progress.

We've identified a potential cause for this issue and are working to rectify.

We are continuing to investigate this issue. We apologize for any inconvenience this may cause and thank you for your patience while we work on getting this resolved.

We are continuing to investigate this issue.

We are currently experiencing an issue affecting some mail being received into or sent from some SEDNA tenants in the Virginia1 Cluster region. Our Engineering team is actively working to resolve this and all pending mail will be sent and received once the incident is resolved.

This incident has been resolved. A post incident report will be shared in due course.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is in progress.

We have received complaints from a small number of customer of the inability to send messages. We continue to investigate with the highest priority and will provide an update in due course.

We have received some reports of an inability to send messages from the SEDNA System. We are investigating this with the highest urgency and will report on progress as soon as possible.

Our Engineering team has fixed the issue and we are seeing messages being received into SEDNA as expected.

Our Engineering team have deployed a fix for this issue and we are currently monitoring the situation.

Users accessing SEDNA at www.sednanewtork.com are currently experiencing no messages being received in SEDNA, our Engineering team is actively investigating this issue and working to a resolution.

Our Engineering team has now resolved this issue and users should now be able to view message within the SEDNA iOS app, if you are still experiencing issues we recommend users log out and log back into the app.

We are experiencing an issue with users not being able to view messages on the iOS mobile app, our Engineering team is currently investigating the cause of this. We recommend users access SEDNA via the web browser on their mobile device for the time-being until we have resolved the issue.

Our team has confirmed that all affected messages have now been sent and received into SEDNA.

Our team has been investigating issues with messages being received in SEDNA, we are actively working on a fix for this.

Our team has been investigating issues with messages being received in SEDNA, we are actively working on a fix for this.

During a routine deployment activity a change was introduced which prevented users from seeing new messages coming into the system. This was a view-only issue and no emails were lost during the incident. Once the incident was identified and fixed, full service was restored, including views to any messages received during the outage. A full report will follow.

Our team has confirmed that all affected messages have now been sent and received into SEDNA.

Our team have implemented the fix and can confirm messages will now flow in and out of SEDNA as expected. Please reach out to support@sedna.com should you experience any further issues.

Since 18:52 (UTC) our team has been investigating issues with messages being received in SEDNA, we are actively working on a fix for this.

Our team has resolved the issue that was causing our default cluster to not load and all users should be able to log in as normal again. If you see any issues please reach out to our Support team at support@sedna.com.

The team has resolved the issue and we are seeing Inbox and Search functionality return to normal. Some searches are experiencing longer load times than usual and this will continue to improve over the next while. We will continue to monitor this issue and will provide an update when the issue has been fully resolved and full functionality has been restored.

Our team has identified are now working to resolve an issue that is prohibiting users in our Default Cluster from accessing their messages list, with a loading spinner. We are expecting to be back to full operation very shortly. We deeply thank all affected for their patience and we will provide updates through this status page.

We are continuing to investigate this issue.

Our team is currently investigating an issue where SEDNA is intermittently not loading the message list and seeing spinners in SEDNA. This is affecting users who login via sednanetwork.com.

This incident has been confirmed resolved. Please feel free to reach out to support@sedna.com if you need further assistance.

A fix has been implemented by the Engineering team and has been found to resolve the issue which we are currently monitoring.

We are currently investigating an issue where some users have reported not being able to send or receive messages, also not being able to open SEDNA on a new instance.

We are seeing that the Engineering team's fix has resolved the issue, users are now able to log in successfully to SEDNA.

The Engineering team has implemented a fix that resolved the issue and will continue to monitor it.

We are currently investigating an issue where some users are not able to log in to SEDNA on a new tab, showing the page consistently reloads.

We are seeing that the fix deployed by our Engineering team has resolved the issue where the Important filter was not returning any messages.

Our Engineering team has released a fix for this issue and we are seeing that the Important filter is working as expected.

Users are experiencing an issue with the Important view not showing any message and receiving a constant spinner, our Engineering team is actively investigating the cause of this issue.

We experienced an issue where no messages were appearing in the Important view, our team has now resolved this and users should see messages flowing into the Important view as expected.

We have resolved the issue which was affecting mail being sent or received in some SEDNA tenants. Affected messages have been processed and there should no longer be any delays affecting inbound or outbound mail.

The fix applied has been successful and mail is now being sent and received from SEDNA. All messages are queued and there will be a small delay whilst the backlog reduces.

We've identified a potential cause for this issue and are working to rectify.

We are currently experiencing an issue affecting some mail being received into or sent from some SEDNA tenants in the eu-west-1 region. Our Engineering team are actively working to resolve this and all pending mail will be sent and received once the incident is resolved.

Our team has resolve the issue and all messages have been successfully received into SEDNA.

We are currently experiencing an issue with ingesting mail into SEDNA, our Engineering team are actively working to resolve this and all mail will be received once the incident is resolved.

Our team has resolved the issue that was causing our us-east-1 cluster to not load and all users should be able to log in as normal again. If you see any issues please reach out to our Support team at support@sedna.com.

Our team has resolved the issue that was causing our us-east-1 cluster to not load and all users should be able to log in as normal again. We are continuing to monitor the situation and advise any users experiencing issues to contact support for immediate further assistance.

Our team has resolved the issue that was causing our us-east-1 cluster to not load and all users should be able to log in as normal again. We are continuing to monitor the situation and advise any users experiencing issues to contact support for immediate further assistance.

Users in our us-east-1 cluster are currently experiencing issues with accessing SEDNA. Our team is actively investigating the root cause and working towards a fix.

The slowness issue in SEDNA for some customers has been resolved and all loading of SEDNA should be working as expected. If you see any issues please reach out to our Support team at support@sedna.com.

Our Engineering team has completed deployment for the fix raised to address the slowness issues in SEDNA. We continue to monitor our logs and performance.

Some users logging into SEDNA on one of our clusters may be experiencing slowness in loading SEDNA or may see slowness in using SEDNA. Our Engineering team has identified the cause of this slowness and is working towards deploying a fix.

Our team has confirmed the slowness issues within SEDNA have been resolved. If you continue to experience any issues please reach out to our Support team at support@sedna.com.

Our team has implemented a fix that resolves the slow loading in SEDNA and we continue to monitor the system.

Our Engineering Team has implemented a step in resolving the slowness being experienced in SEDNA are are working towards resolving the root cause.

Our Engineering team is actively investigating into reported issues with slowness and the list not loading in SEDNA.

**SEDNA Incident** **03 March 2022** **Summary** On March 3, 2022, users on multiple application clusters experienced issues with long loading times and slowness in SEDNA. **Why this happened** The database which powers SEDNA's fast search experienced latency issues across a small number of oversized indexes. This caused a backlog of requests to build up which in turn affected the entire search performance for the respective application cluster. **Actions and opportunities for improvement** 1. Increased the capacity of the affected application clusters by approx 20% **Completed** 2. Improving the data indexing efficiency of our search databases **In Progress**

Our Engineering team has identified and resolved the issue which was causing SEDNA not to load correctly for users. If you continue to experience any issues please reach out to support@sedna.com.

Our Engineering team are seeing that SEDNA's performance is stabilising and the system is loading as expected, we continue to monitor the situation.

Our Engineering team continue to investigate the slowness being experienced in SEDNA.

Our Engineering team continue to actively investigate the cause of the slowness being experienced with SEDNA.

Users are seeing a constant spinner in SEDNA and messages are not loading, our Engineering team is actively investigating the cause of this issue.

**SEDNA Incident** **09 March 2022** **Summary** On March 9, 2022, users on multiple application clusters experienced issues with long loading times and slowness in SEDNA. **Why this happened** The database which powers SEDNA's fast search experienced latency issues across a small number of oversized indexes. This caused a backlog of requests to build up which in turn affected the entire search performance for the respective application cluster. **Actions and opportunities for improvement** 1. Increased the capacity of the affected application clusters by approx 20% **Completed** 2. Improving the data indexing efficiency of our search databases **In Progress**

Our team has confirmed that SEDNA loading speeds are back to normal and everything is working as expected. The team will continue to monitor this, if you continue to experience issues please reach out to support@sedna.com.

Users on our Default cluster are currently experiencing slowness issues on SEDNA. This includes spinners when the list not loading or slowness in search amongst others. Our Engineering Team is investigating this with the highest priority.

Our team has confirmed that SEDNA loading speeds are back to normal and everything is working as expected. If you continue to experience issues please reach out to support@sedna.com.

Our team has made improvements to SEDNA's performance and we are seeing that SEDNA is loading as expected, we continue to monitor the situation.

Our team continues to actively investigate the loading times being experienced in SEDNA

Our team continue to investigate the long loading times in SEDNA.

Our Engineering team is actively investigating an issue with SEDNA where users are experiencing long loading times.

SEDNA is now back up and running for our customers on our Dublin2 cluster, if you continue to experience any issues please reach out to our Support team at support@sedna.com.

Our team has resolved the issue that was causing our Dublin2 cluster to not load and all users can log in as expected. We continue to monitor SEDNA.

Our team has identified the issue causing the Dublin2 cluster to not load and is working on resolving the issue.

Users on our Dublin2 cluster are currently experiencing issues with accessing SEDNA. Our team is actively investigating the root cause and working towards a fix.

Our Engineering team has identified and resolved the issue which was causing SEDNA not to load correctly for users. If you continue to experience any issues please reach out to support@sedna.com.

Users are seeing a constant spinner in SEDNA and messages are not loading, our Engineering team is actively investigating the cause of this issue

Incident Report **SEDNA Incident**  **19 Jan 2022** ## **Summary** On January 19, 2022, users on our dublin1 cluster experienced issues with loading buckets and search in SEDNA.  ## **Why this happened** The slow search loading affected a small section of our search infrastructure which in turn affected the servers and resulted in degraded performance. We have performed a thorough investigation into what caused the issue and steps have been taken to ensure this does not happen again.  **Actions and opportunities for improvement** 1. Write internal playbook for how this issue was resolved  - **COMPLETE** 2. Deploy fix to search infrastructure to ensure this does not happen again - **COMPLETE**

Our team has confirmed that SEDNA loading speeds are back to normal and everything is working as expected. If you continue to experience issues please reach out to support@sedna.com.

Our team has implemented a resolution and we are seeing SEDNA functionality is back to regular service. We continue to monitor the situation.

Our team has identified what is causing the slowness issue within SEDNA and are working towards resolving this to reinstate SEDNA's full functionality.

Users on our Dublin1 cluster are currently experiencing slowness issues on SEDNA. This includes spinners when switching teams, the list not loading or slowness in search amongst others. Our Engineering Team is investigating this with the highest priority.

Incident Report **SEDNA Incident**  **11 Jan 2022** ## **Summary** On January 11, 2022 users on our default cluster experienced issues with SEDNA not loading messages being received by teams.  ## **Why this happened** As part of improvements SEDNA was making to our Search feature there was a temporary issue with importing data which caused a spike in load on our servers which resulted in the degraded performance users experienced. **Actions and opportunities for improvement** 1. Improve logging and reporting on the search functionality - **COMPLETE** 2. Revisit and improve change management process - **IN PROGRESS**

This incident has been resolved.

Our Engineering team has resolved the issue and all messages have now been loaded in SEDNA.

We are continuing to monitor the situation with SEDNA not loading messages.

Our Engineering team has deployed a fix and are seeing that SEDNA is stabilising. We are continuing to monitor the situation.

Our team has identified the issue that is causing the message to not load in SEDNA and are actively looking at ways to resolve this.

Our team continues to investigate the issue which is causing a long delay in messages being loaded in SEDNA

Our team is actively investigating an issue that is causing messages not to load in SEDNA.

Our team has fully resolved the issues being experienced with SEDNA and users will no longer see any problems with sending messages or logging in and out of SEDNA. If you continue to see any issues please report them directly to support@sedna.com.

All messages have now been received into SEDNA and we are currently monitoring the issue experienced with users not being able to send messages or log in to SEDNA.

Our third-party server provider is currently experiencing an outage which is causing messages to not be received or sent in SEDNA. This is also affecting our third-party identity provider (powers SEDNA login) which means users will not be able to login to SEDNA, this will not affect users who are already logged in so we recommend users do not log out of SEDNA until this has been resolved. We apologies for the inconvenience you may be experiencing due to this outage.

Messages are not being received into SEDNA since 12:10 pm (UTC) due to an outage being experienced by our third-party server provider, our team is actively investigating this issue. We apologise for the inconvenience you may be experiencing due to this issue.

Amazon has resolved their outage and in turn, our third-party identity provider is back up and running. All users can now log in to SEDNA as expected after logging out.

Our third-party identity provider (powers SEDNA login) is currently experiencing an outage associated with the ongoing Amazon outage internet-wide. Users who are not currently logged into SEDNA will not be able to log in however those already logged in will not have a disruption in their use of SEDNA and are advised not to log out. We are monitoring the situation and will provide updates periodically.

The team has fully resolved the issue users were seeing with issues with archiving messages, tagging messages and delayed inbound messages. If you continue to see any issues please report them directly to support@sedna.com.

Our team has identified an issue affecting only our Default cluster where users are seeing archive function not working, tags aren't applying and delayed incoming messages and are actively working towards resolving this issue.

We are continuing to investigate this issue.

Our team has identified an issue affecting only our Default cluster where users are seeing archive function not working, tags aren't applying and delayed incoming messages. We are actively working towards resolving this issue.

Our third-party server provider has resolved the issue where messages are being delayed. If you continue to see any issues please report them directly to support@sedna.com.

Our team is continuing to monitor the issues experienced by our third-party server provider and is awaiting updates on a resolution.

We are continuing to monitor the issues experienced by our third-party server provider and are awaiting updates on a resolution.

We continue to monitor and wait for our third-party server provider to resolve the issues they are experiencing.

We continue to experience issues with our third-party server provider. We are monitoring their progress and will provide updates as they become available.

We are continuing to monitor the outage affecting our third-party server provider and are awaiting updates from them on a resolution.

We continue to monitor the situation with our third-party server provider and await updates from them on resolution.

We continue to monitor the outage affecting our third-party server provider. We do not have a current timeline on resolution and will provide updates as and when they become available.

Our third-party server provider is currently experiencing an outage on their side which is causing some of our customers (located on our default/US) on one of our clusters to be seeing a delay in receiving mail or not receiving mail. We are monitoring the situation and will provide updates as they become available.

**SEDNA Incident**  **01 Dec 2021** ## **Summary** On Dec 1, 2021 users experienced issues with logging in, loading and general use of SEDNA between 08:45-09:39 GMT.  ## **Why this happened** The slowness in SEDNA was caused due to an action made within SEDNA. THis caused the application to slow down and was unable to recover automatically fast enough thus resulting in users seeing issues with using SEDNA.  **Actions and opportunities for improvement** 1. Deployed initial changes to improve the efficiency and robustness of message processing in SEDNA - **COMPLETED** ‌ 2. Continued work on improving the efficiency and robustness of the process which caused the slow down  - **IN PROGRESS**

The team has fully resolved the issue users were seeing with SEDNA loading slowly and being unusable. If you continue to see any issues please report them directly to support@sedna.com.

Our team has resolved the issue that was causing users to see slowness and lag in SEDNA, we continue to monitor the application.

Our team is working on resolving the issue with users seeing slowness in SEDNA and intermittent loading issues. The team is working on this as a top priority.

Our team continues to work on resolving the slowness issues users are reporting, performance has been restored for some users and others may continue to see slowness. This is being worked on as a top priority with urgency.

Our team has identified an issue affecting only our Dublin1 cluster where users are seeing slow loading of the SEDNA app or are unable to login and are actively working towards resolving this issue.

Our team has deployed a fix for this issue and all messages that were not received have now been ingested into SEDNA.

Since 12:03 (UTC) our team has been investigating issues with messages being received in SEDNA, we are actively deploying a fix for this.

Since 12:03 (UTC) our team has been investigating issues with messages being received in SEDNA and are actively deploying a fix.

**SEDNA Incident** **14 Oct 2021** **Summary** On October 14th 2021 between 14:43 UTC and 15:14 UTC an upgrade to the SEDNA infrastructure resulted in our search platform not returning any results and no messages were being returned to the Message List. As a result, teams could not view messages during this time. **Why this happened** This update in our application configuration resulted in too few servers trying to handle traffic for one of our production clusters in North America causing the interruption to service and degraded performance. The number of servers was then scaled to a value appropriate for that cluster and full service was restored. **Actions and opportunities for improvement** We internally reviewed this incident and have agreed to the following action: 1. Added correct autoscaling configurations for ALL clusters to prevent this specific issue from happening again.

A change in application configuration led to too few servers trying to handle traffic for one of our production clusters in North America causing a brief interruption to service and degraded performance. The number of servers has been scaled to a value appropriate for that cluster and service has been restored

We are continuing to monitor for any further issues.

We can confirm the incident has been isolated and only impacted our customer hosted on our default cluster. We are currently monitoring the issue and will continue to share any updates.

We are currently experiencing an issue where users are unable to load SEDNA. The team is currently investigating the issue.

The login issues due to our third-party identity provider have been resolved. If you continue to experience any issues please contact us at support@sedna.com

Our third-party identity provider has resolved issues on their side and all users will see resumed login speeds in SEDNA. We will continue to monitor on our end to ensure smooth operation.

Our third-party identity provider has isolated the issue on their side and is working on restoring the service fully. Users will continue to see long loading times when trying to log in, if login does not work the first time please try again after a moment. Users who are actively logged in are advised not to log out of SEDNA.

Our third-party identity provider has isolated the issue on their side and is working on resolving the issue. Users will continue to see long loading times when trying to log in, if login does not work the first time please try again after a moment. Users who are actively logged in are advised not to log out of SEDNA.

We are currently experiencing an issue with our third-party identity provider wherein users are unable to log in to SEDNA or are seeing a long loading time when trying to log in. We advise all users who are currently logged in to not log out of SEDNA.

Today between 9:15 UTC and 9:30 UTC, some customers hosted on our Dublin2 tenant may have experienced some difficulties in loading Sedna. This incident is now resolved and we are working on an Incident report. Please accept our apologies for the inconvenience this may have caused. Do reach out to support@sedna.com with any questions.