Grafana Cloud incident: Failures Submitting Self-Serve Configuration Changes for Grafana Cloud Logs in AWS Sweden (prod-eu-north-0)

1. resolvedSep 12, 2026, 23:00 UTC

   Between approximately 23:00 UTC on September 12, 2026 and 09:12 UTC on September 14, 2026, some Grafana Cloud Logs customers in AWS Sweden (prod-eu-north-0) may have intermittently experienced errors when submitting configuration changes through the Cloud Portal. This has been resolved, and configuration change requests are being accepted normally.

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.

• Elasticsearch: Replication bug causing slow recoveriesMajor · Sep 1, 2026, 08:16 UTC
• MongoDB Atlas: Impaired Cluster operations in AWS me-central-1 and AWS me-south-1Major · Sep 3, 2026, 16:44 UTC
• Elasticsearch: Elastic Agent enrollment/check-in failures on 9.5.3 (and 9.4.6) with Fleet remote Elasticsearch outputMajor · Sep 9, 2026, 20:44 UTC
• Anthropic: Degraded functionality for Claude Cowork on WindowsMajor · Sep 10, 2026, 15:54 UTC
• Shippo: Elevated error rate on Royal Mail_SF TrackingMajor · Sep 12, 2026, 21:47 UTC
• Twilio: Voice Call Failures from a Subset of Twilio Phone Numbers to Hong KongMinor · Sep 12, 2026, 00:16 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