Is Opus 5.5 down?
Up
No, Opus 5.5 is up.
It passed its latest check 11 h ago in 350 ms. It has passed every check since 25 Oct 2026, 18:43 UTC.
Latest check
- Last check
- 11 h ago (26 Oct 2026, 19:07 UTC)
- Response time
- 350 ms (typical 356 ms)
- Next check
- In about 2 h
- How often
- About every 10 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 10 hours over the last 7 days.
Outages in the last 30 days
2 outages, 3 days of failed checks in total, the longest 2 days 4 h.
| Started | Duration | Failed checks | First error |
|---|---|---|---|
| 23 Oct 2026, 14:58 UTC | 2 days 4 h | 3 | initialize returned HTTP 429 |
| 22 Oct 2026, 08:55 UTC | 20 h 6 min | 2 | initialize returned HTTP 429 |
Times are when our checks ran, about every 10 hours for this listing, so start times and durations are accurate to about that.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 26 Oct 2026, 19:07 UTC | Passed | 200 | 350 ms |
| 26 Oct 2026, 07:04 UTC | Passed | 200 | 361 ms |
| 25 Oct 2026, 18:43 UTC | Passed | 200 | 340 ms |
| 24 Oct 2026, 12:32 UTC | initialize returned HTTP 429 | 429 | 378 ms |
| 24 Oct 2026, 02:12 UTC | initialize returned HTTP 429 | 429 | 355 ms |
| 23 Oct 2026, 14:58 UTC | initialize returned HTTP 429 | 429 | 364 ms |
| 23 Oct 2026, 05:01 UTC | Passed | 200 | 397 ms |
| 22 Oct 2026, 19:14 UTC | initialize returned HTTP 429 | 429 | 416 ms |
| 22 Oct 2026, 08:55 UTC | initialize returned HTTP 429 | 429 | 322 ms |
| 21 Oct 2026, 23:25 UTC | Passed | 200 | 348 ms |
How we check
Up means the MCP handshake and the tool list worked, or the server asked for sign-in or payment.
Checks come from our server, about every 10 hours for this listing over the last 7 days. A failure can also mean the service blocks our checks. Two failed checks in a row count as an outage, which ends at the next passing check.
If you think a check is wrong, contact hello@toolvet.app. More on how we check and score.