outages.live
Live
Grafana CloudIncident · 2026-09-08 16:14 UTC

High Latency in prod-us-east-2

ResolvedOfficial update

This incident has been resolved.

The latest update from Grafana Cloud.

State

Resolved

Started

54 d ago

2026-09-08 16:14 UTC

Lasted

4 h 19 min

until 2026-09-08 20:34 UTC

Worst impact

Degraded

Timeline

3 updates
16:1417:1918:2419:2920:34
DegradedUpdate postedTimes in UTC

Investigating

49 min 19%

Monitoring

3 h 30 min 81%

Updates

Times in UTC

As posted by Grafana Cloud

Resolved2026-09-08 20:34 UTC

This incident has been resolved.

Monitoring2026-09-08 17:04 UTC

We have observed latency return to normal levels, and we will continue to monitor this incident.

Investigating2026-09-08 16:14 UTC

We are currently investigating an issue causing high latency for deployments in the prod-us-east-2 cluster.

Affected components

2
AWS US East (OH) - prod-us-east-2Grafana - AWS US East - prod-us-east-2

Grafana Cloud in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

44

Days with an incident

36

Median duration

2 h 53 min

This incident

1.5× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

14 days
median 2 h 53 min
90 days agoToday

Other Grafana Cloud incidents

All incidents

Grafana Cloud·Frontend Observability Outage in prod-eu-west-2

This incident has been resolved.

Resolvedresolved 5 d ago

Grafana Cloud·Degraded Cloud Integrations

This incident has been resolved.

Resolvedresolved 4 d ago

Grafana Cloud·ingestion errors in mimir-prod-66

the issue is resolved now, we're watching the cell

Resolvedresolved 6 d ago

Grafana Cloud·Some Grafana Instances Experiencing Issues Coming Online after Restart

This incident has been resolved.

Resolvedresolved 9 d ago

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

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.

Resolvedresolved 9 d ago

Follow Grafana Cloud

Your coding agent knows when Grafana Cloud is down, and tells you when a failure is theirs, not yours. You can also get Grafana Cloud incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "grafana" and tell me if Grafana Cloud has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=grafana
Slack
/feed subscribe https://outages.cc/feed.xml?providers=grafana

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane