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.
Jul 02, 2026 - 18:10 UTC
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
Metrics
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 by restarting the affected services.
Jul 2, 06:49 UTC
Update -
The AWS Logs integration in the same region is affected as well. We will provide further updates as our investigation progresses.
Jul 2, 04:57 UTC
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.
Jul 2, 04:55 UTC
Resolved -
We’ve implemented a fix and can confirm the issue is fully resolved as of 20:25 UTC.
Thank you for your patience.
Jul 1, 22:00 UTC
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.
Jul 1, 19:43 UTC
Resolved -
Since the mitigation has been applied, we have not seen the errors return. At this point, we are considering the incident resolved.
Jun 30, 08:20 UTC
Identified -
We've identified a possible cause, and a mitigation is in place to prevent further occurrences.
Jun 29, 17:47 UTC
Update -
The errors and latency have now recovered, we continue investigating the root cause.
Jun 29, 15:37 UTC
Update -
The errors are recovering, and we are still looking into the root cause of this.
Jun 29, 13:52 UTC
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.
Jun 29, 11:37 UTC
Resolved -
This incident has been resolved.
Jun 29, 14:27 UTC
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.
Jun 29, 12:37 UTC
Resolved -
This incident has been resolved.
Jun 29, 13:12 UTC
Monitoring -
A fix has been applied and we are currently monitoring results.
Jun 29, 11:14 UTC
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.
Jun 29, 10:34 UTC
Resolved -
This incident has been resolved.
Jun 28, 02:35 UTC
Update -
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).
Jun 26, 23:30 UTC
Update -
Update: Changed incident title to "Test run metrics processing is delayed"
We have found the issue and are working on deploying the fix.
Jun 26, 16:33 UTC
Update -
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.
Jun 26, 14:09 UTC
Update -
A small update: The issue is isolated to new test runs, and users can go see the metrics of all the previous test runs
Jun 26, 13:19 UTC
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.
Jun 26, 13:08 UTC
Completed -
The scheduled maintenance has been completed.
Jun 24, 16:07 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 24, 12:00 UTC
Scheduled -
We'll be performing scheduled maintenance on the Cloud Migration Assistant ("Migrate to Grafana Cloud" feature). During this window, the ability to start or run migrations to Grafana Cloud will be temporarily unavailable while we roll the update out. What's affected: the Cloud Migration Assistant tooling only. What's not affected: your existing Grafana Cloud stacks — dashboards, metrics, logs, traces, alerting, and all other services continue to operate normally. If you're in the middle of a migration, you may need to re-create your migration snapshot once maintenance is complete. No action is required for existing, completed migrations. We'll update this notice as the maintenance progresses and confirm once it's complete. Thanks for your patience.
Jun 22, 13:15 UTC
Resolved -
This incident has been resolved. Error rates continued to remain near 0 and operations are performing as expected.
Jun 24, 12:46 UTC
Update -
Error rates have remained near zero, and we continue to monitor.
Jun 23, 17:54 UTC
Update -
We are continuing to monitor for further issues.
Jun 23, 13:15 UTC
Update -
We have deployed additional mitigations that should help with remaining errors. We are continuing to monitor error rates.
Jun 23, 09:14 UTC
Update -
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.
Jun 22, 17:16 UTC
Update -
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.
Jun 19, 19:07 UTC
Update -
Due to the linked GCP outage below, users located in India may have trouble loading parts of Grafana.
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.
Jun 19, 02:33 UTC
Monitoring -
Due to the linked GCP outage below, users located in India may have trouble loading parts of Grafana.
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.
Jun 18, 16:57 UTC
Investigating -
Due to the linked GCP outage below, users located in India may have trouble loading parts of Grafana.
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.
Jun 18, 15:18 UTC
Resolved -
Starting June 20, 2026 at approximately 20:00 UTC, some Grafana Cloud customers experienced unexpectedly elevated logs query usage. The issue persisted until it was resolved on June 22, 2026 at approximately 16:00 UTC.
Our engineering team identified and mitigated the issue. Systems have since stabilized and are operating normally. Grafana Labs is reviewing affected accounts for appropriate remediation.
Jun 20, 20:00 UTC
Resolved -
This incident has been resolved. Thank you for your patience.
Jun 19, 19:19 UTC
Update -
We’re continuing to track progress post-mitigation. While we don’t have new information to share yet, our team remains actively engaged.
Jun 19, 17:46 UTC
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.
Jun 19, 16:39 UTC
Resolved -
This incident has been resolved. Thank you for your patience.
Jun 18, 18:50 UTC
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.
Jun 18, 18:09 UTC
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.
Jun 18, 17:01 UTC
Resolved -
This incident has been resolved. Thank you for your patience.
Jun 18, 16:21 UTC
Update -
We are continuing to monitor for any further issues.
Jun 18, 14:04 UTC
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.
Jun 18, 13:15 UTC
Update -
We are continuing to investigate this issue.
Jun 18, 11:45 UTC
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.
Jun 18, 11:25 UTC
Resolved -
This incident has been resolved.
Jun 18, 14:08 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Jun 18, 08:04 UTC
Update -
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.
Jun 17, 23:22 UTC
Update -
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.
Jun 17, 21:43 UTC
Update -
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.
Jun 17, 20:55 UTC
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 viewed and managed directly through the Loki ruler API (for example, using cortextool against /loki/api/v1/rules).
A fix has been identified and is in progress. We will provide a further update once it has been rolled out.
Jun 17, 20:17 UTC
Resolved -
A fix has been deployed and the issue after monitoring as been fixed.
Jun 18, 10:13 UTC
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.
Jun 18, 08:48 UTC