- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us, us-west-2
- Down Index
- 37of 100
What to do
Check whether you use Browserbase in us, us-west-2. 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 51m it lasted.
Anything that failed between 2025-11-27 16:49 UTC and 2025-11-27 17:41 UTC may need a replay.Subscribe to Browserbase's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=browserbase works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Browserbase 3
- investigating
We're currently experiencing reduced browser capacity in US West 2 and are investigating. Browser creation may be slower than usual.
provider
- monitoring
We are monitoring the resolution of the earlier disruption. Capacity has normalized in US-West-2. Thank you for your patience.
provider
- resolved
After monitoring the fix, we can confirm our team has resolved the disruption. We appreciate your patience and understanding with our team today as we worked to address this.
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-60f0623746
Is Browserbase still down?
No, this incident was resolved 2025-11-27 17:41 UTC. For Browserbase's live state, see https://down.guide/browserbase.
How long did it last?
51m, from 2025-11-27 16:49 UTC to 2025-11-27 17:41 UTC, by the times Browserbase posted.
What was affected?
Browserbase named in us, us-west-2.
What caused it?
Browserbase hasn't published a root cause. If it does, it shows here.
Where does this come from?
Browserbase's official status page, https://status.browserbase.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.