Jul <var data-var='date'> 8</var>, <var data-var='time'>15:33</var> 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.

Loki Billing Data Lost

Jul <var data-var='date'> 8</var>, <var data-var='time'>14:23</var> UTC Monitoring - We are in the process of rolling out the fix. Our engineers are monitoring the progress. Jul <var data-var='date'> 8</var>, <var data-var='time'>12:17</var> 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

Grafana rulers crash-looping on prometheus

Jul <var data-var='date'> 8</var>, <var data-var='time'>11:00</var> 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 <var data-var='date'> 8</var>, <var data-var='time'>10:28</var> 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.

Cannot access dashboard set up as a home page

Jul <var data-var='date'> 7</var>, <var data-var='time'>13:44</var> 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.

Delayed usage and billing data

Jul <var data-var='date'> 6</var>, <var data-var='time'>07:37</var> UTC Resolved - We haven't noticed any further issues in this region for alert group processing since yesterday. This incident i fully resolved. Jul <var data-var='date'> 5</var>, <var data-var='time'>13:38</var> 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 <var data-var='date'> 5</var>, <var data-var='time'>11:37</var> 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.

Grafana Cloud IRM alert groups failing to produce alerts in us-east-3 region.

Jul <var data-var='date'> 3</var>, <var data-var='time'>14:27</var> 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.

Partial Write Outage for Grafana Cloud Logs in prod-eu-north-0.

Jul <var data-var='date'> 2</var>, <var data-var='time'>21:35</var> UTC Resolved - This incident has been resolved. Thank you for your patience. Jul <var data-var='date'> 2</var>, <var data-var='time'>20:16</var> 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 <var data-var='date'> 2</var>, <var data-var='time'>18:10</var> 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.

Some Queries Failing

Jul <var data-var='date'> 2</var>, <var data-var='time'>06:49</var> UTC Resolved - This incident has been resolved by restarting the affected services. Jul <var data-var='date'> 2</var>, <var data-var='time'>04:57</var> UTC Update - The AWS Logs integration in the same region is affected as well. We will provide further updates as our investigation progresses. Jul <var data-var='date'> 2</var>, <var data-var='time'>04:55</var> 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.

Loki and Frontend Observability - Major Outage in prod-us-central-0 region

Jul <var data-var='date'> 1</var>, <var data-var='time'>22:00</var> 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 <var data-var='date'> 1</var>, <var data-var='time'>19:43</var> 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.

Elevated Loki Query Bytes Reporting

Jun <var data-var='date'>30</var>, <var data-var='time'>08:20</var> 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 <var data-var='date'>29</var>, <var data-var='time'>17:47</var> UTC Identified - We've identified a possible cause, and a mitigation is in place to prevent further occurrences. Jun <var data-var='date'>29</var>, <var data-var='time'>15:37</var> UTC Update - The errors and latency have now recovered, we continue investigating the root cause. Jun <var data-var='date'>29</var>, <var data-var='time'>13:52</var> UTC Update - The errors are recovering, and we are still looking into the root cause of this. Jun <var data-var='date'>29</var>, <var data-var='time'>11:37</var> 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.

Mimir read errors and high latency in prod-eu-west-0

Jun <var data-var='date'>29</var>, <var data-var='time'>14:27</var> UTC Resolved - This incident has been resolved. Jun <var data-var='date'>29</var>, <var data-var='time'>12:37</var> 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.

Confluent API Outage

Jun <var data-var='date'>29</var>, <var data-var='time'>13:12</var> UTC Resolved - This incident has been resolved. Jun <var data-var='date'>29</var>, <var data-var='time'>11:14</var> UTC Monitoring - A fix has been applied and we are currently monitoring results. Jun <var data-var='date'>29</var>, <var data-var='time'>10:34</var> 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.

Rule evaluation error on cluster prod-gb-south-0

Jun <var data-var='date'>28</var>, <var data-var='time'>02:35</var> UTC Resolved - This incident has been resolved. Jun <var data-var='date'>26</var>, <var data-var='time'>23:30</var> 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 <var data-var='date'>26</var>, <var data-var='time'>16:33</var> 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 <var data-var='date'>26</var>, <var data-var='time'>14:09</var> 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 <var data-var='date'>26</var>, <var data-var='time'>13:19</var> 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 <var data-var='date'>26</var>, <var data-var='time'>13:08</var> 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.

K6 - Test run metrics processing is delayed

Jun <var data-var='date'>24</var>, <var data-var='time'>16:07</var> UTC Completed - The scheduled maintenance has been completed. Jun <var data-var='date'>24</var>, <var data-var='time'>12:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Jun <var data-var='date'>22</var>, <var data-var='time'>13:15</var> 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.

Scheduled maintenance: Grafana Cloud Migration Assistant

Jun <var data-var='date'>24</var>, <var data-var='time'>12:46</var> UTC Resolved - This incident has been resolved. Error rates continued to remain near 0 and operations are performing as expected. Jun <var data-var='date'>23</var>, <var data-var='time'>17:54</var> UTC Update - Error rates have remained near zero, and we continue to monitor. Jun <var data-var='date'>23</var>, <var data-var='time'>13:15</var> UTC Update - We are continuing to monitor for further issues. Jun <var data-var='date'>23</var>, <var data-var='time'>09:14</var> UTC Update - We have deployed additional mitigations that should help with remaining errors. We are continuing to monitor error rates. Jun <var data-var='date'>22</var>, <var data-var='time'>17:16</var> 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 <var data-var='date'>19</var>, <var data-var='time'>19:07</var> 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 <var data-var='date'>19</var>, <var data-var='time'>02:33</var> UTC Update - Due to the linked GCP outage below, users located in India may have trouble loading parts of Grafana. https://status.cloud.google.com/incidents/5fGQt4VbkDnr3Yp8PXPr 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 <var data-var='date'>18</var>, <var data-var='time'>16:57</var> UTC Monitoring - Due to the linked GCP outage below, users located in India may have trouble loading parts of Grafana. https://status.cloud.google.com/incidents/5fGQt4VbkDnr3Yp8PXPr 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 <var data-var='date'>18</var>, <var data-var='time'>15:18</var> UTC Investigating - Due to the linked GCP outage below, users located in India may have trouble loading parts of Grafana. https://status.cloud.google.com/incidents/5fGQt4VbkDnr3Yp8PXPr 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.

Potential Issues Loading Grafana for Users in India

Jun <var data-var='date'>20</var>, <var data-var='time'>20:00</var> 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.

Elevated Logs Query Usage — Unexpected Billing Impact

Jun <var data-var='date'>19</var>, <var data-var='time'>19:19</var> UTC Resolved - This incident has been resolved. Thank you for your patience. Jun <var data-var='date'>19</var>, <var data-var='time'>17:46</var> 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 <var data-var='date'>19</var>, <var data-var='time'>16:39</var> 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.

Rule Evaluation Outage in prod-us-central-0

Jun <var data-var='date'>18</var>, <var data-var='time'>18:50</var> UTC Resolved - This incident has been resolved. Thank you for your patience. Jun <var data-var='date'>18</var>, <var data-var='time'>18:09</var> 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 <var data-var='date'>18</var>, <var data-var='time'>17:01</var> 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.

Issues with actions in the Grafana IRM mobile app

Jun <var data-var='date'>18</var>, <var data-var='time'>16:21</var> UTC Resolved - This incident has been resolved. Thank you for your patience. Jun <var data-var='date'>18</var>, <var data-var='time'>14:04</var> UTC Update - We are continuing to monitor for any further issues. Jun <var data-var='date'>18</var>, <var data-var='time'>13:15</var> 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 <var data-var='date'>18</var>, <var data-var='time'>11:45</var> UTC Update - We are continuing to investigate this issue. Jun <var data-var='date'>18</var>, <var data-var='time'>11:25</var> 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.

Degraded k6 cloud UI performance

Jun <var data-var='date'>18</var>, <var data-var='time'>14:08</var> UTC Resolved - This incident has been resolved. Jun <var data-var='date'>18</var>, <var data-var='time'>08:04</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Jun <var data-var='date'>17</var>, <var data-var='time'>23:22</var> 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 <var data-var='date'>17</var>, <var data-var='time'>21:43</var> 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 <var data-var='date'>17</var>, <var data-var='time'>20:55</var> 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 <var data-var='date'>17</var>, <var data-var='time'>20:17</var> 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.

Loki data source-managed alert rules not visible in the Grafana Cloud Alerting UI

Jun <var data-var='date'>18</var>, <var data-var='time'>10:13</var> UTC Resolved - A fix has been deployed and the issue after monitoring as been fixed. Jun <var data-var='date'>18</var>, <var data-var='time'>08:48</var> 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.

Frontend Observability - Suspected commit feature not working as expected

Jun <var data-var='date'>17</var>, <var data-var='time'>09:58</var> UTC Resolved - Following our ongoing communications regarding the complete outage in prod-me-central-1, we are now closing this incident. As noted in the latest AWS update, the Middle East (UAE) region (ME-CENTRAL-1) has suffered significant damage and restoration is expected to take several months. We strongly recommend all affected customers migrate workloads to an alternate Grafana Cloud region as soon as possible. If you have not already done so, please follow the migration steps outlined in our previous updates: 1. Create a Grafana Cloud stack in an alternate region 2. Update clients to send telemetry to the new region, if using Grafana Alloy then you can use Fleet Management https://grafana.com/docs/grafana-cloud/send-data/fleet-management/introduction/ 3. If your instance remains available and you have not configured your dashboards as code, then you may be able to use `grafanactl` to migrate dashboards https://grafana.com/docs/grafana/latest/as-code/observability-as-code/grafana-cli/grafanacli-workflows/ https://grafana.github.io/grafanactl/ For further details, please refer to the AWS incident communication directly: https://health.aws.amazon.com/health/status Please reach out to our Support team if you need any assistance with the above - https://grafana.com/profile/org#support We will continue to monitor the situation and update the incident once circumstances change. May <var data-var='date'>27</var>, <var data-var='time'>17:10</var> UTC Update - The TLS certificates serving prod-me-central-1 endpoints expire on May 30, 2026. Replacement certificates have been imported, but the ongoing AWS regional incident is preventing them from propagating to all load balancer nodes, so customers may see certificate errors after that date until AWS restores normal operation. We do not have any additional updates to share at this time. Our team is actively monitoring the situation and will provide further information as it becomes available. In the meantime, please continue to refer to the AWS Status Page for the most detailed and up-to-date information. May <var data-var='date'>21</var>, <var data-var='time'>11:41</var> UTC Update - AWS UAE - prod-me-central-1: Public Probe checks might suffer degraded experience. We recommend migrating checks from the UAE probe to the next nearest probe suitable for your use case. May <var data-var='date'>13</var>, <var data-var='time'>21:59</var> UTC Update - We do not have any additional updates to share at this time. Our team is actively monitoring the situation and will provide further information as it becomes available. In the meantime, please continue to refer to the AWS Status Page for the most detailed and up-to-date information. Apr <var data-var='date'>20</var>, <var data-var='time'>15:11</var> UTC Update - We are continuing to investigate this issue. Mar <var data-var='date'>19</var>, <var data-var='time'>12:13</var> UTC Update - We have not received any further updates from AWS at this time. However, we are actively monitoring the outage and will provide additional information as it becomes available. Also, please continue to refer to the AWS status page for more detailed updates. https://health.aws.amazon.com/health/status All the guidance previously included about stack migration is still relevant. Please reach out to our Support team if you have any questions. Mar <var data-var='date'> 4</var>, <var data-var='time'>22:22</var> UTC Update - We are actively monitoring the situation, but at this time there are no new updates to share. The next update will be provided once we have more information to share. Please reach out to our Support team if you have any questions. Mar <var data-var='date'> 4</var>, <var data-var='time'>10:28</var> UTC Update - We are continuing to investigate this issue. Mar <var data-var='date'> 2</var>, <var data-var='time'>22:18</var> UTC Update - Please continue to refer to the AWS status page for more detailed updates specific to AWS. https://health.aws.amazon.com/health/status AWS are recommending that affected customers move workloads to alternate regions, and we are recommending the same. Customers who are impacted and who cannot wait for a restoration of service are asked to: 1. Create a Grafana Cloud stack in an alternate region 2. Update clients to send telemetry to the new region, if using Grafana Alloy then you can use Fleet Management https://grafana.com/docs/grafana-cloud/send-data/fleet-management/introduction/ 3. If your instance remains available and you have not configured your dashboards as code, then you may be able to use `grafanactl` to migrate dashboards https://grafana.com/docs/grafana/latest/as-code/observability-as-code/grafana-cli/grafanacli-workflows/ https://grafana.github.io/grafanactl/ We are continuing to work with our CSP at this time, and will provide updates as they are available. Mar <var data-var='date'> 2</var>, <var data-var='time'>10:31</var> UTC Update - AWS are recommending that affected customers move workloads to alternate regions https://health.aws.amazon.com/health/status and we are recommending the same. Customers who are impacted and who cannot wait for a restoration of service are asked to: 1. Create a Grafana Cloud stack in an alternate region 2. Update clients to send telemetry to the new region, if using Grafana Alloy then you can use Fleet Management https://grafana.com/docs/grafana-cloud/send-data/fleet-management/introduction/ 3. If your instance remains available and you have not configured your dashboards as code, then you may be able to use `grafanactl` to migrate dashboards https://grafana.com/docs/grafana/latest/as-code/observability-as-code/grafana-cli/grafanacli-workflows/ https://grafana.github.io/grafanactl/ We will provide updates when we have them, but we do not have an expected resolution time at this point. Mar <var data-var='date'> 2</var>, <var data-var='time'>10:04</var> UTC Update - Customers are recommended to configure a new blank stack in an alternative Grafana Cloud region and to reconfigure their clients (such as Grafana Alloy) to send telemetry to that region, Fleet Management can be used for this purpose https://grafana.com/docs/grafana-cloud/send-data/fleet-management/introduction/ Mar <var data-var='date'> 2</var>, <var data-var='time'>08:36</var> UTC Update - We are updating this incident to reflect a complete outage in prod-me-central-1, due to an on-going AWS UAE data center issue. We will provide further updates accordingly. Mar <var data-var='date'> 2</var>, <var data-var='time'>08:21</var> UTC Update - We are observing write and read outage errors across all databases (metrics, logs, traces) in prod-me-central-1, due to an on-going AWS UAE data center issue. We will provide further updates accordingly. Mar <var data-var='date'> 2</var>, <var data-var='time'>08:14</var> UTC Update - We are observing write and read outage errors across all databases (metrics, logs, traces) in prod-me-central-1, due to an on-going AWS UAE data center issue. We will provide further updates accordingly. Mar <var data-var='date'> 2</var>, <var data-var='time'>06:43</var> UTC Investigating - We are seeing elevated write and read path errors in prod-me-central-1, due to an on-going AWS UAE data center issue. We will provide further updates accordingly.

