Browserbase

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-26 21:34 UTC

   We are currently experiencing a disruption that is impacting user's ability to log in to the Dashboard.

2. monitoring 2026-05-26 22:05 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.

3. resolved 2026-05-26 22:22 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.

Excerpts are shortened. Read the full incident on Browserbase's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-28 00:01 UTC

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

2. monitoring 2026-04-28 02:12 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.

3. resolved 2026-04-28 03:09 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.

Excerpts are shortened. Read the full incident on Browserbase's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2026-03-17 00:13 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...

Excerpts are shortened. Read the full incident on Browserbase's status page.

Failure mode: Traffic surge or denial-of-service attack. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-02 17:08 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...

2. monitoring 2026-02-02 18:55 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.

3. resolved 2026-02-02 21:58 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.

4. resolved 2026-02-03 01:01 UTC

   Added incident details regarding replay and metrics endpoint.

5. resolved 2026-02-03 01:09 UTC

   Updated timeline details.

6. resolved 2026-02-03 01:14 UTC

   More timeline details.

Excerpts are shortened. Read the full incident on Browserbase's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-01-30 17:14 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.

2. resolved 2026-01-30 17:42 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

3. resolved 2026-01-30 21:44 UTC

   Updated incident timeline

4. resolved 2026-01-30 21:46 UTC

   Added details about root cause being a missing database index.

Excerpts are shortened. Read the full incident on Browserbase's status page.

Failure mode: AI model returned degraded, wrong or empty output (not errors or timeouts). Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-01-21 02:35 UTC

   We are currently experiencing degraded captcha solving that is impacting some websites.

2. resolved 2026-01-21 06:20 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.

Excerpts are shortened. Read the full incident on Browserbase's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-01-07 15:58 UTC

   A primary region (US West) has reduced availability, impacting session availability. Our team is actively addressing the issue and will continue providing updates here as this fix progresses.

2. resolved 2026-01-07 16:10 UTC

   Available browsers and session fulfillment has recovered. We appreciate your patience. Please contact customer support if you continue to experience degraded session availability.

Excerpts are shortened. Read the full incident on Browserbase's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-12-18 09:07 UTC

   We are experiencing an issue with browser capacity in us-west-2. Users will experiencing errors connecting to newly created sessions at this time.

2. monitoring 2025-12-18 09:31 UTC

   Capacity restored in us-west-2.

3. resolved 2025-12-18 10:10 UTC

   Rate limits restored for customers experiencing them while capacity recovers.

Excerpts are shortened. Read the full incident on Browserbase's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-12-18 01:20 UTC

   We are currently experiencing and investigating a disruption that is impacting session creation in the dashboard playground.

2. identified 2025-12-18 01:36 UTC

   Engineering has identified the root cause and are deploying a fix shortly.

3. resolved 2025-12-18 01:43 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.

Excerpts are shortened. Read the full incident on Browserbase's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-12-12 19:46 UTC

   We are currently experiencing a disruption that is impacting some services.

2. monitoring 2025-12-12 19:59 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.

3. resolved 2025-12-12 20:07 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.

Excerpts are shortened. Read the full incident on Browserbase's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2025-12-08 18:30 UTC

   us-west-2 experienced an outage from 10:35 to 11:00 am PST. During this time, no sessions could be created due to an availability issue. Availability has been restored at this time.

Excerpts are shortened. Read the full incident on Browserbase's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-11-27 16:49 UTC

   We're currently experiencing reduced browser capacity in US West 2 and are investigating. Browser creation may be slower than usual.

2. monitoring 2025-11-27 17:04 UTC

   We are monitoring the resolution of the earlier disruption. Capacity has normalized in US-West-2. Thank you for your patience.

3. resolved 2025-11-27 17:41 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.

Excerpts are shortened. Read the full incident on Browserbase's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-10-03 02:40 UTC

   We are currently experiencing a disruption that is impacting our proxies. Sessions without proxies are unaffected.

2. monitoring 2025-10-03 03:04 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.

3. resolved 2025-10-03 03:59 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.

Excerpts are shortened. Read the full incident on Browserbase's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-10-01 01:25 UTC

   We are currently experiencing an issue with our built-in proxies that is impacting sessions using them. Sessions not using proxies or that use external proxies are unaffected.

2. monitoring 2025-10-01 01:46 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.

3. resolved 2025-10-01 02:05 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.

Excerpts are shortened. Read the full incident on Browserbase's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2025-09-13 01:17 UTC

   We are currently experiencing a capacity constraint in browsers for us-east-1. Our team is investigating. Existing browser sessions will not be stopped, but some requests for browsers in us-east-1 will be delayed.

2. resolved 2025-09-13 01:41 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.

Excerpts are shortened. Read the full incident on Browserbase's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-06-26 06:37 UTC

   We are currently experiencing a disruption that is impacting users ability to log into the dashboard. All backend and browser services remain operational at this time.

2. monitoring 2025-06-26 07:10 UTC

   We are monitoring the resolution of the earlier disruption. We will continue providing updates here as things progress. Thank you for your patience.

3. resolved 2025-06-26 07:28 UTC

   We can confirm that the disruption has been resolved. We appreciate your patience and understanding with our team today as we worked to address this.

Excerpts are shortened. Read the full incident on Browserbase's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-06-12 18:11 UTC

   We are currently experiencing a service outage impacting the Dashboard. We are investigating and will provide further updates.

2. investigating 2025-06-12 18:29 UTC

   We are experience an outage from an upstream service provider impacting Dashboard authentication. We are continuing to investigate the scope of impact.

3. investigating 2025-06-12 18:44 UTC

   We've confirmed impact is limited to Dashboard. Browser sessions are functioning normally.

4. monitoring 2025-06-12 19:10 UTC

   We are monitoring the upstream provider for resolution and restored service. Thank you for your patience.

5. resolved 2025-06-12 21:15 UTC

   We can confirm the outage has been resolved. We appreciate your patience and understanding with our team today as we worked to address this.

Excerpts are shortened. Read the full incident on Browserbase's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. identified 2025-04-30 04:42 UTC

   We're experiencing limited capacity in our us-east-1 region. We're increasing capacity and recovery is in progress.

2. resolved 2025-04-30 04:59 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.

Excerpts are shortened. Read the full incident on Browserbase's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-03-22 17:04 UTC

   We are currently experiencing a outage that is impacting the Dashboard. We are investigating.

2. investigating 2025-03-22 17:22 UTC

   We're currently experiencing service disruption with an upstream provider impacting Dashboard and the legacy API endpoint (www.browserbase.com). We are continuing to investigate. The current API endpoint (api.browserbase.com) is operating normally.

3. monitoring 2025-03-22 17:42 UTC

   Upstream service has been restored. We are continuing to monitor.

4. resolved 2025-03-23 01:01 UTC

   After monitoring, we can confirm we have resolved the outage. We appreciate your patience and understanding with our team today as we worked to address this.

Excerpts are shortened. Read the full incident on Browserbase's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-03-04 19:49 UTC

   We are currently experiencing a disruption that may impact browser session connections in ap-southeast-1. We are investigating.

2. resolved 2025-03-04 22:28 UTC

   We have resolved the potential disruption. We will continue to monitor.

Excerpts are shortened. Read the full incident on Browserbase's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-02-18 16:37 UTC

   We're currently investigating intermittent disruptions related to our user metadata functionality on the `POST /v1/sessions` endpoint.

2. resolved 2025-02-18 16:52 UTC

   Further investigation and testing has validated service is working normally. We will continue to monitor.

Excerpts are shortened. Read the full incident on Browserbase's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-02-06 21:50 UTC

   We are experience a service outage from a downstream provider blocking the ability to log into the Dashboard. We are investigating and will provide further updates as we learn more.

2. monitoring 2025-02-06 22:17 UTC

   Service from our auth provider has been restored and it is now possible to log into the Dashboard. We will continuing to monitor.

3. resolved 2025-02-06 22:33 UTC

   After monitoring the restored service, we can confirm that the Dashboard login outage has been resolved. We appreciate your patience and understanding with our team today as we worked to address this.

Excerpts are shortened. Read the full incident on Browserbase's status page.

Failure mode: Traffic surge or denial-of-service attack. Root cause: An external attack. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-02-04 21:52 UTC

   We're investigating a customer reported API outage. We will provide more information as we get it.

2. investigating 2025-02-04 22:06 UTC

   The service disruption appears to be intermittent and related to rate limiting. We are continuing to investigate.

3. investigating 2025-02-04 22:22 UTC

   We are experiencing a targeted surge of unusual and potentially artificial traffic that is impacting API availability. We are actively working to restore normal service levels.

4. investigating 2025-02-04 22:54 UTC

   We have increased API capacity to help mitigate the service disruption and are continuing to investigate root cause.

5. investigating 2025-02-04 23:28 UTC

   We've determined the downloads API endpoint received a major surge in traffic causing service degradation. As a further mitigation, we're introducing reduced rate limits on that endpoint to improve API stability.

6. monitoring 2025-02-05 00:42 UTC

   Our team has identified root cause and is now deploying a fix. We will continue to monitor API services to confirm the outage has been resolved and will provide further updates. Thank you for your patience.

7. monitoring 2025-02-05 02:06 UTC

   Our team has released a fix for the earlier disruption. We will continue to monitor. If you are still experiencing issues, please contact us.

8. resolved 2025-02-05 02:13 UTC

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

Excerpts are shortened. Read the full incident on Browserbase's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-01-27 17:12 UTC

   We are currently experiencing a disruption that is impacting proxy usage. We are investigating.

2. investigating 2025-01-27 18:43 UTC

   We are experiencing a service outage from a downstream proxy service provider. We are working with them to resolve the problem.

3. investigating 2025-01-27 20:53 UTC

   Proxies for domains ending in `.gov` or `.ca` are operational. We're continuing to work with our downstream provider to resolve the outage.

4. resolved 2025-01-28 15:04 UTC

   The outage with the downstream service provider has been resolved. We appreciate your patience as we worked to address this.

Excerpts are shortened. Read the full incident on Browserbase's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2024-12-16 22:30 UTC

   We are currently experiencing a disruption that is impacting browsers in us-west-2 and us-east-1

2. investigating 2024-12-16 23:12 UTC

   We are currently experiencing a disruption that is impacting browsers in us-west-2

3. monitoring 2024-12-16 23:32 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.

4. monitoring 2024-12-16 23:33 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.

5. resolved 2024-12-16 23:47 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.

Excerpts are shortened. Read the full incident on Browserbase's status page.