- Level
- confirmed
- Worst impact
- Partial outage
- Regions
- us
- Down Index
- 40of 100
What to do
Check whether you use Browserbase in us. 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 12m it lasted.
Anything that failed between 2026-01-07 15:58 UTC and 2026-01-07 16:10 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 2
- monitoring
A primary region (US West) has reduced availability, impacting session availability. Our team is actively addressing the issue and will continue providing updates here as this fix progresses.
provider
- resolved
Available browsers and session fulfillment has recovered. We appreciate your patience. Please contact customer support if you continue to experience degraded session availability.
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-a8bf6e2d84
Is Browserbase still down?
No, this incident was resolved 2026-01-07 16:10 UTC. For Browserbase's live state, see https://down.guide/browserbase.
How long did it last?
12m, from 2026-01-07 15:58 UTC to 2026-01-07 16:10 UTC, by the times Browserbase posted.
What was affected?
Browserbase named in us.
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.