Complete outage in prod-me-central-1

Jun <var data-var='date'>12</var>, <var data-var='time'>19:52</var> UTC Resolved - This incident has been resolved. Thank you for your patience. Jun <var data-var='date'> 8</var>, <var data-var='time'>21:36</var> UTC Update - The incident has been mitigated, and services are operating normally. We continue to monitor the service to ensure full stability. Jun <var data-var='date'> 7</var>, <var data-var='time'>11:00</var> UTC Monitoring - The incident has been mitigated, and services are operating normally. We are currently monitor the service to ensure full stability. Jun <var data-var='date'> 7</var>, <var data-var='time'>06:00</var> UTC Update - We’re making ongoing progress on the investigation alongside our upstream provider. Jun <var data-var='date'> 7</var>, <var data-var='time'>03:50</var> UTC Update - We are continuing to investigate this issue. Jun <var data-var='date'> 7</var>, <var data-var='time'>02:46</var> UTC Update - Intermittent spikes in rule evaluations continuing. Jun <var data-var='date'> 7</var>, <var data-var='time'>01:39</var> UTC Investigating - From 00:20:00 to 00:27:00 and again 00:32:00 to 00:38:00 there were brief spikes in rule evaluation failures. Engineers are investigating.

Brief Rule Evaluation Failures in prod-eu-west-3

Jun <var data-var='date'>12</var>, <var data-var='time'>18:30</var> UTC Resolved - Our team had discovered a read issue around 19:35-20:08 UTC. Impact at the time would have provided errors similar to context deadline exceeded (DatasourceError response). This has since been resolved, and should not have caused any data loss, only a short query disruption.

Brief Loki Prod-012-eu-west-2 Disruption

Jun <var data-var='date'>11</var>, <var data-var='time'>05:36</var> UTC Resolved - This incident has been resolved. Jun <var data-var='date'>10</var>, <var data-var='time'>10:49</var> UTC Investigating - We’re currently investigating an issue affecting The Grafana Dashboards page. When set to view by folders, is currently experiencing an issue where no dashboards are shown. Our team is working on fixing the problem. In the meantime, switching to ‘View as list’ allows access to dashboards as usual”.

Grafana Dashboards page not displaying when set to ‘View by Folders’

AWS Australia - prod-ap-southeast-2

AWS Brazil - prod-sa-east-1

AWS Canada - prod-ca-east-0

AWS Germany - prod-eu-west-2

AWS Germany - prod-eu-west-4

AWS India - prod-ap-south-1

AWS Japan - prod-ap-northeast-0

AWS UAE - prod-me-central-1

AWS Singapore - prod-ap-southeast-1

AWS Sweden - prod-eu-north-0

AWS US East - prod-us-east-0

AWS US East - prod-us-east-2

AWS US West - prod-us-west-0

AWS Australia - prod-au-southeast-1

AWS UK - prod-gb-south-1

AWS Ireland - prod-eu-west-6

Azure US Central - us-central2

AWS Switzerland - prod-eu-central-0

Azure Netherlands - prod-eu-west-3

GCP Australia - prod-au-southeast-0

GCP Belgium - prod-eu-west-0

GCP Brazil - prod-sa-east-0

GCP India - prod-ap-south-0

GCP Singapore - prod-ap-southeast-0

GCP UK - prod-gb-south-0

GCP US Central - prod-us-central-0

GCP US Central - prod-us-central-3

GCP US Central - prod-us-central-4

GCP US East - prod-us-east-1

play.grafana.org

Federal Cloud - AWS US Gov West

Grafana

AWS Australia - prod-ap-southeast-2: Querying

AWS Australia - prod-ap-southeast-2: Ingestion

AWS Brazil - prod-sa-east-1: Querying

AWS Brazil - prod-sa-east-1: Ingestion

AWS Canada - prod-ca-east-0: Querying

AWS Canada - prod-ca-east-0: Ingestion

AWS Germany - prod-eu-west-2: Querying

AWS Germany - prod-eu-west-2: Ingestion

AWS UAE - prod-me-central-1: Querying

AWS UAE - prod-me-central-1: Ingestion

AWS India - prod-ap-south-1: Querying

AWS India - prod-ap-south-1: Ingestion

AWS Japan - prod-ap-northeast-0: Querying

AWS Japan - prod-ap-northeast-0: Ingestion

AWS Singapore - prod-ap-southeast-1: Querying

AWS Singapore - prod-ap-southeast-1: Ingestion

AWS Sweden - prod-eu-north-0: Querying

AWS Sweden - prod-eu-north-0: Ingestion

AWS US East - prod-us-east-0: Querying

AWS US East - prod-us-east-0: Ingestion

AWS US West - prod-us-west-0: Querying

AWS US West - prod-us-west-0: Ingestion

Azure Netherlands - prod-eu-west-3: Querying

Azure Netherlands - prod-eu-west-3: Ingestion

Azure US Central - us-central2: Querying

Azure US Central - us-central2: Ingestion

Azure US Central - us-central7: Ingestion

GCP Australia - prod-au-southeast-0: Querying

GCP Australia - prod-au-southeast-0: Ingestion

GCP Belgium - prod-eu-west-0: Querying

GCP Belgium - prod-eu-west-0: Ingestion

GCP Brazil - prod-sa-east-0: Querying

GCP Brazil - prod-sa-east-0: Ingestion

GCP India - prod-ap-south-0: Querying

GCP India - prod-ap-south-0: Ingestion

GCP Singapore - prod-ap-southeast-0: Querying

GCP Singapore - prod-ap-southeast-0: Ingestion

GCP UK - prod-gb-south-0: Querying

GCP UK - prod-gb-south-0: Ingestion

GCP US Central - prod-us-central-0: Querying

GCP US Central - prod-us-central-0: Ingestion

GCP US Central - prod-us-central-5: Querying

GCP US Central - prod-us-central-5: Ingestion

GCS US - cortex-prod-04: Ingestion

GCS US - cortex-prod-04: Querying

Azure US Central - prod-us-central-7: Querying

Azure US Central - prod-us-central-7: Ingestion

Metrics

AWS Australia - prod-ap-southeast-2: Rule Evaluation

AWS Australia - prod-ap-southeast-2: Alertmanager and Rules Configuration API

AWS Australia - prod-ap-southeast-2: Alertmanager

AWS Brazil - prod-sa-east-1: Rule Evaluation

AWS Brazil - prod-sa-east-1: Alertmanager and Rules Configuration API

AWS Brazil - prod-sa-east-1: Alertmanager

AWS Canada - prod-ca-east-0: Rule Evaluation

AWS Canada - prod-ca-east-0: Alertmanager and Rules Configuration API

AWS Canada - prod-ca-east-0: Alertmanager

AWS Germany - prod-eu-west-2: Rule Evaluation

AWS Germany - prod-eu-west-2: Alertmanager and Rules Configuration API

AWS Germany - prod-eu-west-2: Alertmanager

AWS UAE - prod-me-central-1: Rule Evaluation

AWS UAE - prod-me-central-1: Alertmanager and Rules Configuration API

AWS UAE - prod-me-central-1: Alertmanager

AWS India - prod-ap-south-1: Rule Evaluation

AWS India - prod-ap-south-1: Alertmanager and Rules Configuration API

AWS Japan - prod-ap-northeast-0: Rule Evaluation

AWS Japan - prod-ap-northeast-0: Alertmanager and Rules Configuration API

AWS Singapore - prod-ap-southeast-1: Rule Evaluation

AWS Singapore - prod-ap-southeast-1: Alertmanager and Rules Configuration API

AWS Singapore - prod-ap-southeast-1: Alertmanager

AWS Sweden - prod-eu-north-0: Alertmanager and Rules Configuration API

AWS Sweden - prod-eu-north-0: Alertmanager

AWS Sweden - prod-eu-north-0: Rule Evaluation

AWS US East - prod-us-east-0: Rule Evaluation

AWS US East - prod-us-east-0: Alertmanager and Rules Configuration API

AWS US East - prod-us-east-0: Alertmanager

AWS US West - prod-us-west-0: Rule Evaluation

AWS US West - prod-us-west-0: Alertmanager and Rules Configuration API

AWS US West - prod-us-west-0: Alertmanager

Azure Netherlands - prod-eu-west-3: Rule Evaluation

Azure Netherlands - prod-eu-west-3: Alertmanager and Rules Configuration API

Azure Netherlands - prod-eu-west-3: Alertmanager

Azure US Central - us-central2: Rule Evaluation

Azure US Central - us-central2: Alertmanager and Rules Configuration API

Azure US Central - us-central2: Alertmanager

GCP Australia - prod-au-southeast-0: Rule Evaluation

GCP Australia - prod-au-southeast-0: Alertmanager and Rules Configuration API

GCP Australia - prod-au-southeast-0: Alertmanager

GCP Belgium - prod-eu-west-0: Rule Evaluation

GCP Belgium - prod-eu-west-0: Alertmanager and Rules Configuration API

GCP Belgium - prod-eu-west-0: Alertmanager

GCP Brazil - prod-sa-east-0: Rule Evaluation

GCP Brazil - prod-sa-east-0: Alertmanager and Rules Configuration API

GCP Brazil - prod-sa-east-0: Alertmanager

GCP India - prod-ap-south-0: Rule Evaluation

GCP India - prod-ap-south-0: Alertmanager and Rules Configuration API

GCP India - prod-ap-south-0: Alertmanager

GCP Singapore - prod-ap-southeast-0: Rule Evaluation

GCP Singapore - prod-ap-southeast-0: Alertmanager and Rules Configuration API

GCP Singapore - prod-ap-southeast-0: Alertmanager

GCP UK - prod-gb-south-0: Rule Evaluation

GCP UK - prod-gb-south-0: Alertmanager and Rules Configuration API

GCP UK - prod-gb-south-0: Alertmanager

GCP US Central - prod-us-central-0: Rule Evaluation

GCP US Central - prod-us-central-0: Alertmanager and Rules Configuration API

GCP US Central - prod-us-central-0: Alertmanager

Alerting and SLO

Azure US Central - us-central7

GCP US Central - prod-us-central-5

Logs

AWS Australia - prod-ap-southeast-2: Metrics Generator

AWS Brazil - prod-sa-east-1: Metrics Generator

AWS Canada - prod-ca-east-0: Metrics Generator

AWS Germany - prod-eu-west-2: Metrics Generator

AWS India - prod-ap-south-1: Metrics Generator

AWS Japan - prod-ap-northeast-0: Metrics Generator

AWS Singapore - prod-ap-southeast-1: Metrics Generator

AWS Sweden - prod-eu-north-0: Metrics Generator

AWS US East - prod-us-east-0: Metrics Generator

Traces

Is Grafana down?

Grafana status is DEGRADED

Components with issues

Lastest published events

Loki Billing Data Lost

Grafana rulers crash-looping on prometheus

Cannot access dashboard set up as a home page

Grafana Services, Components and Regions

Recent Grafana events

Loki Billing Data Lost

Grafana rulers crash-looping on prometheus

Cannot access dashboard set up as a home page

Delayed usage and billing data

Grafana Cloud IRM alert groups failing to produce alerts in us-east-3 region.

Partial Write Outage for Grafana Cloud Logs in prod-eu-north-0.

Get your FREE account now,
5 monitors included!

Is Grafana down?

Grafana status is DEGRADED

Components with issues

Lastest published events

Loki Billing Data Lost

Grafana rulers crash-looping on prometheus

Cannot access dashboard set up as a home page

Grafana Services, Components and Regions

Recent Grafana events

Loki Billing Data Lost

Grafana rulers crash-looping on prometheus

Cannot access dashboard set up as a home page

Delayed usage and billing data

Grafana Cloud IRM alert groups failing to produce alerts in us-east-3 region.

Partial Write Outage for Grafana Cloud Logs in prod-eu-north-0.

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!