A fix has been implemented and we are monitoring the results.
Posted Jun 18, 2026 - 08:04 UTC
Update
We are continuing to deploy the fix and monitor recovery efforts. As part of the rollout, we identified an issue that required adjustments to our deployment plan, which has extended the timeline for mitigation. Work remains actively underway, and we will share additional updates as progress continues.
Posted Jun 17, 2026 - 23:22 UTC
Update
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.
Posted Jun 17, 2026 - 21:43 UTC
Update
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.
Posted Jun 17, 2026 - 20:55 UTC
Identified
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.
Posted Jun 17, 2026 - 20:17 UTC
This incident affected: Alerting and SLO (AWS Australia - prod-ap-southeast-2: Alertmanager and Rules Configuration API, AWS Brazil - prod-sa-east-1: Alertmanager and Rules Configuration API, AWS Canada - prod-ca-east-0: Alertmanager and Rules Configuration API, AWS Germany - prod-eu-west-2: Alertmanager and Rules Configuration API, AWS UAE - prod-me-central-1: Alertmanager and Rules Configuration API, AWS India - prod-ap-south-1: Alertmanager and Rules Configuration API, AWS Japan - prod-ap-northeast-0: Alertmanager and Rules Configuration API, AWS Singapore - prod-ap-southeast-1: Alertmanager and Rules Configuration API, AWS Sweden - prod-eu-north-0: Alertmanager and Rules Configuration API, AWS US East - prod-us-east-0: Alertmanager and Rules Configuration API, AWS US West - prod-us-west-0: Alertmanager and Rules Configuration API, Azure Netherlands - prod-eu-west-3: Alertmanager and Rules Configuration API, Azure US Central - us-central2: Alertmanager and Rules Configuration API, GCP Australia - prod-au-southeast-0: Alertmanager and Rules Configuration API, GCP Belgium - prod-eu-west-0: Alertmanager and Rules Configuration API, GCP Brazil - prod-sa-east-0: Alertmanager and Rules Configuration API, GCP India - prod-ap-south-0: Alertmanager and Rules Configuration API, GCP Singapore - prod-ap-southeast-0: Alertmanager and Rules Configuration API, GCP UK - prod-gb-south-0: Alertmanager and Rules Configuration API, GCP US Central - prod-us-central-0: Alertmanager and Rules Configuration API).