Rewindex

CompaniesGrafana CloudIncidents

Grafana Cloud: Synthetic monitoring - Stockholm probe - elevated latency and error rates

No impact listedStatus: resolvedStarted Resolved (0 min)1 updatestatus.grafana.com (opens in new tab)
Part of an outage event

AWS outage, Feb 13, 2025 · 11 vendors, 11 incidents

Grafana Cloud’s incident blames AWS as the cause. (hop 1, posted +5 h 57 min vs the first vendor naming AWS)

“…and error rates in our Stockholm probe. This was related to a network connectivity within AWS in the EU-NORTH-1 region. The issue is resolved and the probe is operating normally. See the AWS service h…”

Swipe sideways to see the whole diagram.

AWSown incident not archivedWithin an hour2 vendors, 1 blamed AWSCourier, Teleport1 to 4 hours later5 vendors, 4 blamed AWSCoralogix, SingleStore, Aptible, Snowflake +1Later1 vendor, 1 blamed AWSGrafana CloudGrafana Cloud (this incident)posted +5 h 57 min
AWSown incident not archivedWithin an hour2 vendors, 1 blamed AWSCourier, Teleport1 to 4 hours later5 vendors, 4 blamed AWSCoralogix, SingleStore, Aptible,Snowflake +1Later1 vendor, 1 blamed AWSGrafana CloudGrafana Cloud (this incident)posted +5 h 57 min
Grafana Cloud is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
flowchart LR
  root["AWS<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>2 vendors, 1 blamed AWS<br/>Courier, Teleport"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>5 vendors, 4 blamed AWS<br/>Coralogix, SingleStore, Aptible, Snowflake +1"]:::blames
  root --> h4
  later["Later<br/>1 vendor, 1 blamed AWS<br/>Grafana Cloud"]:::blames
  root --> later
  me["Grafana Cloud (this incident)<br/>posted +5 h 57 min"]:::me
  later --- me

Full event: timeline, evidence and all vendors →

Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.

Timeline of updates

  1. resolved

    From February 13th 23:30 UTC to February 14th 00:30 UTC, we saw higher latency and error rates in our Stockholm probe. This was related to a network connectivity within AWS in the EU-NORTH-1 region. The issue is resolved and the probe is operating normally. See the AWS service health page for more information.

From Grafana Cloud’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.

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.

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

This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.

Impact, status and times are the vendor’s own, as last archived. View on status.grafana.com (opens in new tab).

Grafana Cloud profileRecent Grafana Cloud incidentsMarkdownJSON