- Level
- confirmed
- Worst impact
- Degraded
- Components
- GCP US Central - prod-us-central-0, GCP US Central - prod-us-central-5, GCP US Central - prod-us-central-0: Ingestion, GCP US Central - prod-us-central-5: Ingestion, GCP US Central - prod-us-central-0: Ingestion
- Regions
- us, us-central-0, us-central-5
- Down Index
- 35of 100
What to do
Check whether you use Grafana Cloud GCP US Central - prod-us-central-0, GCP US Central - prod-us-central-5, GCP US Central - prod-us-central-0: Ingestion, GCP US Central - prod-us-central-5: Ingestion and 1 more in us, us-central-0, us-central-5. 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 22h 16m it lasted.
Anything that failed between 2026-05-13 08:50 UTC and 2026-05-14 07:06 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 7
- investigating
We’re currently investigating an issue causing intermittent errors and high latency when writing to Cloud Metrics. Our team is actively working to identify the cause. Thank you for your patience.
provider
- investigating
We’re continuing to investigate the issue causing intermittent errors and high latency when writing to Cloud Metrics. We are in contact with the cloud provider’s support team, and they are investigating the issue alongside us.
provider
- investigating
We have identified expanded impact affecting Grafana Cloud Logs and Grafana Cloud Traces in addition to Cloud Metrics, causing intermittent errors and increased latency when writing data. Our teams continue working on a fix and investigating the issue with the cloud provider’s support team.
provider
- monitoring
We are seeing signs of recovery and improved stability across impacted services over the past hour. Our teams continue to closely monitor the situation while working with the cloud provider.
provider
- monitoring
We continue to see signs of recovery and improved stability across impacted services. Our teams continue to closely monitor the situation while working with the cloud provider.
provider
- monitoring
We continue to see signs of recovery and improved stability across impacted services. Our teams continue to closely monitor the situation while working with the cloud provider.
provider
- resolved
We continue to observe an extended period of recovery and we're marking the incident as resolved at this point in time.
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-016922352c
Is Grafana Cloud still down?
No, this incident was resolved 2026-05-14 07:06 UTC. For Grafana Cloud's live state, see https://down.guide/grafana-cloud.
How long did it last?
22h 16m, from 2026-05-13 08:50 UTC to 2026-05-14 07:06 UTC, by the times Grafana Cloud posted.
What was affected?
Grafana Cloud named GCP US Central - prod-us-central-0, GCP US Central - prod-us-central-5, GCP US Central - prod-us-central-0: Ingestion, GCP US Central - prod-us-central-5: Ingestion and 1 more in us, us-central-0, us-central-5.
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.