Is Browserbase down?
Right now
No. Browserbase is operational.
No incidents reported.
Read from status.browserbase.com · every 120s
For agents
proceed
Proceed.
GET upbutler.com/status/browserbase/status.agent.json
MCP: upstream_status {"service":"browserbase"}
Hosted headless browsers for agents.
What Browserbase reports
Operational
Taken as is from Browserbase's own status page API. Incident titles and component names below are theirs.
Open status.browserbase.comUpButler's independent probe
There is no keyless endpoint of Browserbase that says anything useful, so UpButler does not probe it. To check your own Browserbase account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.
Browserbase components
5 operational
- APIOperational
- ConnectOperational
- DashboardOperational
- DirectorOperational
- Stagehand APIOperational
Browserbase incidents, last 90 days
No finished incidents on record yet. UpButler keeps what Browserbase publishes for 90 days from the day it starts tracking a service.
Tell your outage from Browserbase's
Declare that your project depends on Browserbase. When one of your monitors fails while Browserbase has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.
npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.
# upbutler.yaml
dependencies:
- browserbasecurl -s https://upbutler.com/status/browserbase/status.agent.json{
"schema": "upbutler.upstream-status/v1",
"service": "browserbase",
"verdict": "proceed",
"status": "operational",
"reason": "No incidents reported",
"retryAfterSec": null,
"incident": null,
"probe": null
}Questions
- Is Browserbase down right now?
- No. As of 2026-10-10 05:07 UTC, Browserbase is operational. This page reads the status again every 2 minutes.
- Where does this status come from?
- From Browserbase's own status page API at https://status.browserbase.com. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are Browserbase's words.
- How can my agent or app check Browserbase status?
- Fetch https://upbutler.com/status/browserbase/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"browserbase"}, on https://upbutler.com/mcp/public.
- How do I know whether an outage is mine or Browserbase's?
- Add "browserbase" to the dependencies of your UpButler workspace. When one of your monitors fails while Browserbase has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.
More in hosting and compute
UpButler is not affiliated with Browserbase. Status and incident text belong to Browserbase and are read from their public status source; the probe result is UpButler's own measurement.