[BUG] status.claude.ai Dashboard Does Not Reflect Outage

Status Fixed / completed
Maintainer reply ✓ Yes — igorkofman
Activity 8 comments · opened Jun 9, 2025 · closed Jun 9, 2025
💡 Likely answer: A maintainer (igorkofman, collaborator) responded on this thread — see the highlighted reply below.

Describe the bug
On the night of 2025-06-09, status.claude.ai reported an outage affecting multiple services, including Claude.ai and Claude Code. Despite this, the status dashboard continued to show Claude Code as fully operational (green).

!Image

Evidence of the issue

  • Multiple GitHub tickets reporting overloaded_error for Claude Code during the same period:

View GitHub search for overloaded\_error in anthropics/claude-code

  • Users were experiencing clear disruptions with Claude Code.

Impact

  • The status dashboard did not reflect the ongoing outage for Claude Code.
  • Email notifications regarding Claude Code's status were not triggered.
  • As a result, automated alerting (relying on email notifications) failed to detect the issue.

Expected behavior

  • The status dashboard should accurately reflect the service status of all affected components.
  • Email notifications should be triggered when there are outages or degraded performance, enabling downstream monitoring and alerting.

View original on GitHub ↗

8 Comments

igorkofman collaborator · 1 year ago

I'm seeing it reflect the outage now. Please re-open if this happens again or you're not seeing that.

gwpl · 1 year ago

Claude Code is "all green" on status.claude.ai , while it clearly had outage:

!Image

gwpl · 1 year ago
Please re-open if this happens again or you're not seeing that.

Sure, could you please give me permissions allowing me to re-open?

!Image

igorkofman collaborator · 1 year ago

You meantioned an outage on 6/9 - I believe this is reflected here:

<img width="911" alt="Image" src="https://github.com/user-attachments/assets/903bf08e-b8ff-42de-8459-3b21466ae891" />

gwpl · 1 year ago

Hard to say, this UI is not very readable...

Probably it's it lack of clarity or my confusion on timezones, as in my timezone I had problems on 9th , but maybe in timezone of dashboard it was on 8th :).

Therefore, let's assume it was timezone different and that issue is closed, However let me share with you my artifacts below that I generated to double check, in case someone will find them useful:

!Image

It it written 8th Jul , below that there is link to https://status.anthropic.com/incidents/y25lyp4q33ff

however there is also link to 9th Jul https://status.anthropic.com/incidents/xpkqv7g6jkpz

I experienced problems on 9th Jul after midnight, so it could be timezone difference, hard to say.

I hope that this report will help you to double check if both outages correlate with Claude Code and if times and timezones map correctly:

---

Report with timestamps when overload error was reported:

---

Claude Code Overloaded Error Issues

Timezone Information

All timestamps in this report are in UTC (Coordinated Universal Time). This is determined by the 'Z' suffix in the API responses (e.g., "2025-06-09T11:28:57Z"), where 'Z' stands for "Zulu time" - the military/aviation designation for UTC. GitHub's API consistently returns all timestamps in UTC for standardization across global users.

June 2025

  • 2025-06-08 22:51:48 UTC - user @slyfox1186 reporting "API Request Failures: Persistent 529 Overloaded Errors During Initialization" issue #1815
  • 2025-06-08 23:03:16 UTC - user @richarddaros reporting "Experiencing 529 Overloaded Error After Single Prompt" issue #1816
  • 2025-06-08 22:50:31 UTC - user @rcrumpto14 reporting "API Request Failures: API Error (529..." issue #1814
  • 2025-06-08 22:37:29 UTC - user @kramaiyer reporting "Backend Overload: Repeated 529 Errors During Data Seeding" issue #1811
  • 2025-06-08 22:37:12 UTC - user @neno-is-ooo reporting "API Request Failures: 529 Overloaded Error Consistently Occurring" issue #1809
  • 2025-06-08 22:36:41 UTC - user @BenAWise reporting "API Error 529" issue #1808
  • 2025-06-08 22:38:01 UTC - user @ptiwariml reporting "529 Overload Error" issue #1812

May 2025

  • 2025-05-19 13:46:59 UTC - user @slyfox1186 reporting "API Request Failures: Repeated 529 Overloaded Errors" issue #1166
  • 2025-05-15 21:56:09 UTC - user @mattgodbolt reporting "File Append Failure with Large Test Suites" issue #1119

April 2025

  • 2025-04-03 21:30:42 UTC - user @omararambula reporting "API Error" issue #702

March 2025

  • 2025-03-31 06:33:47 UTC - user @scottleibrand reporting "API Error: Overloaded no longer automatically retrying" issue #661
  • 2025-03-21 08:16:15 UTC - user @scottleibrand reporting "API Error: Overloaded should automatically retry w/ backoff" issue #583
  • 2025-03-18 08:28:24 UTC - user @tech-sumit reporting "API Request Failure: Server Overloaded Error" issue #547
  • 2025-03-18 08:15:58 UTC - user @timeless-residents reporting "Claude Code runs under Bun on some systems" issue #546
  • 2025-03-04 01:20:38 UTC - user @andrewreece reporting "API Error: 'overloaded_error' is causing Claude to fail on tool use" issue #302
  • 2025-03-04 05:18:05 UTC - user @mohanraj-u reporting "API Service Overloaded - Request Failure" issue #308
  • 2025-03-04 05:25:59 UTC - user @ampsarfraz reporting "Server Overloaded: API Request Failed Due to High Load" issue #309
JakeDetels · 1 year ago

@igorkofman, this seems to still be an issue. Can you please re-open? (If you think ticket author [or others] should have access to re-opening tickets, please report to your GitHub admin since that option is currently disabled.) I also can't reopen the ticket.

The outage that has occurred today for Claude Code (and most other components) are currently not reflected. CC has been down for over half hour now, but not reflected in the visual on the status page:

<img width="903" alt="Image" src="https://github.com/user-attachments/assets/956ff784-2493-4966-917a-ea9fd8a4d167" />

igorkofman collaborator · 1 year ago

Sorry for the miss, updated.

github-actions[bot] · 1 year ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.