Grafana incident

Synthetic Scripted/Browser checks failure

Resolved after 6 hours 44 minutes, affecting AWS Australia - prod-au-southeast-1: API and AWS Australia - prod-au-southeast-1: Public Probes and 1 more, on June 3, 2026.

identified Jun 03, 2026, 05:07 PM UTC

We are in the process of deploying a fix for this issue.

Started
Jun 03, 2026, 11:38 AM UTC
Resolved
Jun 03, 2026, 06:22 PM UTC
Duration
6h 44m
Detected by Pingoru
Jun 03, 2026, 11:38 AM UTC

Affected components

AWS Australia - prod-au-southeast-1: APIAWS Australia - prod-au-southeast-1: Public ProbesAWS Brazil - prod-sa-east-1: APIAWS Brazil - prod-sa-east-1: Public ProbesAWS Canada - prod-ca-east-0: APIAWS Canada - prod-ca-east-0: Public ProbesAWS Germany - prod-eu-west-2: APIAWS Germany - prod-eu-west-2: Public ProbesAWS India - prod-ap-south-1: APIAWS India - prod-ap-south-1: Public Probes

Update timeline

  1. investigating Jun 03, 2026, 11:38 AM UTC

    We’re currently investigating an issue affecting Synthetic Monitoring where updates for Scripted/Browser checks might fail. Our team is actively working to identify the cause. Thank you for your patience.

  2. identified Jun 03, 2026, 05:07 PM UTC

    We are in the process of deploying a fix for this issue.

  3. resolved Jun 03, 2026, 06:22 PM UTC

    This incident has been resolved.

Your product runs on more than Grafana

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →