Live

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 updates
21:1221:2121:3021:3921:47
DegradedUpdate postedTimes in UTC

Investigating

8 min 21%

Identified

28 min 79%

Updates

Times in UTC

As posted by Kernel

Resolved2026-10-22 21:47 UTC

This incident is resolved.

Identified2026-10-22 21:20 UTC

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

Investigating2026-10-22 21:12 UTC

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 history
90 days agoToday

Incidents in 90 days

7

Days with an incident

7

Median duration

55 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 55 min
90 days agoToday

Other Kernel incidents

All incidents

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

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

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane