Grafana incident
Increased Execution Time for Browser Checks in Synthetic Monitoring
Resolved after 1 hour 16 minutes, affecting AWS Australia - prod-au-southeast-1: Public Probes and AWS Brazil - prod-sa-east-1: Public Probes and 1 more, on September 15, 2026.
Between September 9 and September 15, 2026, some browser checks in Synthetic Monitoring experienced longer than usual execution times, with impact varying by location. This has been resolved and check execution times have returned to baseline. Thank you for your patience.
Affected components
Update timeline
- identified Sep 15, 2026, 10:00 AM UTC
Since September 9, 2026, some browser checks in Synthetic Monitoring may take longer to complete than usual, with impact varying by location. We have identified the cause and are actively working on a fix. Next update by 10:49 UTC.
- identified Sep 15, 2026, 10:51 AM UTC
A fix has been merged and is now being rolled out across affected locations. We are monitoring deployment progress. Next update by 11:49 UTC.
- monitoring Sep 15, 2026, 10:58 AM UTC
A fix has been deployed and CPU throttling is returning to normal. Check execution times should return to baseline shortly. We will continue monitoring recovery. Next update by 11:56 UTC.
- resolved Sep 15, 2026, 11:17 AM UTC
Between September 9 and September 15, 2026, some browser checks in Synthetic Monitoring experienced longer than usual execution times, with impact varying by location. This has been resolved and check execution times have returned to baseline. Thank you for your patience.
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.
Amazon Web Services