Browserbase incident

Sessions using Contexts experienced connection failures

Minor Resolved View vendor source →
Started
Mar 17, 2026, 12:13 AM UTC
Resolved
Mar 17, 2026, 12:13 AM UTC
Duration
Detected by Pingoru
Mar 17, 2026, 12:13 AM UTC

Affected components

DirectorConnectDashboardAPIStagehand API

Update timeline

  1. 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)

Looking to track Browserbase downtime and outages?

Pingoru polls Browserbase's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Browserbase reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Browserbase alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Browserbase for free

5 free monitors · No credit card required