New Multi-region uptime checks and custom-domain status pages

Grafana Cloud Outage History

Daily provider-status observations and published incident history for Grafana Cloud.

Operational

Grafana Cloud is operational. Verified . Official provider source.

Looking for an update now? Check the current status, or follow Grafana Cloud for future changes.

21.1% of 38 verified observed days had no reported provider issue

90-Day Trend

Jul 23Oct 20

Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.

Recorded Daily Status (Last 91 Days)

Jul 22 Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

October 2026
Degraded Performance with Increased Latency for Grafana Cloud Metrics and Traces in GCP US Central
major Observed active window 11h 33m

View incident details and source

Started:

GCP US Central - prod-us-central-0 GCP US Central - prod-us-central-5 GCP US Central - prod-us-central-0: Ingestion GCP US Central - prod-us-central-5: Ingestion GCP US Central - prod-us-central-0: Ingestion
investigating
We are investigating degraded performance and increased latency in the ingestion path for Grafana Cloud Metrics in GCP US Central (prod-us-central-0 and prod-us-central-5) and Grafana Cloud Traces in prod-us-central-0. Customers may experience intermittent errors or delays when sending metrics and traces. We continue to investigate the issue with our cloud provider. We do not have an estimated time to resolution at this time.
investigating
We are investigating degraded performance and increased latency in the ingestion path for Grafana Cloud Metrics in GCP US Central (prod-us-central-0 and prod-us-central-5) and Grafana Cloud Traces in prod-us-central-0. Customers may experience intermittent errors or delays when sending metrics and traces. We continue to investigate the issue with our cloud provider. We do not have an estimated time to resolution at this time.
investigating
We are investigating degraded performance and increased latency in the ingestion path for Grafana Cloud Metrics in GCP US Central (prod-us-central-0 and prod-us-central-5) and Grafana Cloud Traces in prod-us-central-0. Customers may experience intermittent errors or delays when sending metrics and traces. We have also received reports that some customers using Google Managed Prometheus in this region are experiencing issues when querying their GMP instances. We continue to investigate the issue with our cloud provider. We do not have an estimated time to resolution at this time.
investigating
We are investigating degraded performance and increased latency in the ingestion path for Grafana Cloud Metrics in GCP US Central (prod-us-central-0 and prod-us-central-5) and Grafana Cloud Traces in prod-us-central-0. Customers may experience intermittent errors or delays when sending metrics and traces. We have also received reports that some customers using Google Managed Prometheus in this region are experiencing issues when querying their GMP instances. We continue to investigate the issue with our cloud provider. We do not have an estimated time to resolution at this time.
investigating
We are investigating degraded performance with increased latency in the ingestion path for Grafana Cloud Metrics in GCP US Central (prod-us-central-0 and prod-us-central-5) and for Grafana Cloud Traces in prod-us-central-0. Customers may experience intermittent errors or delays when sending metrics and traces. We continue to investigate this with our cloud provider. We do not have an estimated time of resolution at this time. Next update by 18:30 UTC
investigating
We continue seeing elevated error rates and latency, and keep working with our cloud provider on this issue. Next update by 17:30 UTC.
investigating
We are investigating degraded performance with increased latency in the ingestion path for Grafana Cloud Metrics in GCP US Central (prod-us-central-0 and prod-us-central-5) and for Grafana Cloud Traces in prod-us-central-0. Customers may experience intermittent errors or delays when sending metrics and traces. We are investigating this with our cloud provider. We do not have an estimated time of resolution at this time. Next update by 16:30 UTC.
investigating
We are investigating degraded performance with increased latency in the ingestion path for Grafana Cloud Metrics in GCP US Central (prod-us-central-0 and prod-us-central-5) and for Grafana Cloud Traces in prod-us-central-0. Customers may experience intermittent errors or delays when sending metrics and traces. We are investigating this with our cloud provider. We do not have an estimated time of resolution at this time. Next update by 15:30 UTC.
investigating
We continue to investigate intermittent elevated error rates and latency affecting Grafana Cloud Metrics in GCP US Central (prod-us-central-0 and prod-us-central-5), and periodic increased latency affecting Grafana Cloud Traces in prod-us-central-0. Intermittent errors and latency may still occur. We are working with our cloud provider as part of the investigation. We do not have an estimated time of resolution at this time. Next update by 14:30 UTC.
investigating
Update to scope: we have not confirmed any impact to Grafana Cloud Logs, and Logs has been removed from the affected components. We continue to investigate intermittent elevated error rates and latency affecting Grafana Cloud Metrics in GCP US Central (prod-us-central-0 and prod-us-central-5), and periodic increased latency affecting Grafana Cloud Traces in prod-us-central-0. Error rates have decreased, but intermittent errors and latency may still occur. We are working with our cloud provider as part of the investigation. We do not have an estimated time of resolution at this time. Next update by 14:30 UTC.
investigating
We continue to investigate intermittent elevated error rates and latency affecting Grafana Cloud Metrics and Logs in GCP US Central (prod-us-central-0 and prod-us-central-5), and periodic increased latency affecting Grafana Cloud Traces in prod-us-central-0. Error rates have decreased, but intermittent errors and latency may still occur. We are working with our cloud provider as part of the investigation. We do not have an estimated time of resolution at this time. Next update by 14:30 UTC.
investigating
Beginning around 10:20 UTC, we have been seeing intermittent elevated error rates and latency affecting Grafana Cloud Metrics and Logs in GCP US Central (prod-us-central-0 and prod-us-central-5), and periodic increased latency and occasional errors affecting Grafana Cloud Traces in prod-us-central-0. Customers may see errors or delays when sending metrics, logs and traces. We are actively investigating. Next update by 13:40 UTC.
Intermittent Errors and Latency for Grafana Cloud Metrics and Logs in GCP US Central (prod-us-central-0 and prod-us-central-5)
major Observed active window 6m

View incident details and source

Started:

GCP US Central - prod-us-central-0 GCP US Central - prod-us-central-5 GCP US Central - prod-us-central-0: Ingestion GCP US Central - prod-us-central-5: Ingestion
investigating
Beginning around 10:20 UTC, we have been seeing intermittent elevated error rates and latency affecting Grafana Cloud Metrics and Logs in GCP US Central (prod-us-central-0 and prod-us-central-5). Customers may see errors or delays when sending metrics and logs. We are actively investigating. Next update by 13:40 UTC.
IRM Unable to Send SMS to Thailand Numbers
minor Observed active window 331h 27m

View incident details and source

Started:

Incident Management and Response (IRM)
identified
SMS delivery to Bangladesh has been restored. SMS delivery to Thailand is still affected, and we are continuing to work on a resolution. We will provide another update as soon as we have more information to share. In the meantime, we recommend that affected users configure mobile push or phone calls as notifications.
identified
SMS delivery to Austrian numbers has been restored. SMS delivery to Thailand and Bangladesh is still affected, and we are continuing to work on a resolution. We will provide another update as soon as we have more information to share. In the meantime, we recommend that affected users configure mobile push or phone calls as notifications.
identified
We are continuing working on a resolution, and will provide another update as soon as we have more information to share. In the meantime we recommend, affected users to configure mobile push or phone calls as notifications.
identified
We are continuing working on a resolution, and will provide another update as soon as we have more information to share. In the meantime we recommend, affected users to configure mobile push or phone calls as notifications.
identified
This issue is also impacting numbers from Thailand and Bangladesh. The title of this status page has been updated to reflect this. Users should configure mobile push or phone calls as notifications. We are working on a resolution, and we will provide another update as soon as we have more information to share.
identified
The issue has been identified. We are working on a resolution, but do not have an ETA at this time. We will provide another update as soon as we have more information to share. Users should configure mobile push or phone calls as notifications.
investigating
We are currently investigating an issue impacting all SMS attempts to Austria for IRM. All SMS attempts to Austria for IRM are currently blocked. We are working on a resolution, and an update will follow as soon as we have more info. Users should configure mobile push or phone calls as notifications.
Degraded data source queries
minor Observed active window 14m

View incident details and source

Started:

AWS Germany - prod-eu-west-2 AWS Germany - prod-eu-west-4 AWS US East - prod-us-east-2 GCP Australia - prod-au-southeast-0 GCP US Central - prod-us-central-4
investigating
We are investigating reduced query throughput for some data source plugins in multiple regions. Some queries may fail or be slow.
Elevated Write Latency and Errors for Grafana Cloud Logs in Azure Netherlands
minor Observed active window 4h 1m

View incident details and source

Started:

Azure Netherlands - prod-eu-west-3
investigating
We are continuing to investigate this issue. Next update by 11:30 UTC.
investigating
We are investigating elevated write latency and intermittent errors affecting Grafana Cloud Logs in Azure Netherlands. Customers may see delayed log ingestion and some failed write requests. Next update by 11:30 UTC.
September 2026
Elevated Latency and Errors for Grafana Cloud Logs in AWS US East (VA)
minor Observed active window 2h 59m

View incident details and source

Started:

AWS US East - prod-us-east-3
identified
An additional brief recurrence affected a small number of requests after our mitigation was deployed, though impact was smaller than earlier today. We continue to monitor and investigate a related, longer-running pattern. Next update by 15:40 UTC.
identified
We have identified a contributing factor to the elevated latency and are rolling out a mitigation to increase write capacity in AWS US East (VA). We continue to investigate a related, longer-running pattern. Next update by 14:40 UTC.
investigating
We are continuing to investigate this issue.
investigating
We are investigating elevated latency and a small number of failed requests for Grafana Cloud Logs in AWS US East (VA). Some customers writing logs to this region may see delayed ingestion or occasional write errors. We are actively investigating and will share more as we learn it. Next update by 13:38 UTC.
Grafana Access Issues
critical Observed active window 1h 52m

View incident details and source

Started:

AWS US East - prod-us-east-3
identified
We have identified the issue, and put a mitigation in place. We continue to work towards a resolution
investigating
We are continuing to investigate the issue, and will provide updates once we have more to share.
investigating
We are currently investigating an issue causing issues accessing the platform.
Cloud Provider Observability - Hosted Azure metrics issues
minor Observed active window 53m

View incident details and source

Started:

Integrations
monitoring
A fix has been implemented and we are monitoring the results.
investigating
Since approximately 00:19Z there has been an increase in errors returning metrics from Azure's germanywestcentral. We are currently investigating this issue.
Azure Monitor increased timeouts and errors in prod-eu-west-5
minor Observed active window 39m

View incident details and source

Started:

Integrations
investigating
Since approximately 07:49 UTC on 23 September 2026, Azure Monitor metric collection in the prod-eu-west-5 region has been experiencing increased timeouts and errors. Customers may see delayed or missing metrics. The issue remained ongoing as of 08:41 UTC. We are currently investigating this.
Kubernetes Observability Billing & Usage Incorrect
minor Observed active window 16h 42m

View incident details and source

Started:

Cost Management and Billing
monitoring
A fix has been implemented and we are monitoring the results.
investigating
Some customers may see a sudden spike in reported Kubernetes Observability usage even if they haven't activated the product. We are investigating the root cause, and will ensure the amount is corrected before any usage is invoiced.

Legacy Incident Archive

101 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.

June 2026
Rule Evaluation Outage in prod-us-central-0
major Source not attested
Last archived state: resolved
View archived record details
monitoring
We’re continuing to track progress post-mitigation. While we don’t have new information to share yet, our team remains actively engaged.
monitoring
We had an outage affecting rule evaluations between 15:16-15:59 UTC in the prod-us-central-0 region. Our team quickly identified the issue and has since mitigated. The engineering team is monitoring.
Issues with actions in the Grafana IRM mobile app
major Source not attested
Last archived state: resolved
View archived record details
monitoring
We've verified a fix in our staging environment to restore functionality to the mobile app. The fix is currently being deployed to production. Thanks for your patience as we continue to roll this out and monitor the resolution.
identified
We're noticing an uptick in users being unable to respond to actions on the mobile app (acknowledging and silencing alerts, for example). Users working in the web UI should not be affected. Ingestion and notification delivery are working as expected. We have a fix in place and are in the process of deploying.
Potential Issues Loading Grafana for Users in India
major Source not attested
Last archived state: resolved
View archived record details
monitoring
Error rates have remained near zero, and we continue to monitor.
monitoring
We are continuing to monitor for further issues.
monitoring
We have deployed additional mitigations that should help with remaining errors. We are continuing to monitor error rates.
monitoring
We’ve verified and begun to implement a fix that will improve loading errors. We are continuing to roll this out to all regions and monitor for efficacy.
monitoring
We're actively monitoring this issue and working with our 3rd party provider. The next update will be sent on Monday unless there's new information to share.
monitoring
Due to the linked GCP outage below, users located in India may have trouble loading parts of Grafana. https://status.cloud.google.com/incidents/5fGQt4VbkDnr3Yp8PXPr We are continuing to work with our CSP on this investigation. Impacted users may receive intermittent error messages such as "Error Loading" or "Failed to load Assets". To be clear, it does not matter the region the stack is located, but the geography where the user is physically in.
monitoring
Due to the linked GCP outage below, users located in India may have trouble loading parts of Grafana. https://status.cloud.google.com/incidents/5fGQt4VbkDnr3Yp8PXPr Impacted users may receive intermittent error messages such as "Error Loading" or "Failed to load Assets". To be clear, it does not matter the region the stack is located, but the geography where the user is physically in. We continue to work with our CSP on this investigation.
investigating
Due to the linked GCP outage below, users located in India may have trouble loading parts of Grafana. https://status.cloud.google.com/incidents/5fGQt4VbkDnr3Yp8PXPr Impacted users may receive error messages such as "Error Loading" or "Failed to load Assets". To be clear, it does not matter the region the stack is located, but the geography where the user is physically in. We are currently investigating this issue from our end, and will provide updates as they are available.
Degraded k6 cloud UI performance
critical Source not attested
Last archived state: resolved
View archived record details
monitoring
We are continuing to monitor for any further issues.
monitoring
The root cause of the issue has been identified and a fix has been successfully deployed. We are observing widespread improvements across all systems. Our team is currently monitoring the environment to ensure performance remains stable.
investigating
We are continuing to investigate this issue.
investigating
We’re currently investigating an issue resulting in degraded k6 cloud UI performance and API response time. Our team is actively working to rectify this issue.
Frontend Observability - Suspected commit feature not working as expected
minor Source not attested
Last archived state: resolved
View archived record details
investigating
We’re currently investigating an issue affecting Frontend Observability product. The "Suspected commit" feature is not currently working as expected. Ingestion and querying is unaffected by this. Our team has identified the cause and is actively working on a fix. Thank you for your patience.
Loki data source-managed alert rules not visible in the Grafana Cloud Alerting UI
major Source not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
We are continuing to deploy the fix and monitor recovery efforts. As part of the rollout, we identified an issue that required adjustments to our deployment plan, which has extended the timeline for mitigation. Work remains actively underway, and we will share additional updates as progress continues.
identified
Deployment of the fix is still in progress. We are continuing to monitor the rollout and validate recovery across affected systems. We will share further updates as they become available.
identified
Our Engineering Team has implemented a fix which is now being rolled out. We will continue to monitor the situation and update as soon as we have more information.
identified
We have identified an issue where alert rules and alerts managed directly in a Loki data source (data source-managed alerting) are not displayed in the Grafana Cloud Alerting UI. Rules created via Prometheus/Mimir data sources and Grafana-managed alert rules are not affected. Impact is limited to visibility and management in the UI. Affected alert rules continue to evaluate and send notifications normally — there is no impact to alert delivery. Workaround: Loki alert rules can still be vi...
Grafana Dashboards page not displaying when set to ‘View by Folders’
major Source not attested
Last archived state: resolved
View archived record details
investigating
We’re currently investigating an issue affecting The Grafana Dashboards page. When set to view by folders, is currently experiencing an issue where no dashboards are shown. Our team is working on fixing the problem. In the meantime, switching to ‘View as list’ allows access to dashboards as usual”.
Investigating Issues with Data Source-Managed Alerting
major Source not attested
Last archived state: resolved
View archived record details
monitoring
Our team has implemented a fix and we are currently monitoring the results of this.
investigating
We are currently investigating an issue affecting data source-managed alerting management functionality in Grafana Cloud. Customers may experience problems viewing, creating, updating, or managing alerts through Grafana when using data source-managed alerting. This issue is limited to alert management functionality within Grafana. Alert evaluation and backend alerting services continue to operate normally. Direct alerting APIs for Mimir and Loki remain fully operational and are unaffected. ...
IRM Degraded Performance
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
We've released a fix to the IRM app that should restore service for affected customers with issues related to labels. Thanks for your patience while investigating. We're continuing to monitor as we confirm the resolution in place.
identified
We are continuing to work on a fix for this. To further clarify, this issue is not about accessing IRM or alert ingestion/notification/delivery, but rather with handling labels.
identified
The degraded performance is about labels, and we have seen this degradation in more regions.
identified
We are continuing to work on a fix for this issue.
identified
The issue has been identified and a fix is being implemented.
investigating
We are continuing to investigate this issue.
investigating
We are experiencing access issues in IRM as there are elevated 500 API responses in prod-us-central-0.
Brief Rule Evaluation Failures in prod-eu-west-3
major Source not attested
Last archived state: resolved
View archived record details
monitoring
The incident has been mitigated, and services are operating normally. We continue to monitor the service to ensure full stability.
monitoring
The incident has been mitigated, and services are operating normally. We are currently monitor the service to ensure full stability.
investigating
We’re making ongoing progress on the investigation alongside our upstream provider.
investigating
We are continuing to investigate this issue.
investigating
Intermittent spikes in rule evaluations continuing.
investigating
From 00:20:00 to 00:27:00 and again 00:32:00 to 00:38:00 there were brief spikes in rule evaluation failures. Engineers are investigating.