Live

Alert rule creation, deletion, and update degradation in prod-us-east-2

The issue has been mitigated and there's a code fix pending.

The latest update from Grafana Cloud.

State

Resolved

Started

58 d ago

2026-09-04 13:36 UTC

Lasted

2 h 56 min

until 2026-09-04 16:32 UTC

Worst impact

Degraded

Timeline

2 updates
13:3614:2015:0415:4816:32
DegradedUpdate postedTimes in UTC

Investigating

2 h 56 min 100%

Updates

Times in UTC

As posted by Grafana Cloud

Resolved2026-09-04 16:32 UTC

The issue has been mitigated and there's a code fix pending.

Investigating2026-09-04 13:36 UTC

We’re currently investigating an issue affecting alert rule creation, deletion, and updates in prod-us-east-2. Our team is actively working to identify the cause. Thank you for your patience.

Affected components

4
AWS US East (OH) - prod-us-east-0: Alertmanager and Rules Configuration APIAWS US East (OH) - prod-us-east-0: AlertmanagerAlerting and SLO - AWS US East - prod-us-east-0: Alertmanager and Rules Configuration APIAlerting and SLO - AWS US East - prod-us-east-0: Alertmanager

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

About 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

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