Skip to main content
Grafana Cloud

Tempo Write Failures in prod-us-central-0

Partial outage Lasted 5h 43m · started · Grafana Cloud's page

Level
confirmed
Worst impact
Partial outage
Components
GCP US Central - prod-us-central-0: Ingestion
Regions
us, us-central-0
Down Index
39of 100

What to do

  • Check whether you use Grafana Cloud GCP US Central - prod-us-central-0: Ingestion in us, us-central-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 5h 43m it lasted.

    Anything that failed between 2026-10-15 16:10 UTC and 2026-10-15 21:53 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.

Root cause

We are investigating Intermittent write failures in tempo-prod (prod-us-central-0) due to Google Cloud Storage internal errors.
Read the postmortem

Updates from Grafana Cloud 3

  1. investigating

    We are investigating Intermittent write failures in tempo-prod (prod-us-central-0) due to Google Cloud Storage internal errors.

    provider

  2. monitoring

    Things are starting to recover, and we continue to monitor the issue.

    provider

  3. 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-07be841a6e

Is Grafana Cloud still down?

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

How long did it last?

5h 43m, from 2026-10-15 16:10 UTC to 2026-10-15 21:53 UTC, by the times Grafana Cloud posted.

What was affected?

Grafana Cloud named GCP US Central - prod-us-central-0: Ingestion in us, us-central-0.

What caused it?

Grafana Cloud wrote: "We are investigating Intermittent write failures in tempo-prod (prod-us-central-0) due to Google Cloud Storage internal errors." The postmortem: https://stspg.io/0w7m43wy213v

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.