- Level
- confirmed
- Worst impact
- Major outage
- Components
- Automate
- Down Index
- 45of 100
What to do
Check whether you use BrowserStack Automate. 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 6h 13m it lasted.
Anything that failed between 2026-07-07 12:47 UTC and 2026-07-07 19:00 UTC may need a replay.Subscribe to BrowserStack's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=browserstack works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from BrowserStack 2
- investigating
We are currently investigating this issue.
provider
- resolved
Between 12:47 and 19:00 UTC, a subset of users running test sessions on Chrome 149 and 150 experienced an elevated rate of idle timeouts. This was caused by an configuration change, which has since been identified and rolled back. The issue is now fully resolved, and sessions on Chrome 149/150 are operating normally.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-0b8328642e
Is BrowserStack still down?
No, this incident was resolved 2026-07-07 19:00 UTC. For BrowserStack's live state, see https://down.guide/browserstack.
How long did it last?
6h 13m, from 2026-07-07 12:47 UTC to 2026-07-07 19:00 UTC, by the times BrowserStack posted.
What was affected?
BrowserStack named Automate.
What caused it?
BrowserStack hasn't published a root cause. If it does, it shows here.
Where does this come from?
BrowserStack's official status page, https://status.browserstack.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.