outages.live
Live
KernelIncident · 2026-09-10 14:01 UTC

Browser connection failures

ResolvedOfficial update

Services are operating normally

The latest update from Kernel.

State

Resolved

Started

54 d ago

2026-09-10 14:01 UTC

Lasted

55 min

until 2026-09-10 14:55 UTC

Worst impact

Partial outage

Timeline

3 updates
14:0114:1414:2814:4214:55
Partial outageUpdate postedTimes in UTC

Investigating

9 min 17%

Monitoring

45 min 83%

Updates

Times in UTC

As posted by Kernel

Resolved2026-09-10 14:55 UTC

Services are operating normally

Monitoring2026-09-10 14:10 UTC

The issue has stabilized and we are monitoring performance

Investigating2026-09-10 14:01 UTC

There are issues with connecting to some browser instances

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

About 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

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.

Resolvedresolved 11 d ago

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

This incident is resolved.

Resolvedresolved 11 d ago

Kernel·Captcha solver ERR_ZERO_BALANCE error

This was resolved, apologies for the disruption.

Resolvedresolved 14 d ago

Kernel·Elevated API errors for browser operations

This incident is resolved. The API is healthy again.

Resolvedresolved 15 d ago

Kernel·Popup windows freezing browser sessions

The fix has been deployed.

Resolvedresolved 32 d ago

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