Update - We continue to work on resolving the issue impacting dashboard view and error counts. There are no new updates to share at this time. Our next update will be provided within 24 hours.
Jul 16, 2026 - 13:34 UTC
Update - We continue to work on resolving this issue. We'll provide another update within the next 24 hours, or sooner if additional information becomes available.
Jul 15, 2026 - 20:52 UTC
Update - We continue to work on resolving this issue. We'll provide another update within the next 24 hours, or sooner if additional information becomes available.
Jul 15, 2026 - 12:05 UTC
Identified - We've identified the cause of the issue impacting dashboard view and error counts in the Dashboards and Folder list. Our team is currently working on implementing a fix and validating the solution. We will provide another update within the next 24 hours, or sooner if we have additional information to share.
Jul 14, 2026 - 14:27 UTC
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.
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 14, 2026 - 08:10 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 -
The incident is now fully resolved.
Jul 16, 14:58 UTC
Monitoring -
Services are fully recovered now. We're monitoring to be sure the issue won't re-occur.
Jul 16, 13:45 UTC
Identified -
We're currently facing an issue with Adaptive Metrics aggregation delay in the eu-west-0 region (GCP Belgium). The issue started at around 11:50 UTC, but we were able to identify the issue and the appropriate fix is already deployed. We're seeing services recovering. More updated to come soon.
Jul 16, 12:56 UTC
Resolved -
This incident has been resolved.
Jul 16, 03:54 UTC
Monitoring -
We have applied the mitigation and are monitoring as the backlog catches up. We will post another update once that is complete.
Thank you for your patience.
Jul 15, 21:23 UTC
Identified -
We are currently investigating a delay in aggregated metric results for tenants using Adaptive Metrics in the prod-us-central-0 region.
Our engineering team has identified the issue and is actively working on a mitigation. We will provide further updates as the investigation progresses.
Jul 15, 19:19 UTC
Resolved -
This incident has been resolved. Thank you for your patience.
Jul 15, 23:36 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.
Jul 15, 22:53 UTC
Update -
We are continuing to investigate this issue.
Jul 15, 22:38 UTC
Update -
We are investigating a broader issue affecting multiple Grafana Cloud products in prod-eu-west-2. This appears to be caused by a third-party provider issue rather than a Loki-specific problem.
Impact is currently inconsistent: some components are affected while others continue to function normally. We have also seen some impact to Tempo write paths.
We are continuing to investigate and will share another update as soon as we have more information.
Jul 15, 22:35 UTC
Investigating -
We are investigating an issue affecting Loki queries in prod-eu-west-2.
We first observed this behavior at approximately 21:57 UTC. Affected users may see elevated query errors, timeouts, or intermittent failures when running Loki queries in this region.
The issue appears to be improving, but it is not fully resolved yet. We are continuing to investigate and will share another update as soon as we have more information.
Jul 15, 22:24 UTC
Resolved -
This incident has been resolved. Thank you for your patience.
Jul 15, 21:00 UTC
Update -
The fix is in the process of being rolled out.
Jul 15, 20:50 UTC
Identified -
We believe we have found the cause and are working on remediation. It is also worth mentioning that only stacks on the "slow" release channel are impacted.
Jul 15, 18:47 UTC
Investigating -
We are currently investigating an issue impacting a small subset of stacks in the impacted regions. We will provide more details as they become available.
Jul 15, 18:07 UTC
Resolved -
Between 9:45 and 12:00 UTC, we experienced an issue affecting the Fleet Management interface. During this time, the Remote Configuration tab for production stacks returned a 404 error when accessed through the UI.
Backend systems were not affected. Configuration-as-code workflows and other non-UI methods of interacting with Fleet Management continued to operate normally throughout the incident.
This issue has since been resolved.
Jul 15, 13:54 UTC
Resolved -
This incident has been resolved.
Jul 14, 19:03 UTC
Monitoring -
The outage is recovered as of 16:56 UTC, and we're continuing to monitor.
Jul 14, 17:23 UTC
Identified -
We're investigating backend degradation which has resulted in a partial write outage beginning around 16:40 UTC. This degradation has also impacted reads and rule evaluation. Issue has been identified and we are working on mitigation.
Jul 14, 17:09 UTC
Resolved -
This incident has been resolved.
Jul 13, 13:00 UTC
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, 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, 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, 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, 20:27 UTC
Resolved -
At this stage, we are considering the incident resolved.
Jul 13, 05:23 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 13, 05:21 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, 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, 15:57 UTC
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