Kernel reported "Captcha solver ERR_ZERO_BALANCE error" on its status page at 2026-10-20 07:30 UTC.

Kernel did not name the affected components. The updates on this page have the details.

When did the incident start and end?

It started at 2026-10-20 07:30 UTC and ended at 2026-10-20 07:56 UTC. It lasted 26 min.

How do I get alerts for Kernel?

Subscribe to the Kernel live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of Kernel. outages.live reads it every few minutes and keeps every update.

KernelIncident · 2026-10-20 07:30 UTC

Captcha solver ERR_ZERO_BALANCE error

ResolvedOfficial update

This was resolved, apologies for the disruption.

The latest update from Kernel.

State

Resolved

Started

14 d ago

2026-10-20 07:30 UTC

Lasted

26 min

until 2026-10-20 07:56 UTC

Worst impact

Degraded

Timeline

2 updates

07:3007:3707:4307:5007:56

DegradedUpdate postedTimes in UTC

Identified

26 min 100%

Updates

Times in UTC

As posted by Kernel

Resolved2026-10-20 07:56 UTC

This was resolved, apologies for the disruption.

Identified2026-10-20 07:30 UTC

Our captcha solver is not working. The issue has been identified and we are working on triage.

Kernel in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

55 min

This incident

52% 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

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

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.

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

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane