Elevated check failure rate in ap-northeast-1 (Tokyo)

What to do

• Check whether you use Checkly in ap-northeast-1, apac. Check your stack

  Drop a package.json, lockfile, Terraform or a list of domains at down.guide 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-11 17:51 UTC and 2026-11-11 17:51 UTC may need a replay.

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

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

Updates from Checkly 3

1. updateNov 11, 2026, 5:51 PM UTC

   Status: Investigating We are investigating the issue. Affected components Playwright check runtime API Check Runtime Browser check runtime Multistep check runtime

   provider

2. resolvedNov 11, 2026, 5:51 PM UTC

   Status: Investigating We are investigating the issue. Affected components Playwright check runtime API Check Runtime Browser check runtime Multistep check runtime

   provider

3. resolvedNov 11, 2026, 6:50 PM UTC

   Status: Resolved On November 11, 2026, from 17:51 to 19:50 UTC (about 2 hours), the failure rate on checks was elevated in the ap-northeast-1 (Tokyo) location, following an upstream AWS incident in that region. The issue is resolved. Affected components Playwright check runtime API Check Runtime Browser check runtime Multistep check runtime

   provider

Corrections

None so far.

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