Synthetic Monitoring — Jakarta Public Probe Degradation

Summary

Grafana Cloud says a network issue at its Jakarta public probe raised DNS check failures from ~0.3% to ~15% between 08:31 and 09:17 UTC on 6 November 2026. The incident is resolved, and TCP checks and other probe locations were not affected.

Written by anthropic/claude-haiku-5.5 from Grafana Cloud's own updates.

What to do

• Check whether you use Grafana Cloud AWS Indonesia - prod-ap-southeast-2: Public Probes in ap-southeast-2, apac. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

  Anything that failed between 2026-11-06 10:12 UTC and 2026-11-06 10:12 UTC may need a replay.

• Subscribe to Grafana Cloud's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=grafana-cloud works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Grafana Cloud 1

1. resolvedNov 6, 2026, 10:12 AM UTC

   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

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.