Incident History

Elevated Logs Query Usage — Unexpected Billing Impact

Starting June 20, 2026 at approximately 20:00 UTC, some Grafana Cloud customers experienced unexpectedly elevated logs query usage. The issue persisted until it was resolved on June 22, 2026 at approximately 16:00 UTC.

Our engineering team identified and mitigated the issue. Systems have since stabilized and are operating normally. Grafana Labs is reviewing affected accounts for appropriate remediation.

1782166232 - 1782166232 Resolved

Rule Evaluation Outage in prod-us-central-0

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

1781887162 - 1781896797 Resolved

Issues with actions in the Grafana IRM mobile app

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

1781802108 - 1781808638 Resolved

Potential Issues Loading Grafana for Users in India

We have deployed additional mitigations that should help with remaining errors. We are continuing to monitor error rates.

1781795882 Ongoing

Degraded k6 cloud UI performance

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

1781781950 - 1781799714 Resolved

Frontend Observability - Suspected commit feature not working as expected

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

1781772516 - 1781777594 Resolved

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

This incident has been resolved.

1781727457 - 1781791728 Resolved

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

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.

1781301256 - 1781301256 Resolved

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

This incident has been resolved.

1781088597 - 1781156187 Resolved

Investigating Issues with Data Source-Managed Alerting

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

1781046683 - 1781097088 Resolved
⮜ Previous