outages.live
Live
KernelIncident ·

Elevated errors creating and connecting to browsers

ResolvedOfficial update
0

Kernel reported elevated errors that stopped some browser creation requests and blocked some new browser CDP connections. Kernel later reported that the incident is resolved. It started at 01:44 UTC, the fix was deployed at 02:27 UTC, and it lasted about 29 minutes. Browsers made between 01:44 UTC and 02:27 UTC that will not connect must be deleted and created again.

State

Resolved

Started

Lasted

29 min

Worst impact

Partial outage

Timeline

3 updates
02:1202:2002:2702:3402:41
Partial outageUpdate postedTimes in UTC

Identified

20 min 70%

Monitoring

9 min 30%

Updates

Times in UTC

As posted by Kernel

Resolved

This incident is resolved. Browser creation and connections are healthy again as of 6:27pm PT. If a browser created between 5:44pm and 6:27pm PT still won't connect, delete it and create a new one.

Monitoring

As of 6:27pm PT, a fix has been deployed and browser creation and connections have recovered. Browsers created between 5:44pm and 6:27pm PT that won't connect should be deleted and recreated. We're monitoring.

Identified

Since 5:44pm PT (01:44 UTC), some requests to create a browser are failing with 529 capacity errors, and some newly created browsers are rejecting CDP connections. We've identified the cause and are rolling out a fix. If a browser created during this window won't connect, delete it and create a new one. We'll post another update once it's resolved.

Kernel in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

8

Days with an incident

8

Median duration

45 min

This incident

35% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

9 h 36 min
median 45 min
90 days agoToday

Other Kernel incidents

All incidents

Kernel·High residential and mobile proxies failure rates

We have shifted traffic to other proxy vendors. We will continue to monitor their health as well, but normal operations have resumed.

Resolved

Kernel·Dashboard project selector missing; some sessions show "not found"

This incident is resolved.

Resolved

Kernel·Captcha solver ERR_ZERO_BALANCE error

This was resolved, apologies for the disruption.

Resolved

Kernel·Elevated API errors for browser operations

This incident is resolved. The API is healthy again.

Resolved

Kernel·Popup windows freezing browser sessions

The fix has been deployed.

Resolved

Follow Kernel

Your coding agent knows when Kernel is down, and tells you when a failure is theirs, not yours. You can also get Kernel incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "kernel" and tell me if Kernel has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=kernel
Slack
/feed subscribe https://outages.cc/feed.xml?providers=kernel

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane