Grafana Outage History

Grafana is up right now

Pingoru has recorded 195 incidents for Grafana: 195 in the last 12 months and 70 in the last 90 days.

Source: status.grafana.com

195incidents recorded
195last 12 months
70last 90 days
31 hourstypical duration
Incidents per month
02040AprMayJunJulAugSepOct26
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct62%
Pingoru began tracking Grafana in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202623367 of 720 (51%)
May 20261365 of 744 (9%)
June 202623391 of 720 (54%)
July 202639292 of 744 (39%)
August 20261418 of 744 (2%)
September 20262385 of 720 (12%)
October 202626366 of 592 (62%)

Incidents, newest first

Major July 21, 2026 Cloud Log Exporter Unavailable 2h 22m AWS Brazil - prod-sa-east-1, AWS Canada - prod-ca-east-0, AWS Germany - prod-eu-west-2, AWS India - prod-ap-south-1 and 11 more

Started Jul 21, 2026, 06:43 PM UTC· resolved Jul 21, 2026, 09:06 PM UTC

  1. investigating Jul 21, 2026, 06:43 PM UTC

    Cloud Log Exporter is temporarily not available in the marked regions. We are currently investigating this issue and will update as soon as we have more info to share.

  2. monitoring Jul 21, 2026, 08:04 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jul 21, 2026, 09:06 PM UTC

    This incident has been resolved.

Read the full incident report →

Major July 20, 2026 PDC Issues 1h 15m AWS Germany - prod-eu-west-2, AWS US East - prod-us-east-2

Started Jul 20, 2026, 01:48 PM UTC· resolved Jul 20, 2026, 03:03 PM UTC

  1. investigating Jul 20, 2026, 01:48 PM UTC

    We are currently investigating an issue that is causing issues with PDC in the prod-eu-west-2 region. We will provide another update in 1-2 hours.

  2. investigating Jul 20, 2026, 02:13 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Jul 20, 2026, 02:23 PM UTC

    A fix has been implemented, and we are observing recovery. We will continue to monitor the results.

  4. resolved Jul 20, 2026, 03:03 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 17, 2026 Grafana Cloud login issues for users with role of None 18h 52m AWS Australia - prod-au-southeast-2, AWS Brazil - prod-sa-east-1, AWS Canada - prod-ca-east-0, AWS Germany - prod-eu-west-2 and 27 more

Started Jul 17, 2026, 06:22 PM UTC· resolved Jul 18, 2026, 01:15 PM UTC

  1. investigating Jul 17, 2026, 06:22 PM UTC

    We’re currently investigating an issue with user logins with the None role in Grafana Cloud. Our team is actively working to identify the cause. Thank you for your patience.

  2. identified Jul 17, 2026, 07:28 PM UTC

    We’ve identified the cause of the issue impacting users with the role of None from logging in. Our team is currently implementing a fix.

  3. identified Jul 17, 2026, 09:33 PM UTC

    We are in the process of implementing a fix and are monitoring the rollout. Thank you for your patience.

  4. resolved Jul 18, 2026, 01:15 PM UTC

    Users with the None role authenticating via Grafana.com should be able to access their stacks again

Read the full incident report →

Minor July 16, 2026 Adaptive Metrics aggregation delay in eu-west-0 region. 2h 2m GCP Belgium - prod-eu-west-0: Ingestion

Started Jul 16, 2026, 12:56 PM UTC· resolved Jul 16, 2026, 02:58 PM UTC

  1. identified Jul 16, 2026, 12:56 PM UTC

    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.

  2. monitoring Jul 16, 2026, 01:45 PM UTC

    Services are fully recovered now. We're monitoring to be sure the issue won't re-occur.

  3. resolved Jul 16, 2026, 02:58 PM UTC

    The incident is now fully resolved.

Read the full incident report →

Major July 15, 2026 Partial Outage in prod-eu-west-2 1h 12m AWS Germany - prod-eu-west-2, AWS Germany - prod-eu-west-2, AWS Germany - prod-eu-west-2, AWS Germany - prod-eu-west-2 and 14 more

Started Jul 15, 2026, 10:24 PM UTC· resolved Jul 15, 2026, 11:36 PM UTC

  1. investigating Jul 15, 2026, 10:24 PM UTC

    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.

  2. investigating Jul 15, 2026, 10:35 PM UTC

    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.

  3. investigating Jul 15, 2026, 10:38 PM UTC

    We are continuing to investigate this issue.

  4. monitoring Jul 15, 2026, 10:53 PM UTC

    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.

  5. resolved Jul 15, 2026, 11:36 PM UTC

    This incident has been resolved. Thank you for your patience.

Read the full incident report →

Minor July 15, 2026 Delayed Aggregated Metrics (prod-us-central-0) 8h 35m GCP US Central - prod-us-central-0: Ingestion

Started Jul 15, 2026, 07:19 PM UTC· resolved Jul 16, 2026, 03:54 AM UTC

  1. identified Jul 15, 2026, 07:19 PM UTC

    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.

  2. monitoring Jul 15, 2026, 09:23 PM UTC

    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.

  3. resolved Jul 16, 2026, 03:54 AM UTC

    This incident has been resolved.

Read the full incident report →

Major July 15, 2026 Some Reports of Grafana Not Loading. 2h 53m AWS US East (OH) - prod-us-east-0, GCP US Central - prod-us-central-0, GCP US Central - prod-us-central-3, GCP US Central - prod-us-central-4

Started Jul 15, 2026, 06:07 PM UTC· resolved Jul 15, 2026, 09:00 PM UTC

  1. investigating Jul 15, 2026, 06:07 PM UTC

    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.

  2. identified Jul 15, 2026, 06:47 PM UTC

    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.

  3. identified Jul 15, 2026, 08:50 PM UTC

    The fix is in the process of being rolled out.

  4. resolved Jul 15, 2026, 09:00 PM UTC

    This incident has been resolved. Thank you for your patience.

Read the full incident report →

Minor July 15, 2026 Fleet Managment Interface 404's –

Started Jul 15, 2026, 01:54 PM UTC· resolved Jul 15, 2026, 01:54 PM UTC

  1. resolved Jul 15, 2026, 01:54 PM UTC

    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.

Read the full incident report →

Minor July 14, 2026 Mimir Write Performance Degradation 1h 32m GCP US Central - prod-us-central-0: Ingestion

Started Jul 14, 2026, 08:28 PM UTC· resolved Jul 14, 2026, 10:00 PM UTC

  1. monitoring Jul 14, 2026, 08:28 PM UTC

    From 19:24 until 19:40 UTC, backend performance degradation impacted ingestion. We are currently monitoring.

  2. resolved Jul 14, 2026, 10:00 PM UTC

    This incident has been resolved. Thank you for your patience.

Read the full incident report →

Major July 14, 2026 Mimir Partial Write Outage 1h 53m GCP US Central - prod-us-central-0: Querying, GCP US Central - prod-us-central-0: Ingestion

Started Jul 14, 2026, 05:09 PM UTC· resolved Jul 14, 2026, 07:03 PM UTC

  1. identified Jul 14, 2026, 05:09 PM UTC

    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.

  2. monitoring Jul 14, 2026, 05:23 PM UTC

    The outage is recovered as of 16:56 UTC, and we're continuing to monitor.

  3. resolved Jul 14, 2026, 07:03 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 14, 2026 Issue with Dashboard Views Being Registered 6d 2h AWS Australia - prod-au-southeast-2, AWS Brazil - prod-sa-east-1, AWS Canada - prod-ca-east-0, AWS Germany - prod-eu-west-2 and 27 more

Started Jul 14, 2026, 08:10 AM UTC· resolved Jul 20, 2026, 10:15 AM UTC

  1. investigating Jul 14, 2026, 08:10 AM UTC

    This is related to https://status.grafana.com/incidents/rhrk2ck6ly0y which was resolved by mistake. 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.

  2. identified Jul 14, 2026, 02:27 PM UTC

    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.

  3. identified Jul 15, 2026, 12:05 PM UTC

    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.

  4. identified Jul 15, 2026, 08:52 PM UTC

    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.

  5. identified Jul 16, 2026, 01:34 PM UTC

    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.

  6. identified Jul 16, 2026, 09:27 PM UTC

    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.

  7. identified Jul 20, 2026, 08:17 AM UTC

    We are currently working on a fix related to this incident. There are no new updates to share at this time.

  8. resolved Jul 20, 2026, 10:15 AM UTC

    A fix has been implemented and dashboard view and error counts in the Dashboards and Folder list are updating as expected. Thank you for your patience while we worked to address this issue.

