Cloud Native Scans service degradation
Incident Lifecycle
Incident Timeline
Identified
Restore process is still in progress. A further update will be sent once the restoration is completed
Mar 18, 2026 at 5:32 PM UTC
Identified
Restore process is progressing. A further update will be sent once the restoration is completed
Mar 18, 2026 at 12:23 PM UTC
Identified
Our team is continuing to work on restoring historical reachability data, we will post further updates as soon as possible
Mar 18, 2026 at 8:24 AM UTC
Identified
We are continuing to work on a fix for this issue.
Mar 17, 2026 at 11:48 PM UTC
Identified
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.
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.
Mar 17, 2026 at 11:47 PM UTC
Investigating
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.
Mar 17, 2026 at 11:17 PM UTC
Was your business affected by this Mend outage?
Set up instant alerts for Mend — be the first to know about outages via email, Slack, Teams, or Discord.