Grafana Cloud

Affected: GCk6 App

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. identified 2026-10-21 13:22 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 2026-10-21 14:22 UTC

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

3. resolved 2026-10-21 15:29 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

Names an upstream provider: AWS.

1. investigating 2026-10-21 11:48 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 2026-10-21 12:12 UTC

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

3. monitoring 2026-10-21 13:12 UTC

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

4. resolved 2026-10-21 13:26 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Affected: AWS US East - prod-us-east-3: API, AWS US East - prod-us-east-3: Public Probes

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-10-21 07:10 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

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Affected: AWS Brazil - prod-sa-east-1, AWS Brazil - prod-sa-east-1: API, AWS Brazil - prod-sa-east-1: Public Probes

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-10-20 21:36 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 2026-10-20 22:14 UTC

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

3. investigating 2026-10-20 23:39 UTC

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

4. resolved 2026-10-21 00:09 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Affected: GCk6 App

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-10-20 14:36 UTC

   We are currently investigating this issue impacting some GCK6 app project pages. We will provide an update once we have more information.

2. resolved 2026-10-20 16:08 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Affected: 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 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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-10-20 07:28 UTC

   We are currently investigating this issue.

2. investigating 2026-10-20 07:29 UTC

   We are continuing to investigate this issue.

3. investigating 2026-10-20 07:36 UTC

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

4. monitoring 2026-10-20 08:04 UTC

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

5. resolved 2026-10-20 10:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Affected: Grafana.com, Support Tickets, Integrations, Cost Management and Billing, Fleet Management, Incident Management and Response (IRM), Public Snapshots, GCP UK - prod-gb-south-0, GCP UK - prod-gb-south-0, GCP UK - prod-gb-south-0, GCP UK - prod-gb-south-0, GCP UK - prod-gb-south-0, GCP UK - prod-gb-south-0, GCP UK - prod-gb-south-0, GCP UK - prod-gb-south-0, GCP UK - prod-gb-south-0, GCP UK - prod-gb-south-0: Querying, GCP UK - prod-gb-south-0: API, GCP UK - prod-gb-south-0: Ingestion, GCP UK - prod-gb-south-0: Public Probes, 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: Querying, GCP UK - prod-gb-south-0: Alertmanager, GCP UK - prod-gb-south-0: Ingestion, GCP UK - prod-gb-south-0: Metrics Generator

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

Names an upstream provider: Google Cloud.

Started during Google Cloud: Multiple services were experiencing issues in the europe-west2 region..

1. investigating 2026-10-20 06:49 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 2026-10-20 06:54 UTC

   We are continuing to investigate this issue.

3. investigating 2026-10-20 11:37 UTC

   We are continuing to investigate this issue.

4. identified 2026-10-20 12:43 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...

5. identified 2026-10-20 14:29 UTC

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

6. resolved 2026-10-20 16:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-10-19 15:06 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 2026-10-19 15:48 UTC

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

3. resolved 2026-10-19 17:56 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Affected: AWS US East (VA) - prod-us-east-3

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-10-16 21:05 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 2026-10-16 21:08 UTC

   We are continuing to investigate this issue.

3. monitoring 2026-10-16 23:27 UTC

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

4. monitoring 2026-10-16 23:28 UTC

   We are continuing to monitor for any further issues.

5. resolved 2026-10-17 01:55 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

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

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

Names an upstream provider: Google Cloud.

1. investigating 2026-10-15 16:10 UTC

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

2. monitoring 2026-10-15 18:00 UTC

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

3. resolved 2026-10-15 21:53 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. identified 2026-10-15 14:35 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 2026-10-15 15:20 UTC

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

3. identified 2026-10-15 16:08 UTC

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

4. resolved 2026-10-15 16:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-10-14 12:57 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...

2. identified 2026-10-14 13:58 UTC

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

3. identified 2026-10-14 15:00 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 2026-10-14 15:25 UTC

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

5. resolved 2026-10-14 15:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Affected: GCP US Central - prod-us-central-4

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-10-13 19:55 UTC

   A small number of customers with stacks in prod-us-central-4 are receiving "forbidden" errors when querying Prometheus data sources. We are investigating and will provide an update soon.

2. investigating 2026-10-13 20:01 UTC

   We are continuing to investigate this issue.

3. monitoring 2026-10-13 20:29 UTC

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

4. resolved 2026-10-13 20:46 UTC

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

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Affected: Incident Management and Response (IRM)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-10-13 09:23 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...

2. investigating 2026-10-13 21:35 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...

3. investigating 2026-10-16 19:44 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...

4. resolved 2026-10-19 11:39 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...

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Affected: AWS US East (VA) - prod-us-east-3

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

Names an upstream provider: AWS.

1. investigating 2026-10-12 09:45 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 2026-10-12 10:08 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 2026-10-12 10:55 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...

4. identified 2026-10-12 11:56 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...

5. identified 2026-10-12 12:53 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...

6. identified 2026-10-12 14:01 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...

7. identified 2026-10-12 15:01 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...

8. resolved 2026-10-12 16:42 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...

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

Names an upstream provider: AWS.

1. resolved 2026-10-12 01:30 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.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

Names an upstream provider: AWS.

1. resolved 2026-10-09 08:30 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...

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Affected: GCP US Central - prod-us-central-0, GCP US Central - prod-us-central-5, GCP US Central - prod-us-central-0: Ingestion, GCP US Central - prod-us-central-5: Ingestion, GCP US Central - prod-us-central-0: Ingestion

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

Names an upstream provider: Google Cloud.

Started during Google Cloud: Google Cloud Storage (GCS) customers experienced elevated latencies and error rates when performing upload or write operations..

1. investigating 2026-10-08 13:06 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...

2. investigating 2026-10-08 13:25 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...

3. investigating 2026-10-08 13:39 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...

4. investigating 2026-10-08 13:52 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...

5. investigating 2026-10-08 14:40 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...

6. investigating 2026-10-08 15:19 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...

7. investigating 2026-10-08 16:21 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 2026-10-08 17:30 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...

9. investigating 2026-10-08 18:15 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...

10. investigating 2026-10-08 19:13 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...

11. investigating 2026-10-08 20:41 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...

12. investigating 2026-10-08 21:42 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...

13. resolved 2026-10-09 00:39 UTC

    This incident has been resolved

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-10-07 08:40 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.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Affected: Incident Management and Response (IRM)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-10-05 16:17 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...

2. identified 2026-10-05 21:47 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 2026-10-06 13:42 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...

4. identified 2026-10-09 12:51 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 2026-10-13 21:35 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 2026-10-15 09:33 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...

7. identified 2026-10-16 15:20 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...

8. resolved 2026-10-19 11:40 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...

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Affected: AWS Germany - prod-eu-west-2, AWS Germany - prod-eu-west-4, AWS US East (OH) - prod-us-east-2, GCP Australia - prod-au-southeast-0, GCP US Central - prod-us-central-4

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-10-04 18:20 UTC

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

2. resolved 2026-10-04 18:33 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.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

Names an upstream provider: Google Cloud.

1. investigating 2026-10-03 13:53 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 2026-10-03 13:54 UTC

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

3. monitoring 2026-10-03 15:07 UTC

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

4. resolved 2026-10-03 19:43 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.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

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

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

Names an upstream provider: Azure.

1. investigating 2026-10-02 10:03 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 11:30 UTC.

2. investigating 2026-10-02 11:06 UTC

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

3. identified 2026-10-02 14:02 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 2026-10-02 14:03 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.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Affected: AWS US East (VA) - prod-us-east-3

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

