Previous incidents

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

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

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.