Elevated Write Latency and Errors for Grafana Cloud Logs in Azure Netherlands
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.
The latest update from Grafana Cloud.
State
Resolved
Started
31 d ago
2026-10-02 10:03 UTC
Lasted
4 h
until 2026-10-02 14:03 UTC
Worst impact
Degraded
Timeline
4 updatesInvestigating
4 h 100%
Identified
1 min 0%
Updates
Times in UTCAs posted by Grafana Cloud
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.
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.
We are continuing to investigate this issue. Next update by 11:30 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.
Affected components
2Grafana Cloud in the last 90 days
Full historyIncidents in 90 days
45
Days with an incident
37
Median duration
2 h 53 min
This incident
1.4× the median
Other Grafana Cloud incidents
All incidentsGrafana Cloud·IRM Unable to Voice Call Brazil Numbers
Grafana Cloud reports that voice calls to Brazil do not work for Incident Management and Response (IRM). Grafana Cloud is investigating the issue. Users can configure mobile push or SMS as notifications.
Grafana Cloud·Frontend Observability Outage in prod-eu-west-2
This incident has been resolved.
Grafana Cloud·Degraded Cloud Integrations
This incident has been resolved.
Grafana Cloud·ingestion errors in mimir-prod-66
the issue is resolved now, we're watching the cell
Grafana Cloud·Some Grafana Instances Experiencing Issues Coming Online after Restart
This incident has been resolved.
Follow Grafana Cloud
Your coding agent knows when Grafana Cloud is down, and tells you when a failure is theirs, not yours. You can also get Grafana Cloud incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "grafana" and tell me if Grafana Cloud has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.live/feed.xml?providers=grafana/feed subscribe https://outages.live/feed.xml?providers=grafanaFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane