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 claude-haiku-5-5 with low confidence (taxonomy v0.2).

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 claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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 claude-haiku-5-5 with low confidence (taxonomy v0.2).

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 claude-haiku-5-5 with low confidence (taxonomy v0.2).

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 claude-haiku-5-5 with low confidence (taxonomy v0.2).

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 claude-haiku-5-5 with low confidence (taxonomy v0.2).

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 claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

Started during Google Cloud: Multiple services are 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 claude-haiku-5-5 with low confidence (taxonomy v0.2).

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 claude-haiku-5-5 with low confidence (taxonomy v0.2).

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 claude-haiku-5-5 with high confidence (taxonomy v0.2).

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 claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

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: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

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: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

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: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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 claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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 claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

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 claude-haiku-5-5 with low confidence (taxonomy v0.2).

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 claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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 claude-haiku-5-5 with high confidence (taxonomy v0.2).

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: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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 claude-haiku-5-5 with low confidence (taxonomy v0.2).

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 claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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 claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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 claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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 claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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 claude-haiku-5-5 with low confidence (taxonomy v0.2).

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: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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 claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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 claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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 claude-haiku-5-5 with low confidence (taxonomy v0.2).

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: Login, tokens, certificates or credentials failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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 claude-haiku-5-5 with low confidence (taxonomy v0.2).

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 claude-haiku-5-5 with high confidence (taxonomy v0.2).

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 claude-haiku-5-5 with high confidence (taxonomy v0.2).

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: A configuration change caused the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

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 claude-haiku-5-5 with low confidence (taxonomy v0.2).

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 claude-haiku-5-5 with low confidence (taxonomy v0.2).

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 claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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 claude-haiku-5-5 with high confidence (taxonomy v0.2).

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: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

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: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

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 claude-haiku-5-5 with low confidence (taxonomy v0.2).

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 claude-haiku-5-5 with low confidence (taxonomy v0.2).

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 claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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.