Skip to main content
Grafana Cloud

DB issues in prod-sa-east-1

Degraded Lasted 2h 33m · started · Grafana Cloud's page

Level
confirmed
Worst impact
Degraded
Components
AWS Brazil - prod-sa-east-1, AWS Brazil - prod-sa-east-1: API, AWS Brazil - prod-sa-east-1: Public Probes
Regions
latam, sa-east-1
Down Index
27of 100

What to do

  • Check whether you use Grafana Cloud AWS Brazil - prod-sa-east-1, AWS Brazil - prod-sa-east-1: API, AWS Brazil - prod-sa-east-1: Public Probes in latam, sa-east-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 2h 33m it lasted.

    Anything that failed between 2026-10-20 21:36 UTC and 2026-10-21 00:09 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 4

  1. investigating

    We are currently investigating an issue in the prod-sa-east-1 region causing slow requests, or some stacks struggling to start. We will provide an update as soon as we have more information to share.

    provider

  2. investigating

    Synthetic Monitoring alerting is also impacted. We are continuing to investigate this issue.

    provider

  3. investigating

    Synthetic Monitoring alerting has recovered. We are continuing to monitor.

    provider

  4. 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-cb8eb1cce5

Is Grafana Cloud still down?

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

How long did it last?

2h 33m, from 2026-10-20 21:36 UTC to 2026-10-21 00:09 UTC, by the times Grafana Cloud posted.

What was affected?

Grafana Cloud named AWS Brazil - prod-sa-east-1, AWS Brazil - prod-sa-east-1: API, AWS Brazil - prod-sa-east-1: Public Probes in latam, sa-east-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.