Grafana Cloud
Grafana Cloud is reporting degraded
Partially Degraded Service
History
Incidents in 90 days
45
Days with an incident
37
Median duration
2 h 53 min
Longest incident
14 days
Components
542Website and Support
Profiles
Oct 27, 2026
Oct 23, 2026
This incident has been resolved.status.grafana.com
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.status.grafana.com
Oct 21, 2026
This incident has been resolved.status.grafana.com
This incident has been resolved.status.grafana.com
As of 21 Oct, 06:20 am UTC, we became aware of an issue with possible incorrect evaluation of Synthetic Monitoring alert rules in cluster prod-us-east-3. The issue has been ended 07:00 am UTCstatus.grafana.com
Oct 20, 2026
This incident has been resolved.status.grafana.com
This incident has been resolved.status.grafana.com
This incident has been resolved.status.grafana.com
This incident has been resolved.status.grafana.com
Oct 15, 2026
Oct 13, 2026
This incident has been resolved. Thank you for your patience.status.grafana.com
Following further investigation, we've confirmed that SMS delivery to certain destinations is not currently supported. We've updated our documentation to clarify the supported destinations and available notification options. We recommend using mobile push notifications or phone calls as alternatives where SMS delivery is unavailable.status.grafana.com
Maintenance
Scheduled Database Maintenance – Temporary Grafana Instance Unavailability
Your Grafana instance will be temporarily unavailable due to scheduled maintenance. Downtime is expected to last between 5 to 15 minutes depending on your instance size. Alerts and scheduled reports may be impacted during this period. No action is required — your instance will return to its normal working state automatically once maintenance is complete. We apologize for the inconvenience.
Scheduled Database Maintenance – Temporary Grafana Instance Unavailability
Your Grafana instance will be temporarily unavailable due to scheduled maintenance. Downtime is expected to last between 5 to 15 minutes depending on your instance size. Alerts and scheduled reports may be impacted during this period. No action is required — your instance will return to its normal working state automatically once maintenance is complete. We apologize for the inconvenience.
Scheduled Database Maintenance – Temporary Grafana Instance Unavailability
Your Grafana instance will be temporarily unavailable due to scheduled maintenance. Downtime is expected to last between 5 to 15 minutes depending on your instance size. Alerts and scheduled reports may be impacted during this period. No action is required — your instance will return to its normal working state automatically once maintenance is complete. We apologize for the inconvenience.
Scheduled Database Maintenance – Temporary Grafana Instance Unavailability
Your Grafana instance will be temporarily unavailable due to scheduled maintenance. Downtime is expected to last between 5 to 15 minutes depending on your instance size. Alerts and scheduled reports may be impacted during this period. No action is required — your instance will return to its normal working state automatically once maintenance is complete. We apologize for the inconvenience.
Scheduled Database Maintenance – Temporary Grafana Instance Unavailability
Your Grafana instance will be temporarily unavailable due to scheduled maintenance. Downtime is expected to last between 5 to 15 minutes depending on your instance size. Alerts and scheduled reports may be impacted during this period. No action is required — your instance will return to its normal working state automatically once maintenance is complete. We apologize for the inconvenience.
Affected components
1- Incident Management and Response (IRM)Degraded
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.live/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.live/feed.xml?providers=grafana/feed subscribe https://outages.live/feed.xml?providers=grafanaGo from tracking outages to fixing production issues with Polylane.
Try Polylane