GCP US Central - prod-us-central-0GCP US Central - prod-us-central-5GCP US Central - prod-us-central-0: IngestionGCP US Central - prod-us-central-5: IngestionGCP 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)
GCP US Central - prod-us-central-0GCP US Central - prod-us-central-5GCP US Central - prod-us-central-0: IngestionGCP 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.
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.
AWS Germany - prod-eu-west-2AWS Germany - prod-eu-west-4AWS US East - prod-us-east-2GCP Australia - prod-au-southeast-0GCP 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
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)
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.
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
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.
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.
July 2026
Grafana rulers crash-looping on prometheus
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We are in the process of rolling out the fix. Our engineers are monitoring the progress.
investigating
We are investigating issues with the grafana-ruler service on prod-us-east-2 and prod-us-west-0 which are causing periodic crash conditions. A code fix is currently being deployed to mitigate this
Cannot access dashboard set up as a home page
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are currently investigating an issue affecting some customers who are unable to load or access their dashboards when configured as their home page. We will update once we have more information on this.
Grafana Cloud IRM alert groups failing to produce alerts in us-east-3 region.
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
The work on bringing services back to healthy state is completed and alerts should be created correctly, without a delay now. We're keeping the incident open and monitoring for any potential hiccups that might occur.
identified
Some IRM alert groups in us-east-3 region may not be able to produce alerts and could be sluggish/misbehaving in general. The issue started around 01:00 UTC on July 3rd. The issue has been identified and the cause of the issue has been fixed. Our team is actively working on getting the service back to healthy state.
Some Queries Failing
minorSource not attested
Last archived state: resolved
View archived record details
identified
We are continuing to work on rolling back a PR responsible for this behavior. Once we have more information, we will share it here.
Thank you for your patience.
identified
Queries with drop __error__, including log volume histogram queries (the queries that generate the histogram visualization in Grafana), are failing due to a bug with series limit checks.
The Root cause has been identified, and we are working on a fix.
Loki and Frontend Observability - Major Outage in prod-us-central-0 region
criticalSource not attested
Last archived state: resolved
View archived record details
investigating
The AWS Logs integration in the same region is affected as well. We will provide further updates as our investigation progresses.
investigating
We are currently investigating a major outage in Loki writes and Frontend Observability in the prod-us-central-0 region. Our Engineering team is investigating this and we will provide further updates as our investigation progresses.
Elevated Loki Query Bytes Reporting
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are investigating an issue where some customers may see higher Loki query byte usage reported than was actually consumed. This affects usage reporting only; there is no impact to query execution or service availability.
The issue began at approximately 13:20 UTC and is ongoing. We expect the issue to be resolved soon and will provide another update as more information becomes available.
June 2026
Confluent API Outage
majorSource not attested
Last archived state: resolved
View archived record details
investigating
We are investigating an issue affecting Confluent metrics ingestion across all regions. Due to an elevated error rate on the Confluent side, some metrics may not be ingested, resulting in potential data loss. We are actively investigating the issue and will provide updates as more information becomes available.
Mimir read errors and high latency in prod-eu-west-0
minorSource not attested
Last archived state: resolved
View archived record details
identified
We've identified a possible cause, and a mitigation is in place to prevent further occurrences.
investigating
The errors and latency have now recovered, we continue investigating the root cause.
investigating
The errors are recovering, and we are still looking into the root cause of this.
investigating
We are currently investigating an issue with Mimir in prod-eu-west-0 we are seeing read errors and high latency. This incident is currently ongoing. The errors are recovering but we are currently looking into the route cause of this.
Rule evaluation error on cluster prod-gb-south-0
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been applied and we are currently monitoring results.
investigating
We are currently investigating Rule Evaluation errors on the cluster prod-gb-south-0 which is leading to error codes showing within the stacks. We are looking into the issue and will update accordingly.
K6 - Test run metrics processing is delayed
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We've improved the metric ingestion delay time and are working on additional fixes to bring it down to expected range. Customers can currently expect a delay of 2 to 5 minutes before their test run metrics show up (after starting a test).
investigating
Update: Changed incident title to "Test run metrics processing is delayed"
We have found the issue and are working on deploying the fix.
investigating
We are experiencing intermittent delays with secondary metrics processing for k6 Cloud test runs due to heavy load. We don't expect any data loss or impact on user runs, but results may take longer time to appear in UI.
investigating
A small update: The issue is isolated to new test runs, and users can go see the metrics of all the previous test runs
investigating
We’re currently investigating an issue causing metrics not to appear during test runs. . Our team is actively working to identify the cause. Thank you for your patience.
