Incident History

Synthetic Monitoring Outage in AWS US East ( prod-us-east-0)

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 published from any probe locations. The incident is resolved but we continue to investigate the root cause.

1737393902 - 1737393902 Resolved

Rare intermittent write failures in Tempo

This incident has been resolved.

1737143796 - 1737673457 Resolved

Pattern Degradation/Delay in Recognizing Patterns in Explore Logs

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.

1737073164 - 1737075419 Resolved

Hosted Grafana API Partial Outage

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.

1736983404 - 1736984898 Resolved

Errors in Newly Created Stacks

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

1736962394 - 1736978583 Resolved

K6 Ingest Tests degradation

This incident has been resolved.

1736859808 - 1736860799 Resolved

Confluent Cloud Integration disruption

This incident has been resolved.

1736533060 - 1736552789 Resolved

Intermittent delays in startup time - AWS US East and EU West regions.

The incident is now resolved - we haven't observed any occurrence nor manifestation since yesterday's update.

1736527534 - 1736843925 Resolved

Logins to environments failing on AzureAD

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.

1736499076 - 1736500312 Resolved

Loki Read Outage

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.

1736462777 - 1736462777 Resolved
⮜ Previous Next ⮞