Forsta Outage History

Started May 21, 2026, 04:46 PM UTC· resolved May 22, 2026, 02:23 PM UTC

1. investigating May 21, 2026, 04:46 PM UTC

   Cases are not being generated on the US site. We are investigating. We are looking into performing a rollback. Will provide an update ASAP.

2. monitoring May 21, 2026, 05:37 PM UTC

   We have rolled back the affected component. Case creation appears to be working now. We will monitor for the rest of the day.

3. monitoring May 21, 2026, 07:46 PM UTC

   Case generation is catching up, but it may take until tomorrow morning before all missed cases are generated. It is recommended that triggers on the US be set to a case creation window of 3 days or higher to make sure that no cases are missed.

4. resolved May 22, 2026, 02:23 PM UTC

   This issue has been resolved.

Read the full incident report →

Started May 20, 2026, 12:18 PM UTC· resolved May 21, 2026, 07:47 PM UTC

1. investigating May 20, 2026, 12:18 PM UTC

   Affected users will see an error in all Studio widgets using Action management data if they try to filter by reporting period. If they disable the filter, affected users will see delays in case data updating for these widgets. Note that case creation is not affected at this time. We are actively investigating.

2. monitoring May 20, 2026, 06:00 PM UTC

   A fix has been implemented and we are monitoring the results. Initial results seem promising. Will continue to monitor throughout the rest of the day and tomorrow's deployment. A few customers may continue to see errors throughout the day, but these should clear up by tomorrow. Will provide an update tomorrow morning.

3. identified May 21, 2026, 12:49 PM UTC

   The situation remains stable on most sites. We are now seeing this issue on the AUS site, but that should resolve with the next deployment, which should be within the next few hours. I will provide an update within four hours.

4. monitoring May 21, 2026, 06:11 PM UTC

   Case data should be up to date on all sites now. Will monitor for a few hours to confirm.

5. resolved May 21, 2026, 07:47 PM UTC

   This issue has been resolved.

Read the full incident report →

Started May 18, 2026, 11:15 AM UTC· resolved May 19, 2026, 11:51 AM UTC

1. investigating May 18, 2026, 11:15 AM UTC

   Updated status will be provided within 60 minutes.

2. investigating May 18, 2026, 12:15 PM UTC

   We are continuing to look into this issue. Updated status will be provided within 60 minutes

3. investigating May 18, 2026, 01:15 PM UTC

   We are continuing to look into this issue. Updated status will be provided within 60 minutes

4. investigating May 18, 2026, 02:15 PM UTC

   We are continuing to look into this issue. Updated status will be provided within 60 minutes

5. investigating May 18, 2026, 03:16 PM UTC

   The Ops and R&D teams are continuing to look into this issue. An update will be posted when we have more news on this issue.

6. monitoring May 19, 2026, 09:35 AM UTC

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

7. resolved May 19, 2026, 11:51 AM UTC

   This issue has been resolved.

Read the full incident report →

Started May 06, 2026, 10:00 AM UTC· resolved May 06, 2026, 10:00 AM UTC

1. resolved May 07, 2026, 02:03 PM UTC

   This issue has been resolved.

Read the full incident report →

Started Apr 29, 2026, 10:16 AM UTC· resolved Apr 29, 2026, 12:45 PM UTC

1. investigating Apr 29, 2026, 10:16 AM UTC

   Updated status will be provided within 60 minutes

2. investigating Apr 29, 2026, 11:09 AM UTC

   We are continuing to investigate this issue. Updated status will be provided within 60 minutes.

3. monitoring Apr 29, 2026, 11:56 AM UTC

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

4. resolved Apr 29, 2026, 12:45 PM UTC

   This issue has been resolved.

Read the full incident report →

Started Apr 20, 2026, 11:39 AM UTC· resolved Apr 22, 2026, 12:25 PM UTC

1. investigating Apr 20, 2026, 11:39 AM UTC

   We are currently investigating this issue.

2. identified Apr 20, 2026, 01:26 PM UTC

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

3. identified Apr 20, 2026, 05:18 PM UTC

   We are continuing to work on a fix for this issue.

4. identified Apr 21, 2026, 07:33 AM UTC

   We are continuing to work on a fix for this issue.

5. identified Apr 21, 2026, 02:15 PM UTC

   We are continuing to work on a fix for this issue.

6. resolved Apr 22, 2026, 12:25 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 13, 2026, 08:41 AM UTC· resolved Apr 13, 2026, 12:38 PM UTC

1. investigating Apr 13, 2026, 08:41 AM UTC

   Updated status will be provided within 60 minutes.

2. investigating Apr 13, 2026, 09:33 AM UTC

   We are continuing to investigate this issue. Updated status will be provided within 60 minutes.

3. investigating Apr 13, 2026, 09:50 AM UTC

   The issue with exports should now be resolved. We are still looking into the issue regarding survey launches. Updated status will be provided within 60 minutes

4. investigating Apr 13, 2026, 10:57 AM UTC

   We are continuing to investigate the issue with survey launches. Updated status will be provided within 60 minutes.

5. investigating Apr 13, 2026, 11:52 AM UTC

   We are still looking into the issue regarding survey launches. Updated status will be provided within 60 minutes

6. resolved Apr 13, 2026, 12:38 PM UTC

   This issue has now been resolved.

Read the full incident report →

Started Apr 09, 2026, 08:08 AM UTC· resolved Apr 09, 2026, 12:15 PM UTC

1. identified Apr 09, 2026, 08:08 AM UTC

   Updated status will be provided within 60 minutes.

2. identified Apr 09, 2026, 08:17 AM UTC

   Patching is currently in progress to address the identified issue.

3. monitoring Apr 09, 2026, 08:43 AM UTC

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

4. monitoring Apr 09, 2026, 09:11 AM UTC

   We are continuing to monitor for any further issues.

5. resolved Apr 09, 2026, 12:15 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 19, 2026, 09:14 AM UTC· resolved Mar 19, 2026, 09:32 AM UTC

1. investigating Mar 19, 2026, 09:14 AM UTC

   Updated status will be provided within 60 minutes.

2. resolved Mar 19, 2026, 09:32 AM UTC

   This issue has been resolved.

Read the full incident report →

Started Mar 16, 2026, 12:57 PM UTC· resolved Mar 17, 2026, 06:22 PM UTC

1. investigating Mar 16, 2026, 12:57 PM UTC

   Pre-overdue, overdue, and post-overdue email notifications are not being sent in Action Management. We are currently investigating, and should have an update by the end of the day Eastern Time.

2. identified Mar 16, 2026, 08:31 PM UTC

   A potential fix is being implemented. We will provide an update tomorrow morning.

3. monitoring Mar 17, 2026, 01:11 PM UTC

   A fix has been implemented. We will monitor the results to confirm whether or not this has resolved the issue. We can provide an update by the end of the day.

4. resolved Mar 17, 2026, 06:22 PM UTC

   This issue has been resolved.

Read the full incident report →

Started Mar 11, 2026, 11:04 AM UTC· resolved Mar 11, 2026, 02:13 PM UTC

1. investigating Mar 11, 2026, 11:04 AM UTC

   We are currently investigating this issue.

2. resolved Mar 11, 2026, 02:13 PM UTC

   The PowerMTA instance was instable due to disk related problem. Emailing send outs were impacted with delays as a result. Rackspace has now corrected the disk problem and the issue should be stable again.

Read the full incident report →

Started Feb 25, 2026, 02:19 PM UTC· resolved Feb 25, 2026, 03:17 PM UTC

1. investigating Feb 25, 2026, 02:19 PM UTC

   Updated status will be provided within 2 hours.

2. investigating Feb 25, 2026, 02:24 PM UTC

   We are continuing to investigate this issue.

3. investigating Feb 25, 2026, 02:24 PM UTC

   We are continuing to investigate this issue.

4. resolved Feb 25, 2026, 03:17 PM UTC

   This issue has been resolved.

Read the full incident report →

Started Feb 11, 2026, 09:13 AM UTC· resolved Feb 11, 2026, 09:24 AM UTC

1. investigating Feb 11, 2026, 09:13 AM UTC

   Updated status will be provided within 30 minutes.

2. resolved Feb 11, 2026, 09:24 AM UTC

   This issue has been resolved.

Read the full incident report →

Started Feb 10, 2026, 10:30 AM UTC· resolved Feb 10, 2026, 10:30 AM UTC

1. resolved Feb 11, 2026, 01:24 PM UTC

   Some specific users could not access Studio via login. When entering they received a permission denied error in browser. Problem was reproducible by support when impersonating users. Studio was rolled back and problem was resolved. Problem will be identified and solution implemented to prevent further outages.

Read the full incident report →

Started Jan 22, 2026, 10:25 PM UTC· resolved Jan 23, 2026, 02:37 PM UTC

1. investigating Jan 22, 2026, 10:25 PM UTC

   Service Impact: Text Analytics & AutoCombined Survey (Vault) Data Flows Start Time: 2 PM Eastern time Region: US SaaS Environment We are currently investigating an issue affecting Text Analytics and Vault data processing within the US SaaS environment. Impacted data flows are failing to start or progressing unsuccessfully, which may result in delayed or missing processing for customer projects relying on these services. Current Status Our engineering and platform operations teams are actively analyzing the root cause. Initial indications suggest a backend processing component is not triggering required pipelines as expected. We are working to isolate the issue and restore normal data flow operations.

2. monitoring Jan 23, 2026, 12:39 PM UTC

   Service Impacted: Text Analytics & Vault Data Flows Region: US SaaS Environment Status: Monitoring Update We have identified the underlying issue affecting Text Analytics and Vault data flows in the US SaaS environment. To mitigate the impact, we have applied additional resource scaling to the affected components. Current State Data flows are beginning to recover and processing is resuming. Our teams are actively monitoring the platform to ensure continued stability and to confirm that all impacted workloads return to normal operation.

3. resolved Jan 23, 2026, 02:37 PM UTC

   Resolution The issue affecting Text Analytics and Vault data flows in the US SaaS environment has been resolved. All impacted services are now operating normally, and data flows are processing as expected. Details The underlying issue that prevented certain data flows from starting or completing successfully has been identified and addressed. Any queued or delayed jobs have been restarted and are progressing.

Read the full incident report →

Started Jan 21, 2026, 08:34 AM UTC· resolved Jan 21, 2026, 11:45 AM UTC

1. investigating Jan 21, 2026, 08:34 AM UTC

   Updated status will be provided within 30 minutes.

2. monitoring Jan 21, 2026, 08:52 AM UTC

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

3. resolved Jan 21, 2026, 11:45 AM UTC

   This issue has been resolved.

Read the full incident report →

Started Jan 14, 2026, 11:38 AM UTC· resolved Jan 14, 2026, 04:50 PM UTC

1. investigating Jan 14, 2026, 11:38 AM UTC

   We are currently investigating an issue with access to the US site

2. monitoring Jan 14, 2026, 12:01 PM UTC

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

3. resolved Jan 14, 2026, 04:50 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 13, 2026, 08:06 AM UTC· resolved Jan 13, 2026, 02:11 PM UTC

1. investigating Jan 13, 2026, 08:06 AM UTC

   Updated status will be provided within 60 minutes.

2. investigating Jan 13, 2026, 08:55 AM UTC

   We are continuing to investigate this issue. Updated status will be provided within 60 minutes

3. investigating Jan 13, 2026, 10:10 AM UTC

   We are continuing to investigate the issue. Updated status will be provided within 60 minutes.

4. investigating Jan 13, 2026, 11:19 AM UTC

   We are continuing to investigate this issue. Updated status will be provided within 60 minutes

5. monitoring Jan 13, 2026, 11:23 AM UTC

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

6. resolved Jan 13, 2026, 02:11 PM UTC

   This issue has been resolved.

