# Sessions using Contexts experienced connection failures

- Provider: [Browserbase](https://down.guide/providers/browserbase)
- Confidence: Confirmed
- Impact: Degraded
- lasted 0m
- started 2026-03-20 00:08 UTC
- id: DWN-3a37572ffe
- Official page: https://status.browserbase.com/incidents/01KM494JPDFAGBP2YT594B73FX

## Updates from Browserbase
### 2026-03-17 00:13 UTC: 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.

From the builder: does your app depend on Browserbase? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=browserbase) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention Browserbase.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-3a37572ffe), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.