Names an upstream provider: AWS.

1. investigating 2026-09-30 12:40 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...

2. investigating 2026-09-30 13:40 UTC

   We are continuing to investigate this issue.

3. identified 2026-09-30 13:43 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 2026-09-30 14:31 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 2026-09-30 15:39 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.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Affected: AWS US East (VA) - prod-us-east-3

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-09-28 17:32 UTC

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

2. investigating 2026-09-28 18:00 UTC

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

3. identified 2026-09-28 18:38 UTC

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

4. resolved 2026-09-28 19:21 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

Names an upstream provider: Azure.

1. resolved 2026-09-28 12:02 UTC

   Between 09:39 and 10:03 UTC on September 28, 2026, some Grafana Cloud Logs customers in Azure Netherlands (EU) experienced intermittent errors sending log data, in two brief periods totaling approximately 14 minutes. This has been fully resolved and log ingestion is operating...

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Affected: Integrations

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

Names an upstream provider: Azure.

1. investigating 2026-09-26 02:11 UTC

   Since approximately 00:19Z there has been an increase in errors returning metrics from Azure's germanywestcentral. We are currently investigating this issue.

2. monitoring 2026-09-26 02:33 UTC

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

3. resolved 2026-09-26 03:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Affected: Cost Management and Billing

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-09-22 21:27 UTC

   Some customers may see a sudden spike in reported Kubernetes Observability usage even if they haven't activated the product. We are investigating the root cause, and will ensure the amount is corrected before any usage is invoiced.

2. monitoring 2026-09-22 23:10 UTC

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

3. resolved 2026-09-23 14:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Affected: Incident Management and Response (IRM)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-09-22 14:57 UTC

   We are currently investigating an issue that may cause a small group of users to experience unexpected IRM access issues, or undelivered pages. Most users should not be affected.

2. identified 2026-09-22 15:55 UTC

   The issue has been identified, and we are working on a fix.

3. monitoring 2026-09-22 17:19 UTC

   A fix is currently being rolled out and will be deployed progressively over the next few hours. We appreciate your patience as this reaches all affected customers.

4. monitoring 2026-09-22 18:57 UTC

   The fix has been deployed to the majority of deployments. We continue to monitor progress.

5. resolved 2026-09-23 11:07 UTC

   Between 14:57 UTC on 22 September and 09:00 UTC on 23 September, a small group of users experienced unexpected access issues and undelivered pages in Grafana IRM. This has been fully resolved and all affected users should now have normal access. Thank you for your patience.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-21 18:00 UTC

   There was an impact of increased 5xx on writes with metrics. The error rates have returned back to normal, and our team is continuing to investigate the cause.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Affected: AWS Australia - prod-au-southeast-1: Public Probes, AWS Brazil - prod-sa-east-1: Public Probes, AWS Canada - prod-ca-east-0: Public Probes, AWS Germany - prod-eu-west-2: Public Probes, AWS India - prod-ap-south-1: Public Probes, AWS Japan - prod-ap-northeast-0: Public Probes, AWS Singapore - prod-ap-southeast-1: Public Probes, AWS Sweden - prod-eu-north-0: Public Probes, AWS US East - prod-us-east-0: Public Probes, AWS US East - prod-us-east-3: Public Probes, AWS US West - prod-us-west-0: Public Probes, Azure Netherlands - prod-eu-west-3: Public Probes, Azure US Central - prod-us-central2: Public Probes, Azure US Central - prod-us-central7: Public Probes, GCP Australia - prod-au-southeast-0: Public Probes, GCP Belgium - prod-eu-west-0: Public Probes, GCP Brazil - prod-sa-east-0: Public Probes, GCP India - prod-ap-south-0: Public Probes, GCP Singapore - prod-ap-southeast-0: Public Probes, GCP UK - prod-gb-south-0: Public Probes, GCP US Central - prod-us-central-0: Public Probes, AWS UAE - prod-me-central-1: Public Probes, AWS UK - prod-gb-south-1: Public Probes, AWS Switzerland - prod-eu-central-0: Public Probes, AWS Indonesia - prod-ap-southeast-2: Public Probes, AWS Ireland - prod-eu-west-6: Public Probes, GCP Saudi Arabia - prod-me-central-0: Public Probes, GCP US East - prod-us-east-1: Public Probes

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. identified 2026-09-15 10:00 UTC

   Since September 9, 2026, some browser checks in Synthetic Monitoring may take longer to complete than usual, with impact varying by location. We have identified the cause and are actively working on a fix. Next update by 10:49 UTC.

2. identified 2026-09-15 10:51 UTC

   A fix has been merged and is now being rolled out across affected locations. We are monitoring deployment progress. Next update by 11:49 UTC.

3. monitoring 2026-09-15 10:58 UTC

   A fix has been deployed and CPU throttling is returning to normal. Check execution times should return to baseline shortly. We will continue monitoring recovery. Next update by 11:56 UTC.

4. resolved 2026-09-15 11:17 UTC

   Between September 9 and September 15, 2026, some browser checks in Synthetic Monitoring experienced longer than usual execution times, with impact varying by location. This has been resolved and check execution times have returned to baseline. Thank you for your patience.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

Names an upstream provider: Google Cloud.

1. resolved 2026-09-14 15:30 UTC

   Between 15:31 and 20:43 UTC on September 14, 2026 (approximately 5 hours 12 minutes), some customers in GCP US Central (prod-us-central-0) may have experienced intermittent errors or delays when writing metrics. This has been fully resolved and all services are operating...

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-09-14 12:00 UTC

   Some customers experienced timeouts affecting CloudWatch traffic in prod-us-central-0 for approximately one hour. Service has since been restored. This incident did not affect all customers. We are publishing this update retrospectively and apologise for the disruption.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

Names an upstream provider: Google Cloud.

1. resolved 2026-09-14 03:30 UTC

   Between 03:30 UTC on September 14, 2026 and 10:50 UTC on September 17, 2026 (approximately 3 days), customers managing cloud provider integrations in GCP US Central may have experienced elevated latency when creating, viewing, or removing integrations. This has been fully...

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: A configuration change caused the failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

Names an upstream provider: AWS.

1. resolved 2026-09-12 23:00 UTC

   Between approximately 23:00 UTC on September 12, 2026 and 09:12 UTC on September 14, 2026, some Grafana Cloud Logs customers in AWS Sweden (prod-eu-north-0) may have intermittently experienced errors when submitting configuration changes through the Cloud Portal. This has been...

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Affected: AWS Germany - prod-eu-west-4

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

Names an upstream provider: AWS.

1. investigating 2026-09-09 11:27 UTC

   We are investigating elevated database load affecting infrastructure supporting a subset of Grafana Cloud instances in the AWS Germany region (prod-eu-west-4). Affected users may experience slow responses when accessing Grafana. We will provide an update as more information...

2. monitoring 2026-09-09 12:44 UTC

   A fix has been implemented and we have been seeing recovery to the affected region. We will continue to monitor.

3. resolved 2026-09-09 13:51 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Affected: AWS Australia - prod-au-southeast-1, AWS Australia - prod-au-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 Ireland - prod-eu-west-6, AWS Japan - prod-ap-northeast-0, AWS Singapore - prod-ap-southeast-1, AWS Sweden - prod-eu-north-0, AWS Switzerland - prod-eu-central-0, AWS UAE - prod-me-central-1, AWS UK - prod-gb-south-1, AWS US East (OH) - prod-us-east-0, AWS US East (OH) - prod-us-east-2, AWS US West - prod-us-west-0, AWS US East (VA) - prod-us-east-3, Azure US Central - us-central2, 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 Saudi Arabia - prod-me-central-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

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. identified 2026-09-08 18:05 UTC

   Some geomap tiles are displaying the “api key required". The issue has been identified, and our team is working on a fix. As a workaround, you can open the Geomap panel, navigate to the Map layers section, and change the Basemap layer from CARTO, or "Default base layer," to...

2. resolved 2026-09-08 22:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Affected: AWS US East (OH) - prod-us-east-2

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-09-08 16:14 UTC

   We are currently investigating an issue causing high latency for deployments in the prod-us-east-2 cluster.

2. monitoring 2026-09-08 17:04 UTC

   We have observed latency return to normal levels, and we will continue to monitor this incident.

3. resolved 2026-09-08 20:34 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Affected: GCP US Central - prod-us-central-0, GCP US Central - prod-us-central-3, GCP US Central - prod-us-central-4

Failure mode: A zone, region or data center became unavailable. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. identified 2026-09-04 17:03 UTC

   We are aware of an issue causing some Grafana Cloud stacks in the US region to be unavailable or fail to load. The cause is reduced compute capacity in one of our cloud provider's availability zones, which is preventing affected stacks from starting. Other regions are...

2. monitoring 2026-09-04 18:24 UTC

   We are currently observing minimal impact and continuing to monitor the situation.

3. resolved 2026-09-04 20:42 UTC

   The US Central region is now fully operational and this incident is now resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Affected: 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, GCP US Central - prod-us-central-0: Querying, GCP US Central - prod-us-central-0: Ingestion, GCP US Central - prod-us-central-0: Metrics Generator, GCP US Central - prod-us-central-5: Querying, GCP US Central - prod-us-central-5: Ingestion

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. identified 2026-09-04 16:45 UTC

   We’re currently investigating an issue affecting the us central region due to ongoing cloud provider incident. Multiple components impacted. Our team is actively working on this. Thank you for your patience.

2. monitoring 2026-09-04 18:58 UTC

   The underlying cloud provider issue is not yet fully resolved, but our systems have recovered and affected Grafana Cloud stacks are loading normally again. Some customers may still see brief intermittent slowness. We are continuing to monitor until our provider confirms...

3. resolved 2026-09-04 23:00 UTC

   The US Central region is fully recovered now and the issue is now resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Affected: AWS US East (OH) - prod-us-east-0: Alertmanager and Rules Configuration API, AWS US East (OH) - prod-us-east-0: Alertmanager

Failure mode: The text does not say enough to tell. Root cause: A bug in the vendor's own code. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-09-04 13:36 UTC

   We’re currently investigating an issue affecting alert rule creation, deletion, and updates in prod-us-east-2. Our team is actively working to identify the cause. Thank you for your patience.

2. resolved 2026-09-04 16:32 UTC

   The issue has been mitigated and there's a code fix pending.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Affected: AWS US West - prod-us-west-0: Querying, AWS US West - prod-us-west-0: Ingestion, AWS US West - prod-us-west-0: Querying, AWS US West - prod-us-west-0: Ingestion

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. identified 2026-09-03 22:13 UTC

   The issue has been identified and a fix is being implemented.

2. identified 2026-09-03 22:31 UTC

   Cluster Metrics are healthy for the last 15 minutes

3. monitoring 2026-09-03 22:48 UTC

   Tempo recovered.

4. resolved 2026-09-04 00:55 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-09-03 09:32 UTC

   We are currently investigating an issue impacting deployments in prod-ap-south-1. Impacted customers may be experiencing increased latency and issues with ingestion.

2. monitoring 2026-09-03 11:37 UTC

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

3. resolved 2026-09-03 12:49 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-09-02 14:14 UTC

   We observed elevated latency in Grafana Cloud Logs between 08:00 and 11:00 UTC for a subset of deployments in prod-ap-south-1. The issue is now resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-09-01 15:25 UTC

   We are investigating reports of errors affecting Grafana Cloud in US Central (prod-us-central-0, prod-us-central-5). Customers in this region may see timeouts or failed requests when writing or querying logs and metrics. We are looking into this and will post another update as...

2. identified 2026-09-01 16:14 UTC

   We have identified the cause as an issue in our cloud provider’s US Central region. A mitigation is in place and recovery is in progress. Customers in prod-us-central-0 and prod-us-central-5 may still see errors or delays with metrics, logs, or Grafana while services come back....

3. resolved 2026-09-01 20:20 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Affected: AWS US East (VA) - prod-us-east-3

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. identified 2026-08-28 17:12 UTC

   We’ve identified the cause of an issue impacting Log writes. Our team is currently implementing a fix.

2. monitoring 2026-08-28 17:55 UTC

   This incident also had impact on Frontend Observability for the same region. A fix has been deployed, and things have stablized. We will continue to monitor on our end.

3. resolved 2026-08-28 18:42 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. identified 2026-08-28 00:58 UTC

   Some Grafana UI features may be unavailable or reverting to legacy behaviour

2. identified 2026-08-28 01:08 UTC

   a resolution is rolling out to resolve the issues

3. resolved 2026-08-28 02:40 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-08-27 12:09 UTC

   We are investigating elevated error rates affecting metrics writes in prod-us-central-0. Customers in this region may see failed or delayed metrics ingestion, gaps in recent data on dashboards and queries, and alert rules that depend on the affected series may not evaluate as...

2. monitoring 2026-08-27 12:37 UTC

   A fix has been applied and metrics write error rates in prod-us-central-0 have returned to normal levels. Metrics ingestion is operating as expected. We are continuing to monitor the affected systems to confirm full recovery before marking this incident resolved.

3. resolved 2026-08-27 13:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-27 01:54 UTC

   Mimir writes in the prod-us-central-0 region had elevated error rates for approximately 15 minutes from 1:05 to 1:20 UTC. The issue has been resolved and we are monitoring.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Affected: Incident Management and Response (IRM)

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-08-25 10:39 UTC

   We are investigating an outage affecting Grafana Incident in the US Central region (prod-us-central-0). Customers are unable to create, view, or query Incidents, and requests to the Incident public API are timing out. All customers in this region are affected. Grafana OnCall is...

2. monitoring 2026-08-25 10:49 UTC

   A fix has been applied and Incident Management in US Central is recovering. The Incident public API is responding normally, and customers can create, view, and query Incidents again. We are continuing to monitor the recovery to confirm the service is fully stable.

3. monitoring 2026-08-25 11:01 UTC

   We are continuing to monitor for any further issues.

