Sessions using Contexts experienced connection failures

What to do

• Check whether your product depends on Browserbase. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

  Anything that failed between 2026-03-20 00:08 UTC and 2026-03-17 00:13 UTC may need a replay.

• Subscribe to Browserbase's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=browserbase works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Browserbase 1

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

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.