Is Kernel down?

Last checked 7m ago
Current status
Kernel is up

No incidents right now.

  • Official status page: status.kernel.sh
  • Checked every 5 minutes
  • 3 components tracked

Kernel is operational right now. Last checked 7m ago; the most recent incident resolved 1d ago.

Real-time Kernel status, recent outages, and incident history: pulled directly from Kernel's official status page at status.kernel.sh every 5 minutes. Pingoru tracks 3 Kernel services and has captured 5 incidents in the last 90 days (97.41% uptime). Get email, Slack, Discord, or webhook alerts the moment Kernel reports a new incident, free for 3 monitors, no credit card.

Users who monitor Kernel also follow these Cloud Infrastructure services: Amazon Web Services DigitalOcean Cisco Umbrella Wasabi Vercel Hetzner HashiCorp Egnyte Dyn Genesys Cloud View all 8,000+ providers
Kernel uptime 97.41% uptime · past 90 days
Mon Wed Fri
JulAugSepOct
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 26m
    Started Oct 20, 2026, 07:30 AM UTC · Resolved Oct 20, 2026, 07:56 AM UTC
    Browsers
    Timeline · 2 updates
    • identified · Oct 20, 2026, 07:30 AM UTC

      Status: Identified Our captcha solver is not working. The issue has been identified and we are working on triage. Affected components Browsers (Degraded performance)

    • resolved · Oct 20, 2026, 07:56 AM UTC

      Status: Resolved This was resolved, apologies for the disruption. Affected components Browsers (Operational)

    Latest: Status: Resolved This was resolved, apologies for the disruption. Affected components Browsers (Operational)

  2. Resolved 3m
    Started Oct 19, 2026, 07:34 PM UTC · Resolved Oct 19, 2026, 07:38 PM UTC
    AppsBrowsers
    Timeline · 3 updates
    • identified · Oct 19, 2026, 07:34 PM UTC

      Status: Identified Between 12:10 and 12:23 PT (19:10–19:23 UTC), a degradation caused most API requests to get, list, update, or delete browsers to fail with 500 errors. Some browser create requests also failed, and browsers that were already running may have had network or proxy connection problems during this window. We rolled back the deploy and error rates returned to normal at 12:23 PT. We're monitoring to confirm everything stays stable. If a browser created during this window is misbehaving, delete it and create a new one. Affected components Browsers (Full outage) Apps (Full outage)

    • monitoring · Oct 19, 2026, 07:36 PM UTC

      Status: Monitoring As of 12:23pm PT, a fix has been deployed and we are monitoring. Affected components Apps (Full outage) Browsers (Full outage)

    • resolved · Oct 19, 2026, 07:38 PM UTC

      Status: Resolved This incident is resolved. The API is healthy again. Affected components Apps (Operational) Browsers (Operational)

    Latest: Status: Resolved This incident is resolved. The API is healthy again. Affected components Apps (Operational) Browsers (Operational)

  3. Resolved 1h 10m
    Started Oct 01, 2026, 10:18 PM UTC · Resolved Oct 01, 2026, 11:29 PM UTC
    Browsers
    Timeline · 2 updates
    • monitoring · Oct 01, 2026, 10:18 PM UTC

      Status: Monitoring A browser image released at 14:03 UTC on October 1 causes window.open: http://window.open popups to remain on about:blank while the opening page freezes. Sessions controlled through live view, the computer API, Selenium, or raw CDP are affected. Playwright and Puppeteer sessions are not affected. The cause has been identified and a corrected image is being deployed. We expect it to reach production within the hour. Sessions created after the deployment completes will not be affected. Workaround: if a session is frozen, run the following command against it to resume the popup and the original page. kernel browsers playwright execute 'return 1' We will post another update once the fix is live. Affected components Browsers (Partial outage)

    • resolved · Oct 01, 2026, 11:29 PM UTC

      Status: Resolved The fix has been deployed. Affected components Browsers (Operational)

    Latest: Status: Resolved The fix has been deployed. Affected components Browsers (Operational)

  4. Resolved 9h 36m
    Started Sep 29, 2026, 03:49 AM UTC · Resolved Sep 29, 2026, 01:25 PM UTC
    AppsBrowsers
    Timeline · 3 updates
    • identified · Sep 29, 2026, 03:49 AM UTC

      Status: Identified We have been sporadic errors on residential and mobile proxy creation since ~19:00 UTC today. We have traced this to a downstream vendor and are working with them. Existing proxies are healthy and our recommendation is to re-use existing proxies. We will provide updates as we learn more. Affected components Apps (Degraded performance) Browsers (Degraded performance)

    • identified · Sep 29, 2026, 04:11 AM UTC

      Status: Identified The error is coming from increased response latency in our downstream provider. Until this is resolved, we recommend increasing response timeouts. If you are using our SDK, recommended example snippet: import Kernel from '@onkernel/sdk'; // client-wide: applies to every request const client = new Kernel({ timeout: 5 * 60 * 1000, // 5 minutes }); // or per request (options are the last argument) const browser = await client.browsers.create( { stealth: true }, { timeout: 5 * 60 * 1000 }, ); Affected components Apps (Degraded performance) Browsers (Degraded performance)

    • resolved · Sep 29, 2026, 01:25 PM UTC

      Status: Resolved 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. Affected components Apps (Operational) Browsers (Operational)

    Latest: Status: Resolved Elevated latency affecting residential and mobile proxy creation has subsided, and proxy creation is back to normal. Existing proxy traffic and ISP and datacenter …

  5. Resolved 54m
    Started Sep 10, 2026, 02:01 PM UTC · Resolved Sep 10, 2026, 02:55 PM UTC
    Browsers
    Timeline · 3 updates
    • investigating · Sep 10, 2026, 02:01 PM UTC

      Status: Investigating There are issues with connecting to some browser instances Affected components Browsers (Partial outage)

    • monitoring · Sep 10, 2026, 02:10 PM UTC

      Status: Monitoring The issue has stabilized and we are monitoring performance Affected components Browsers (Partial outage)

    • resolved · Sep 10, 2026, 02:55 PM UTC

      Status: Resolved Services are operating normally Affected components Browsers (Operational)

    Latest: Status: Resolved Services are operating normally Affected components Browsers (Operational)

Outage history

Past 90 days · 5 incidents View full outage history →