Kilo Code Outage History

Kilo Code is up right now

There were 7 Kilo Code outages since February 5, 2026 totaling 359h 57m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.kilo.ai/

Major March 23, 2026

Kilo Code Outage

Detected by Pingoru
Mar 23, 2026, 07:24 PM UTC
Resolved
Mar 23, 2026, 07:24 PM UTC
Duration
—
Affected: Kilo Code (Kilo AI Gateway)Kilo Code (KiloClaw)Kilo Code (KiloBot)
Timeline · 1 update
  1. resolved Mar 23, 2026, 07:24 PM UTC

    app.kilo.ai has recovered

Read the full incident report →

Minor March 20, 2026

Issues deploying/restarting...

Detected by Pingoru
Mar 20, 2026, 08:16 PM UTC
Resolved
Mar 20, 2026, 08:16 PM UTC
Duration
—
Affected: Kilo Code (KiloClaw)
Timeline · 1 update
  1. resolved Mar 20, 2026, 08:16 PM UTC

    Our upstream provider is experiencing issues with machines in the DFW region.

Read the full incident report →

Minor March 13, 2026

KiloClaw instances in the O...

Detected by Pingoru
Mar 13, 2026, 04:37 PM UTC
Resolved
Mar 13, 2026, 04:37 PM UTC
Duration
—
Affected: Kilo Code (KiloClaw)
Timeline · 1 update
  1. resolved Mar 13, 2026, 04:37 PM UTC

    Our upstream provider is experiencing issues with machines in the ORD region. We are working on a resolution to this issue with them. Users may experience issues provisioning new KiloClaw instances.

Read the full incident report →

Minor March 5, 2026

Kilo for Slack delayed resp...

Detected by Pingoru
Mar 05, 2026, 10:01 PM UTC
Resolved
Mar 05, 2026, 10:01 PM UTC
Duration
—
Affected: Kilo Code (KiloBot)
Timeline · 1 update
  1. resolved Mar 05, 2026, 10:01 PM UTC

    Due to an ongoing upstream incident with Slack (https://slack-status.com/2026-03/e63ca9cc0d76539c), Kilo for Slack invocations and responses may be delayed.

Read the full incident report →

Minor February 27, 2026

Intermittent KiloClaw manag...

Detected by Pingoru
Feb 27, 2026, 07:05 PM UTC
Resolved
Feb 27, 2026, 08:49 PM UTC
Duration
1h 44m
Affected: Kilo Code (KiloClaw)
Timeline · 2 updates
  1. investigating Feb 27, 2026, 07:05 PM UTC

    We're currently seeing increased errors and slow loading in portions of the KiloClaw management UI due to issues with an upstream provider.

  2. resolved Feb 27, 2026, 08:49 PM UTC

    The upstream issue has been resolved. You should now be able to create/destroy or otherwise manage KiloClaw instances.

Read the full incident report →

Minor February 24, 2026

KiloClaw: upstream provider...

Detected by Pingoru
Feb 24, 2026, 03:28 PM UTC
Resolved
Mar 11, 2026, 01:41 PM UTC
Duration
14d 22h
Affected: Kilo Code (KiloClaw)
Timeline · 2 updates
  1. investigating Feb 24, 2026, 03:28 PM UTC

    We're experiencing service disruptions due to resource quota limitations with our cloud infrastructure provider. Some operations may be failing or experiencing delays.

  2. resolved Mar 11, 2026, 01:41 PM UTC

    The issue with the upstream provider has been resolved, all systems are back to normal.

Read the full incident report →

Looking to track Kilo Code downtime and outages?

Pingoru polls Kilo Code's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Kilo Code reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Kilo Code alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Kilo Code for free

5 free monitors · No credit card required