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.

Regional incident

Grafana Cloud has an active regional incident; no global outage is indicated. 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

September 2026
Investigating issues in US Central (prod-us-central-0, prod-us-central-5)
minor Observed active window 4h 59m

View incident details and source

Started:

identified
We have identified the cause as an issue in our cloud provider’s US Central region. A mitigation is in place and recovery is in progress. Customers in prod-us-central-0 and prod-us-central-5 may still see errors or delays with metrics, logs, or Grafana while services come back. We will update this page as recovery continues.
investigating
We are investigating reports of errors affecting Grafana Cloud in US Central (prod-us-central-0, prod-us-central-5). Customers in this region may see timeouts or failed requests when writing or querying logs and metrics. We are looking into this and will post another update as soon as we have more information.
August 2026
Partial Logs Write Outage
major Observed active window 1h 32m

View incident details and source

Started:

AWS US East - prod-us-east-3
monitoring
This incident also had impact on Frontend Observability for the same region. A fix has been deployed, and things have stablized. We will continue to monitor on our end.
identified
We’ve identified the cause of an issue impacting Log writes. Our team is currently implementing a fix.
Some Grafana UI features may be unavailable or reverting to legacy behaviour
minor Observed active window 1h 41m

View incident details and source

Started:

identified
a resolution is rolling out to resolve the issues
identified
Some Grafana UI features may be unavailable or reverting to legacy behaviour
Elevated error rates affecting metrics writes in prod-us-central-0
minor Observed active window 1h 0m

View incident details and source

Started:

GCP US Central - prod-us-central-0: Ingestion
monitoring
A fix has been applied and metrics write error rates in prod-us-central-0 have returned to normal levels. Metrics ingestion is operating as expected. We are continuing to monitor the affected systems to confirm full recovery before marking this incident resolved.
investigating
We are investigating elevated error rates affecting metrics writes in prod-us-central-0. Customers in this region may see failed or delayed metrics ingestion, gaps in recent data on dashboards and queries, and alert rules that depend on the affected series may not evaluate as expected.

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.

April 2026
Tempo Write Outage
major Source not attested
Last archived state: resolved
View archived record details
monitoring
We’ve implemented a fix and are monitoring the results to confirm the issue is fully resolved. Services may start to recover during this time. We’ll update again within an hour.
investigating
We are currently investigating a write outage affecting prod-us-east-3. The issue began at 18:50 UTC. Users may experience errors, timeouts, or unavailability while we work to identify the cause and restore service.
K6 Browser Testing/Timeline Not Available
minor Source not attested
Last archived state: resolved
View archived record details
investigating
We’re currently investigating an issue affecting browser testing. Users running browser tests will not be able to see the browser timeline. Our team is actively working to identify the cause and will share an update within two hours. Thank you for your patience.
Unable to Edit Notification Policies
minor Source not attested
Last archived state: resolved
View archived record details
identified
We’ve identified the cause of the issue impacting notification policies. Our team is currently implementing a fix. We’ll provide another update in 2 hours or sooner if the situation changes.
identified
We’ve identified the cause of the issue impacting notification policies. Our team is currently implementing a fix. We’ll provide another update in 2 hours or sooner if the situation changes.
investigating
We’re currently investigating an issue affecting notification policies. Our team is actively working to identify the cause and will share an update within 2 hours. Thank you for your patience.
Notification Policies and Contact Points Missing in UI on the Slow Release Channel
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
We’ve implemented a fix and are monitoring the results to confirm the issue is fully resolved. Services may start to recover during this time. We’ll update again within 2 hours.
identified
We’ve identified the cause of the issue impacting the Notification Policy and Contact Point UI. Our team is currently implementing a fix. We’ll provide another update when the fix is deployed and we monitor the expected improvement.
investigating
We’re continuing to investigate the issue with the alerting UI. While we don’t have new information to share yet, our team is working to identify the root cause. Next update in 2 hours.
investigating
We’re currently investigating an issue affecting notification policies and contact points for instances on the slow release channel. Alerting API calls for contact points and notification policies return data as expected, so this appears to be limited to the UI. Our team is actively working to identify the cause and will share an update within 1-2 hours. Thank you for your patience.
Partial K6 Test Run Outage
major Source not attested
Last archived state: resolved
View archived record details
investigating
We're experiencing an outage affecting test runs that use k6 extensions. The issue prevents users from executing these types of test runs both locally and in Grafana Cloud. Test runs that do not use extensions are not affected by this incident.
AWS integration Degraded Performance
minor Source not attested
Last archived state: resolved
View archived record details
investigating
We are investigating a noticeable drop in active series for the AWS integration that began around 18:15 UTC. This issue may cause scrapes to hit rate limits, which can result in individual data points not being collected for the serverless integration. The impact is intermittent and may affect any customer using the AWS integration, regardless of region. We are currently working to identify the cause and will provide an update as soon as we have more information.
Query degradation and possible rule evaluation failure on prod-eu-west-0.cortex-prod-01
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We are continuing to investigate this issue.
investigating
We are currently observing delays in ingesting data, possibly causing partial query results and failed rule evaluations for prod-eu-west-0.cortex-prod-01 metrics cell.
March 2026
Some of the CloudWatch queries are failing
major Source not attested
Last archived state: resolved
View archived record details
monitoring
We are continuing to monitor for any further issues.
monitoring
Some of the CloudWatch queries were failing. Started at 08:37 UTC Monitoring from 09:21 UTC
Some Grafana Instances Unavailable
major Source not attested
Last archived state: resolved
View archived record details
monitoring
We’ve implemented a fix and are monitoring the results to confirm the issue is fully resolved. Services may start to recover during this time. We’ll update again in 1 hour.
identified
We’ve identified the cause of the issue impacting the instances. Our team is currently implementing a fix. We’ll provide another update in 1–2 hours, or sooner, if the situation changes.
investigating
We’re continuing to investigate the issue with Grafana instances. While we don’t have new information to share yet, our team is working to identify the root cause. Next update in 1-2 hours.
investigating
We’re continuing to investigate the issue with Grafana instances. While we don’t have new information to share yet, our team is working to identify the root cause. Next update in 1-2 hours.
investigating
We’re currently investigating an issue which is affecting primarily users on the Free tier. Impacted users will be met with a "your Grafana instance is loading" message indefinitely. Our team is actively working to identify the cause and will share an update within 1-2 hours. Thank you for your patience.
Prometheus writes in prod-eu-west-3 are degraded
critical Source not attested
Last archived state: resolved
View archived record details
monitoring
We are continuing to monitor for any further issues.
monitoring
We have deployed mitigation and seen improvement in write failures over the past week. We are still seeing intermittent spikes in latency and continue to monitor.
monitoring
We are still seeing intermittent issues and continue to seek a resolution
monitoring
We are continuing to monitor for any further issues.
monitoring
We are continuing to monitor this through the weekend.
monitoring
We are continuing to monitor the previously impacted environments.
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We are continuing to investigate this issue.
investigating
The metric writes issue reported in https://status.grafana.com/incidents/gfshj17lxj5z is still ongoing. Our Engineering team is actively investigating this and we will provide further updates as our investigation progresses.