Traycer
status

Kilo Code status

Read from the status pages Kilo Code depends on, checked by Traycer's servers.

Checks every 60s · last checked

Current state

Kilo Code

operational

90 days99.99% uptime

Depends on:Kilo ↗

Kilo

Kilo

degraded

90 dayslowest: Kilo Cloud Platform 99.96% uptime

fresh · checked Status page ↗

Components

  • Kilo Websitekilo.aioperational · 100% uptime
  • Cloudflare Workersoperational
  • Kilo Cloud Platformapp.kilo.aidegraded · 99.96% uptime
  • Cloudflare Workers KVoperational
  • Kilo AI Gatewayoperational · 99.99% uptime
  • Cloudflare Durable Objectsoperational
  • KiloClawoperational · 100% uptime
  • Fly.io Machines APIoperational
  • Kilo Botoperational · 100% uptime
  • Fly.io Persistent Storage (Volumes)operational
  • Fly.io Customer Applicationsoperational
  • WorkOS SSOoperational

Incidents

  • 23 Sep 2026 · · Kilo

    ongoing

    KiloPass MiniMax coding plan subscriptions issues

    Customers who have purchased a MiniMax coding plan may be experiencing failures. We are investigating with MiniMax and working to resolve the issue. Please reach out to support at hi@kilo.ai with any questions.

  • 22 Sep 2026 · · Kilo

    resolved in 2 h 48 min

    Anthropic models temporarily unavailable

    This incident has been resolved.

  • 18 Sep 2026 · · Kilo

    resolved in 22 min

    Increased latency and error rates

    This incident has been resolved.

  • 17 Sep 2026 · · Kilo

    resolved in 0 min

    Kilo AI Gateway & API Degraded

    From 07:08 UTC to approximately 07:24 UTC, the Kilo AI Gateway service and API services were degraded. During this period, requests to Kilo AI Gateway and other core API endpoints may have returned 500 Internal Server errors.

  • 12 Aug 2026 · · Kilo

    resolved in 82 min

    Kilo Cloud platform is not accessible.

    This incident has been resolved.

  • 12 Aug 2026 · · Kilo

    resolved in 458 h 30 min

    Usage page is not showing any data for users.

    This incident has been resolved.

  • 9 Aug 2026 · · Kilo

    resolved in 0 min

    Update to Kilo Bot for Slack Degraded

    We were affected by the recent security incident at Metabase. For more details about the Metabase incident, please see this post on the Anaconda blog: https://www.anaconda.com/metabase-incident-impacting-kilo-code-customer-data As a result of our investigation, all Kilo Slackbot instances were deactivated and the small subset of Kilo-Slack users were notified to reauthenticate. For more information on reactivating Kilo Slackbot, please see the documentation: https://kilo.ai/docs/code-with-ai/platforms/slack#setup

  • 7 Aug 2026 · · Kilo

    resolved in 46 h 59 min

    Kilo Bot for Slack degraded

    This incident has been resolved.

  • 3 Aug 2026 · · Kilo

    resolved in 9 min

    Ling 3.0 Flash (inclusionai/ling-3.0-flash) unavailable

    The upstream provider issue affecting inclusionai/ling-3.0-flash has been resolved. Requests are succeeding normally, and traffic has remained stable. We will continue to monitor the service.

← Every harness

what's next

Your coding agents are fast.
We keep them on track

Join thousands of developers already experiencing a better way to build software with AI.