Is Browserbase down?

Last checked 6m ago
Current status
Browserbase is up

No incidents right now.

Official status page: https://status.browserbase.com · Polled every 5 minutes · 5 components tracked

Browserbase is operational right now. Last checked 6m ago; the most recent incident resolved 18d ago.

Real-time Browserbase status, recent outages, and incident history — pulled directly from Browserbase's official status page at https://status.browserbase.com every 5 minutes. Pingoru tracks 5 Browserbase services and has captured 4 incidents in the last 90 days (98.22% uptime). Get email, Slack, Discord, or webhook alerts the moment Browserbase reports a new incident — free for 5 monitors, no credit card.

Users who monitor Browserbase also follow these Development services: Bitbucket OpenAI Datadog US1 Sentry NPM Travis CI Postman Pusher Pendo SonarCloud View all 6,000+ providers
Browserbase uptime 98.22% uptime · past 90 days
Mon Wed Fri
MarAprMayJun
Less More

Recent outages & incidents

Past 90 days
  1. Resolved
    Started May 26, 2026, 10:22 PM UTC · Resolved May 26, 2026, 10:22 PM UTC
    Dashboard
    Timeline · 3 updates
    • investigating · May 26, 2026, 09:34 PM UTC

      Status: Investigating We are currently experiencing a disruption that is impacting user's ability to log in to the Dashboard. Affected components Dashboard (Full outage)

    • monitoring · May 26, 2026, 10:05 PM UTC

      Status: Monitoring We are monitoring the resolution of the earlier disruption. Our team has released a fix and we will continue providing updates here as this fix progresses. Thank you for your patience. Affected components Dashboard (Full outage)

    • resolved · May 26, 2026, 10:22 PM UTC

      Status: Resolved After monitoring the fix, we can confirm our team has resolved the disruption. We appreciate your patience and understanding with our team today as we worked to address this. Affected components Dashboard (Operational)

    Latest: Status: Resolved After monitoring the fix, we can confirm our team has resolved the disruption. We appreciate your patience and understanding with our team today as we worked to ad…

  2. Resolved
    Started Apr 28, 2026, 03:09 AM UTC · Resolved Apr 28, 2026, 03:09 AM UTC
    Timeline · 3 updates
    • investigating · Apr 28, 2026, 12:01 AM UTC

      Status: Investigating We are currently experiencing a disruption that is impacting sessions with proxies.

    • monitoring · Apr 28, 2026, 02:12 AM UTC

      Status: Monitoring We are monitoring the resolution of the earlier disruption. Our team has released a fix and we will continue providing updates here as this fix progresses. Thank you for your patience.

    • resolved · Apr 28, 2026, 03:09 AM UTC

      Status: Resolved After monitoring the fix, we can confirm our team has resolved the disruption. We appreciate your patience and understanding with our team today as we worked to address this.

    Latest: Status: Resolved After monitoring the fix, we can confirm our team has resolved the disruption. We appreciate your patience and understanding with our team today as we worked to ad…

  3. Resolved
    Started Mar 20, 2026, 12:08 AM UTC · Resolved Mar 17, 2026, 12:13 AM UTC
  4. Resolved
    Started Mar 17, 2026, 12:13 AM UTC · Resolved Mar 17, 2026, 12:13 AM UTC
    DirectorConnectDashboardAPIStagehand API
    Timeline · 1 update
    • resolved · Mar 17, 2026, 12:13 AM UTC

      Status: Resolved A browser service deployment introduced a compatibility issue that caused sessions using Contexts (persistent browser profiles) to fail on navigation. Affected sessions experienced connection timeouts, 503 errors, and inability to load pages. • Affected users: A small percentage of customers, specifically those who created sessions with a contextId during the impact window • Impact window: ~17 hours, from approximately 5:13 PM PT on March 16 through 8:03 AM PT on March 17, 2026 • Resolution: The browser service deployment was rolled back and full recovery was confirmed. Sessions created after the rollback operated normally. • Customer action: Customers whose Contexts were created or updated during the impact window may have experienced corruption. Affected Contexts should be deleted and recreated. Contexts created before or after the impact window were not affected. Affected components Director (Operational) Stagehand API (Operational) Dashboard (Operational) API (Operational) Connect (Operational)

    Latest: Status: Resolved A browser service deployment introduced a compatibility issue that caused sessions using Contexts (persistent browser profiles) to fail on navigation. Affected ses…

Outage history

Past 90 days · 4 incidents View full outage history →