Browserbase Outage History
15 incidents recorded over the last 365 days, 15 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Browserbase Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| May 26, 2026 | Dashboard outageAfter 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. | 48 min | Resolved |
| Apr 28, 2026 | Issue with Browserbase proxiesAfter 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. | 59 min | Resolved |
| Mar 20, 2026 | Sessions using Contexts experienced connection failuresA 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… | -4315 min | Resolved |
| Feb 2, 2026 | Degraded Performance on Stagehand APIMore timeline details. | 1h 10m | Resolved |
| Jan 30, 2026 | Degraded Performance on Stagehand APIAdded details about root cause being a missing database index. | -223 min | Resolved |
| Jan 21, 2026 | Degraded Captcha SolvingAfter 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. | 1h 17m | Resolved |
| Jan 7, 2026 | Reduced regional availabilityAvailable browsers and session fulfillment has recovered. We appreciate your patience. Please contact customer support if you continue to experience degraded session availability. | 11 min | Resolved |
| Dec 18, 2025 | Browser capacity us-west-2Rate limits restored for customers experiencing them while capacity recovers. | -435 min | Resolved |
| Dec 18, 2025 | Playground session creation degradedAfter 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. | 23 min | Resolved |
| Dec 12, 2025 | Capacity issue in us-west-2After 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. | 20 min | Resolved |
| Dec 8, 2025 | Outage in us-west-2us-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. | -50 min | Resolved |
| Nov 27, 2025 | Browser Availability In US-West-2After 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. | 51 min | Resolved |
| Oct 3, 2025 | Browserbase Proxies degradedAfter 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. | 1h 18m | Resolved |
| Oct 1, 2025 | Built-in proxies unavailableAfter 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. | 39 min | Resolved |
| Sep 13, 2025 | Browser Availability in us-east-1After 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. | 23 min | Resolved |
How to Read This Browserbase Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Browserbase acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Browserbase outage in this window ran 1h 18m, against a mean recovery of 45 min. If you depend on Browserbase in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.