- Level
- confirmed
- Worst impact
- Major outage
- Down Index
- 51of 100
What to do
Check whether your product depends on Browserbase. 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-06-26 06:37 UTC and 2025-06-26 07: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 3
- investigating
We are currently experiencing a disruption that is impacting users ability to log into the dashboard. All backend and browser services remain operational at this time.
provider
- monitoring
We are monitoring the resolution of the earlier disruption. We will continue providing updates here as things progress. Thank you for your patience.
provider
- resolved
We can confirm that the disruption has been resolved. 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-71a94422cc
Is Browserbase still down?
No, this incident was resolved 2025-06-26 07:28 UTC. For Browserbase's live state, see https://down.guide/browserbase.
How long did it last?
51m, from 2025-06-26 06:37 UTC to 2025-06-26 07:28 UTC, by the times Browserbase posted.
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.