Incidents | Kilo Code Incidents reported on status page for Kilo Code https://status.kilo.ai/ en Kilo Code Outage https://status.kilo.ai/incident/855712 Mon, 23 Mar 2026 19:24:00 -0000 https://status.kilo.ai/incident/855712#b2054dbca69a9bddfac9c84cd7de34439ea2d1ce8880cddb53cf6d2816781441 app.kilo.ai has recovered Issues deploying/restarting KiloClaw instances in DFW https://status.kilo.ai/incident/853844 Fri, 20 Mar 2026 20:16:00 -0000 https://status.kilo.ai/incident/853844#926f41c6bee854d695cc2f7237e102761a746ec8e5ff2e901fc2adb6a2f001c3 Our upstream provider is experiencing issues with machines in the DFW region. Kilo AI Gateway recovered https://status.kilo.ai/ Wed, 18 Mar 2026 09:25:39 +0000 https://status.kilo.ai/#662c1b8637bfa904a3b19a547a1a29b6a66705775ed9f54cc563edb9ad01d50a Kilo AI Gateway recovered Kilo AI Gateway went down https://status.kilo.ai/ Wed, 18 Mar 2026 09:14:58 +0000 https://status.kilo.ai/#662c1b8637bfa904a3b19a547a1a29b6a66705775ed9f54cc563edb9ad01d50a Kilo AI Gateway went down KiloClaw instances in the ORD region are experiencing interrupted service https://status.kilo.ai/incident/848640 Fri, 13 Mar 2026 16:37:00 -0000 https://status.kilo.ai/incident/848640#4a7225ac949939915abd3bb0ce2c94b94acb162b65b993596d40e04a40c08ae2 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 https://status.kilo.ai/incident/847924 Thu, 12 Mar 2026 17:32:00 -0000 https://status.kilo.ai/incident/847924#a05db4cc101508d5d40b62332bba84cc02f5cf7c995fabe80f5d232652bbf965 Our upstream provider is experiencing issues with machines in the ORD region. We are working on a resolution to this issue with them. KiloClaw: upstream provider capacity disruption https://status.kilo.ai/incident/833005 Wed, 11 Mar 2026 13:41:00 -0000 https://status.kilo.ai/incident/833005#a4193dbddb56a9a6818a77962493baae65ba8d25304fa19bcae837aba4926c78 The issue with the upstream provider has been resolved, all systems are back to normal. KiloClaw: upstream provider capacity disruption https://status.kilo.ai/incident/833005 Wed, 11 Mar 2026 09:51:00 -0000 https://status.kilo.ai/incident/833005#c7e51efb0bda5c5dbfaf809bb2ae1a3eebe2a2b72feba23833aa201a1958b37f An ongoing data migration at out upstream provider's secret storage service is causing degraded Machines API functionality. Kilo for Slack delayed responses https://status.kilo.ai/incident/841794 Thu, 05 Mar 2026 22:01:00 -0000 https://status.kilo.ai/incident/841794#122f3442cb17513e87f23cdb3eaf4b3f34e20077de7e03f33bc4dcc8e401ec05 Due to an ongoing upstream incident with Slack (https://slack-status.com/2026-03/e63ca9cc0d76539c), Kilo for Slack invocations and responses may be delayed. Intermittent KiloClaw management failures https://status.kilo.ai/incident/835442 Fri, 27 Feb 2026 20:49:00 -0000 https://status.kilo.ai/incident/835442#8fe0c83a40fe78e462c27968c65a50bc0e7584938b71a8e9876e2f40e9663f79 The upstream issue has been resolved. You should now be able to create/destroy or otherwise manage KiloClaw instances. Intermittent KiloClaw management failures https://status.kilo.ai/incident/835442 Fri, 27 Feb 2026 19:05:00 -0000 https://status.kilo.ai/incident/835442#444431838b2fbdc78c536c313e47c8d660da0f77cadf6cbb58409e2a034982f2 We're currently seeing increased errors and slow loading in portions of the KiloClaw management UI due to issues with an upstream provider. KiloClaw: upstream provider capacity disruption https://status.kilo.ai/incident/833005 Wed, 25 Feb 2026 18:09:00 -0000 https://status.kilo.ai/incident/833005#d8fe441b31fb4d994156e7d50e5d92799a4f1dbff6ee70c2b08504c13996f762 This incident has been resolved. Deployment capacity has been restored and operations are back to normal. Note: If you're still unable to start a machine, destroy and re-create it to automatically select a region with available capacity. Thank you for your patience during this incident. KiloClaw: upstream provider capacity disruption https://status.kilo.ai/incident/833005 Wed, 25 Feb 2026 15:18:00 -0000 https://status.kilo.ai/incident/833005#f7f1ac2d0cf88c66c5545e7241b06e2b74ccc7e85f359b24782c87765820c0d8 We are observing a reduction in pending deployments and improved service availability following our mitigation efforts. Our team continues to monitor the situation and work closely with our upstream provider to secure additional capacity and ensure full resolution. We will provide the next update within 2 hours. KiloClaw: upstream provider capacity disruption https://status.kilo.ai/incident/833005 Wed, 25 Feb 2026 14:09:00 -0000 https://status.kilo.ai/incident/833005#2397d65cb5b9517ae7385f0bb376701ffbfcd18939f8c5e69fb43cabb5246c10 We have deployed to additional regions to try to alleviate deploy pressures while still working directly with our upstream provider to enable additional capacity. KiloClaw: upstream provider capacity disruption https://status.kilo.ai/incident/833005 Wed, 25 Feb 2026 13:51:00 -0000 https://status.kilo.ai/incident/833005#ff75db11a24d65e272f112fb05f563d5ba0f0ff2a069d3dfb1538711bc0da9b7 We're experiencing service disruptions due to resource quota limitations with our cloud infrastructure provider. Some operations may be failing or experiencing delays. Our team is actively working with the provider to increase our resource quotas and restore full functionality. We expect resolution once additional capacity is allocated. We'll continue to monitor and provide updates as the situation progresses. KiloClaw: upstream provider capacity disruption https://status.kilo.ai/incident/833005 Tue, 24 Feb 2026 19:29:00 -0000 https://status.kilo.ai/incident/833005#1dfb88777ba26fea1248e91c3e5863b2ff7f2977b1089ecf36ce5a63a25e51d0 Deploys appear to have recovered and are proceeding within normal limits Kilo AI Gateway recovered https://status.kilo.ai/ Tue, 24 Feb 2026 17:42:10 +0000 https://status.kilo.ai/#655b5c8f5860ac83bb7949da62715e2a0f71506f8ef67b03032d0c8b8ff15c37 Kilo AI Gateway recovered Kilo AI Gateway went down https://status.kilo.ai/ Tue, 24 Feb 2026 17:36:15 +0000 https://status.kilo.ai/#655b5c8f5860ac83bb7949da62715e2a0f71506f8ef67b03032d0c8b8ff15c37 Kilo AI Gateway went down KiloClaw: upstream provider capacity disruption https://status.kilo.ai/incident/833005 Tue, 24 Feb 2026 15:28:00 -0000 https://status.kilo.ai/incident/833005#971b01ce110c2eae00cb7277119457c5b30c3d7e8573bef4df158300e7f97678 We're experiencing service disruptions due to resource quota limitations with our cloud infrastructure provider. Some operations may be failing or experiencing delays. Kilo AI Gateway recovered https://status.kilo.ai/ Tue, 24 Feb 2026 14:46:34 +0000 https://status.kilo.ai/#a357b88a04acfb77dc26165935328f81c44f5e68451eb12c052854b15ca0e047 Kilo AI Gateway recovered Kilo AI Gateway went down https://status.kilo.ai/ Tue, 24 Feb 2026 14:43:51 +0000 https://status.kilo.ai/#a357b88a04acfb77dc26165935328f81c44f5e68451eb12c052854b15ca0e047 Kilo AI Gateway went down Kilo AI Gateway recovered https://status.kilo.ai/ Thu, 05 Feb 2026 12:31:11 +0000 https://status.kilo.ai/#62c0d27ed835db43d502b251f69439d5070cb0dfbfe86e2c724a97cdc334b275 Kilo AI Gateway recovered Kilo AI Gateway went down https://status.kilo.ai/ Thu, 05 Feb 2026 12:29:37 +0000 https://status.kilo.ai/#62c0d27ed835db43d502b251f69439d5070cb0dfbfe86e2c724a97cdc334b275 Kilo AI Gateway went down