Read the full incident report →

Major July 10, 2026 Network Degredation in prod-us-central-0 –

Started Jul 10, 2026, 09:31 PM UTC· resolved Jul 10, 2026, 09:31 PM UTC

  1. resolved Jul 10, 2026, 09:31 PM UTC

    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.

Read the full incident report →

Minor July 10, 2026 IRM Mobile App forcing some users to logout 2d 16h Incident Management and Response (IRM)

Started Jul 10, 2026, 08:27 PM UTC· resolved Jul 13, 2026, 01:00 PM UTC

  1. investigating Jul 10, 2026, 08:27 PM UTC

    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.

  2. investigating Jul 10, 2026, 08:37 PM UTC

    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.

  3. identified Jul 10, 2026, 10:17 PM UTC

    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.

  4. monitoring Jul 11, 2026, 03:58 AM UTC

    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.

  5. resolved Jul 13, 2026, 01:00 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical July 9, 2026 PDC Degraded performance 8h 17m AWS Australia - prod-au-southeast-1, AWS Germany - prod-eu-west-2, AWS Germany - prod-eu-west-4, AWS Singapore - prod-ap-southeast-1 and 2 more

Started Jul 09, 2026, 11:37 AM UTC· resolved Jul 09, 2026, 07:54 PM UTC

  1. investigating Jul 09, 2026, 11:37 AM UTC

    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.

  2. investigating Jul 09, 2026, 12:36 PM UTC

    We are still currently investigating the issue.

  3. monitoring Jul 09, 2026, 01:04 PM UTC

    A fix has been applied and we are seeing recovery. We will continue to monitor this.

  4. monitoring Jul 09, 2026, 02:10 PM UTC

    We are continuing to monitor for any further issues.

  5. monitoring Jul 09, 2026, 02:44 PM UTC

    We are continuing to monitor for any further issues.

  6. identified Jul 09, 2026, 04:08 PM UTC

    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.

  7. monitoring Jul 09, 2026, 05:52 PM UTC

    We are now seeing recovery of PDC traffic to the affected customers. Our team will continue to monitor across shifts.

  8. resolved Jul 09, 2026, 07:54 PM UTC

    This incident has been resolved. Thank you for your patience.

Read the full incident report →

Minor July 9, 2026 Delayed ingestion and recording rule evaluation failures for Mimir in prod-ap-south-1 2h 39m AWS India - prod-ap-south-1: Rule Evaluation, AWS India - prod-ap-south-1: Alertmanager and Rules Configuration API

Started Jul 09, 2026, 10:28 AM UTC· resolved Jul 09, 2026, 01:07 PM UTC

  1. investigating Jul 09, 2026, 10:28 AM UTC

    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.

  2. monitoring Jul 09, 2026, 11:18 AM UTC

    A fix has been implemented. We are currently monitoring the results.

  3. resolved Jul 09, 2026, 01:07 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 9, 2026 Loki read path in prod-eu-west-2 was down – AWS Germany - prod-eu-west-2

Started Jul 09, 2026, 07:37 AM UTC· resolved Jul 09, 2026, 07:37 AM UTC

  1. resolved Jul 09, 2026, 07:37 AM UTC

    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.

Read the full incident report →

Minor July 8, 2026 Loki Billing Data Lost –

Started Jul 08, 2026, 03:33 PM UTC· resolved Jul 08, 2026, 03:33 PM UTC

  1. resolved Jul 08, 2026, 03:33 PM UTC

    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.

Read the full incident report →

Minor July 8, 2026 Grafana rulers crash-looping on prometheus 5h 6m AWS US East (OH) - prod-us-east-0: Rule Evaluation, AWS US West - prod-us-west-0: Rule Evaluation

