Grafana incident

Loki data source-managed alert rules not visible in the Grafana Cloud Alerting UI

Major Ongoing View vendor source →

Grafana is currently experiencing a major incident affecting AWS Australia - prod-ap-southeast-2: Alertmanager and Rules Configuration API and AWS Brazil - prod-sa-east-1: Alertmanager and Rules Configuration API and 1 more component, which began 2h ago. The vendor's full update timeline is below.

Started
Jun 17, 2026, 08:17 PM UTC
Resolved
Ongoing
Duration
● 2h 6m
Detected by Pingoru
Jun 17, 2026, 08:17 PM UTC

Affected components

AWS Australia - prod-ap-southeast-2: Alertmanager and Rules Configuration APIAWS Brazil - prod-sa-east-1: Alertmanager and Rules Configuration APIAWS Canada - prod-ca-east-0: Alertmanager and Rules Configuration APIAWS Germany - prod-eu-west-2: Alertmanager and Rules Configuration APIAWS UAE - prod-me-central-1: Alertmanager and Rules Configuration APIAWS India - prod-ap-south-1: Alertmanager and Rules Configuration APIAWS Japan - prod-ap-northeast-0: Alertmanager and Rules Configuration APIAWS Singapore - prod-ap-southeast-1: Alertmanager and Rules Configuration APIAWS Sweden - prod-eu-north-0: Alertmanager and Rules Configuration APIAWS US East - prod-us-east-0: Alertmanager and Rules Configuration API

Update timeline

  1. identified Jun 17, 2026, 08:17 PM UTC

    We have identified an issue where alert rules and alerts managed directly in a Loki data source (data source-managed alerting) are not displayed in the Grafana Cloud Alerting UI. Rules created via Prometheus/Mimir data sources and Grafana-managed alert rules are not affected. Impact is limited to visibility and management in the UI. Affected alert rules continue to evaluate and send notifications normally — there is no impact to alert delivery. Workaround: Loki alert rules can still be viewed and managed directly through the Loki ruler API (for example, using cortextool against /loki/api/v1/rules). A fix has been identified and is in progress. We will provide a further update once it has been rolled out.

  2. identified Jun 17, 2026, 08:55 PM UTC

    Our Engineering Team has implemented a fix which is now being rolled out. We will continue to monitor the situation and update as soon as we have more information.

  3. identified Jun 17, 2026, 09:43 PM UTC

    Deployment of the fix is still in progress. We are continuing to monitor the rollout and validate recovery across affected systems. We will share further updates as they become available.