Cloud Native Scans service degradation

Update timeline

1. investigating Mar 17, 2026, 11:17 PM UTC

   We are currently experiencing a degradation in our Cloud Native Scans service due to Azure region capacity constraints. Some scans may be delayed or fail to complete. We are actively investigating and will provide updates as they become available.

2. identified Mar 17, 2026, 11:47 PM UTC

   The Azure region capacity constraints affecting the Cloud Native Scans service have been mitigated. Scans are now running normally. However, historical reachability data is currently unavailable while we work to restore it. We apologize for the inconvenience and will post further updates on data availabilit.

3. identified Mar 17, 2026, 11:48 PM UTC

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

4. identified Mar 18, 2026, 08:24 AM UTC

   Our team is continuing to work on restoring historical reachability data, we will post further updates as soon as possible

5. identified Mar 18, 2026, 12:23 PM UTC

   Restore process is progressing. A further update will be sent once the restoration is completed

6. identified Mar 18, 2026, 05:32 PM UTC

   Restore process is still in progress. A further update will be sent once the restoration is completed

7. resolved Mar 19, 2026, 11:25 AM UTC

   Recent reachability traces (since January 2026) were restored The rest of the history will be restored continuously until it is completed successfully.