Skip to main content
Grafana Cloud

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

Partial outage Lasted 17h 51m · started · Grafana Cloud's page

Level
confirmed
Worst impact
Partial outage
Components
AWS Australia - prod-au-southeast-1: 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 (OH) - 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
Regions
ap-northeast-0, ap-south-0, ap-south-1, ap-southeast-0, ap-southeast-1, apac, au, ca, ca-east-0, eu, eu-north-0, eu-west-0, eu-west-2, eu-west-3, in, jp, latam, me, me-central-1, sa-east-0, sa-east-1, us, us-central-0, us-central2, us-east-0, us-west-0
Down Index
53of 100

What to do

  • Check whether you use Grafana Cloud AWS Australia - prod-au-southeast-1: 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 and 16 more in ap-northeast-0, ap-south-0, ap-south-1, ap-southeast-0. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 17h 51m it lasted.

    Anything that failed between 2026-06-17 20:17 UTC and 2026-06-18 14:08 UTC may need a replay.
  • Subscribe to Grafana Cloud's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=grafana-cloud works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Grafana Cloud 6

  1. 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.

    provider

  2. identified

    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.

    provider

  3. identified

    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.

    provider

  4. identified

    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.

    provider

  5. monitoring

    A fix has been implemented and we are monitoring the results.

    provider

  6. resolved

    This incident has been resolved.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-ada8bf6740

Is Grafana Cloud still down?

No, this incident was resolved 2026-06-18 14:08 UTC. For Grafana Cloud's live state, see https://down.guide/grafana-cloud.

How long did it last?

17h 51m, from 2026-06-17 20:17 UTC to 2026-06-18 14:08 UTC, by the times Grafana Cloud posted.

What was affected?

Grafana Cloud named AWS Australia - prod-au-southeast-1: 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 and 16 more in ap-northeast-0, ap-south-0, ap-south-1, ap-southeast-0.

What caused it?

Grafana Cloud hasn't published a root cause. If it does, it shows here.

Where does this come from?

Grafana Cloud's official status page, https://status.grafana.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.