Synthetic Monitoring — Jakarta Public Probe Degradation
Between 08:31 and 09:17 UTC on 6 November 2026, a network issue at the Jakarta public probe caused elevated check failures for monitors running from that location. - DNS checks: failure rate increased from ~0.3% to ~15% - HTTP, ping, traceroute, and browser checks: <1% failure rate - Browser checks: some delays and retries observed - TCP checks: not affected - All other probe locations: not affected
The latest update from Grafana Cloud.
State
Resolved
Started
Lasted
1 min
Worst impact
Notice
Timeline
1 updateResolved
1 min 100%
Updates
Times in UTCAs posted by Grafana Cloud
Between 08:31 and 09:17 UTC on 6 November 2026, a network issue at the Jakarta public probe caused elevated check failures for monitors running from that location. - DNS checks: failure rate increased from ~0.3% to ~15% - HTTP, ping, traceroute, and browser checks: <1% failure rate - Browser checks: some delays and retries observed - TCP checks: not affected - All other probe locations: not affected
Affected components
2Grafana Cloud in the last 90 days
Full historyIncidents in 90 days
52
Days with an incident
41
Median duration
2 h 42 min
This incident
100% shorter than the median
Other Grafana Cloud incidents
All incidentsGrafana Cloud·GitHub returning 403 for all Git Sync repositories
Grafana Cloud Git Sync repositories showed as unhealthy and syncs were skipped in all listed AWS regions. The provider identified the problem, deployed a fix to all production clusters, and monitored the result. Grafana Cloud resolved the incident after 1 hour and 58 minutes.
Grafana Cloud·October usage report visualization issue
Grafana Cloud reports that October usage shows as 0 in the Cost Management and Billing app. Grafana Cloud has identified the problem and works to backfill the correct data. The problem is a visualization issue only and did not affect billing.
Grafana Cloud·Increased query latency for Logs in GCP US Central (prod-us-central-0)
Grafana Cloud reports slower than usual Logs queries in GCP US Central (prod-us-central-0). Grafana Cloud also reports delayed Metrics alert and recording rule evaluations in the same region. Grafana Cloud resolved the incident, and the degraded period lasted about 91 minutes.
Grafana Cloud·Elevated Request Errors for Grafana Across Multiple Regions
Grafana request errors affected multiple Grafana Cloud regions. Dashboards and Explore queries loaded slowly or failed. Grafana Cloud reports the incident resolved. The incident lasted about 1 hour 12 minutes.
Grafana Cloud·Grafana Cloud: k6 timeouts
We had a transient database slowdown causing a limited number of customers' k6 cloud runs to time out or abort in a window of a few minutes after Nov 2, 15:00 UTC. We are investigating the cause.
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