Grafana Outage History

Started Oct 21, 2026, 01:22 PM UTC· resolved Oct 21, 2026, 03:29 PM UTC

1. identified Oct 21, 2026, 01:22 PM UTC

   We are currently investigating this issue impacting some GCK6 app project pages. We are in the process of providing a fix for this.

2. identified Oct 21, 2026, 02:22 PM UTC

   We are continuing to work on a fix for the issue.

3. resolved Oct 21, 2026, 03:29 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 21, 2026, 11:48 AM UTC· resolved Oct 21, 2026, 01:26 PM UTC

1. investigating Oct 21, 2026, 11:48 AM UTC

   Since approximately 20:30 UTC on October 20, we have observed an increase in alert rule evaluation errors affecting rules that query Grafana Cloud Prometheus (Mimir) data sources in Cluster AWS Germany. Our engineering team is actively investigating and working on remediation.

2. identified Oct 21, 2026, 12:12 PM UTC

   The root cause of the issue has been indentified and we are working on the remediation steps.

3. monitoring Oct 21, 2026, 01:12 PM UTC

   Remediation measures have been applied, and we are monitoring the recovery.

4. resolved Oct 21, 2026, 01:26 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 21, 2026, 06:20 AM UTC· resolved Oct 21, 2026, 07:00 AM UTC

1. resolved Oct 21, 2026, 07:10 AM UTC

   As of 21 Oct, 06:20 am UTC, we became aware of an issue with possible incorrect evaluation of Synthetic Monitoring alert rules in cluster prod-us-east-3. The issue has been ended 07:00 am UTC

Read the full incident report →

Started Oct 20, 2026, 09:36 PM UTC· resolved Oct 21, 2026, 12:09 AM UTC

1. investigating Oct 20, 2026, 09:36 PM UTC

   We are currently investigating an issue in the prod-sa-east-1 region causing slow requests, or some stacks struggling to start. We will provide an update as soon as we have more information to share.

2. investigating Oct 20, 2026, 10:14 PM UTC

   Synthetic Monitoring alerting is also impacted. We are continuing to investigate this issue.

3. investigating Oct 20, 2026, 11:39 PM UTC

   Synthetic Monitoring alerting has recovered. We are continuing to monitor.

4. resolved Oct 21, 2026, 12:09 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 20, 2026, 07:28 AM UTC· resolved Oct 20, 2026, 10:33 AM UTC

1. investigating Oct 20, 2026, 07:28 AM UTC

   We are currently investigating this issue.

2. investigating Oct 20, 2026, 07:29 AM UTC

   We are continuing to investigate this issue.

3. investigating Oct 20, 2026, 07:36 AM UTC

   Only the public API is affected for prod-eu-west-0

4. monitoring Oct 20, 2026, 08:04 AM UTC

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

5. resolved Oct 20, 2026, 10:33 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 20, 2026, 06:49 AM UTC· resolved Oct 20, 2026, 04:33 PM UTC

1. investigating Oct 20, 2026, 06:49 AM UTC

   As of 06:30 UTC, we became aware of to an issue with Grafana Cloud unavailibity in the prod-gb-south-0 region. Engineering is actively engaged and assessing the issue. We will provide updates accordingly.

2. investigating Oct 20, 2026, 06:54 AM UTC

   We are continuing to investigate this issue.

3. investigating Oct 20, 2026, 11:37 AM UTC

   We are continuing to investigate this issue.

4. identified Oct 20, 2026, 12:43 PM UTC

   Between 06:15 and 12:15 UTC, Grafana Cloud Frontend Observability in GCP UK (prod-gb-south-0) experienced errors accepting incoming telemetry data. This has been resolved and Frontend Observability is operating normally in this region. We are continuing to investigate and monitor the remaining impacted services.

5. identified Oct 20, 2026, 02:29 PM UTC

   We are seeing errors in Frontend o11y again. We are continuing to investigate and monitor the impacted services.

6. resolved Oct 20, 2026, 04:33 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 19, 2026, 03:06 PM UTC· resolved Oct 19, 2026, 05:56 PM UTC

1. investigating Oct 19, 2026, 03:06 PM UTC

   We are currently investigating an issue causing elevated read and ruler errors. We will provide another update as soon as we have more to share.

2. monitoring Oct 19, 2026, 03:48 PM UTC

   Errors have stopped since 15:15 UTC. We are continuing to monitor.

3. resolved Oct 19, 2026, 05:56 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 16, 2026, 09:05 PM UTC· resolved Oct 17, 2026, 01:55 AM UTC

1. investigating Oct 16, 2026, 09:05 PM UTC

   We’re currently investigating an issue affecting metrics reads and rule evaluations in mimir-prod-66. Our team is actively working to identify the cause. Thank you for your patience.

2. investigating Oct 16, 2026, 09:08 PM UTC

   We are continuing to investigate this issue.

3. monitoring Oct 16, 2026, 11:27 PM UTC

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

4. monitoring Oct 16, 2026, 11:28 PM UTC

   We are continuing to monitor for any further issues.

5. resolved Oct 17, 2026, 01:55 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 15, 2026, 04:10 PM UTC· resolved Oct 15, 2026, 09:53 PM UTC

1. investigating Oct 15, 2026, 04:10 PM UTC

   We are investigating Intermittent write failures in tempo-prod (prod-us-central-0) due to Google Cloud Storage internal errors.

2. monitoring Oct 15, 2026, 06:00 PM UTC

   Things are starting to recover, and we continue to monitor the issue.

3. resolved Oct 15, 2026, 09:53 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 15, 2026, 02:35 PM UTC· resolved Oct 15, 2026, 04:58 PM UTC

1. identified Oct 15, 2026, 02:35 PM UTC

   We observed some spikes in latency starting at approximately 12:50 UTC. We are working on a resolution. Next update by 15:30 UTC

2. identified Oct 15, 2026, 03:20 PM UTC

   We are continuing to work on a fix for this issue. Next update by 16:30 UTC

3. identified Oct 15, 2026, 04:08 PM UTC

   Things are starting to stabilize as we continue to work on a mitigation.

4. resolved Oct 15, 2026, 04:58 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 14, 2026, 12:57 PM UTC· resolved Oct 14, 2026, 03:45 PM UTC

1. investigating Oct 14, 2026, 12:57 PM UTC

   We are investigating increased authentication errors affecting Grafana Cloud in the prod-us-west-0 region. Customers may experience intermittent failures for requests that require authentication. Our engineering team has identified database performance degradation affecting the authentication service and is investigating the underlying cause. We will provide another update as more information becomes available.

2. identified Oct 14, 2026, 01:58 PM UTC

   The issue has been identified, and we have applied mitigations on our end. We are currently observing the progress.

3. identified Oct 14, 2026, 03:00 PM UTC

   We have noticed improvements across services. We will now be applying a more permanent fix. Impacted users may experience a disruption in the auth-api service of up to 15min while we apply a DB patch that will improve performance.

4. monitoring Oct 14, 2026, 03:25 PM UTC

   The fix has been implemented, and we are monitoring the results.

5. resolved Oct 14, 2026, 03:45 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 13, 2026, 07:55 PM UTC· resolved Oct 13, 2026, 08:46 PM UTC

1. investigating Oct 13, 2026, 07:55 PM UTC

   A small group of customers with stacks in prod-us-central-4 are getting forbidden errors when querying prometheus datasource. We are actively investigating and will share more as we learn.

2. investigating Oct 13, 2026, 08:01 PM UTC

   We are continuing to investigate this issue.

3. monitoring Oct 13, 2026, 08:29 PM UTC

   We have put some mitigations in place which seem to have helped with the errors. We continue to monitor the results.

4. resolved Oct 13, 2026, 08:46 PM UTC

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

Read the full incident report →

Started Oct 13, 2026, 09:23 AM UTC· resolved Oct 19, 2026, 11:39 AM UTC

1. investigating Oct 13, 2026, 09:23 AM UTC

   Phone call notifications to numbers in Russia and Kazakhstan are currently blocked. We are working to resolve the issue. As SMS support is limited in these countries, we recommend using mobile push notifications as an alternative. We do not currently have an estimated resolution time. We will provide further updates as more information becomes available.

2. investigating Oct 13, 2026, 09:35 PM UTC

   Phone call notifications to numbers in Russia and Kazakhstan are currently blocked. We are working to resolve the issue. As SMS support is limited in these countries, we recommend using mobile push notifications as an alternative. We do not currently have an estimated resolution time. We will provide further updates as more information becomes available.

3. investigating Oct 16, 2026, 07:44 PM UTC

   Phone call notifications to numbers in Russia and Kazakhstan are still blocked. We are working to resolve the issue. As SMS support is limited in these countries, we recommend using mobile push notifications as an alternative. We do not currently have an estimated resolution time. We will provide further updates as more information becomes available.

4. resolved Oct 19, 2026, 11:39 AM UTC

   Following further investigation, we've confirmed that SMS delivery to certain destinations is not currently supported. We've updated our documentation to clarify the supported destinations and available notification options. We recommend using mobile push notifications or phone calls as alternatives where SMS delivery is unavailable.

Read the full incident report →

Started Oct 12, 2026, 09:45 AM UTC· resolved Oct 12, 2026, 04:42 PM UTC

1. investigating Oct 12, 2026, 09:45 AM UTC

   We are investigating an issue affecting metrics ingestion for Grafana Cloud Metrics customers in AWS US East (VA). Customers may see failed or delayed writes. Next update by 10:15 UTC.

2. investigating Oct 12, 2026, 10:08 AM UTC

   We are continuing to investigate an issue affecting metrics ingestion for Grafana Cloud Metrics customers in AWS US East (VA). Customers may see failed or delayed writes. Next update by 11:00 UTC.

3. investigating Oct 12, 2026, 10:55 AM UTC

   We are continuing to investigate an issue affecting metrics ingestion for Grafana Cloud Metrics customers in AWS US East (VA). Customers may see failed or delayed writes to Grafana Cloud Metrics, this may also impact Metrics written by Frontend Observability and/or Synthetic Monitoring. Next update by 12:00 UTC.

4. identified Oct 12, 2026, 11:56 AM UTC

   We have identified the cause of an issue affecting metrics ingestion for Grafana Cloud Metrics customers in AWS US East (VA) - prod-us-east-3. Customers may see failed or delayed writes to Grafana Cloud Metrics, this may also impact Metrics written by Frontend Observability and/or Synthetic Monitoring. We are continuing to work on mitigations and are monitoring the impact to Grafana Cloud Metrics. Next update by 13:00 UTC.

5. identified Oct 12, 2026, 12:53 PM UTC

   We have identified the cause of an issue affecting metrics ingestion for Grafana Cloud Metrics customers in AWS US East (VA) - prod-us-east-3. Customers may see failed or delayed writes to Grafana Cloud Metrics, this may also impact Metrics written by Frontend Observability and/or Synthetic Monitoring. We are continuing to work on mitigations and are monitoring the impact to Grafana Cloud Metrics. Next update by 14:00 UTC.

6. identified Oct 12, 2026, 02:01 PM UTC

   We have isolated infrastructure suspected of contributing to the metrics ingestion issue in AWS US East (VA) - prod-us-east-3. We are validating recovery and completing mitigation steps. Customers may continue to experience failed or delayed metric writes while this work continues.

7. identified Oct 12, 2026, 03:01 PM UTC

   We have isolated infrastructure suspected of contributing to the metrics ingestion issue in AWS US East (VA) - prod-us-east-3. We are validating recovery and completing mitigation steps. Customers may continue to experience failed or delayed metric writes while this work continues.

8. resolved Oct 12, 2026, 04:42 PM UTC

   From 09:45 UTC on 2026-10-12, customers in AWS US East (VA) experienced failed or delayed metric writes to Grafana Cloud Metrics, which may have also affected Frontend Observability and Synthetic Monitoring data in that region. This has been fully resolved and all services are operating normally again.

Read the full incident report →

Started Oct 12, 2026, 01:30 AM UTC· resolved Oct 12, 2026, 03:00 PM UTC

1. resolved Oct 12, 2026, 04:07 PM UTC

   Between 14:40 and 15:00 UTC on 2026-10-12 (approximately 20 minutes), customers in AWS US East (OH) - prod-us-east-0, may have experienced failed metric writes to Grafana Cloud Metrics. This has been fully resolved and all services are operating normally.

Read the full incident report →

Started Oct 09, 2026, 08:30 AM UTC· resolved Oct 09, 2026, 10:45 AM UTC

1. resolved Oct 12, 2026, 09:58 AM UTC

   Between 09:38 and 10:45 UTC on 9 October 2026, customers using Private Data Source Connect (PDC) in the AWS US East (OH) - prod-us-east-2 Grafana Cloud Region, experienced failed or timed-out data source queries. This has been fully resolved and all services are operating normally.

Read the full incident report →

Started Oct 08, 2026, 01:06 PM UTC· resolved Oct 09, 2026, 12:39 AM UTC

1. investigating Oct 08, 2026, 01:06 PM UTC

   Beginning around 10:20 UTC, we have been seeing intermittent elevated error rates and latency affecting Grafana Cloud Metrics and Logs in GCP US Central (prod-us-central-0 and prod-us-central-5), and periodic increased latency and occasional errors affecting Grafana Cloud Traces in prod-us-central-0. Customers may see errors or delays when sending metrics, logs and traces. We are actively investigating. Next update by 13:40 UTC.

2. investigating Oct 08, 2026, 01:25 PM UTC

   We continue to investigate intermittent elevated error rates and latency affecting Grafana Cloud Metrics and Logs in GCP US Central (prod-us-central-0 and prod-us-central-5), and periodic increased latency affecting Grafana Cloud Traces in prod-us-central-0. Error rates have decreased, but intermittent errors and latency may still occur. We are working with our cloud provider as part of the investigation. We do not have an estimated time of resolution at this time. Next update by 14:30 UTC.

3. investigating Oct 08, 2026, 01:39 PM UTC

   Update to scope: we have not confirmed any impact to Grafana Cloud Logs, and Logs has been removed from the affected components. We continue to investigate intermittent elevated error rates and latency affecting Grafana Cloud Metrics in GCP US Central (prod-us-central-0 and prod-us-central-5), and periodic increased latency affecting Grafana Cloud Traces in prod-us-central-0. Error rates have decreased, but intermittent errors and latency may still occur. We are working with our cloud provider as part of the investigation. We do not have an estimated time of resolution at this time. Next update by 14:30 UTC.

4. investigating Oct 08, 2026, 01:52 PM UTC

   We continue to investigate intermittent elevated error rates and latency affecting Grafana Cloud Metrics in GCP US Central (prod-us-central-0 and prod-us-central-5), and periodic increased latency affecting Grafana Cloud Traces in prod-us-central-0. Intermittent errors and latency may still occur. We are working with our cloud provider as part of the investigation. We do not have an estimated time of resolution at this time. Next update by 14:30 UTC.

5. investigating Oct 08, 2026, 02:40 PM UTC

   We are investigating degraded performance with increased latency in the ingestion path for Grafana Cloud Metrics in GCP US Central (prod-us-central-0 and prod-us-central-5) and for Grafana Cloud Traces in prod-us-central-0. Customers may experience intermittent errors or delays when sending metrics and traces. We are investigating this with our cloud provider. We do not have an estimated time of resolution at this time. Next update by 15:30 UTC.

6. investigating Oct 08, 2026, 03:19 PM UTC

   We are investigating degraded performance with increased latency in the ingestion path for Grafana Cloud Metrics in GCP US Central (prod-us-central-0 and prod-us-central-5) and for Grafana Cloud Traces in prod-us-central-0. Customers may experience intermittent errors or delays when sending metrics and traces. We are investigating this with our cloud provider. We do not have an estimated time of resolution at this time. Next update by 16:30 UTC.

7. investigating Oct 08, 2026, 04:21 PM UTC

   We continue seeing elevated error rates and latency, and keep working with our cloud provider on this issue. Next update by 17:30 UTC.

8. investigating Oct 08, 2026, 05:30 PM UTC

   We are investigating degraded performance with increased latency in the ingestion path for Grafana Cloud Metrics in GCP US Central (prod-us-central-0 and prod-us-central-5) and for Grafana Cloud Traces in prod-us-central-0. Customers may experience intermittent errors or delays when sending metrics and traces. We continue to investigate this with our cloud provider. We do not have an estimated time of resolution at this time. Next update by 18:30 UTC

9. investigating Oct 08, 2026, 06:15 PM UTC

   We are investigating degraded performance and increased latency in the ingestion path for Grafana Cloud Metrics in GCP US Central (prod-us-central-0 and prod-us-central-5) and Grafana Cloud Traces in prod-us-central-0. Customers may experience intermittent errors or delays when sending metrics and traces. We have also received reports that some customers using Google Managed Prometheus in this region are experiencing issues when querying their GMP instances. We continue to investigate the issue with our cloud provider. We do not have an estimated time to resolution at this time.

10. investigating Oct 08, 2026, 07:13 PM UTC

    We are investigating degraded performance and increased latency in the ingestion path for Grafana Cloud Metrics in GCP US Central (prod-us-central-0 and prod-us-central-5) and Grafana Cloud Traces in prod-us-central-0. Customers may experience intermittent errors or delays when sending metrics and traces. We have also received reports that some customers using Google Managed Prometheus in this region are experiencing issues when querying their GMP instances. We continue to investigate the issue with our cloud provider. We do not have an estimated time to resolution at this time.

11. investigating Oct 08, 2026, 08:41 PM UTC

    We are investigating degraded performance and increased latency in the ingestion path for Grafana Cloud Metrics in GCP US Central (prod-us-central-0 and prod-us-central-5) and Grafana Cloud Traces in prod-us-central-0. Customers may experience intermittent errors or delays when sending metrics and traces. We continue to investigate the issue with our cloud provider. We do not have an estimated time to resolution at this time.

12. investigating Oct 08, 2026, 09:42 PM UTC

    We are investigating degraded performance and increased latency in the ingestion path for Grafana Cloud Metrics in GCP US Central (prod-us-central-0 and prod-us-central-5) and Grafana Cloud Traces in prod-us-central-0. Customers may experience intermittent errors or delays when sending metrics and traces. We continue to investigate the issue with our cloud provider. We do not have an estimated time to resolution at this time.

13. resolved Oct 09, 2026, 12:39 AM UTC

    This incident has been resolved

Read the full incident report →

Started Oct 08, 2026, 12:48 PM UTC· resolved Oct 08, 2026, 01:07 PM UTC

1. investigating Oct 08, 2026, 12:48 PM UTC

   Beginning around 10:20 UTC, we have been seeing intermittent elevated error rates and latency affecting Grafana Cloud Metrics and Logs in GCP US Central (prod-us-central-0 and prod-us-central-5). Customers may see errors or delays when sending metrics and logs. We are actively investigating. Next update by 13:40 UTC.

2. investigating Oct 08, 2026, 12:57 PM UTC

   We are continuing to investigate this issue.

3. investigating Oct 08, 2026, 12:58 PM UTC

   We are continuing to investigate this issue.

Read the full incident report →

Started Oct 07, 2026, 12:00 AM UTC· resolved Oct 07, 2026, 08:40 AM UTC

1. resolved Oct 07, 2026, 09:29 AM UTC

   A transient issue prevented Grafana Cloud k6 from serving metrics to a small number of customers for approximately 3–4 minutes. The issue has been resolved, and normal service has been restored.

Read the full incident report →

Started Oct 05, 2026, 04:17 PM UTC· resolved Oct 19, 2026, 11:40 AM UTC

1. investigating Oct 05, 2026, 04:17 PM UTC

   We are currently investigating an issue impacting all SMS attempts to Austria for IRM. All SMS attempts to Austria for IRM are currently blocked. We are working on a resolution, and an update will follow as soon as we have more info. Users should configure mobile push or phone calls as notifications.

2. identified Oct 05, 2026, 09:47 PM UTC

   The issue has been identified. We are working on a resolution, but do not have an ETA at this time. We will provide another update as soon as we have more information to share. Users should configure mobile push or phone calls as notifications.

3. identified Oct 06, 2026, 01:42 PM UTC

   This issue is also impacting numbers from Thailand and Bangladesh. The title of this status page has been updated to reflect this. Users should configure mobile push or phone calls as notifications. We are working on a resolution, and we will provide another update as soon as we have more information to share.

4. identified Oct 09, 2026, 12:51 PM UTC

   We are continuing working on a resolution, and will provide another update as soon as we have more information to share. In the meantime we recommend, affected users to configure mobile push or phone calls as notifications.

5. identified Oct 13, 2026, 09:35 PM UTC

   We are continuing working on a resolution, and will provide another update as soon as we have more information to share. In the meantime we recommend, affected users to configure mobile push or phone calls as notifications.

6. identified Oct 15, 2026, 09:33 AM UTC

   SMS delivery to Austrian numbers has been restored. SMS delivery to Thailand and Bangladesh is still affected, and we are continuing to work on a resolution. We will provide another update as soon as we have more information to share. In the meantime, we recommend that affected users configure mobile push or phone calls as notifications.

7. identified Oct 16, 2026, 03:20 PM UTC

   SMS delivery to Bangladesh has been restored. SMS delivery to Thailand is still affected, and we are continuing to work on a resolution. We will provide another update as soon as we have more information to share. In the meantime, we recommend that affected users configure mobile push or phone calls as notifications.

8. resolved Oct 19, 2026, 11:40 AM UTC

   Following further investigation, we've confirmed that SMS delivery to certain destinations is not currently supported. We've updated our documentation to clarify the supported destinations and available notification options. We recommend using mobile push notifications or phone calls as alternatives where SMS delivery is unavailable.

Read the full incident report →

Started Oct 04, 2026, 06:20 PM UTC· resolved Oct 04, 2026, 06:33 PM UTC

1. investigating Oct 04, 2026, 06:20 PM UTC

   We are investigating reduced query throughput for some data source plugins in multiple regions. Some queries may fail or be slow.

2. resolved Oct 04, 2026, 06:33 PM UTC

   Incident started around 15:51 UTC, resolved around 18:11 UTC. After investigation, we found that no customer queries were affected; only our internal metrics systems were impacted.

Read the full incident report →

Started Oct 03, 2026, 01:53 PM UTC· resolved Oct 03, 2026, 07:43 PM UTC

1. investigating Oct 03, 2026, 01:53 PM UTC

   Between 12:44 and 13:15 UTC, Grafana Cloud experienced elevated write latency and errors across multiple products, including Logs, Metrics, and Traces. Services have recovered and the underlying issue is being investigated and actively monitored.

2. monitoring Oct 03, 2026, 01:54 PM UTC

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

3. monitoring Oct 03, 2026, 03:07 PM UTC

   The issue is currently resolved but we are continuing to investigate and monitor things at this time.

4. resolved Oct 03, 2026, 07:43 PM UTC

   We've identified the issue as related to an increase in latency and errors rates with our cloud provider's infrastructure. We are working with the provider on a root cause analysis. The service has recovered and is operating normally.

Read the full incident report →

Started Oct 02, 2026, 10:03 AM UTC· resolved Oct 02, 2026, 02:03 PM UTC

1. investigating Oct 02, 2026, 11:03 AM UTC

   We are investigating elevated write latency and intermittent errors affecting Grafana Cloud Logs in Azure Netherlands. Customers may see delayed log ingestion and some failed write requests. Next update by 10:03 UTC.

2. investigating Oct 02, 2026, 11:06 AM UTC

   We are continuing to investigate this issue. Next update by 11:30 UTC.

3. identified Oct 02, 2026, 02:02 PM UTC

   We have identified the issue as related to a cloud provider dependency affecting the write path for Grafana Cloud Logs in Azure Netherlands. Latency has recovered to normal levels. We are continuing to monitor before fully closing this incident.

4. resolved Oct 02, 2026, 02:03 PM UTC

   Between 10:03 and 12:37 UTC, Grafana Cloud Logs in Azure Netherlands experienced elevated write latency and intermittent errors due to a cloud provider dependency issue. Service has fully recovered and is operating normally. Thank you for your patience.

Read the full incident report →

Started Sep 30, 2026, 12:40 PM UTC· resolved Sep 30, 2026, 03:39 PM UTC

1. investigating Sep 30, 2026, 12:40 PM UTC

   We are investigating elevated latency and a small number of failed requests for Grafana Cloud Logs in AWS US East (VA). Some customers writing logs to this region may see delayed ingestion or occasional write errors. We are actively investigating and will share more as we learn it. Next update by 13:38 UTC.

2. investigating Sep 30, 2026, 01:40 PM UTC

   We are continuing to investigate this issue.

3. identified Sep 30, 2026, 01:43 PM UTC

   We have identified a contributing factor to the elevated latency and are rolling out a mitigation to increase write capacity in AWS US East (VA). We continue to investigate a related, longer-running pattern. Next update by 14:40 UTC.

4. identified Sep 30, 2026, 02:31 PM UTC

   An additional brief recurrence affected a small number of requests after our mitigation was deployed, though impact was smaller than earlier today. We continue to monitor and investigate a related, longer-running pattern. Next update by 15:40 UTC.

5. resolved Sep 30, 2026, 03:39 PM UTC

   Between 12:09 and 15:39 UTC on September 30, Grafana Cloud Logs in AWS US East (VA) experienced intermittent elevated latency and a small number of failed requests. Impact has returned to normal levels and all services are operating as expected. Thank you for your patience.

Read the full incident report →

Started Sep 28, 2026, 05:32 PM UTC· resolved Sep 28, 2026, 07:21 PM UTC

1. investigating Sep 28, 2026, 05:32 PM UTC

   We are currently investigating an issue causing issues accessing the platform.

2. investigating Sep 28, 2026, 06:00 PM UTC

   We are continuing to investigate the issue, and will provide updates once we have more to share.

3. identified Sep 28, 2026, 06:38 PM UTC

   We have identified the issue, and put a mitigation in place. We continue to work towards a resolution

4. resolved Sep 28, 2026, 07:21 PM UTC

   This incident has been resolved.

Read the full incident report →