Incident History

Grafana Cloud having a datasource with PDC enabled using localhost address are getting 403 status responses.

The incident has been resolved.

1730119782 - 1730213269 Resolved

MS SQL Data source unavailable for production instances on Daily or Instant RRC

Engineering has released a fix and as of 19:20 UTC, customers should no longer experience any issues with the MS SQL plugin. At this time, we are considering this issue resolved. No further updates.

1729177280 - 1729192901 Resolved

Tempo Query Failures in AWS Clusters

The fix has been rolled out and issue has been reoslved.

1728731784 - 1728735242 Resolved

Degraded Reads in Loki

At approximately ~11:30 UTC some customers in the prod-us-east-0 region experienced either extremely slow Loki queries, or Loki queries not returning at all. This lasted until ~ 15:30 UTC when the fix was rolled out.

1728663348 - 1728663348 Resolved

Grafana OnCall degraded perfomance

This incident has been resolved.

1728652530 - 1728656364 Resolved

k6: Operational issue

This incident has been resolved.

1728331384 - 1728333357 Resolved

Slow access to OnCall UI and delayed notifications for prod-us-central-0 cluster

Engineering has released a fix and as of Thu Oct 3rd, around 23:00 UTC, customers should no longer experience delays while accessing OnCall UI. At this time, we are considering this issue resolved. No further updates.

1727904170 - 1728037151 Resolved

Synthetic monitoring failures, London probe location

This incident has been resolved.

1727839442 - 1727880299 Resolved

Grafana Cloud Partial Outage

No further instances of this issue have been detected following our mitigation. Customers should no longer experience any downtime. At this time, we are considering this issue resolved. No further updates.

1727811941 - 1727827424 Resolved

Synthetic Monitoring: London and Mumbai probes temporary disruption of service

A transient stability issue in our infrastructure caused public probes to report MultiHTTP and Scripted checks as failures in:

The error has been addressed and all probes should now be operating normally.

1727781277 - 1727781277 Resolved
⮜ Previous Next ⮞