Grafana Cloud Outage History
Uptime record, past incidents, and downtime history for Grafana Cloud.
Checking current status...
90-Day Trend
Monthly Uptime
| Month | Uptime | Days Tracked | Days with Issues |
|---|---|---|---|
| May 2026 | 0% | 25 | 25 |
| April 2026 | 0% | 30 | 30 |
| March 2026 | 0% | 31 | 31 |
| February 2026 | 0% | 5 | 5 |
Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.
Daily Status (Last 91 Days)
Feb 24
Today
Operational
Degraded
Partial Outage
Major Outage
Maintenance
No Data
Incident History
May 2026
Grafana K6 metrics processing and test runs degradation
Started: May 18, 8:24 AM
monitoring
We've stabilized the system and test runs no longer result in timeout. There is a small delay (a few minutes) in processing metrics at the end of the test run, but most users shouldn't be too negatively impacted by that. We expected the delay/lag to also resolve within the next 30-60 minutes.
May 18, 2:30 PM
investigating
We have identified that test runs are getting timed out as a result of the issue
This issue first occurred on May 05/15/2026 at 8:00PM UTC.
May 18, 10:27 AM
investigating
We’re currently investigating an issue that is resulting in degraded performance in metrics processing and test run metrics may take longer than usual to show up. Our team is actively working to identify the cause. Thank you for your patience.
May 18, 8:24 AM
Intermittent Errors and High latency Writing to Cloud Metrics, Cloud Logs and Cloud Traces
Started: May 13, 8:50 AM
monitoring
We continue to see signs of recovery and improved stability across impacted services. Our teams continue to closely monitor the situation while working with the cloud provider.
May 13, 9:10 PM
monitoring
We continue to see signs of recovery and improved stability across impacted services. Our teams continue to closely monitor the situation while working with the cloud provider.
May 13, 3:41 PM
monitoring
We are seeing signs of recovery and improved stability across impacted services over the past hour. Our teams continue to closely monitor the situation while working with the cloud provider.
May 13, 1:37 PM
investigating
We have identified expanded impact affecting Grafana Cloud Logs and Grafana Cloud Traces in addition to Cloud Metrics, causing intermittent errors and increased latency when writing data. Our teams continue working on a fix and investigating the issue with the cloud provider’s support team.
May 13, 10:25 AM
investigating
We’re continuing to investigate the issue causing intermittent errors and high latency when writing to Cloud Metrics. We are in contact with the cloud provider’s support team, and they are investigating the issue alongside us.
May 13, 10:01 AM
investigating
We’re currently investigating an issue causing intermittent errors and high latency when writing to Cloud Metrics. Our team is actively working to identify the cause. Thank you for your patience.
May 13, 8:50 AM
"Failed to Load Dashboard" Errors
Started: May 11, 9:38 PM
identified
The fix is currently being rolled out to all impacted environments.
May 12, 2:13 PM
identified
Our teams continue working on a fix for this issue. We do not have additional information to share at this time, but we will continue to provide updates as progress is made.
May 12, 11:11 AM
identified
We are continuing to work on a fix for this issue. While we do not have additional updates to share at this time, our teams remain actively engaged and we will provide further updates as soon as they become available.
May 12, 8:58 AM
identified
Customers on Grafana Cloud may see an error on dashboard panels with "Failed to load dashboard ... json unmarshal number ...". We have identified the issue and are working to deploy out the fix.
May 11, 9:38 PM
SSL/TLS Connectivity Issues
Started: May 11, 8:49 PM
investigating
We are currently investigating reports of service disruption affecting a subset of customers.
Customers may experience intermittent connectivity issues, degraded performance, or SSL/TLS certificate validation errors when accessing affected services. Our engineering teams are actively working to identify the scope of impact and restore full functionality as quickly as possible.
We will continue to provide updates as more information becomes available.
May 11, 8:49 PM
Cloud Metrics -High Write Latency and Errors in prod-us-central-7
Started: May 8, 9:16 PM
monitoring
From approximately 20:40-21:00 UTc, we experienced an issue affecting Grafana Cloud Metrics in prod-us-central-7. Affected users may have experienced high latency and/or errors during ingestion and rule evaluation.
Our team has identified the cause and mitigated. We are currently monitoring for long-term stability.
May 8, 9:16 PM
Metrics read errors in prod-ap-south-1 region
Started: May 7, 7:18 AM
monitoring
Engineering has released a fix and as of 07:50 UTC, customers should no longer experience errors when querying metrics. We will continue to monitor for recurrence and provide updates accordingly.
May 7, 7:53 AM
investigating
From approximately 06:24 UTC, we were alerted to an issue with read errors in mimir-prod-43. Users with instances hosted in the prod-ap-south-1 region experiencing this issue may encounter an error message when querying metrics.
Engineering is actively engaged and assessing the issue. We will provide updates accordingly.
May 7, 7:18 AM
Datasource Query Performance Issues
Started: May 6, 8:07 PM
investigating
We’re currently investigating an issue affecting Datasource query performance in prod-us-east-4. Our team is actively working to identify the cause. Thank you for your patience.
May 6, 8:07 PM
Elevated Error Rate of Browser Checks in PoP Oregon
Started: May 5, 4:11 PM
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.
May 5, 7:44 PM
identified
We’ve identified the cause of the issue impacting browser checks. Our team is currently implementing a fix.
May 5, 6:13 PM
investigating
We’re currently investigating an issue affecting browser checks in the PoP Oregon region. Our team is actively working to identify the cause. Thank you for your patience.
May 5, 4:11 PM
k6 Partial Outage
Started: May 4, 10:58 PM
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.
May 5, 12:04 AM
investigating
After further investigation, this issue may also be affecting Synthetic Monitoring.
We continue to identify the cause and will update as soon as we have more information.
May 4, 11:23 PM
investigating
We’re currently investigating an issue affecting k6. Our team is actively working to identify the cause. Thank you for your patience.
May 4, 10:58 PM
Ingestion Errors for AWS Cloud Provider Observability Metric Streams in prod-us-central-7
Started: May 1, 9:14 AM
monitoring
A fix has been implemented and we are monitoring the results.
May 1, 9:43 AM
investigating
We are continuing to investigate this issue.
May 1, 9:42 AM
investigating
We are investigating an issue with ingesting Metrics for AWS Cloud Provider Observability with Metric Streams. Users experiencing this issue may encounter ingestion errors in the "prod-us-central-7" region only starting from ~06:30UTC.
Engineering is actively engaged and assessing the issue. We will provide updates accordingly.
May 1, 9:14 AM
April 2026
Investigating Issues Saving SQL Datasource Credentials
Started: Apr 28, 6:46 PM
monitoring
We’ve identified the cause of the issue impacting SQL datasources. Our team is currently implementing a fix and are monitoring the results to confirm the issue is fully resolved. Services may start to recover during this time.
Apr 28, 6:59 PM
investigating
We are currently investigating reports of issues affecting SQL-based data sources where users are unable to save credentials.
This appears to impact a subset of customers and may be occurring across multiple regions. We are actively working to determine the scope and root cause.
We will provide updates as more information becomes available.
Apr 28, 6:46 PM
Gateway Slowness Detected in Prod (US-East-1)
Started: Apr 28, 9:20 AM
investigating
Successful requests have dropped, users may not be able to access their instances.. The issue is under investigation.
Apr 28, 9:20 AM
InfluxDB Datasource - Intermittent Failures
Started: Apr 27, 5:08 PM
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.
Apr 27, 11:13 PM
identified
We’ve identified the cause of the issue impacting the InfluxDB datasource. Our team is currently implementing a fix.
Apr 27, 6:01 PM
investigating
We’re currently investigating an issue affecting the InfluxDB plugin. Some users may see intermittent failures.
Our team is actively working to identify the cause. Thank you for your patience.
Apr 27, 5:08 PM
Cloudwatch Datasource Outage
Started: Apr 23, 2:26 PM
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.
Apr 23, 2:39 PM
investigating
We’re currently investigating an issue affecting Cloudwatch datasources. Our team is actively working to identify the cause. Thank you for your patience.
Apr 23, 2:26 PM
Restrictions on Alerts & Reports for Grafana Cloud Free/Trial Users
Started: Apr 20, 9:12 PM
monitoring
Grafana Labs is implementing measures to safeguard the Grafana Cloud platform against ongoing unauthorized use while preserving the capabilities relied upon by our community. Effective immediately, we have made the following modifications to the platform:
Alerting
Email alerting has been disabled for new Grafana Cloud Free and Trial accounts; however, all other integrations such as webhooks remain functional. Additionally, Cloud Alertmanager is now disabled for Grafana instances in these acc...
Apr 22, 3:03 PM
monitoring
We are continuing to monitor for any further issues.
Apr 20, 10:07 PM
monitoring
Grafana Labs is taking steps to safeguard our Grafana Cloud platform against unauthorized use while maintaining the Grafana Cloud Free and Trial tiers of service our users and the community have come to rely on. As of Monday April 20, alerting and reporting capabilities have been disabled in new Grafana Cloud Free and trial stacks. We are working towards deploying improvements and restoring those functionalities in a way that keeps our platform secure and open for all of our users.
Apr 20, 9:12 PM
Elevated 429 Errors Impacting Metrics Querying Across Multiple Regions
Started: Apr 20, 2:09 PM
investigating
The issue is now confirmed to be widespread, affecting Prometheus across all regions.
Customers may continue to experience elevated 429 (rate limit) errors, particularly when querying metrics, with failures or inconsistent responses possible.
Our engineering team remains fully engaged and is actively working on mitigation and resolution efforts with the highest priority.
Apr 20, 2:21 PM
investigating
We are currently experiencing a major incident causing elevated 429 (rate limit) errors across multiple regions, primarily impacting metrics querying.
This is a high-priority issue, and our engineering team is actively engaged and working urgently to identify the root cause and restore full service as quickly as possible. Customers may experience widespread failures or delays when querying metrics during this time.
We understand the significant impact this may have and will continue to prov...
Apr 20, 2:09 PM
Query Caching - Degraded Performance
Started: Apr 17, 9:23 PM
monitoring
Currently prod-us-east-0 and prod-eu-west-3 have recovered, and we are continuing to monitor prod-us-central-0 which is in the process of recovery.
Apr 17, 10:09 PM
investigating
As of 20:52 UTC, we are currently investigating degraded Query Caching performance in multiple regions. For datasources where query caching is configured, some queries may take longer than usual.
Our team is actively working to identify the cause. Thank you for your patience.
Apr 17, 9:23 PM
Issues on Stack creation
Started: Apr 16, 12:52 PM
monitoring
The issue is fixed and we are currently monitoring the service.
Apr 16, 1:19 PM
identified
Since today 16th at ~12:11UTC we are seeing issues on stack creation across all our regions. Customers will experience error message when attempting to create a stack.
Our engineering team has identified the source of the issue as external to Grafana (provider), and they are tracking its recovery.
Apr 16, 12:52 PM
Degraded Ticket Visibility in Support System
Started: Apr 15, 4:07 PM
monitoring
We are currently experiencing an issue with our ticketing system provider that is affecting how tickets appear within our internal support views.
We are continuing to receive all new tickets successfully, and no requests are being lost at this time.
Our team is actively monitoring the situation and working to ensure all incoming requests are reviewed, including those that may not be immediately visible in standard views.
We will provide further updates as we receive more information from o...
Apr 15, 4:07 PM
K6 Sporadic DNS Issues
Started: Apr 14, 9:22 AM
monitoring
Our engineering team has deployed a fix and we are currently monitoring the behaviour of the system until full resolution.
Apr 14, 2:29 PM
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.
Apr 14, 2:29 PM
identified
We are having sporadic DNS issues that occasionally affect the start of cloud test runs, causing them to abort. We are currently working to resolve. The issue has been occurring since April 9.
Apr 14, 9:22 AM
Grafana Cloud Logs - Write degradation in us-east-3
Started: Apr 10, 11:53 PM
investigating
We are seeing issues on the write path for Loki in cluster in us-east-3, and we are actively investigating this issue.
Apr 10, 11:53 PM
Tempo Write Outage
Started: Apr 10, 7:42 PM
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.
Apr 10, 7:53 PM
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.
Apr 10, 7:42 PM
K6 Browser Testing/Timeline Not Available
Started: Apr 9, 5:34 PM
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.
Apr 9, 5:34 PM
Unable to Edit Notification Policies
Started: Apr 7, 3:17 PM
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, 6:03 PM
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, 4:52 PM
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, 3:17 PM
Notification Policies and Contact Points Missing in UI on the Slow Release Channel
Started: Apr 6, 2:48 PM
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, 11:58 PM
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, 9:04 PM
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.
Apr 6, 4:13 PM
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, 2:48 PM
Partial K6 Test Run Outage
Started: Apr 3, 3:29 PM
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, 3:29 PM
AWS integration Degraded Performance
Started: Apr 1, 8:17 PM
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, 8:17 PM
Query degradation and possible rule evaluation failure on prod-eu-west-0.cortex-prod-01
Started: Apr 1, 9:56 AM
monitoring
A fix has been implemented and we are monitoring the results.
Apr 1, 10:12 AM
investigating
We are continuing to investigate this issue.
Apr 1, 10:11 AM
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, 9:56 AM
March 2026
Some of the CloudWatch queries are failing
Started: Mar 31, 9:48 AM
monitoring
We are continuing to monitor for any further issues.
Mar 31, 9:49 AM
monitoring
Some of the CloudWatch queries were failing.
Started at 08:37 UTC
Monitoring from 09:21 UTC
Mar 31, 9:48 AM
Some Grafana Instances Unavailable
Started: Mar 27, 1:36 PM
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, 8:16 PM
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, 6:10 PM
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.
Mar 27, 4:36 PM
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.
Mar 27, 2:51 PM
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, 1:36 PM
Prometheus writes in prod-eu-west-3 are degraded
Started: Mar 25, 2:11 PM
monitoring
We are continuing to monitor for any further issues.
Apr 20, 3:08 PM
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.
Apr 14, 8:11 PM
monitoring
We are still seeing intermittent issues and continue to seek a resolution
Apr 8, 8:32 PM
monitoring
We are continuing to monitor for any further issues.
Apr 2, 9:38 PM
monitoring
We are continuing to monitor this through the weekend.
Mar 27, 9:05 PM
monitoring
We are continuing to monitor the previously impacted environments.
Mar 26, 5:45 PM
monitoring
A fix has been implemented and we are monitoring the results.
Mar 26, 12:04 PM
investigating
We are continuing to investigate this issue.
Mar 25, 9:35 PM
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.
Mar 25, 2:11 PM
Prometheus writes, Logs, and Synthetic Monitoring in prod-eu-west-3 are degraded
Started: Mar 24, 9:08 AM
investigating
This is also now impacting Logs and Synthetic Monitoring in prod-eu-west-3.
For Synthetic Monitoring, users might observe errors pushing check execution metrics, and this can eventually lead to missing data.
In addition, users might observe errors evaluating Synthetic Monitoring provisioned alert rule evaluations, and this can lead to missed alerts.
For Logs, there is no immediate impact on alerts, however, remote writes to Mimir is delayed which means users may see gaps in their recordin...
Mar 25, 7:43 AM
investigating
We are moving this back to 'Investigating' as we are now observing a substantial drop in successful ingestion and increase in write path errors, and elevated rule evaluation latency and error. Reads are mostly fine. Our Engineering team is actively investigating this and we will provide further updates as our investigation progresses.
Mar 25, 7:04 AM
monitoring
We have not observed any recent errors, but we will continue to monitor while we work with our CSP.
Mar 24, 9:23 PM
monitoring
A fix has been implemented and we are monitoring the results.
Mar 24, 9:19 AM
investigating
We are currently experiencing degraded writes for mimir-prod-22 in prod-eu-west-3 since 08:45Z.
Mar 24, 9:08 AM
Grafana Assistant Unavailable in prod-us-east-0
Started: Mar 23, 5:03 PM
identified
The issue has been identified, and we are implementing a fix.
Mar 23, 6:25 PM
investigating
The impact extends beyond the TOS check. Assistant is completely unavailable in the impacted region.
Mar 23, 6:07 PM
investigating
We are continuing to investigate this issue.
Mar 23, 6:01 PM
investigating
We are aware of an issue currently impacting Grafana Assistant. Impacted users are met with a request to accept the TOS, however the plugin is failing upon accepting. Our engineering are currently investigating this issue.
Mar 23, 5:03 PM
Authentication API Database Down in prod-eu-west-2 and prod-eu-west-4
Started: Mar 20, 3:00 PM
investigating
We have observed impact in prod-eu-west-4 as well.
Mar 20, 3:08 PM
investigating
We are currently investigating an issue impacting the main database for Authentication API's in the prod-eu-west-2 region. Writes are currently failing, but reads are operational.
Mar 20, 3:00 PM
Various Datasource Issues
Started: Mar 19, 4:46 PM
monitoring
We are continuing to monitor for any further issues.
Mar 19, 5:56 PM
monitoring
We have observed recovery for the Cloudwatch Datasource.
We are now seeing failures for the following Datasources:
Aurora
Opensearch
X-Ray
Timestream
Redshift
Sitewise
A fix for the above is being rolled out now, and we will monitor progress.
We will also change the name of this incident from "Cloudwatch Datasource Issues" to "Various Datasource Issues" to more accurately reflect impact.
Mar 19, 5:56 PM
monitoring
We have identified the issue, and are rolling out the fix. We are already seeing improvements and will continue to monitor progress.
Mar 19, 5:13 PM
investigating
We are currently investigating an issue impacting the CloudWatch Datasource causing failures.
Mar 19, 4:46 PM
Degraded performance of Grafana Cloud k6 test runs
Started: Mar 19, 11:17 AM
investigating
Some customers are seeing degraded performance and errors from certain v6 API endpoints. We are investigating the issue.
Mar 19, 11:17 AM
Grafana Cloud Logs - Write degradation in Azure Netherlands (eu-west-3)
Started: Mar 13, 10:28 AM
investigating
We are continuing to investigate this issue with our CSP, and will provide updates as they become available.
Mar 13, 9:22 PM
investigating
We are seeing issues on the write path for Loki in cluster Azure Netherlands (eu-west-3). Impact will reflect in degradation of logs ingestion on that cluster. Our engineering team is already working on restoring the service.
Mar 13, 10:28 AM
Increased number of Aborted-by-Systems with a k6 binary building errors
Started: Mar 13, 7:41 AM
monitoring
A fix has been implemented and we are monitoring the results.
Mar 13, 12:49 PM
identified
The issue has been identified and a fix is being implemented.
Mar 13, 8:45 AM
investigating
We are seeing an increased number of Aborted-by-Systems with a k6 binary building error. We are investigating the issue.
The first occurrence of this happened back on March 9, has now been identified as a blocking issue for some customers.
Mar 13, 7:41 AM
Rule Evaluation Outage in prod-us-west-0
Started: Mar 11, 5:10 PM
monitoring
A fix has been implemented and we are monitoring the results.
Mar 11, 6:02 PM
investigating
We are currently investigating an issue impacting rule evaluation for a subset of customers in the prod-us-west-0 region. We will provide updates as they become available.
Mar 11, 5:10 PM
Grafana Cloud Logs - Write degradation in Azure Netherlands (eu-west-3)
Started: Mar 11, 8:31 AM
investigating
We are also reporting impact to Faro performance in the same region. We are continuing to investigate this issue.
Mar 11, 9:13 AM
investigating
We are seeing issues on the write path for Loki in cluster Azure Netherlands (eu-west-3). Impact will reflect in degradation of logs ingestion on that cluster. Our engineering team is already working on restoring the service.
Mar 11, 8:31 AM
Complete outage in prod-me-central-1
Started: Mar 2, 6:43 AM
investigating
AWS UAE - prod-me-central-1: Public Probe checks might suffer degraded experience. We recommend migrating checks from the UAE probe to the next nearest probe suitable for your use case.
May 21, 11:41 AM
investigating
We do not have any additional updates to share at this time. Our team is actively monitoring the situation and will provide further information as it becomes available.
In the meantime, please continue to refer to the AWS Status Page for the most detailed and up-to-date information.
May 13, 9:59 PM
investigating
We are continuing to investigate this issue.
Apr 20, 3:11 PM
investigating
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, 12:13 PM
investigating
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 4, 10:22 PM
investigating
We are continuing to investigate this issue.
Mar 4, 10:28 AM
investigating
Please continue to refer to the AWS status page for more detailed updates specific to AWS.
https://health.aws.amazon.com/health/status
AWS are recommending that affected customers move workloads to alternate regions, and we are recommending the same.
Customers who are impacted and who cannot wait for a restoration of service are asked to:
1. Create a Grafana Cloud stack in an alternate region
2. Update clients to send telemetry to the new region, if using Grafana Alloy then you can use Fle...
Mar 2, 10:18 PM
investigating
AWS are recommending that affected customers move workloads to alternate regions https://health.aws.amazon.com/health/status and we are recommending the same.
Customers who are impacted and who cannot wait for a restoration of service are asked to:
1. Create a Grafana Cloud stack in an alternate region
2. Update clients to send telemetry to the new region, if using Grafana Alloy then you can use Fleet Management https://grafana.com/docs/grafana-cloud/send-data/fleet-management/introduction/...
Mar 2, 10:31 AM
investigating
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 2, 10:04 AM
investigating
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 2, 8:36 AM
investigating
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 2, 8:21 AM
investigating
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 2, 8:14 AM
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 2, 6:43 AM
February 2026
Grafana Cloud Metrics - Intermittent Write Latency in prod-us-central, prod-us-central-5, and prod-eu-west-0
Started: Feb 25, 7:54 PM
monitoring
We are rolling out a mitigation across the environments in these regions, and preemptively where possible to ensure it doesn’t spread elsewhere.
Mar 6, 9:44 PM
monitoring
We have seen an increase in latency in our cloud providers services, and are rolling out a change to mitigate the issue. We are monitoring.
Mar 6, 8:53 PM
monitoring
We are continuing to investigate this issue alongside the CSP, and have taken steps to escalate through the appropriate channels. The mitigation in place continues to work as expected, and any notable updates will continue to be shared here for tracking.
Mar 5, 10:22 PM
monitoring
We are continuing to investigate this issue alongside the CSP. Any notable updates will continue to be shared here for tracking.
Feb 27, 10:05 PM
monitoring
We've implemented mitigation in place and are continuing to monitoring and investigating this issue.
Feb 27, 2:55 PM
investigating
We have begun rolling out mitigation steps to reduce write latency in the prod-us-central-0 and prod-us-central-5 regions. While these measures are expected to improve performance, we are continuing to investigate the underlying root cause of the issue. We will provide additional updates as more information becomes available.
Feb 26, 4:23 PM
investigating
Since February 19, we have been investigating an intermittent issue causing increased write latency in the prod-us-central-0 and prod-us-central-5 regions. The issue does not affect all traffic but may result in delayed write operations for some customers. Our engineering team is actively working to identify the root cause and stabilize performance. We will share additional updates as progress is made.
Feb 25, 7:54 PM