Scope and ATLAS Exit unavailable for some customers

Update timeline

1. investigating Aug 27, 2026, 09:09 AM UTC

   We are currently investigating an unscheduled downtime of several Scope servers.

2. identified Aug 27, 2026, 09:42 AM UTC

   We identified the underlying issue with one of our datacenters and are working on a mitigation

3. identified Aug 27, 2026, 10:04 AM UTC

   We are working with our datacenter supplier on solving the underlying issue.

4. identified Aug 27, 2026, 10:27 AM UTC

   Our datacenter supplier has identified details about the underlying issue and is working on rolling back to a working state.

5. identified Aug 27, 2026, 11:08 AM UTC

   Mitigation efforts are ongoing. Our engineers are taking a cautious and methodical approach to minimize any risk to other production systems and maintain overall service stability.

6. identified Aug 27, 2026, 11:11 AM UTC

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

7. identified Aug 27, 2026, 11:42 AM UTC

   A proper mitigation for the issue has been found and is currently being applied.

8. identified Aug 27, 2026, 12:43 PM UTC

   Unfortunately, the mitigation measures implemented recently have not resolved the issue as intended. Our engineers are currently evaluating additional options and working to identify the most effective path to restoration.

9. identified Aug 27, 2026, 01:12 PM UTC

   We have identified additional options to address the issue and are currently implementing them in parallel. We will continue to monitor progress closely and provide further updates as they become available.

10. identified Aug 27, 2026, 01:55 PM UTC

    We are still actively working to resolve the issue. Additional mitigation efforts remain underway, and we will share more information as it becomes available.

11. identified Aug 27, 2026, 02:32 PM UTC

    The mitigation measures implemented have not resolved the issue as expected. Our engineers are continuing to work on additional remediation actions and will provide further updates as they become available.

12. identified Aug 27, 2026, 03:14 PM UTC

    Despite our tremendous efforts, we have unfortunately not yet been able to identify a breakthrough or sustainable solution to the issue. Please be assured that we continue to work on this with the highest priority and full commitment. We have already mobilized all available resources, including our international experts and support teams, to leverage every possible avenue toward resolving the problem. We remain fully focused on finding a solution as quickly as possible and will continue to provide updates on our progress.

13. monitoring Aug 27, 2026, 03:39 PM UTC

    We have identified a successful remediation and are currently rolling it out. The affected services are recovering and becoming available again. Our team continues to monitor the environment closely to confirm a full restoration of service.

14. resolved Aug 27, 2026, 03:56 PM UTC

    The fix has been successfully deployed, and service has been fully restored. All affected systems are operating normally. We will continue to monitor the environment to ensure stability and prevent recurrence.