- Level
- confirmed
- Worst impact
- Partial outage
- Regions
- ap-southeast-1
What to do
Check whether you use Browserbase in ap-southeast-1. 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 2h 39m it lasted.
Anything that failed between 2025-03-04 19:49 UTC and 2025-03-04 22:28 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
- investigating
We are currently experiencing a disruption that may impact browser session connections in ap-southeast-1. We are investigating.
provider
- resolved
We have resolved the potential disruption. We will continue to monitor.
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-55bfbf9ebb
Is Browserbase still down?
No, this incident was resolved 2025-03-04 22:28 UTC. For Browserbase's live state, see https://down.guide/providers/browserbase.
How long did it last?
2h 39m, from 2025-03-04 19:49 UTC to 2025-03-04 22:28 UTC, by the times Browserbase posted.
What was affected?
Browserbase named in ap-southeast-1.
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.