Read the full incident report →

Started Dec 23, 2025, 04:17 PM UTC· resolved Jan 14, 2026, 02:08 PM UTC

1. investigating Dec 23, 2025, 04:17 PM UTC

   We are currently investigating this issue.

2. monitoring Dec 23, 2025, 04:44 PM UTC

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

3. monitoring Jan 14, 2026, 02:07 PM UTC

   We are continuing to monitor for any further issues.

4. resolved Jan 14, 2026, 02:08 PM UTC

   This issue has been resolved.

Read the full incident report →

Started Dec 22, 2025, 05:00 PM UTC· resolved Dec 23, 2025, 12:00 PM UTC

1. resolved Dec 23, 2025, 02:50 PM UTC

   Starting at approximately 4:00 AM AEDT on December 23, an issue occurred with sending email from the Australia Cloud server. During this time, emails were not sent but were successfully queued on the mail server. The Global Forsta Cloud Operations team was engaged and identified a configuration issue, which was resolved by 11:00 PM AEDT. All queued emails have since been processed and delivered. Impact Email sending from the Australia Cloud was delayed during the incident window. It's our understanding that all emails were eventually attempted to be sent from the system once the email server came online. Current Status The issue has been fully resolved, and systems are operating normally.

Read the full incident report →

Started Dec 19, 2025, 06:44 PM UTC· resolved Jan 16, 2026, 01:01 PM UTC

1. investigating Dec 19, 2025, 06:44 PM UTC

   Some reporting views show delayed Action Management case data for programs with very high case volumes and a large number of assigned users. As a result, recent case activity may not yet appear in these views, and case counts may not reflect the latest updates. Please note that no case data has been lost, and Action Management case creation and assignment continues to function normally. We are working on a potential solution we hope to deploy on Monday. We will be able to provide an update in the next few hours.

2. investigating Dec 19, 2025, 09:39 PM UTC

   We are continuing to work on a potential solution to be deployed Monday morning pacific time. We are hoping to have the work ready for this in a few more hours.

3. investigating Dec 20, 2025, 01:02 AM UTC

   Unfortunately we were unable to get the fixes done by the end of the day. We will continue to work on them on Monday. As of now, it looks like we will be able to implement this solution in the production environment on Tuesday around 12-1 PM. We will provide an update on Monday.

4. investigating Dec 22, 2025, 09:22 PM UTC

   Unfortunately, the fix we are working on will not be ready by Tuesday. We are currently conducting an emergency meeting to see if we can make any configuration changes that can help resolve this, or at least mitigate it over the holidays. We should have an update within the next few hours.

5. investigating Dec 23, 2025, 01:16 AM UTC

   Unfortunately there were no easy fixes identified. We will have some further discussions tomorrow. We should have an update around 12-1 PM Eastern Time.

6. investigating Dec 23, 2025, 06:04 PM UTC

   As of now, it appears that for a couple of large clients, case data remains out of sync in reporting. Other clients may experience some delays before the data catches up in their reporting. We will take one last look to see if anything can be done to improve the situation. If so, I will provide an additional update. Otherwise, further updates will follow in the new year, starting on January 5th.

7. investigating Jan 05, 2026, 07:28 PM UTC

   Tomorrow morning we plan to deploy a change to how case data is updated in reports, which will reduce system load. This will hopefully fix the synchronization issues and ensure the case data in reporting is up to date. I will have further updates tomorrow.

8. monitoring Jan 06, 2026, 01:40 PM UTC

   The change has been deployed and initial results look promising. We are currently monitoring and will provide an update by end of day.

9. monitoring Jan 06, 2026, 05:47 PM UTC

   All affected clients are now showing updated case data. We will continue to monitor over the next 24 hours to ensure the issue is resolved.

10. investigating Jan 07, 2026, 09:22 PM UTC

    Unfortunately, it looks like reporting is starting to fall out of sync again. We are actively investigating. We should have an update by tomorrow morning at the latest.

11. investigating Jan 07, 2026, 10:46 PM UTC

    The issue is still present and most severely impacting a few large customers. Smaller customers may see delays in Action Management reporting data as well. We will continue to investigate. I will provide an update by EOD tomorrow at the latest.

12. monitoring Jan 08, 2026, 12:39 PM UTC

    We made a couple configuration tweaks and that seems to have resolved the issue for now, but we will continue to monitor over the next 24 hours before closing this in case the issue reappears.

13. investigating Jan 09, 2026, 03:06 PM UTC

    The situation remains stable on US, but is now degrading on Euro. We will work with our operations team on this and provide an update by the end of the day.

14. monitoring Jan 09, 2026, 07:42 PM UTC

    We were able to stabilize the situation on the EURO site. We will continue to monitor, and I will provide an update on Monday.

15. monitoring Jan 12, 2026, 05:54 PM UTC

    Reporting data for Action Management remains up to date, but behind the scenes we're seeing a few errors. Leaving this in monitoring status for now as we continue to make improvements to system stability over the course of the week.

16. identified Jan 13, 2026, 02:47 PM UTC

    We're seeing sync issues with Action Management reporting data on the Euro site. We have identified the cause and are looking into solutions. We should be able to provide an update by the end of the day Eastern Time.

17. monitoring Jan 13, 2026, 03:29 PM UTC

    Reports are now synced up on Euro again. We will continue monitoring.

18. monitoring Jan 15, 2026, 04:40 PM UTC

    We are continuing to monitor for any further issues.

19. resolved Jan 16, 2026, 01:01 PM UTC

    This issue has been resolved.

Read the full incident report →

Started Dec 06, 2025, 12:42 PM UTC· resolved Dec 06, 2025, 02:35 PM UTC

1. investigating Dec 06, 2025, 12:42 PM UTC

   Updated status will be provided within 60 minutes.

2. monitoring Dec 06, 2025, 12:51 PM UTC

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

3. investigating Dec 06, 2025, 01:21 PM UTC

   We are continuing to investigate this issue. Updated status will be provided within 60 minutes.

4. investigating Dec 06, 2025, 01:21 PM UTC

   We are continuing to investigate this issue.

5. monitoring Dec 06, 2025, 01:40 PM UTC

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

6. resolved Dec 06, 2025, 02:35 PM UTC

   This issue has been resolved.

Read the full incident report →

Started Dec 02, 2025, 06:03 PM UTC· resolved Dec 02, 2025, 09:12 PM UTC

1. investigating Dec 02, 2025, 06:03 PM UTC

   We are currently experiencing an issue where File Library files are not loading due to problems with the fileshare cluster. Our Cloud Operations team and hosting provider are actively troubleshooting the case to restore normal functionality. Impact: Customers using the Euro SaaS platform may be unable to access or load files from the File Library. Next Update: Within 30 minutes Thank you for your patience as we work toward resolution.

2. identified Dec 02, 2025, 06:43 PM UTC

   We have identified that the underlying file storage system is in a degraded state. Based on guidance from our hosting provider, we are moving data to a new storage environment to restore stability. This process involves transferring a large number of files and is expected to take several hours. Impact: Customers may continue to experience issues accessing File Library files and delays in Task Queue processing during this migration. Next Update: Within 60 minutes or sooner if additional information becomes available. Thank you for your patience as we work toward resolution.

3. identified Dec 02, 2025, 08:22 PM UTC

   Update: Work is still ongoing to resolve the storage issue affecting the Euro SaaS platform. We are in the process of migrating data to a new storage environment to restore stability. Due to the large volume of files, this process will take several hours to complete. Impact: Customers may continue to experience issues accessing File Library files and delays in Task Queue processing during this migration. Next Update: Within 60 minutes or sooner if additional information becomes available. Thank you for your patience as we work toward resolution.

4. monitoring Dec 02, 2025, 08:28 PM UTC

   Update: The new file storage server is now online and operational. We have completed the migration and swapped to the new environment. Our team is closely monitoring system performance to ensure stability and confirm that all services are functioning as expected. Impact: File Library and Task Queue functionality should be returning to normal. We will continue to monitor and provide updates if any issues arise. Thank you for your patience throughout this process.

5. resolved Dec 02, 2025, 09:12 PM UTC

   The issue impacting the Euro SaaS platform has been fully resolved. The migration to the new storage environment is complete, and all services, including File Library and Task Queue functionality, are operating normally. Our team has verified system stability and will continue to monitor performance to ensure everything remains fully functional. Thank you for your patience and understanding throughout this process.

Read the full incident report →

Started Nov 27, 2025, 08:37 AM UTC· resolved Nov 27, 2025, 12:00 PM UTC

1. investigating Nov 27, 2025, 08:37 AM UTC

   We are currently investigating this issue.

2. investigating Nov 27, 2025, 08:45 AM UTC

   We are continuing to investigate this issue.

3. identified Nov 27, 2025, 11:10 AM UTC

   A fix is being implemented. Target resolution time is 2 hours. Updated status will be provided within 1 hour.

4. resolved Nov 27, 2025, 12:00 PM UTC

   This issue has been resolved.

Read the full incident report →

Started Nov 26, 2025, 10:36 AM UTC· resolved Dec 02, 2025, 12:16 PM UTC

1. investigating Nov 26, 2025, 10:36 AM UTC

   We are currently investigating this issue together with our hosting provider as well as Microsoft

2. investigating Nov 26, 2025, 01:37 PM UTC

   Investigative work is still ongoing with highest priority with Edarat and Microsoft.

3. investigating Nov 26, 2025, 04:18 PM UTC

   Together with our hosting partner Edarat and Microsoft we are continuing to investigate the issue impacting the KSA platform. The incident remains a top priority, and we are working to identify the root cause. Thank you for your patience as we work toward resolution.

4. investigating Nov 26, 2025, 08:30 PM UTC

   We, together with our hosting partner Edarat and Microsoft, continue to investigate the issue currently affecting the KSA platform. This incident remains our highest priority, and our teams are actively working to isolate the root cause and restore full service as quickly as possible. Thank you for your continued patience and understanding.

5. investigating Nov 26, 2025, 09:25 PM UTC

   We are actively addressing recent performance issues on the KSA SaaS platform. A dedicated team, led by our CTO, is working closely with Edarat and Microsoft to restore full functionality. Initial analysis indicates infrastructure resource limitations impacted performance. Interim measures have improved reporting capabilities, though interviewing remains unavailable. We are committed to resolving this as quickly as possible and will share updates as they become available. Again, thank you for your continued patience and understanding.

6. identified Nov 26, 2025, 10:23 PM UTC

   Our site is now back online, but operating with reduced capacity. The good news is that Studio report viewing is functional, and Web Interviewing is also up and running. At this stage, we need everyone to limit usage to only mission-critical activities so we can keep the platform stable while the team continues working toward full restoration. We will provide further updates as we make progress. Thank you for your patience and your discipline in keeping load to essential tasks only.

7. identified Nov 27, 2025, 08:47 AM UTC

   Thanks for your cooperation so far. The site is online and stable, though still at reduced capacity. Key functions like Studio report viewing and Web Interviewing remain available. As we continue restoring full service, please keep system usage limited to priority and time-sensitive tasks. We’ll keep you updated as progress continues.

8. identified Nov 27, 2025, 03:14 PM UTC

   Our engineering teams, together with Microsoft and our infrastructure partner, have been actively analysing the environment throughout the day. Based on their recommendations, we are implementing a series of non-disruptive improvements to enhance stability and performance. These updates are expected to be completed by the end of the day. The site has remained mostly stable today, with only minor service disruptions observed. An additional configuration change has been recommended and will be scheduled once we have fully assessed its impact. Analysis of system logs is ongoing, and we have continuous support coverage through the night. We will share further updates as new information becomes available.

9. identified Nov 27, 2025, 08:11 PM UTC

   We are currently performing infrastructure updates over the next couple of hours. During this time, you may experience intermittent service disruptions. We will provide an update once the work is complete.

10. identified Nov 27, 2025, 09:59 PM UTC

    For the next 3 hours, we will be performing infrastructure updates. During this window, you may experience significant service degradation, including slow performance or limited availability. Our team is working to complete the updates as quickly and safely as possible. We’ll notify you as soon as full service is restored. Thank you for your patience and understanding.

11. identified Nov 28, 2025, 01:01 AM UTC

    Our maintenance is currently taking longer than expected. Services may continue to experience degradation or limited availability. We are actively working to complete the updates and will provide the next update as soon as possible, or within 1 hour. Thank you for your continued patience.

12. identified Nov 28, 2025, 02:00 AM UTC

    Our maintenance work is still in progress and has exceeded the expected timeline. Some users may continue to experience reduced performance or intermittent availability. We will share the next update as soon as we have more information, or within 1 hour. Thank you for your patience as we work to restore full service.

13. identified Nov 28, 2025, 02:59 AM UTC

    The ongoing maintenance is continuing longer than anticipated. You may still encounter service degradation or intermittent issues during this period. We’ll issue the next update as soon as we have clarity, or in 1 hour at the latest. We appreciate your continued patience while we finish this work.

14. identified Nov 28, 2025, 03:50 AM UTC

    Our maintenance work is still underway, and at this time we do not have an estimated time for full service restoration. The site will remain unavailable while we continue working to resolve the issue. We will share updates as soon as we have new information. Thank you for your patience as we work to bring the service back online.

15. identified Nov 28, 2025, 08:15 AM UTC

    As part of the overnight infrastructure maintenance, we are currently troubleshooting an issue with our load balancer configuration. Our hosting partner, Edarat, together with Microsoft, is actively investigating the root cause. The service remains unavailable while this work continues. We will provide the next update within 1 hour or sooner if new information becomes available.

16. identified Nov 28, 2025, 09:15 AM UTC

    We are still troubleshooting an issue with our load balancer configuration. Our hosting partner, Edarat, together with Microsoft, is actively investigating the root cause. The service remains unavailable while this work continues. We will provide the next update within 1 hour or sooner if new information becomes available.

17. identified Nov 28, 2025, 09:17 AM UTC

    Work is still underway to resolve the load balancer configuration issue encountered during our overnight infrastructure maintenance. Edarat and Microsoft continue to investigate with us, and the service remains impacted. We will share the next update within 1 hour, or sooner if we have new information. Thank you for your continued patience.

18. identified Nov 28, 2025, 10:16 AM UTC

    The issue with our load balancer configuration, identified during overnight infrastructure maintenance, is still ongoing. The case has now been escalated within Microsoft, and their senior engineering team is working with Edarat and our own team to identify and resolve the root cause. The service remains impacted at this time. We will provide the next update within 1 hour, or sooner if we receive new information. Thank you for your continued patience.

19. identified Nov 28, 2025, 11:18 AM UTC

    Our engineering teams, together with our infrastructure partners, continue to work actively on resolving the connectivity issues affecting the environment. Progress is ongoing, and all teams remain fully engaged on the P1 incident. We will provide the next update within the hour, or sooner if new information becomes available.

20. identified Nov 28, 2025, 12:14 PM UTC

    We are continuing to work on the load balancer configuration issue that arose during the overnight infrastructure maintenance. The matter has been escalated within Microsoft, and their engineering team is now collaborating closely with Edarat and our internal teams to drive a resolution. The service remains unavailable or degraded while this investigation continues. Our next update will be provided within 1 hour, or sooner if new details emerge. Thank you for your ongoing patience.

21. identified Nov 28, 2025, 01:14 PM UTC

    Our engineering teams and infrastructure partners remain fully engaged as we continue working to restore full stability. Investigation and remediation efforts are ongoing, and we are actively progressing through the next steps on the P1 incident bridge. We will provide another update within the hour, or sooner if we have new information to share.

