Skip to main content
Grafana Cloud

Elevated Trace Ingestion Latency and Errors for Grafana Cloud Traces in AWS Germany

Partial outage Lasted 45m · started · Grafana Cloud's page

Level
confirmed
Worst impact
Partial outage
Components
AWS Germany - prod-eu-west-2, AWS Germany - prod-eu-west-2: Ingestion
Regions
eu, eu-west-2

What to do

  • Check whether you use Grafana Cloud AWS Germany - prod-eu-west-2, AWS Germany - prod-eu-west-2: Ingestion in eu, eu-west-2. 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 45m it lasted.

    Anything that failed between 2026-10-23 09:31 UTC and 2026-10-23 10:16 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 2

  1. investigating

    We are investigating elevated latency and intermittent errors when ingesting traces for Grafana Cloud Traces in AWS Germany. Customers may see delayed trace ingestion and failed trace writes. Next update by 10:30 UTC.

    provider

  2. resolved

    Between 09:31 and 10:13 UTC on 23 October 2026 (42 minutes), Grafana Cloud Traces in AWS Germany experienced elevated ingestion latency and intermittent trace write failures, affecting both direct trace ingestion and ingestion via the OpenTelemetry endpoint. All services are now operating normally.

    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-ce3ee4d000

Is Grafana Cloud still down?

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

How long did it last?

45m, from 2026-10-23 09:31 UTC to 2026-10-23 10:16 UTC, by the times Grafana Cloud posted.

What was affected?

Grafana Cloud named AWS Germany - prod-eu-west-2, AWS Germany - prod-eu-west-2: Ingestion in eu, eu-west-2.

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.