No impact incident
Grafana Cloud: Synthetic Monitoring — Jakarta Public Probe Degradation
Nov 6, 2026, 10:12 UTC
started
10:12 UTC
resolved
<1 min
duration
Affected: AWS Indonesia - prod-ap-southeast-2: Public Probes
Current status of Grafana Cloud: Minor issues — live Grafana Cloud status
Timeline
- Nov 6, 2026, 10:12 UTCresolvedBetween 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
Updates as published by Grafana Cloud (original).
Other services with incidents at the same time
- Scaleway 10:35 UTC · [DC3] Switch issues in room 4-4 rack B14 / B15
- Buffer 10:14 UTC · Issue with creating some posts and drafts, due to a prompt for uploads to finish before saving.
- Fly.io 09:55 UTC · IPv6 egress issues on a subset of IAD hosts
- Cloudflare 09:47 UTC · Wrangler Deployments, Pages, and Workers Builds failures
- CloudLinux 09:40 UTC · sock-gettstamp-uaf (CVE-2026-98276): UDP socket use-after-free, local crash, KernelCare status
- Oracle NetSuite Service 09:33 UTC · NetSuite Service | UK Newport
More Grafana Cloud incidents
- November 4, 2026 GitHub returning 403 for all Git Sync repositories
- November 3, 2026 October usage report visualization issue
- November 3, 2026 Increased query latency for Logs in GCP US Central (prod-us-central-0)
- November 3, 2026 Elevated Request Errors for Grafana Across Multiple Regions
- November 2, 2026 Grafana Cloud: k6 timeouts
- November 2, 2026 Missing Metrics for Some Synthetic Monitoring Checks using the Montreal, North Virginia, and North California public probes