Kernel reports normal operation on its official status page.

How often does Kernel have incidents?

Kernel reported 7 incidents in the last 90 days, on 7 different days.

Kernel

Kernel is operational

Checked 2 min ago Operational

User reports

What people told outages.live in the last 24 hours, reviewed before it shows. Not from the Kernel status page.

No reviewed reports in the last 24 hours.

History

90 days agoToday

outages.live tracks Kernel since Nov 3, 2026. The days before that show only what Kernel published.

Incidents in 90 days

Days with an incident

Median duration

55 min

Longest incident

9 h 36 min

Components

Dashboard Operational

90 days agoNo incidentsToday

Apps Operational

90 days agoNo incidentsToday

Browsers Operational

90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Oct 23, 2026

Duration1 h 5 min06:27 to 07:32High residential and mobile proxies failure ratesPartial outage

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

Oct 22, 2026

Duration35 min21:12 to 21:47Dashboard project selector missing; some sessions show "not found"Degraded

This incident is resolved.status.kernel.sh

Oct 20, 2026

Duration26 min07:30 to 07:56Captcha solver ERR_ZERO_BALANCE errorDegraded

This was resolved, apologies for the disruption.status.kernel.sh

Oct 19, 2026

Duration4 min19:34 to 19:38Elevated API errors for browser operationsMajor outage

This incident is resolved. The API is healthy again.status.kernel.sh

Oct 1, 2026

Duration1 h 10 min22:18 to 23:29Popup windows freezing browser sessionsPartial outage

The fix has been deployed.status.kernel.sh

Sep 29, 2026

Duration9 h 36 min03:49 to 13:25Elevated errors for residential proxy creationDegraded

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.status.kernel.sh

Sep 10, 2026

Duration55 min14:01 to 14:55Browser connection failuresPartial outage

Services are operating normallystatus.kernel.sh

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

Go from tracking outages to fixing production issues with Polylane.

Try Polylane