- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 20of 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 0m it lasted.
Anything that failed between 2026-01-30 21:25 UTC and 2026-01-30 17:42 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 4
- identified
We are investigating an issue regarding degraded performance on the Stagehand API due to a missing database index. Our team has identified the issue and is actively rolling out the new index which should correct the performance issue promptly.
provider
- resolved
Incident resolved, service confirmed to be operating normally. We appreciate your patience and understanding with our team today as we worked to address this
provider
- resolved
Updated incident timeline
provider
- resolved
Added details about root cause being a missing database index.
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-70526a3d97
Is Browserbase still down?
No, this incident was resolved 2026-01-30 17:42 UTC. For Browserbase's live state, see https://down.guide/browserbase.
How long did it last?
0m, from 2026-01-30 21:25 UTC to 2026-01-30 17:42 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.