Update - We have not received any further updates from AWS at this time. However, we are actively monitoring the outage and will provide additional information as it becomes available. Also, please continue to refer to the AWS status page for more detailed updates. https://health.aws.amazon.com/health/status
All the guidance previously included about stack migration is still relevant. Please reach out to our Support team if you have any questions.
Mar 19, 2026 - 12:13 UTC
Update - We are actively monitoring the situation, but at this time there are no new updates to share. The next update will be provided once we have more information to share. Please reach out to our Support team if you have any questions.
Mar 04, 2026 - 22:22 UTC
Update - We are continuing to investigate this issue.
Mar 04, 2026 - 10:28 UTC
We will provide updates when we have them, but we do not have an expected resolution time at this point.
Mar 02, 2026 - 10:31 UTC
Update - Customers are recommended to configure a new blank stack in an alternative Grafana Cloud region and to reconfigure their clients (such as Grafana Alloy) to send telemetry to that region, Fleet Management can be used for this purpose https://grafana.com/docs/grafana-cloud/send-data/fleet-management/introduction/
Mar 02, 2026 - 10:04 UTC
Update - We are updating this incident to reflect a complete outage in prod-me-central-1, due to an on-going AWS UAE data center issue. We will provide further updates accordingly.
Mar 02, 2026 - 08:36 UTC
Update - We are observing write and read outage errors across all databases (metrics, logs, traces) in prod-me-central-1, due to an on-going AWS UAE data center issue. We will provide further updates accordingly.
Mar 02, 2026 - 08:21 UTC
Update - We are observing write and read outage errors across all databases (metrics, logs, traces) in prod-me-central-1, due to an on-going AWS UAE data center issue. We will provide further updates accordingly.
Mar 02, 2026 - 08:14 UTC
Investigating - We are seeing elevated write and read path errors in prod-me-central-1, due to an on-going AWS UAE data center issue. We will provide further updates accordingly.
Mar 02, 2026 - 06:43 UTC
Grafana Cloud: Hosted Grafana
Operational
AWS Australia - prod-ap-southeast-2
Operational
AWS Brazil - prod-sa-east-1
Operational
AWS Canada - prod-ca-east-0
Operational
AWS Germany - prod-eu-west-2
Operational
AWS Germany - prod-eu-west-4
Operational
AWS India - prod-ap-south-1
Operational
AWS Japan - prod-ap-northeast-0
Operational
AWS UAE - prod-me-central-1
Operational
AWS Singapore - prod-ap-southeast-1
Operational
AWS Sweden - prod-eu-north-0
Operational
AWS US East - prod-us-east-0
Operational
AWS US East - prod-us-east-2
Operational
AWS US West - prod-us-west-0
Operational
AWS Australia - prod-au-southeast-1
Operational
AWS UK - prod-gb-south-1
Operational
AWS Ireland - prod-eu-west-6
Operational
Azure US Central - us-central2
Operational
AWS Switzerland - prod-eu-central-0
Operational
Azure Netherlands - prod-eu-west-3
Operational
GCP Australia - prod-au-southeast-0
Operational
GCP Belgium - prod-eu-west-0
Operational
GCP Brazil - prod-sa-east-0
Operational
GCP India - prod-ap-south-0
Operational
GCP Singapore - prod-ap-southeast-0
Operational
GCP UK - prod-gb-south-0
Operational
GCP US Central - prod-us-central-0
Operational
GCP US Central - prod-us-central-3
Operational
GCP US Central - prod-us-central-4
Operational
GCP US East - prod-us-east-1
Operational
play.grafana.org
Operational
Federal Cloud - AWS US Gov West
Operational
Grafana Cloud: Graphite
Operational
AWS Australia - prod-ap-southeast-2: Querying
Operational
AWS Australia - prod-ap-southeast-2: Ingestion
Operational
AWS Brazil - prod-sa-east-1: Querying
Operational
AWS Brazil - prod-sa-east-1: Ingestion
Operational
Resolved -
This incident has been resolved. Thank you for your patience.
Apr 9, 18:50 UTC
Identified -
We’ve identified the cause of the issue impacting k6 browser testing/timeline. Our team is currently implementing a fix. We’ll provide another update in two hours or sooner if the situation changes.
Apr 9, 18:39 UTC
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.
Resolved -
We had a stability issue for a subset of customers in the prod-gb-south-1 region. The impact was between UTC 15:20-16:30 which impacted roughly 30% of queries and rules evaluations. We've applied mitigations, queries should be back to normal.
Apr 8, 17:00 UTC
Resolved -
This incident has been resolved. Thank you for your patience.
Apr 7, 20:17 UTC
Update -
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.
Apr 7, 18:03 UTC
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.
Apr 7, 16:52 UTC
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.
Apr 7, 15:17 UTC
Resolved -
This incident has been resolved.
Apr 7, 12:26 UTC
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.
Apr 6, 23:58 UTC
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.
Apr 6, 21:04 UTC
Update -
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.
Apr 6, 16:13 UTC
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.
Apr 6, 14:48 UTC
Resolved -
This incident has been resolved. Thank you for your patience.
Apr 3, 17:38 UTC
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.
Apr 3, 15:29 UTC
Resolved -
This incident has been resolved.
Apr 1, 21:13 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Apr 1, 10:12 UTC
Update -
We are continuing to investigate this issue.
Apr 1, 10:11 UTC
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.
Apr 1, 09:56 UTC
Resolved -
This incident has been resolved. Thank you for your patience.
Apr 1, 21:03 UTC
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.
Apr 1, 20:17 UTC
Resolved -
From approximately 11:00 UTC - 15:00 UTC we had a degradation that caused test start errors for a large percentage of Cloud runs managed as scripts in the GCK6 app. This has since been resolved.
Mar 31, 14:59 UTC
Resolved -
This incident has been resolved.
Mar 31, 14:25 UTC
Identified -
Synthetic Monitoring check creation/update for scripted and browser checks might be blocked in the plugin app for some probes. The issue only impacts creating/updating checks from the plugin app. It does not affect checks handled from Terraform or directly to the API.
We’ve identified the cause of an issue impacting Synthetic Monitoring. Our team is currently implementing a fix. We’ll provide another update in 1-2 hours or sooner if the situation changes.
Mar 31, 14:01 UTC
Resolved -
We encountered an issue impacting only a small subset of customers in the prod-us-central-0 region. The incident occurred between 16:20 and 17:50 UTC on 3/30/26. This incident is now resolved.
Mar 30, 16:30 UTC
Resolved -
This incident has been resolved. Thank you for your patience.
Mar 27, 20:48 UTC
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.
Mar 27, 20:16 UTC
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.
Mar 27, 18:10 UTC
Update -
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.
Mar 27, 16:36 UTC
Update -
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.
Mar 27, 14:51 UTC
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.
Mar 27, 13:36 UTC