Checks
Operating system
Linux 7.0.0-1011-aws - Ubuntu 24.04.4 LTS
Expected behaviour
On 2026-09-21 (UTC) I am repeatedly hitting server-side throttling during
normal Kiro CLI chat. Messages seen:
Service is busy, retrying in 2s...
WARNING: Retry #2, retrying within 10.0s..
Service is busy, retrying in 4s...
Retries climb to #3 repeatedly — roughly 10+ times per hour.
Ruled out locally: network healthy (DNS resolves backend endpoints, pings
succeed), machine idle (load avg ~0.09, 18 GB RAM free), CLI version current
(2.21.2). The explicit "Service is busy" text points to backend
throttling/overload, not a client-side issue. Responses do eventually arrive
after the retries but are significantly delayed.
Asking whether there is a known regional/service-side capacity or throttling
issue, and how to mitigate.
Actual behaviour
On 2026-09-21 (UTC) I am repeatedly hitting server-side throttling during
normal Kiro CLI chat. Messages seen:
Service is busy, retrying in 2s...
WARNING: Retry #2, retrying within 10.0s..
Service is busy, retrying in 4s...
Retries climb to #3 repeatedly — roughly 10+ times per hour.
Ruled out locally: network healthy (DNS resolves backend endpoints, pings
succeed), machine idle (load avg ~0.09, 18 GB RAM free), CLI version current
(2.21.2). The explicit "Service is busy" text points to backend
throttling/overload, not a client-side issue. Responses do eventually arrive
after the retries but are significantly delayed.
Asking whether there is a known regional/service-side capacity or throttling
issue, and how to mitigate.
Steps to reproduce
No response
Environment
<This will be visible to anyone. Do not include personal or sensitive information>
[q-details]
version = "2.21.2"
hash = "a4729fa233d8097438cb3dcb4c9c8d2f21cc82d9"
date = "2026-09-08T19:39:39.264567Z (13d ago)"
variant = "minimal"
[system-info]
chip = "Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz"
total-cores = 4
memory = "30.97 GB"
[system-info.os.linux]
kernel_version = "7.0.0-1011-aws"
id = "ubuntu"
name = "Ubuntu"
pretty_name = "Ubuntu 24.04.4 LTS"
version_id = "24.04"
version = "24.04.4 LTS (Noble Numbat)"
[environment]
cwd = "/persistent/vscode-workspace/lead-engine"
cli-path = "/persistent/vscode-workspace/lead-engine"
os = "Linux"
shell-path = "/usr/bin/bash"
shell-version = "5.2.21"
terminal = "VSCode"
install-method = "unknown"
[env-vars]
PATH = "/home/USER/.local/bin:/usr/local/bin:/usr/lib/code-server/lib/vscode/bin/remote-cli:/home/USER/.local/bin:/usr/local/bin:/home/USER/.local/bin:/home/USER/.local/bin:/usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/snap/bin"
Q_SET_PARENT_CHECK = "1"
SHELL = "/bin/bash"
TERM = "xterm-256color"
Checks
q doctorin the affected terminal sessionq restartand replicated the issue againOperating system
Linux 7.0.0-1011-aws - Ubuntu 24.04.4 LTS
Expected behaviour
On 2026-09-21 (UTC) I am repeatedly hitting server-side throttling during
normal Kiro CLI chat. Messages seen:
Service is busy, retrying in 2s...
WARNING: Retry #2, retrying within 10.0s..
Service is busy, retrying in 4s...
Retries climb to #3 repeatedly — roughly 10+ times per hour.
Ruled out locally: network healthy (DNS resolves backend endpoints, pings
succeed), machine idle (load avg ~0.09, 18 GB RAM free), CLI version current
(2.21.2). The explicit "Service is busy" text points to backend
throttling/overload, not a client-side issue. Responses do eventually arrive
after the retries but are significantly delayed.
Asking whether there is a known regional/service-side capacity or throttling
issue, and how to mitigate.
Actual behaviour
On 2026-09-21 (UTC) I am repeatedly hitting server-side throttling during
normal Kiro CLI chat. Messages seen:
Service is busy, retrying in 2s...
WARNING: Retry #2, retrying within 10.0s..
Service is busy, retrying in 4s...
Retries climb to #3 repeatedly — roughly 10+ times per hour.
Ruled out locally: network healthy (DNS resolves backend endpoints, pings
succeed), machine idle (load avg ~0.09, 18 GB RAM free), CLI version current
(2.21.2). The explicit "Service is busy" text points to backend
throttling/overload, not a client-side issue. Responses do eventually arrive
after the retries but are significantly delayed.
Asking whether there is a known regional/service-side capacity or throttling
issue, and how to mitigate.
Steps to reproduce
No response
Environment