Grafana Cloud incident: o11y requests too large for nods in the prod-eu-west-2 region.

Affected components

• AWS Germany - prod-eu-west-2: Alertmanager
• AWS Germany - prod-eu-west-2: Alertmanager and Rules Configuration API
• AWS Germany - prod-eu-west-2: Rule Evaluation

1. resolvedAug 5, 2026, 11:44 UTC

   This incident has been resolved.

2. investigatingAug 5, 2026, 11:41 UTC

   We are currently investigating an issue with critical o11y requests being too large for nods in the prod-eu-west-2 region. This is leading to issues in scaling up services, and may may lead increased errors in requests.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Grafana Cloud's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• MongoDB Atlas: GCP capacity constraints affecting Atlas deploymentsMajor · Aug 5, 2026, 05:17 UTC
• Supabase: Project Upgrade DelaysMinor · Aug 3, 2026, 15:28 UTC
• OVHcloud: [EU-WEST-PAR][Storage] - Object storage incident notificationMinor · Aug 4, 2026, 14:08 UTC
• Snyk: Degraded performance on Security.snyk.io with 502 responses.Minor · Aug 5, 2026, 04:28 UTC
• Anthropic: Degraded performance of multiple modelsMinor · Aug 5, 2026, 07:05 UTC
• GitHub: Some Copilot Cloud Agent jobs not startingMinor · Aug 5, 2026, 11:38 UTC

How often does Grafana Cloud have incidents?

Grafana Cloud reported 41 incidents in the last 90 days, 15 of them major or critical. A typical incident lasted 2h 29m. See Grafana Cloud's uptime and incident history