Elevated API errors for browser operations
This incident is resolved. The API is healthy again.
The latest update from Kernel.
State
Resolved
Started
15 d ago
2026-10-19 19:34 UTC
Lasted
4 min
until 2026-10-19 19:38 UTC
Worst impact
Major outage
Timeline
3 updatesIdentified
2 min 46%
Monitoring
2 min 54%
Updates
Times in UTCAs posted by Kernel
This incident is resolved. The API is healthy again.
As of 12:23pm PT, a fix has been deployed and we are monitoring.
Between 12:10 and 12:23 PT (19:10–19:23 UTC), a degradation caused most API requests to get, list, update, or delete browsers to fail with 500 errors. Some browser create requests also failed, and browsers that were already running may have had network or proxy connection problems during this window. We rolled back the deploy and error rates returned to normal at 12:23 PT. We're monitoring to confirm everything stays stable. If a browser created during this window is misbehaving, delete it and create a new one.
Kernel in the last 90 days
Full historyIncidents in 90 days
7
Days with an incident
7
Median duration
55 min
This incident
93% shorter than the median
Other Kernel incidents
All incidentsKernel·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.
Kernel·Dashboard project selector missing; some sessions show "not found"
This incident is resolved.
Kernel·Captcha solver ERR_ZERO_BALANCE error
This was resolved, apologies for the disruption.
Kernel·Popup windows freezing browser sessions
The fix has been deployed.
Kernel·Elevated errors for residential proxy creation
Elevated latency affecting residential and mobile proxy creation has subsided, and proxy creation is back to normal. Existing proxy traffic and ISP and datacenter proxy creation were not affected. We’re continuing to monitor.
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.
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.live/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.
https://outages.live/feed.xml?providers=kernel/feed subscribe https://outages.live/feed.xml?providers=kernelFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane