Grafana incident

Notification Policies and Contact Points Missing in UI on the Slow Release Channel

Minor Resolved View vendor source →

Grafana experienced a minor incident on April 6, 2026 affecting AWS Australia - prod-ap-southeast-2: Rule Evaluation and AWS Australia - prod-ap-southeast-2: Alertmanager and Rules Configuration API and 1 more component, lasting 21h 38m. The incident has been resolved; the full update timeline is below.

Started
Apr 06, 2026, 02:48 PM UTC
Resolved
Apr 07, 2026, 12:26 PM UTC
Duration
21h 38m
Detected by Pingoru
Apr 06, 2026, 02:48 PM UTC

Affected components

AWS Australia - prod-ap-southeast-2: Rule EvaluationAWS Australia - prod-ap-southeast-2: Alertmanager and Rules Configuration APIAWS Australia - prod-ap-southeast-2: AlertmanagerAWS Brazil - prod-sa-east-1: Rule EvaluationAWS Brazil - prod-sa-east-1: Alertmanager and Rules Configuration APIAWS Brazil - prod-sa-east-1: AlertmanagerAWS Canada - prod-ca-east-0: Rule EvaluationAWS Canada - prod-ca-east-0: Alertmanager and Rules Configuration APIAWS Canada - prod-ca-east-0: AlertmanagerAWS Germany - prod-eu-west-2: Rule Evaluation

Update timeline

  1. investigating Apr 06, 2026, 02:48 PM UTC

    We’re currently investigating an issue affecting notification policies and contact points for instances on the slow release channel. Alerting API calls for contact points and notification policies return data as expected, so this appears to be limited to the UI. Our team is actively working to identify the cause and will share an update within 1-2 hours. Thank you for your patience.

  2. investigating Apr 06, 2026, 04:13 PM UTC

    We’re continuing to investigate the issue with the alerting UI. While we don’t have new information to share yet, our team is working to identify the root cause. Next update in 2 hours.

  3. identified Apr 06, 2026, 09:04 PM UTC

    We’ve identified the cause of the issue impacting the Notification Policy and Contact Point UI. Our team is currently implementing a fix. We’ll provide another update when the fix is deployed and we monitor the expected improvement.

  4. monitoring Apr 06, 2026, 11:58 PM UTC

    We’ve implemented a fix and are monitoring the results to confirm the issue is fully resolved. Services may start to recover during this time. We’ll update again within 2 hours.

  5. resolved Apr 07, 2026, 12:26 PM UTC

    This incident has been resolved.