Kilo Code had 10 outages in the last 2 years totaling 362h 23m of downtime — averaging 0.4 incidents per month.
There were 10 Kilo Code outages since February 5, 2026 totaling 362h 23m of downtime. Each is summarised below — incident details, duration, and resolution information.
Users are unable to provision new KiloClaw instances due to an issue with an upstream provider.
The upstream provider has recovered.
Kilo AI Gateway went down
We are investigating the issue where users are unable to provision new KiloClaw instances.
Provisioning has been restored.
Some users are unable to access their KiloClaw instance.
The issue has been resolved. Our team will continue to monitor the situation closely.
app.kilo.ai has recovered
Our upstream provider is experiencing issues with machines in the DFW region.
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.
Due to an ongoing upstream incident with Slack (https://slack-status.com/2026-03/e63ca9cc0d76539c), Kilo for Slack invocations and responses may be delayed.
We're currently seeing increased errors and slow loading in portions of the KiloClaw management UI due to issues with an upstream provider.
The upstream issue has been resolved. You should now be able to create/destroy or otherwise manage KiloClaw instances.
We're experiencing service disruptions due to resource quota limitations with our cloud infrastructure provider. Some operations may be failing or experiencing delays.
The issue with the upstream provider has been resolved, all systems are back to normal.