Is OUROS down?
Down
Yes, OUROS is down.
It has failed every check since 3 Nov 2026, 01:23 UTC (7 days 15 h, 8 checks). Latest error: initialize returned HTTP 503. It last passed on 2 Nov 2026, 10:40 UTC.
Latest check
- Last check
- 7 h ago (10 Nov 2026, 09:36 UTC)
- Response time
- Not measured (typical 281 ms)
- Next check
- In about 22 h
- How often
- About every 29 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 29 hours over the last 7 days.
Outages in the last 30 days
1 outage, 7 days 15 h of failed checks in total.
| Started | Duration | Failed checks | First error |
|---|---|---|---|
| 3 Nov 2026, 01:23 UTC | Ongoing, 7 days 15 h so far | 8 | initialize returned HTTP 503 |
Times are when our checks ran, about every 29 hours for this listing, so start times and durations are accurate to about that.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 10 Nov 2026, 09:36 UTC | initialize returned HTTP 503 | 503 | 120 ms |
| 9 Nov 2026, 06:22 UTC | initialize returned HTTP 503 | 503 | 80 ms |
| 8 Nov 2026, 01:14 UTC | initialize returned HTTP 503 | 503 | 121 ms |
| 6 Nov 2026, 17:55 UTC | initialize returned HTTP 503 | 503 | 126 ms |
| 5 Nov 2026, 14:13 UTC | initialize returned HTTP 503 | 503 | 60 ms |
| 4 Nov 2026, 05:42 UTC | initialize returned HTTP 503 | 503 | 106 ms |
| 3 Nov 2026, 15:15 UTC | initialize returned HTTP 503 | 503 | 188 ms |
| 3 Nov 2026, 01:23 UTC | initialize returned HTTP 503 | 503 | 258 ms |
| 2 Nov 2026, 10:40 UTC | Passed | 200 | 281 ms |
| 1 Nov 2026, 23:44 UTC | Passed | 200 | 1.3 s |
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 29 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.