Kilo Code Outage History

Kilo Code is up right now

Kilo Code had 11 outages in the last 2 years totaling 362h 38m of downtime — averaging 0.5 incidents per month.

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

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

Major July 20, 2026

KiloClaw is unavailable due...

Detected by Pingoru
Jul 20, 2026, 07:52 AM UTC
Resolved
Jul 20, 2026, 08:07 AM UTC
Duration
15m
Affected: Kilo Code (KiloClaw)
Timeline · 2 updates
  1. investigating Jul 20, 2026, 07:52 AM UTC

    KiloClaw services are experiencing interruptions due to an upstream provider issue. Existing KiloClaw instances should not be affected and will continue to function as expected. Our team is monitoring the situation closely and will communicate once the issue is resolved.

  2. resolved Jul 20, 2026, 08:07 AM UTC

    The incident has been resolved and KiloClaw services are now fully operational again.

Read the full incident report →

Minor June 15, 2026

KiloClaw instance provision...

Detected by Pingoru
Jun 15, 2026, 03:52 PM UTC
Resolved
Jun 15, 2026, 05:05 PM UTC
Duration
1h 13m
Affected: Kilo Code (KiloClaw)
Timeline · 2 updates
  1. investigating Jun 15, 2026, 03:52 PM UTC

    Users are unable to provision new KiloClaw instances due to an issue with an upstream provider.

  2. resolved Jun 15, 2026, 05:05 PM UTC

    The upstream provider has recovered.

Read the full incident report →

Minor May 18, 2026

Users are unable to provisi...

Detected by Pingoru
May 18, 2026, 12:50 PM UTC
Resolved
May 18, 2026, 01:39 PM UTC
Duration
49m
Affected: Kilo Code (KiloClaw)
Timeline · 2 updates
  1. investigating May 18, 2026, 12:50 PM UTC

    We are investigating the issue where users are unable to provision new KiloClaw instances.

  2. resolved May 18, 2026, 01:39 PM UTC

    Provisioning has been restored.

Read the full incident report →

Minor May 14, 2026

KiloClaw not accessible to ...

Detected by Pingoru
May 14, 2026, 01:24 PM UTC
Resolved
May 14, 2026, 01:48 PM UTC
Duration
24m
Affected: Kilo Code (KiloClaw)
Timeline · 2 updates
  1. investigating May 14, 2026, 01:24 PM UTC

    Some users are unable to access their KiloClaw instance.

  2. resolved May 14, 2026, 01:48 PM UTC

    The issue has been resolved. Our team will continue to monitor the situation closely.

Read the full incident report →

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 →