rewindex

CompaniesGrafana CloudIncidents

Grafana Cloud: Azure PrivateLink 503 errors on Mimir and Tempo

No impact listedStatus: resolvedStarted Resolved (0 min)1 updatestatus.grafana.com (opens in new tab)

Timeline of updates

  1. resolved

    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 traffic returned to normal.

From Grafana Cloud’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.

Impact, status and times are the vendor’s own, as last archived. View on status.grafana.com (opens in new tab).

Cite this

Status incident (vendor impact label: none) posted by Grafana Cloud, started 2025-09-18 07:17 UTC, resolved after 0 min, 1 update(s).

Title
Azure PrivateLink 503 errors on Mimir and Tempo
Vendor
Grafana Cloud
Date
URL
https://rewindex.com/company/grafana-cloud/incidents/09ss4ytshl60

Grafana Cloud profileRecent Grafana Cloud incidentsAll outages on September 18, 2025Grafana Cloud in September 2025MarkdownJSON