22. identified Nov 28, 2025, 02:19 PM UTC

    The load balancer configuration issue identified during overnight infrastructure maintenance is still under active investigation. The case is now with Microsoft’s escalated engineering team, who are working alongside Edarat and our technical team to pinpoint and resolve the underlying problem. Service remains impacted at this time. We will provide the next update within 1 hour, or earlier if we have new information to share. Thank you for your patience as we work toward resolution.

23. identified Nov 28, 2025, 03:15 PM UTC

    We are continuing to work on the load balancer configuration issue encountered during overnight infrastructure maintenance. The issue remains under escalated review within Microsoft, with their engineering teams collaborating closely with Edarat and our internal platform engineers. Service continues to be impacted while this investigation progresses. We will provide the next update within 1 hour, or sooner if we receive new information. Thank you for your patience as we work toward resolution.

24. identified Nov 28, 2025, 04:15 PM UTC

    There are no significant changes to report at this time. The load balancer configuration issue identified during overnight infrastructure maintenance remains under active investigation. Microsoft’s escalated engineering team continues to work closely with Edarat and our internal teams. Service remains impacted while this work continues. We will provide the next update within 1 hour, or sooner if new information becomes available. Thank you for your patience.

25. identified Nov 28, 2025, 05:15 PM UTC

    Our teams, along with Edarat and Microsoft’s escalated engineering group, continue to investigate the load balancer configuration issue stemming from the overnight infrastructure maintenance. At this stage, there are no material updates to report. The service remains impacted as the investigation progresses. We will share the next update within 1 hour, or sooner if we receive new information. Thank you for your continued patience.

26. identified Nov 28, 2025, 06:14 PM UTC

    There are no significant changes to report at this time. The load balancer configuration issue from the overnight infrastructure maintenance is still under active investigation. Multiple members of Microsoft’s Product Group engineering teams are now engaged, working alongside Edarat and our internal engineers. Service remains impacted while this work continues. We will provide the next update within 1 hour, or sooner if new information becomes available. Thank you for your patience as the investigation progresses.

27. identified Nov 28, 2025, 07:14 PM UTC

    The investigation into the load balancer configuration issue identified during overnight infrastructure maintenance is still ongoing. At this time, we do not have any new developments to report. Multiple engineers from Microsoft’s Product Group remain actively engaged, working together with Edarat and our internal team. Service continues to be impacted. We will provide the next update within 1 hour, or sooner if new information becomes available. Thank you for your continued patience.

28. identified Nov 28, 2025, 08:25 PM UTC

    We continue to investigate the load balancer configuration issue arising from the overnight infrastructure maintenance. There are no new findings to report at this time. Several engineers from Microsoft’s Product Group remain actively involved, collaborating closely with Edarat and our internal teams. Service remains impacted as this work proceeds. Our next update will be provided within 1 hour. Thank you for your patience.

29. identified Nov 28, 2025, 09:14 PM UTC

    The load balancer configuration issue from the overnight infrastructure maintenance remains under active investigation. At this stage, there are no material updates. Multiple engineers from Microsoft’s Product Group continue to work closely with Edarat and our internal team to identify the root cause. Service continues to be impacted. We will provide the next update within 1 hour. Thank you for your continued patience.

30. identified Nov 28, 2025, 10:15 PM UTC

    The investigation into the load balancer configuration issue identified during the overnight infrastructure maintenance is still in progress. At this time, there are no new developments. Multiple engineers from Microsoft’s Product Group remain actively engaged alongside Edarat and our internal engineering teams. Service remains impacted while the investigation continues. We will share the next update within 1 hour. Thank you for your patience and understanding.

31. monitoring Nov 28, 2025, 11:20 PM UTC

    We have applied changes that appear to address the load balancer configuration issue. While early signs are positive, we are continuing to monitor the environment closely to ensure full stability. With this progress, we will no longer provide hourly updates. We will issue a further update once the fix has been fully validated or if any new information arises. Thank you for your patience throughout this incident.

32. resolved Dec 02, 2025, 12:16 PM UTC

    This issue has been resolved.

Read the full incident report →