Monitoring - A new iOS mobile app version (v2.39.5) has been released, which includes a fix for this issue. We are monitoring the rollout and its impact to ensure the issue has been fully resolved. If you continue to experience any problems after updating to the latest version, please let us know.
Jul 11, 2026 - 03:58 UTC
Identified - A fix has been submitted for review and will be released as Grafana Mobile v2.39.5 once it is approved.
If your app is currently on v2.39.3, we recommend not upgrading to v2.39.4 and instead waiting for v2.39.5 to become available.
Users who have already been signed out by this issue can log back into the app and continue using it.
We will provide another update once v2.39.5 is available.
Jul 10, 2026 - 22:17 UTC
Update - Our investigation has narrowed the impact to version 2.39.4 of the Grafana mobile app on iOS. Users should avoid upgrading to this version until an updated release is available.
As a precaution, we also recommend ensuring you have alternative notification methods configured (such as SMS, email, or phone calls) if you rely on mobile push notifications for alerting.
We are actively working on a resolution and will provide another update as soon as more information is available.
Jul 10, 2026 - 20:37 UTC
Investigating - We are aware of an issue in the latest mobile app release that is causing some users to be signed out and asked to log in again.
We have reproduced the behavior and are investigating and working on a fix. We will share another update as soon as we have more information.
Jul 10, 2026 - 20:27 UTC
Update - We are continuing to investigate the underlying cause of this issue. At this time, the scope and impact remain unchanged, and we have no new information to share. We will provide another update as soon as more information becomes available.
Jul 10, 2026 - 21:40 UTC
Investigating - For some dashboards, the Views/Error counts in the Dashboards/Folder list renders as `-` and never updates, even after dashboards are viewed repeatedly
This is ultimately causing inaccurate or missing view counts.
Jul 10, 2026 - 15:57 UTC
Grafana
Degraded Performance
AWS Australia - prod-ap-southeast-2
Degraded Performance
AWS Brazil - prod-sa-east-1
Degraded Performance
AWS Canada - prod-ca-east-0
Degraded Performance
AWS Germany - prod-eu-west-2
Degraded Performance
AWS Germany - prod-eu-west-4
Degraded Performance
AWS India - prod-ap-south-1
Degraded Performance
AWS Japan - prod-ap-northeast-0
Degraded Performance
Resolved -
From approximately 20:24 UTC - 20:47 UTC a network issue in prod-us-central-0 isolated part of our infrastructure in one availability zone, temporarily cutting off connectivity to a subset of backend services. This caused elevated query latency and some delayed metric evaluations, along with related write-path errors in a logging subsystem. All systems recovered automatically once network connectivity was restored.
Impacted customers may have had queries or rule evaluations fail during the incident, but ingestion was not impacted.
Jul 10, 21:31 UTC
Resolved -
This incident has been resolved. Thank you for your patience.
Jul 9, 19:54 UTC
Monitoring -
We are now seeing recovery of PDC traffic to the affected customers. Our team will continue to monitor across shifts.
Jul 9, 17:52 UTC
Identified -
We are continuing to see disruptions across multiple deployments, ranging from degraded performance to full outages for some customers.
Additional resources have been engaged to mitigate this issue. We will post updates as they become available.
Jul 9, 16:08 UTC
Update -
We are continuing to monitor for any further issues.
Jul 9, 14:44 UTC
Update -
We are seeing recovery in some deployments, while others not just yet. We are continuing to monitor this incident.
Jul 9, 14:10 UTC
Monitoring -
A fix has been applied and we are seeing recovery. We will continue to monitor this.
Jul 9, 13:04 UTC
Update -
We are still currently investigating the issue.
Jul 9, 12:36 UTC
Investigating -
We are currently facing performance degradation on PDC service hosted on Multiple clusters. Our Engineering Team is currently working on fixing the issue, we do apologize for any inconvenience.
Jul 9, 11:37 UTC
Resolved -
This incident has been resolved.
Jul 9, 13:07 UTC
Monitoring -
A fix has been implemented. We are currently monitoring the results.
Jul 9, 11:18 UTC
Investigating -
We are observing delayed ingestion and recording rule evaluation failures for Mimir in prod-ap-south-1. As of yet we have not noticed any customer impact however we are currently observing the cell.
Jul 9, 10:28 UTC
Resolved -
Between 5:49 and 5:54 UTC, the read path in prod-eu-west-2 was down. This has completely recovered by 5:57 UTC. Recording rules may have failed to evaluate during this period which may result in gaps.
Jul 9, 07:37 UTC
Resolved -
This incident has been resolved.
Jul 8, 17:23 UTC
Monitoring -
We are in the process of rolling out the fix. Our engineers are monitoring the progress.
Jul 8, 14:23 UTC
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
Jul 8, 12:17 UTC
Resolved -
Between 13:57 and 14:20 UTC (23 minutes), a data gap occurred affecting billing usage data for Loki. Data for this window was not recorded and cannot be recovered.
Jul 8, 15:33 UTC
Resolved -
We have found that the issues are related to the grafana.unifiedHomepage feature rollout active 16:50 UTC yesterday, to 10:20 UTC today. We have rolled this back and systems are now working as expected.
Jul 8, 11:00 UTC
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.
Jul 8, 10:28 UTC
Resolved -
We identified an issue with the internal job that calculates month-to-date usage and cost data, which caused usage attribution and billing dashboards to display stale information. The root cause has been identified and resolved.
Your billing dashboard may show a sudden jump in usage. This is expected. It reflects several days of accumulated usage that hadn't been showing up while the issue was ongoing, not a sudden change in your actual usage.
This issue does not affect your end-of-month invoice. Your bill will be calculated based on actual usage, not the numbers displayed during this period.
Jul 7, 13:44 UTC
Resolved -
We haven't noticed any further issues in this region for alert group processing since yesterday. This incident i fully resolved.
Jul 6, 07:37 UTC
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.
Jul 5, 13:38 UTC
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.
Jul 5, 11:37 UTC
Resolved -
Grafana Cloud Logs in prod-eu-north-0 experienced a 10-minute partial write outage between 13:45 and 13:54 UTC. Impacted users may have experienced 5xx errors during this time.
Jul 3, 14:27 UTC
Resolved -
This incident has been resolved. Thank you for your patience.
Jul 2, 21:35 UTC
Update -
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.
Jul 2, 20:16 UTC
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 2, 18:10 UTC
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