Unable to fetch account usage data

[baichuanping]

Before opening, please confirm:

• I have searched for duplicate or closed issues

Operating System

windows11

Kiro Version

Version: 0.11.63 (user setup) VSCode Version: 1.107.1 Commit: e6fae8812a5ffe24dbd780f69d8d33736a50f2f5 Date: 2026-03-18T16:01:27.625Z Electron: 39.6.0 Chromium: 142.0.7444.265 Node.js: 22.22.0 V8: 14.2.231.22-electron.0 OS: Windows_NT x64 10.0.26200

Bug Description

Unable to fetch account usage data: Your User ID (f46854d8-2051-706c-4f31-96686f10063e) temporarily is suspended. We've locked your account as a security precaution. To restore access, please contact our support team to verify your identity: https://support.aws.amazon.com/#/contacts/kiro

Steps to Reproduce

1. Being frozen for no reason, applying for unlocking, and being frozen again after a day

Expected Behavior

不要锁我的账号

Conversation ID

Don't lock my account

Additional Context

No response

[github-actions]

🤖 Potential Duplicate Detected

This issue appears to be similar to:

• #6051: Unable to fetch account usage data : user is not authorized to make a call on initial Chat Load (85% similar)
• #5678: Sync Fetch Account Usage Data Between Multiple Kiro Windows (85% similar)
• #4681: can't login kiro (85% similar)

What happens next?

• ⏰ This issue will be automatically closed in 3 days
• 🏷️ If this is not a duplicate, you can prevent automatic closure by adding a comment or reacting with 👎 to this message.
• 💬 Comment on the original issue if you have additional information

Why is this marked as duplicate?
Both report 'Unable to fetch account usage data' with authorization/authentication errors, though one mentions suspension and the other mentions unauthorized calls

[MarshESC]

same thing happened to me, I am just using their spec mode to do all the task and it suspend me

[github-actions]

Thank you for your feedback! 🙏

The duplicate label has been removed and this issue has been sent back for maintainer review.

A maintainer will review this issue shortly.

[ZinedineRizaIC]

can we just stop with this bug? I have experienced the bug too