rewindex

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

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

Incident updateNormal progress (rule, 100%)Changed status.grafana.com (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

What changed

Struck in red is what Grafana Cloud removed; blue is what they added. Muted text is unchanged context.

ChangedStatus#1
Before: investigating
After: resolved
AddedResolved time#2
Before: not present
After: 2026-10-23 10:16 UTC
AddedUpdateresolved#3
Before: not present
After: 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.

Compared with the previous archived version of this incident (10 to 30-minute polling). View the live incident (opens in new tab).

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

History of this incident

YesterdayFriday, October 23Fri, Oct 23

2 incident changes

All Grafana Cloud changesGrafana Cloud profileMarkdownJSON