Skip to main content
Grafana Cloud

Elevated Latency in Grafana Cloud Logs (prod-ap-south-1)

Degraded Lasted 0m · started · Grafana Cloud's page

Level
confirmed
Worst impact
Degraded
Regions
ap-south-1
Down Index
12of 100

What to do

  • Check whether you use Grafana Cloud in ap-south-1. 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 0m it lasted.

    Anything that failed between 2026-09-02 14:14 UTC and 2026-09-02 14:14 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 1

  1. resolved

    We observed elevated latency in Grafana Cloud Logs between 08:00 and 11:00 UTC for a subset of deployments in prod-ap-south-1. The issue is now 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-ed6c3c0ed1

Is Grafana Cloud still down?

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

How long did it last?

0m, from 2026-09-02 14:14 UTC to 2026-09-02 14:14 UTC, by the times Grafana Cloud posted.

What was affected?

Grafana Cloud named in ap-south-1.

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.