Previous incidents
Users are unable to provision new KiloClaw instances
Resolved May 18, 2026 at 1:39pm UTC
Provisioning has been restored.
1 previous update
KiloClaw not accessible to some users
Resolved May 14, 2026 at 1:48pm UTC
The issue has been resolved. Our team will continue to monitor the situation closely.
3 previous updates
Kilo Code Outage
Resolved Mar 23, 2026 at 7:24pm UTC
app.kilo.ai has recovered
Issues deploying/restarting KiloClaw instances in DFW
Resolved Mar 20, 2026 at 8:16pm UTC
Our upstream provider is experiencing issues with machines in the DFW region.
KiloClaw instances in the ORD region are experiencing interrupted service
Resolved Mar 13, 2026 at 4:37pm 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.
KiloClaw instances in the ORD region are experiencing interrupted service
Resolved Mar 12, 2026 at 5:32pm UTC
Our upstream provider is experiencing issues with machines in the ORD region. We are working on a resolution to this issue with them.
Kilo for Slack delayed responses
Resolved Mar 5, 2026 at 10:01pm 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.