4. resolved 2026-08-25 11:02 UTC

   This incident has been resolved. Incident Management in US Central is operating as normal. Customers can create, view, and query Incidents, and the Incident public API is fully available. Grafana OnCall was not affected at any point during this incident.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-18 22:00 UTC

   We observed an issue which impacted the following service: reads of Cloud Logs in the eu-west-2 region. Affected services would include Explore, dashboards, alert evaluation when querying Logs. The time of impact lasted from approximately 22h15 and 22h23 UTC, on loki-prod-012....

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-08-13 16:47 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: Network or DNS. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-08-10 13:30 UTC

   Between 12:20 and 13:15 UTC, we experienced elevated error rates for metrics reads and writes due to a networking issue. Impact was limited to a subset of deployments in the prod-us-central-0 region. A fix has been applied and error rates have since recovered.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-08-08 19:48 UTC

   Due to a software bug the evaluation of some alert rules (primarily ones that have recovery threshold setting) were failing to be evaluated starting 14:00 UTC to 19:30 UTC today.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-08-05 17:57 UTC

   Between approximately 13:40 and 15:05 UTC today, a subset of cloud test runs were unexpectedly terminated and marked Aborted (by system). This affected runs that were in progress during three short windows in that period; test results and metrics for completed runs were not...

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-08-05 11:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-05 01:32 UTC

   We are observing a continued period of stability and at this point, we are marking the incident resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-04 13:49 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-01 08:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-31 19:30 UTC

   We are investigating a partial read outage affecting Loki in prod-us-east-4. Between 19:41 UTC and 19:50 UTC, a significant portion of read queries may have failed or returned errors. The issue has been identified and service has been restored. We are continuing to investigate...

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-31 12:13 UTC

   He have identified the cause and applied a fix for this issue and all effected stacks within the affected regions are not working as expected.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-30 17:40 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-30 15:17 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-30 00:39 UTC

   The issue affecting Grafana IRM in the EU region has been resolved. The IRM UI, public API, and alert notification processing have been restored and are operating normally.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-07-29 18:49 UTC

   Impact period: April 1 – July 29, 2026 Summary: During this period, some customers in a subset of regions may have experienced gaps in select ruler/recording rule metrics within their Grafana Cloud instances. Not all customers or environments in the listed regions were affected....

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-28 19:43 UTC

   The issue affecting OTLP ingestion in the prod-us-east-3 region has been resolved. Between 13:30 UTC and 17:45 UTC, some customers experienced intermittent failures when writing telemetry to the OTLP endpoint. Logs were confirmed to be affected, and metrics and traces may also...

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-24 18:20 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-24 14:03 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-24 05:32 UTC

   Writes are looking stable in the last 6h

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-23 19:47 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-07-23 15:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-07-22 11:25 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-21 21:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-20 15:03 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-07-18 13:15 UTC

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

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-16 14:58 UTC

   The incident is now fully resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-15 23:36 UTC

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

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-16 03:54 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-15 21:00 UTC

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

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-15 13:54 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...

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-14 22:00 UTC

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

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-14 19:03 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-07-20 10:15 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.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-07-10 21:31 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...

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-07-13 13:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-13 05:23 UTC

   At this stage, we are considering the incident resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-09 19:54 UTC

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

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-09 13:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-07-09 07:37 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.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-07-08 15:33 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.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-08 17:23 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-07-08 11:00 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.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-07-07 13:44 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...

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-06 07:37 UTC

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

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-03 14:27 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.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-02 21:35 UTC

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

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-07-02 06:49 UTC

   This incident has been resolved by restarting the affected services.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-01 22:00 UTC

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

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-06-29 14:27 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-06-30 08:20 UTC

   Since the mitigation has been applied, we have not seen the errors return. At this point, we are considering the incident resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-06-29 13:12 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-06-28 02:35 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-06-20 20:00 UTC

   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....

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-06-19 19:19 UTC

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

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-06-18 18:50 UTC

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

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-06-24 12:46 UTC

   This incident has been resolved. Error rates continued to remain near 0 and operations are performing as expected.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-06-18 16:21 UTC

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

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-06-18 10:13 UTC

   A fix has been deployed and the issue after monitoring as been fixed.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-06-18 14:08 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-06-12 18:30 UTC

   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.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-06-11 05:36 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-06-10 13:11 UTC

   We continue to observe a continued period of recovery. At this time, we are considering this issue resolved. No further updates.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-06-08 20:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-06-12 19:52 UTC

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

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-06-05 21:35 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-06-05 15:01 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-06-04 18:28 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-06-04 05:47 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-06-03 18:22 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-06-03 07:46 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-06-01 20:26 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-05-29 10:59 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-05-27 22:59 UTC

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

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-05-18 15:42 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-05-14 07:06 UTC

   We continue to observe an extended period of recovery and we're marking the incident as resolved at this point in time.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-05-12 16:35 UTC

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

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-05-11 22:40 UTC

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

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-05-08 22:30 UTC

   We have continued to observe stability. This incident is now being considered as resolved. Thank you for your patience.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-05-07 07:56 UTC

   At this time, we have confirmed that the query errors have gone and we are considering this issue resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-05-06 05:30 UTC

   We observed an underlying hardware failure on our CSP which triggered an automatic live VM migration. The situation caused a degradation in write performance for Grafana Cloud Metrics on prod-us-west-0 between 05:26 UTC and 05:43 UTC

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-05-05 20:13 UTC

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

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-05-05 02:09 UTC

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

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Names an upstream provider: AWS.

1. resolved 2026-05-01 10:27 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-04-29 12:00 UTC

   We experienced degraded performance affecting Performance Testing from 13:10 UTC to 13:20 UTC. During this time, users may not have been able to start new test runs. The issue has been resolved, and the service is now operating normally. We apologize for any disruption this may...

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Names an upstream provider: AWS.

1. resolved 2026-04-29 10:30 UTC

   We were facing an incident with AWS Metrics Streaming integration in us-east-3 region manifesting in elevated ingestion latency. The incident started at around 10:45 UTC and was resolved at around 12:30 UTC. Some tenants could see an elevated write latency, but all requests were...

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-04-29 13:37 UTC

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

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-04-30 15:11 UTC

   After further review, this was a false alarm and should not have affected any users. This incident has been resolved. Thank you for your patience.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-04-27 23:24 UTC

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

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-04-23 20:01 UTC

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

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-04-24 15:04 UTC

   Grafana Labs has taken steps to safeguard the Grafana Cloud platform against the distribution of unauthorized emails. We have implemented the following changes to new Grafana Cloud Free and Trial accounts, effective immediately: Users who open Grafana Cloud Free and Trial...

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-04-20 14:30 UTC

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

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-04-17 22:58 UTC

   This incident has been resolved

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-04-16 14:02 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-04-15 16:25 UTC

   This incident has been resolved and our ticketing system is fully operational. Thank you for your patience.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-04-14 11:30 UTC

   Between approximately 12:30 UTC and 13:15 UTC, k6 Cloud experienced a service disruption due to issues introduced in a recent API release. During this time, users were unable to access the k6 Cloud application. The issue was mitigated by reverting the release, and service has...

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-04-15 12:59 UTC

   This incident is now resolved. We had intermediary issues with a flaky DNS server that caused random tests to not start properly. Since the DNS server was fixed, we haven't been seeing the issue anymore.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-04-13 11:30 UTC

   There was a period of write instability yesterday. It was between ~1330 -1730 UTC yesterday. This was due to a scheduled maintenance.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-04-11 00:36 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-04-10 21:02 UTC

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

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-04-09 18:50 UTC

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

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-04-08 17:00 UTC

   We had a stability issue for a subset of customers in the prod-gb-south-1 region. The impact was between UTC 15:20-16:30 which impacted roughly 30% of queries and rules evaluations. We've applied mitigations, queries should be back to normal.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-04-07 20:17 UTC

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

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-04-07 12:26 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-04-03 17:38 UTC

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

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Names an upstream provider: AWS.

1. resolved 2026-04-01 21:03 UTC

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

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-04-01 21:13 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-03-31 14:59 UTC

   From approximately 11:00 UTC - 15:00 UTC we had a degradation that caused test start errors for a large percentage of Cloud runs managed as scripts in the GCK6 app. This has since been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-03-31 14:32 UTC

   This is a retroactive status page linked to the following incident: https://status.grafana.com/incidents/38wwbz50ggrp This retroactive status page is meant to clarify the time of impact. This issue first started at ~2026-03-30 18:00 UTC. This is now resolved

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-03-31 14:25 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-03-31 10:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-03-30 16:30 UTC

   We encountered an issue impacting only a small subset of customers in the prod-us-central-0 region. The incident occurred between 16:20 and 17:50 UTC on 3/30/26. This incident is now resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-03-27 20:48 UTC

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

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-04-23 20:07 UTC

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

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Names an upstream provider: AWS, Google Cloud.

1. resolved 2026-03-24 14:00 UTC

   An issue affecting Grafana Cloud instances was diagnosed yesterday 24th of March that avoided Dashboards to be loaded correctly. The incident impacted the following clusters: - GCP US Central (us-central-0) between 13:15 and 13:50 UTC - AWS US East (us-east-0) between 13:43 and...

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-03-25 12:52 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-03-23 18:48 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-03-20 15:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-03-19 18:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-03-19 18:11 UTC

   Our engineering team has deployed a fix and we continue to observe a continued period of recovery. At this time, we are considering this issue resolved. No further updates.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Names an upstream provider: Azure.

1. resolved 2026-03-18 07:13 UTC

   We have been observing stability for a period of time and will mark the incident as resolved at this time.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-03-13 18:11 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-03-13 18:15 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Names an upstream provider: Azure.

1. resolved 2026-03-12 13:18 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-03-10 19:17 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-03-11 21:48 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Names an upstream provider: AWS.

1. resolved 2026-03-10 20:39 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-03-10 21:17 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-03-10 20:54 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Names an upstream provider: AWS.

1. resolved 2026-03-08 20:31 UTC

   We continue to observe a continued period of stability since 19:40 UTC. At this time, we are considering this issue resolved

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Names an upstream provider: AWS.

1. resolved 2026-03-09 08:59 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-03-06 16:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-03-05 23:36 UTC

   We continue to observe a continued period of recovery. At this time, we are considering this issue resolved. No further updates.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-03-04 09:29 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-03-03 13:00 UTC

   Test run browser screenshot upload experienced failures from 13:12 to 14:51 UTC. The issue has been resolved

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Names an upstream provider: Azure.

1. resolved 2026-03-05 18:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-03-02 15:48 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Names an upstream provider: AWS.

Started during AWS: Multiple services (Bahrain): Region Availability.

Started during AWS: Multiple services (UAE): Region Availability.

1. resolved 2026-06-17 09:58 UTC

   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...

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-02-27 16:25 UTC

   A recent rollout caused the AuthZ (RBAC) service to perform many redundant folder-tree fetches for each authorization check. For a small number of tenants in the prod-us-east-0 and prod-eu-west-2 regions with very large folder trees. This added a few milliseconds to every check,...

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-02-27 23:38 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-02-27 15:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-02-27 02:49 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-03-17 18:22 UTC

   This incident is now resolved. During the incident the Cloud Metrics platform experienced intermittent latency spikes communicating with a backend cloud service in the prod-us-central-0 and prod-us-central-5 regions. During the incident the internal CSP-facing issue was...

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-02-25 19:51 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-02-25 17:20 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Names an upstream provider: AWS.

1. resolved 2026-02-25 15:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-02-24 17:09 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Names an upstream provider: Azure.

1. resolved 2026-02-18 14:00 UTC

   We experienced an issue impacting a cell within the Azure prod-us-central-7 region, which occurred between 14:26 and 14:36. Affected users may have noticed increased errors with rule evaluations, as well as a some read/write errors. We have resolved this issue, and will continue...

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-02-18 21:17 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-02-18 05:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-02-17 16:27 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Names an upstream provider: AWS.

1. resolved 2026-02-17 12:47 UTC

   There was a service degradation today from ~12:09 UTC until ~12:35 UTC on the Public Probe of Calgary for Synthetic Monitoring. Impact may include SM check fails where the probe was used.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-02-13 19:08 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-02-13 07:29 UTC

   We continue to observe a continued period of recovery. At this time, we are considering this issue resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-02-13 17:03 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-02-12 14:30 UTC

   We no longer observed any problems with our services - this incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-02-11 21:47 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-02-11 07:25 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-02-10 01:45 UTC

   We continue to observe a continued period of recovery. At this time, we are considering this issue resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-02-09 19:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-02-09 11:21 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-02-06 17:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-02-05 18:30 UTC

   Between 18:32 and 18:46 UTC, Grafana Cloud Metrics within a single cell residing in the prod-us-west-0 region experienced an issue affecting write ingestion only. During this time, some metric writes may have failed or been delayed. Metric reads were not impacted and remained...

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-02-05 18:00 UTC

   From 17:43 UTC to 18:05 UTC, a subset of customers experienced elevated latency and a peak error rate of approximately 22% for trace ingestion.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-02-05 17:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-02-05 15:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-02-04 14:14 UTC

   The HTTP Response time in the Performance trend overview did not show for new test-runs. After the fix, all data should show again.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-02-03 17:56 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-01-28 20:25 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-01-28 00:22 UTC

   We continue to observe a continued period of recovery. At this time, we are considering this issue resolved. No further updates.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-01-27 11:14 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-01-27 07:49 UTC

   We were experiencing increased write error rate for logs in prod-us-west-0 from 6:55 to 7:15 UTC. We have since observed continued stability and are marking this as resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-01-27 00:13 UTC

   Engineering has released a fix and as of 00:13 UTC, customers should no longer experience issues upgrading from Free to Pro subscriptions. At this time, we are considering this issue resolved. No further updates.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-01-23 18:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-01-22 22:29 UTC

   The incident is resolved. We are in contact with customers affected by this change.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-01-21 15:21 UTC

   We consider this incident as resolved since the latency hasn't been elevated since the fix was applied. The issue was caused by a latency spike in a downstream dependency, causing an increased backpressure on the Hosted Traces ingestion path, which degraded gateway performance...

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-01-19 14:30 UTC

   Impact: Between 14:30 and 14:38 UTC, some customers in prod-eu-west-2 may have experienced issues querying metrics. During this time, read requests to the metrics backend were unavailable, resulting in failed or incomplete query responses. The root cause of the issue was...

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Names an upstream provider: AWS.

1. resolved 2026-01-19 01:21 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Names an upstream provider: AWS.

1. resolved 2026-01-17 09:04 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-01-16 04:00 UTC

   This incident has been resolved. Both read and write 5xx's and increased latency were experienced in the two periods: 23:56:15 to 00:32:45 UTC 00:55:30 to 01:36:15 UTC

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Names an upstream provider: Azure.

1. resolved 2026-01-14 20:17 UTC

   The scope of this incident was smaller than originally anticipated. As of 16:27 UTC our engineering team merged a fix for those affected and we are considering this as resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-01-12 18:21 UTC

   We continue to observe a continued period of recovery. At this time, we are considering this issue resolved. No further updates.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-01-12 15:26 UTC

   Engineering has released a fix and we continue to observe a period of recovery. As of 15:12 UTC we are considering this resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-01-09 20:30 UTC

   Between 20:23 UTC and 20:53 UTC, Grafana Cloud Logs in prod-us-east-3 experienced a write degradation, which may have resulted in delayed or failed log ingestion for some customers. The issue has been fully resolved, and the cell is currently operating normally. We are...

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-01-07 17:41 UTC

   There was a ~15 minute partial write outage for some customers in prod-us-central-0. The time frame for this outage was 15:43-15:57 UTC.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-01-06 20:26 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Names an upstream provider: Cloudflare.

1. resolved 2026-01-06 15:09 UTC

   From 20:32 to 20:37 UTC, a DNS record misconfiguration resulted in temporary Cloudflare 1016 DNS errors on many Grafana Cloud stacks. The misconfiguration was mitigated within 5 minutes, and we are working with Cloudflare to better understand why the particular misconfiguration...

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2026-01-02 13:38 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-12-23 21:59 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-12-19 16:50 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Names an upstream provider: Google Cloud.

1. resolved 2025-12-17 13:02 UTC

   Today 17th from 10:00 UTC to 10:38 UTC we experienced logs write path degradation. Customers may have experienced 5xx errors while ingestion on that cluster. Service is fully restored.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Names an upstream provider: Google Cloud.

1. resolved 2025-12-16 12:51 UTC

   Due to an incident today in IRM (OnCall) product, access to this application was degraded from 10:39 UTC until 11:16. Customers may have experienced the app not operable or not accessible. The service is again fully restored.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-12-16 10:42 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-12-12 14:38 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-12-11 23:17 UTC

   We continue to observe a continued period of recovery. At this time, we are considering this issue resolved. No further updates.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-12-10 19:30 UTC

   Users experienced failed log pushes as well as increased latency when sending logs to Loki service hosted on prod-eu-west-0 cluster between 18:30 UTC to ~23:00 UTC. Our engineering team has engaged our Cloud Service Provider and the fix was implemented that mitigated the issue.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-12-10 23:05 UTC

   We continue to observe a continued period of recovery. At this time, we are considering this issue resolved. No further updates.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-12-10 09:06 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Names an upstream provider: AWS.

1. resolved 2025-12-09 13:10 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Names an upstream provider: Cloudflare.

1. resolved 2025-12-05 09:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-12-01 08:00 UTC

   Loki prod-ap-northeast-0-loki-prod-030 cell had writes degradation between 8:11 - 8:58 AM UTC. The engineering team mitigated the situation and the cell is stable now.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-11-27 18:27 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-11-24 11:49 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-11-22 17:06 UTC

   We continue to observe a continued period of recovery. At this time, we are considering this issue resolved. No further updates.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-11-21 15:38 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-11-21 14:52 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-11-20 18:47 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-11-19 21:00 UTC

   We are experiencing issues starting cloud test runs. This is primarily affecting browser test runs and test runs using static IPs.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-11-19 06:20 UTC

   An incident has impacted Loki billing metrics from 05:30 to 06:10 UTC across all clusters. This is currently resolved, however, users may notice some billing metrics missing from the billing dashboard during this time period. There is no impact of logs querying or ingestion.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Names an upstream provider: Cloudflare.

1. resolved 2025-11-18 17:34 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-11-18 00:10 UTC

   We continue to observe a continued period of recovery. As of 00:08 UTC, we are considering this issue resolved. No further updates.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-11-17 23:08 UTC

   As of 23:07 UTC we are considering this incident as resolved. Mitigation efforts have restored normal write performance, and error rates have returned to expected levels. We have confirmed stability across the affected areas and continue to monitor, but no further impact is...

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-11-17 19:01 UTC

   We experienced degraded service with the Hyderabad probe today around 13:20 UTC which was resolved as of 17:30 UTC.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-11-18 07:26 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-11-17 12:23 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-11-17 04:55 UTC

   resolved since 03:02UTC

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-11-12 16:50 UTC

   Spanning from November 10th, 18:00 UTC to November 11th, 22:00 UTC, Synthetic Monitoring experienced degraded browser check performance due to a faulty release that has been rolled back. This impacted all regions, specifically the probes. The API itself experienced no issues.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-11-05 14:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-11-04 19:27 UTC

   Test runs are now working as expected. The duration of this incident was roughly 30 minutes. The test runs were not able to start, and the app and the API were not accessible.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-11-04 17:39 UTC

   The incident is resolved as of 14:35 UTC.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-11-03 15:04 UTC

   From Oct 31st 17:40 UTC to Nov 3rd 14:50 UTC: Due to some internal auth issues, the components evaluating loki-managed rules failed to push the evaluated recording and alert rules to the metrics endpoint for some tenants.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-11-03 14:13 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-10-31 15:30 UTC

   From approximately 16:30-8:15 UTC, a configuration change inadvertently removed a required headless service for hosted traces in one of our production regions. This caused elevated error rates and increased service-level objective (SLO) burn for the trace ingestion pathway. The...

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-10-31 15:04 UTC

   The issue affecting Tempo (prod-us-east-0 & prod-us-west-0) and Loki (prod-us-central-5) has been fully resolved. Metrics generation is now operating normally across all regions, and we continue to monitor for stability.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-10-31 13:49 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-10-30 13:36 UTC

   We consider the incident as resolved now. With regards to the cause - a slow physical partition of the backend database, which is used by the control plane of a critical component caused increased latency and occasional overloading with subsequent failing of the write path. Once...

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-10-29 20:13 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-10-25 06:56 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-10-24 17:15 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-10-23 22:36 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-10-22 12:48 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-10-21 16:42 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-10-20 22:12 UTC

   Engineering has released a fix and as of 21:25 UTC, customers should no longer experience query performance issues. At this time, we are considering this issue resolved. No further updates.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Names an upstream provider: AWS.

1. resolved 2025-10-20 20:23 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Names an upstream provider: AWS.

1. resolved 2025-10-20 20:28 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-10-20 14:00 UTC

   Between ~13:10 UTC and 21:20 UTC on October 20th, 2025, Span Metrics were unavailable in a single cell. During this period, users may have seen missing or stale data in span metrics dashboards and alerts. Trace ingestion and querying were not affected, and no trace data was...

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-10-20 10:53 UTC

   We can confirm full recovery on our Grafana hosted services (since ~9:50 UTC), we have continued monitoring them to ensure no further impact is experienced.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-10-15 10:12 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-10-13 23:35 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-10-13 14:21 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-10-10 13:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Names an upstream provider: AWS.

1. resolved 2025-10-08 19:02 UTC

   Engineering has released a fix and as of 18:45 UTC, customers should no longer experience issues seeing new log lines from the integration. We continued to monitor and are considering this incident resolved at this time.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-10-08 17:01 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-10-07 17:14 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-10-05 13:37 UTC

   We continue to observe a period of recovery. At this time, we are considering this issue resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-10-02 16:09 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-10-02 08:39 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-10-01 10:30 UTC

   From 10:30 UTC until 11:00 UTC, some customers may have experienced errors while accessing Grafana dashboards and folders. We anticipate that this had some degree of impact in all regions.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-09-26 14:29 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Names an upstream provider: Google Cloud.

1. resolved 2025-09-24 21:06 UTC

   We continue to observe a continued period of recovery. At this time, we are considering this issue resolved. No further updates.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-09-24 13:20 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-09-18 18:51 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Names an upstream provider: Azure.

1. resolved 2025-09-18 07:17 UTC

   From 11:00 UTC to 22:09 UTC, customers of Mimir and Tempo using Azure PrivateLink were unable to access services and received 503 errors. This happened because part of our traffic routing setup was unintentionally shut down too early. Once identified, we restored the service and...

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-09-16 21:16 UTC

   The incident is resolved, API in us-central2 is available again as of 21:01 UTC

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-09-16 17:21 UTC

   There were read and write outages in the us-central2 region for Loki from 16:57 to 17:04 UTC. The issue is now resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-09-15 18:17 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-09-15 16:27 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-09-13 00:01 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-09-11 17:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-09-10 22:13 UTC

   We continue to observe a period of stability. At this time, we are considering this issue resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-09-11 11:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-09-02 13:53 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-09-03 18:51 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-09-01 03:07 UTC

   This incident has been resolved as of 03:05 UTC.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-08-28 20:42 UTC

   Engineering has released a fix and as of 20:30 UTC, customers should no longer experience performance issues for Loki queries. At this time, we are considering this issue resolved. No further updates.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-08-28 18:53 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-08-26 12:05 UTC

   We experienced degraded performance on the writing path for traces, today between 9:49 and 11:36 UTC, on prod-eu-west-2 cluster. The issue has been resolved and the service should be back to normal

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-08-25 22:55 UTC

   Our engineering team has applied a fix for this issue and Hosted Grafana instances should be loading normally again at this time.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-08-23 14:10 UTC

   We continue to observe a continued period of recovery. At this time, we are considering this issue resolved. No further updates.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-08-22 16:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-08-22 21:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-08-22 01:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-08-29 13:21 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-08-18 18:34 UTC

   We continue to observe a continued period of recovery. At this time, we are considering this issue resolved. No further updates.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-08-18 18:44 UTC

   We continue to observe a continued period of recovery. At this time, we are considering this issue resolved. No further updates.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-08-15 01:21 UTC

   As of this time, we are considering this incident resolved. No further updates.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-08-13 13:00 UTC

   We observed a brief spike in degraded Tempo writes for a small subset of users in the prod-eu-west-2 region, which have now been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-08-13 10:30 UTC

   The configuration change in our API gateway led to certain endpoints being unreachable. This impacted test runs executed from CLI as they were not able to start.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-08-12 11:51 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-08-12 10:22 UTC

   The incident is now resolved. An error in an infrastructure change meant that the SSH endpoint for PDC in eu-west-3 region was unavailable for customers to connect to. Reverting the change fixed the issue and PDC agents were able to reconnect successfully.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-08-11 21:14 UTC

   We continue to observe a continued period of recovery. At this time, we are considering this issue resolved. No further updates.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-08-08 21:14 UTC

   We continue to observe a continued period of recovery. At this time, we are considering this issue resolved. No further updates.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Names an upstream provider: Google Cloud.

1. resolved 2025-08-06 10:41 UTC

   An incident from our CSP, Google Cloud, caused network issues impacting our customers on prod-us-central-0. The Grafana Cloud incident resolved shortly after the CSP incident was resolved, by 6:00 UTC.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-08-04 23:31 UTC

   Engineering has released a fix and as of 23:30 UTC, customers should no longer experience broken CloudWatch queries. At this time, we are considering this issue resolved. No further updates.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-08-02 00:35 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-08-01 00:49 UTC

   We have addressed the problem and browser synthetics began recovering at 00:00 UTC. Browser checks on all probes have been operating normally since 00:15 UTC.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-07-31 20:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-07-29 21:26 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-07-28 19:53 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-07-23 13:02 UTC

   We confirmed no more issues since the resolution.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-07-23 15:11 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-07-17 14:00 UTC

   At approximately 13:50 UTC a new deployment resulted in pointing to a non-existent plugin version for pinned instances. This resulted in new pods for those instances to fail upon start. Since older pods were still running, users should not have experienced a disruption.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-07-15 18:52 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-07-15 09:30 UTC

   Hosted Grafana experienced degraded performance on the Email notification service today, 15th of July from 11:45 UTC to 13:00 UTC. This impacted the sending/receiving of emails used in modules like alerting or reporting. Service was restored shortly after identification.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-07-14 12:00 UTC

   Due to a configuration change, one cell in prod-ap-southeast-2 region was incorrectly configured causing some trace search results to not return as expected. The issue was fixed on July 28th around 12:20 UTC and all search results are now being returned as expected. No data was...

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-07-10 15:36 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-07-07 07:49 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-07-03 22:28 UTC

   Engineering has released a fix and as of 22:20 UTC, customers should no longer experience any issues. At this time, we are considering this issue resolved. No further updates.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-07-03 14:31 UTC

   The incident was caused by multiple ingesters being unavailable at the same time due to moving ingester pods between nodes. It's a regular operation, but in this particular case the ingester took an unexpected long time to restart which coincided with another ingester eventually...

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-07-03 21:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-06-30 20:52 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-06-27 15:41 UTC

   We observed a brief read & write outage in the prod-gb-south-1 region. This lasted from approximately 11:51-12:14 UTC.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-06-21 18:00 UTC

   Spain public probe was facing issues and had intermittent failures between June 21st 20:00 UTC to June 22nd 8:40 UTC. Synthetic monitoring checks using Spain public probe have been failing intermittently during that window. The issue is now resolved - the probe doesn't suffer...

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-06-20 22:27 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-06-24 16:35 UTC

   This incident has been resolved. No further issues were seen since adjusting the backend configuration on Friday June 20th. (22:22 UTC) The root cause has been identified as node CPU saturation, causing high latency on ingesters.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-06-19 18:47 UTC

   We continue to observe a continued period of recovery. At this time, we are considering this issue resolved. No further updates.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-06-18 17:54 UTC

   There was a read outage impacting Loki tenants in the prod-us-east-0 cluster. This issue has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-06-18 18:14 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-06-18 08:00 UTC

   Between 9:40 to 10:55 AM UTC, Cloud Logs service briefly experienced issue with providing data to query rate metrics only. You may experience gaps in the results for query rates panel in the billing dashboards for the given period. The situation is now mitigated, we apologize...

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-06-17 18:00 UTC

   From 18:15 to 18:25 UTC, our prod-us-west-0 Loki cell experienced a period of degraded write performance. The issue resolved quickly without requiring manual intervention, and the system has remained stable since.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Names an upstream provider: AWS.

1. resolved 2025-06-13 13:30 UTC

   The Tempo service on cluster EU west experienced a traffic increase over the weekend, which caused an elevated error rate in Tempo's write path (ingestion). Our engineering team identified the root cause of the issue, and implemented measurements for palliating and resolving the...

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Names an upstream provider: AWS, Azure, Google Cloud.

1. resolved 2025-06-12 21:51 UTC

   We continue to observe a continued period of recovery. At this time, we are considering this issue resolved. No further updates.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-06-11 21:57 UTC

   We continue to observe a continued period of recovery. At this time, we are considering this issue resolved. No further updates.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-06-04 12:00 UTC

   At approximately 12:00 UTC a feature toggle was rolled out which negatively impacted instances on the slow release channel. Users on this release channel began to receive an "AlertStatesDataLayer" error. A workaround was quickly identified and applied to reporting users. The...

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-06-03 16:12 UTC

   We continue to observe a continued period of recovery. At this time, we are considering this issue resolved. No further updates.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-06-02 17:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-06-02 17:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-05-29 17:11 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-05-27 19:47 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-05-22 16:39 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-05-19 19:17 UTC

   Engineering has released a fix and as of 18:45 UTC, customers should no longer experience issues with creating, editing, updating, or deleting SLOs. We continue to observe a continued period of recovery. At this time, we are considering this issue resolved. No further updates.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-05-16 18:09 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-05-26 02:50 UTC

   We have implemented a fix and verified it with a load test.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-05-14 03:57 UTC

   We continue to observe a continued period of recovery. At this time, we are considering this issue resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-05-12 21:35 UTC

   We continue to observe a continued period of recovery. At this time, we are considering this issue resolved. No further updates.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-05-09 12:00 UTC

   Starting from May 9th 2025 12:00 UTC, we were facing Hosted Traces partial read path outage in us-east-2 region. Traceql metric queries were not returning a recently ingested data. After an investigation, the fix was deployed and the incident was resolved at May 14th at 10:00...

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-05-06 21:34 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-05-05 05:29 UTC

   Engineering has applied a fix and as of 5:30 AM UTC, customers should no longer experience an issue with accessing their instance. At this time, we are considering this issue resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-05-02 14:02 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-05-02 09:21 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-04-29 15:09 UTC

   At approximately 14:20 UTC we observed an issue that caused some deployments in prod-us-east-0 to experience long load times, or issues accessing their instance. The issue was resolved shortly before 15:00 UTC.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Names an upstream provider: Google Cloud.

1. resolved 2025-04-27 20:28 UTC

   API came online again at 19:14 UTC in GCP Singapore and 19:21 UTC in GCP Brazil. While the API was unavailable, probes were unaffected. Synthetic monitoring checks in all probes continued to run and publish data during this incident. The incident was caused by earlier database...

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-04-22 22:36 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-04-25 17:51 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-04-17 06:39 UTC

   We continue to observe a continued period of recovery. At this time, we are considering this issue resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-04-15 09:27 UTC

   This incident has been resolved

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Names an upstream provider: AWS.

1. resolved 2025-04-11 19:55 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Names an upstream provider: Google Cloud.

1. resolved 2025-04-10 20:47 UTC

   As of 20:29 UTC the incident is resolved all probes have reconnected to the API in GCP Saudi Arabia(prod-me-central-0).

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-04-10 16:44 UTC

   At approximately 16:00 UTC some customers in the prod-eu-west-2 region began experiencing connectivity issues with their environment. The issue was remediated by our engineers ~30 minutes later.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-04-10 02:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-04-10 08:02 UTC

   The fix has been rolled out and at this time, we are considering this resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-04-11 08:03 UTC

   We continue to observe a continued period of recovery. At this time, we are considering this issue resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Names an upstream provider: Google Cloud.

1. resolved 2025-04-08 17:19 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-04-08 07:20 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Names an upstream provider: AWS.

1. resolved 2025-04-07 13:00 UTC

   Between 2025-04-07:13:00:00UTC and 2025-04-08:14:00:00UTC some customers in AWS Germany (logs-prod-012) have had their ingestion rate limits incorrectly lowered, causing affected customers to hit rate limits writing their logs. The correct rate limits have been reinstated and we...

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-04-07 06:45 UTC

   Some Loki Queries responded with a 500 Response Code, between 06:45 - 7:15UTC.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-04-06 17:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-04-04 01:25 UTC

   The fix has been rolled out on our "fast" release channel. At this point, we are considering the incident resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-04-04 01:27 UTC

   Engineering has rolled out a fix for this issue. At this point, we are considering the incident resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-04-02 06:32 UTC

   Engineering has released a fix and as of 0600 UTC, customers should no longer experience the inability to change SAML role mapping. At this time, we are considering this issue resolved. No further updates.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-03-28 07:59 UTC

   From 6:23 UTC to 6:39 UTC, we became aware of an issue with instances in the prod-sa-east-1 cluster. Users experiencing this issue may have encountered with requests failing for instances in this cluster. This has stabilised and customers should no longer experience this issue.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-03-26 14:03 UTC

   The stack creation process is now functioning properly in the prod-us-west-0 region.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-03-18 19:55 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-03-20 13:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-03-17 17:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-03-17 17:56 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-03-13 05:59 UTC

   We continue to observe a continued period of recovery. At this time, we are considering this issue resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Names an upstream provider: AWS.

1. resolved 2025-03-12 12:30 UTC

   On 12th of March, between 13:30 UTC and 13:50 UTC we experienced some degraded performance when querying metrics on the AWS Germany cluster. The effects were reflected in unavailability to see metrics on dashboards and alert queries triggering errors during that period. The...

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-03-11 21:00 UTC

   All series are now caught up and the incident is resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-03-07 02:15 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-03-06 16:49 UTC

   Many ingesters were evicted from nodes in cortex-prod-01 at once causing a read path outage. Once the ingesters were rescheduled the read path recovered. The errors lasted about 10 minutes.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-02-28 13:09 UTC

   Our internal queues were affected by a scheduled data migration. For around three hours asynchronous scheduled tasks were affected and their processing delayed, but none cancelled or lost. Test scheduled particularly may have been not run at their intended time during that...

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-02-27 12:55 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-02-26 06:52 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Names an upstream provider: AWS.

1. resolved 2025-03-05 23:27 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-02-24 22:16 UTC

   Our Engineering team has identified that this issue is related to: https://status.grafana.com/incidents/b6yc10yk8kv7 We'll be marking this incident as resolved and will provide updates for this event as well in the status page mentioned above.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-02-20 16:02 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-02-19 22:21 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-02-18 17:22 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Names an upstream provider: AWS.

1. resolved 2025-02-18 14:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Names an upstream provider: AWS.

1. resolved 2025-02-14 04:30 UTC

   From February 13th 23:30 UTC to February 14th 00:30 UTC, we saw higher latency and error rates in our Stockholm probe. This was related to a network connectivity within AWS in the EU-NORTH-1 region. The issue is resolved and the probe is operating normally. See the AWS service...

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-02-14 04:21 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-02-03 17:40 UTC

   We continue to observe a continued period of recovery. At this time, we are considering this issue resolved. No further updates.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-01-30 19:19 UTC

   We have identified the issue and rolled back a new alerting feature for re-release in the near future.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-01-30 14:03 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-01-28 21:11 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-01-27 06:03 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-01-27 07:32 UTC

   We continue to observe a continued period of recovery. At this time, we are considering this issue resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-01-23 23:04 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-01-17 00:56 UTC

   Engineering has released a fix and as of 1:30 UTC 2025-01-17. Customers should no longer experience issues with pattern degradation or delay in Explore Logs. At this time, we are considering this issue resolved. No further updates.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

Names an upstream provider: AWS.

1. resolved 2025-01-16 22:00 UTC

   On Thursday January 16th between 17:05 and 18:05 UTC, there was a Synthetic Monitoring outage in the AWS US East ( prod-us-east-0) Grafana Cloud region. During this window you will notice gaps in your synthetics logs and metrics, as data from synthetic monitoring checks were not...

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-01-15 23:48 UTC

   Engineering has released a fix and as of 23:47 UTC, customers should no longer experience issues with pod restarts or loading screens when accessing their instance. At this time, we are considering this issue resolved. No further updates.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-01-15 22:03 UTC

   We continue to observe a continued period of recovery. At this time, we are considering this issue resolved. No further updates.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-01-14 13:19 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-01-10 23:46 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-01-10 09:11 UTC

   Engineering has released a fix and as of 9:10am UTC, customers should no longer experience an issue with AzureAD login. At this time, we are considering this issue resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-01-09 22:00 UTC

   Loki experienced a read outage from ~21:40-22:00 UTC today. We identified the issue, applied remediation, and continue to monitor for any further disruptions. At this time, we are considering this issue resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2025-01-09 01:34 UTC

   The connections have been stable since 14:50 UTC and all 4 probes operating normally during that time. Transitioning this incident from monitoring to resolved.

Excerpts are shortened. Read the full incident on Grafana Cloud's status page.

1. resolved 2024-12-17 13:54 UTC

   This incident has been resolved.