- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 45of 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 21h 52m it lasted.
Anything that failed between 2025-01-27 17:12 UTC and 2025-01-28 15:04 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
- investigating
We are currently experiencing a disruption that is impacting proxy usage. We are investigating.
provider
- investigating
We are experiencing a service outage from a downstream proxy service provider. We are working with them to resolve the problem.
provider
- investigating
Proxies for domains ending in `.gov` or `.ca` are operational. We're continuing to work with our downstream provider to resolve the outage.
provider
- resolved
The outage with the downstream service provider has been resolved. We appreciate your patience 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-99469f49c4
Is Browserbase still down?
No, this incident was resolved 2025-01-28 15:04 UTC. For Browserbase's live state, see https://down.guide/browserbase.
How long did it last?
21h 52m, from 2025-01-27 17:12 UTC to 2025-01-28 15:04 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.