Claude Taking Longer Than Usual | Claude AI Not Working

While the official Anthropic status page currently shows services as Operational for today, March 9, 2026, there have been significant disruptions over the past week that might be affecting your experience.

Current Status (March 9, 2026)

  • Official Status: All systems are green.

  • Recent Known Issue: A bug was reported involving Daylight Saving Time transitions that caused an “infinite loop” for some users of Claude Code and Claude Cowork. This can make the app hang or feel unresponsive.

  • Recent History: Claude experienced major global outages on March 2nd and 3rd, largely due to a massive surge in users and some reported issues with AWS data centers in the Middle East.


Troubleshooting “Taking Longer Than Usual”

If you are seeing this message or facing a “frozen” interface, try these steps to get back on track:

  1. Check for the DST Bug: If you are using the desktop app or Claude Code, ensure you have updated to version 1.1.5749. If you can’t update, temporarily switching your system timezone to one that doesn’t observe Daylight Saving Time (like UTC) has been known to resolve the “stuck” state.

  2. Clear Metadata Bloat: For heavy users of Claude Code, performance can drop if your ~/.claude.json file becomes too large. Some users have found that backing up and “surgically” removing project metadata can restore speed.

  3. Refresh Your Session: * Web: Sign out and sign back in (this refreshes authentication tokens).

    • Browser: Open Claude in an Incognito/Private window to rule out extension conflicts.

  4. Manage Context: If a specific chat is very long, Claude takes longer to process the history. Try starting a New Chat to see if the speed improves.

Also Read : Romania Government Scholarship 2026

Quick Reference Table

Error Code / Symptom

Likely Cause

Recommended Action

“Taking longer than usual”Backend load or large contextStart a new chat or wait 60 seconds.
HTTP 500 / 529Server OverloadCheck status.claude.com.
App hanging on startupDST Timezone BugUpdate the app or change your timezone.
Login failuresAuthentication OutageClear browser cookies and try again.

Be the first to comment

Leave a Reply