Metrics Alert Rule Evaluation Failures in AWS Australia (prod-au-southeast-1)
Metrics alert and recording rule evaluation did not work correctly in AWS Australia (prod-au-southeast-1). The affected components were Rule Evaluation and Alerting and SLO Rule Evaluation. Grafana Cloud reports that the outage is resolved and that it lasted about 1 hour 40 minutes.
State
Resolved
Started
2 h ago
2026-11-02 09:20 UTC
Lasted
1 h 48 min
until 2026-11-02 11:08 UTC
Worst impact
Degraded
Timeline
4 updatesInvestigating
1 h 48 min 100%
Updates
Times in UTCAs posted by Grafana Cloud
Between approximately 08:00 and 09:40 UTC (about 1 hour 40 minutes), some customers in AWS Australia (prod-au-southeast-1) experienced intermittent failures when evaluating alert and recording rules, which may have caused missed or delayed alert notifications and gaps in recorded series. This has been fully resolved and rule evaluation is operating normally.
We continue to investigate intermittent failures when evaluating alert and recording rules in AWS Australia (prod-au-southeast-1), first observed at approximately 08:00 UTC. Some customers may see rules fail to evaluate or be delayed, which can result in missed or delayed alert notifications and gaps in recorded series. We are continuing to investigate. Next update by 11:15 UTC.
We are investigating an elevated rate of failures when evaluating Metrics alert and recording rules in AWS Australia (prod-au-southeast-1). Some customers may see rules missed or delayed rule evaluations, which can result in missed or delayed alert notifications and gaps in recorded series. Next update by 10:20 UTC.
We are investigating an elevated rate of failures when evaluating Metrics alert and recording rules in AWS Australia (prod-au-southeast-1). Some customers may see rules delayed rule evaluations, which can result in missed or delayed alert notifications and gaps in recorded series. Next update by 10:20 UTC.
Affected components
2Grafana Cloud in the last 90 days
Full historyIncidents in 90 days
46
Days with an incident
37
Median duration
2 h 50 min
This incident
36% shorter than the median
Other Grafana Cloud incidents
All incidentsGrafana Cloud·IRM Unable to Voice Call Brazil Numbers
Grafana Cloud reports that voice calls to Brazil do not work in Incident Management and Response (IRM). Grafana Cloud is investigating the issue. Users can set mobile push or SMS as notifications.
Grafana Cloud·Frontend Observability Outage in prod-eu-west-2
This incident has been resolved.
Grafana Cloud·Degraded Cloud Integrations
This incident has been resolved.
Grafana Cloud·ingestion errors in mimir-prod-66
the issue is resolved now, we're watching the cell
Grafana Cloud·Some Grafana Instances Experiencing Issues Coming Online after Restart
This incident has been resolved.
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.
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.
https://outages.cc/feed.xml?providers=grafana/feed subscribe https://outages.cc/feed.xml?providers=grafanaFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane