Dashboard project selector missing; some sessions show "not found"
This incident is resolved.
The latest update from Kernel.
State
Resolved
Started
11 d ago
2026-10-22 21:12 UTC
Lasted
35 min
until 2026-10-22 21:47 UTC
Worst impact
Degraded
Timeline
3 updatesInvestigating
8 min 21%
Identified
28 min 79%
Updates
Times in UTCAs posted by Kernel
This incident is resolved.
> We've identified the issue causing the missing dashboard project selector and are deploying a fix. Browsers are still created successfully, and the API, SDKs and CLI are not affected. We'll post another update once it's resolved.
We're investigating an issue where the project selector is missing from the Kernel dashboard. Some users working in non-default projects see "not found" when opening a browser session they just created. Browsers created from the dashboard are still created successfully. The API, SDKs and CLI are not affected.
Kernel in the last 90 days
Full historyIncidents in 90 days
7
Days with an incident
7
Median duration
55 min
This incident
35% 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·Captcha solver ERR_ZERO_BALANCE error
This was resolved, apologies for the disruption.
Kernel·Elevated API errors for browser operations
This incident is resolved. The API is healthy again.
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.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.
https://outages.cc/feed.xml?providers=kernel/feed subscribe https://outages.cc/feed.xml?providers=kernelFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane