Browserbase Outage History

Pingoru has recorded 12 incidents for Browserbase: 12 in the last 12 months and 0 in the last 90 days.

12incidents recorded

12last 12 months

0last 90 days

98 minutestypical duration

Incidents per month

Share of hours with an open incident, any severity

Pingoru began tracking Browserbase in April 2026, so earlier months are not shown. Hover a bar for its value.

Show as a table

Incidents, newest first

Minor May 26, 2026 Dashboard outage 48m Dashboard

Started May 26, 2026, 09:34 PM UTC· resolved May 26, 2026, 10:22 PM UTC

investigating May 26, 2026, 09:34 PM UTC

We are currently experiencing a disruption that is impacting user's ability to log in to the Dashboard.
monitoring May 26, 2026, 10:05 PM UTC

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 May 26, 2026, 10:22 PM UTC

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.

Started Apr 28, 2026, 12:01 AM UTC· resolved Apr 28, 2026, 03:09 AM UTC

investigating Apr 28, 2026, 12:01 AM UTC

We are currently experiencing a disruption that is impacting sessions with proxies.
monitoring Apr 28, 2026, 02:12 AM UTC

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

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.

Minor March 17, 2026 Sessions using Contexts experienced connection failures – Director, Connect, Dashboard, API and 1 more

Started Mar 17, 2026, 12:13 AM UTC· resolved Mar 17, 2026, 12:13 AM UTC

resolved Mar 17, 2026, 12:13 AM UTC

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.

Minor February 2, 2026 Degraded Performance on Stagehand API 8h 6m Stagehand API

Started Feb 02, 2026, 05:08 PM UTC· resolved Feb 03, 2026, 01:14 AM UTC

investigating Feb 02, 2026, 05:08 PM UTC

Problem: We are experiencing degraded performance on the Stagehand API. Impact: Customers are encountering slow performance when accessing the Stagehand API `/replay` endpoint (used by `stagehand.metrics`). Causes: We identified that Stagehand session replay metrics retrieval is sporadically overloaded due to high traffic on a few outlier sessions that have thousands of actions logged. Steps to resolve: We have temporarily rate-limited these Stagehand API queries, updated the status page, and investigated both infrastructure and query execution, but a few customers are still experiencing degraded on `/act` and `/replay` endpoints.
monitoring Feb 02, 2026, 06:55 PM UTC

It appears the high burst traffic that was overloading session metrics retrieval has been resolved by our new rate limits and query optimizations. We are monitoring the resolution and will continue posting updates.
resolved Feb 02, 2026, 09:58 PM UTC

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.
resolved Feb 03, 2026, 01:01 AM UTC

Added incident details regarding replay and metrics endpoint.
resolved Feb 03, 2026, 01:09 AM UTC

Updated timeline details.
resolved Feb 03, 2026, 01:14 AM UTC

More timeline details.

Minor January 30, 2026 Degraded Performance on Stagehand API 4h 32m Director, Connect, Dashboard, API and 1 more

Started Jan 30, 2026, 05:14 PM UTC· resolved Jan 30, 2026, 09:46 PM UTC

identified Jan 30, 2026, 05:14 PM UTC

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.
resolved Jan 30, 2026, 05:42 PM UTC

Incident resolved, service confirmed to be operating normally. We appreciate your patience and understanding with our team today as we worked to address this
resolved Jan 30, 2026, 09:44 PM UTC

Updated incident timeline
resolved Jan 30, 2026, 09:46 PM UTC

Added details about root cause being a missing database index.