Started Jul 08, 2026, 12:17 PM UTC· resolved Jul 08, 2026, 05:23 PM UTC

  1. investigating Jul 08, 2026, 12:17 PM UTC

    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

  2. monitoring Jul 08, 2026, 02:23 PM UTC

    We are in the process of rolling out the fix. Our engineers are monitoring the progress.

  3. resolved Jul 08, 2026, 05:23 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 8, 2026 Cannot access dashboard set up as a home page 32m AWS India - prod-ap-south-1, AWS Singapore - prod-ap-southeast-1, AWS Switzerland - prod-eu-central-0, Azure Netherlands - prod-eu-west-3 and 1 more

Started Jul 08, 2026, 10:28 AM UTC· resolved Jul 08, 2026, 11:00 AM UTC

  1. investigating Jul 08, 2026, 10:28 AM UTC

    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.

  2. resolved Jul 08, 2026, 11:00 AM UTC

    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.

Read the full incident report →

Notice July 7, 2026 Delayed usage and billing data –

Started Jul 07, 2026, 01:44 PM UTC· resolved Jul 07, 2026, 01:44 PM UTC

  1. resolved Jul 07, 2026, 01:44 PM UTC

    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.

Read the full incident report →

Major July 5, 2026 Grafana Cloud IRM alert groups failing to produce alerts in us-east-3 region. 19h 59m Incident Management and Response (IRM)

Started Jul 05, 2026, 11:37 AM UTC· resolved Jul 06, 2026, 07:37 AM UTC

  1. identified Jul 05, 2026, 11:37 AM UTC

    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.

  2. monitoring Jul 05, 2026, 01:38 PM UTC

    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.

  3. resolved Jul 06, 2026, 07:37 AM UTC

    We haven't noticed any further issues in this region for alert group processing since yesterday. This incident i fully resolved.

Read the full incident report →

Minor July 3, 2026 Partial Write Outage for Grafana Cloud Logs in prod-eu-north-0. –

Started Jul 03, 2026, 02:27 PM UTC· resolved Jul 03, 2026, 02:27 PM UTC

  1. resolved Jul 03, 2026, 02:27 PM UTC

    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.

Read the full incident report →

Minor July 2, 2026 Some Queries Failing 3h 25m AWS Australia - prod-au-southeast-1, AWS Brazil - prod-sa-east-1, AWS Canada - prod-ca-east-0, AWS Germany - prod-eu-west-2 and 21 more

Started Jul 02, 2026, 06:10 PM UTC· resolved Jul 02, 2026, 09:35 PM UTC

  1. identified Jul 02, 2026, 06:10 PM UTC

    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.

  2. identified Jul 02, 2026, 08:16 PM UTC

    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.

  3. resolved Jul 02, 2026, 09:35 PM UTC

    This incident has been resolved. Thank you for your patience.

Read the full incident report →

Critical July 2, 2026 Loki and Frontend Observability - Major Outage in prod-us-central-0 region 1h 53m GCP US Central - prod-us-central-0, GCP US Central - prod-us-central-0

Started Jul 02, 2026, 04:55 AM UTC· resolved Jul 02, 2026, 06:49 AM UTC

  1. investigating Jul 02, 2026, 04:55 AM UTC

    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.

  2. investigating Jul 02, 2026, 04:57 AM UTC

    The AWS Logs integration in the same region is affected as well. We will provide further updates as our investigation progresses.

  3. resolved Jul 02, 2026, 06:49 AM UTC

    This incident has been resolved by restarting the affected services.

Read the full incident report →

Minor July 1, 2026 Elevated Loki Query Bytes Reporting 2h 17m AWS Australia - prod-au-southeast-1, AWS Brazil - prod-sa-east-1, AWS Canada - prod-ca-east-0, AWS Germany - prod-eu-west-2 and 21 more

Started Jul 01, 2026, 07:43 PM UTC· resolved Jul 01, 2026, 10:00 PM UTC

  1. investigating Jul 01, 2026, 07:43 PM UTC

    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.

  2. resolved Jul 01, 2026, 10:00 PM UTC

    We’ve implemented a fix and can confirm the issue is fully resolved as of 20:25 UTC. Thank you for your patience.

Read the full incident report →