User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 27 min ago. Last stored result reached it in 191 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 16 | 0 | 0.0 | 205 ms | 0 |
| Mon 18 | 0 | 0.0 | 228 ms | 0 |
| Mon 20 | 0 | 0.0 | 76 ms | 0 |
| Mon 22 | 0 | 0.0 | 232 ms | 0 |
| Tue 00 | 0 | 0.0 | 184 ms | 0 |
| Tue 02 | 0 | 0.0 | 455 ms | 0 |
| Tue 04 | 0 | 0.0 | 177 ms | 0 |
| Tue 06 | 0 | 0.0 | 313 ms | 0 |
| Tue 08 | 0 | 0.0 | 172 ms | 0 |
| Tue 11 | 0 | 0.0 | 333 ms | 0 |
| Tue 13 | 0 | 0.0 | 133 ms | 0 |
| Tue 15 | 0 | 0.0 | 193 ms | 0 |
| Tue 17 | 0 | 0.0 | 195 ms | 0 |
| Tue 20 | 0 | 0.0 | 207 ms | 0 |
| Tue 22 | 0 | 0.0 | 179 ms | 0 |
| Wed 00 | 0 | 0.0 | 189 ms | 0 |
| Wed 02 | 0 | 0.0 | 188 ms | 0 |
| Wed 05 | 0 | 0.0 | 113 ms | 0 |
| Wed 07 | 0 | 0.0 | 239 ms | 0 |
| Wed 09 | 0 | 0.0 | 149 ms | 0 |
| Wed 11 | 0 | 0.0 | 163 ms | 0 |
| Wed 13 | 0 | 0.0 | 294 ms | 0 |
| Wed 15 | 0 | 0.0 | 337 ms | 0 |
| Wed 18 | 0 | 0.0 | 140 ms | 0 |
| Wed 20 | 0 | 0.0 | 107 ms | 0 |
| Wed 22 | 0 | 0.0 | 140 ms | 0 |
| Thu 00 | 0 | 0.0 | 284 ms | 0 |
| Thu 02 | 0 | 0.0 | 211 ms | 0 |
| Thu 04 | 0 | 0.0 | 263 ms | 0 |
| Thu 06 | 0 | 0.0 | 189 ms | 0 |
| Thu 09 | 0 | 0.0 | 124 ms | 0 |
| Thu 11 | 0 | 0.0 | 259 ms | 0 |
| Thu 13 | 0 | 0.0 | 195 ms | 0 |
| Thu 15 | 0 | 0.0 | 145 ms | 0 |
| Thu 17 | 0 | 0.0 | 225 ms | 0 |
| Thu 19 | 0 | 0.0 | 171 ms | 0 |
| Thu 20 | 0 | 0.0 | 160 ms | 0 |
| Thu 22 | 0 | 0.0 | 134 ms | 0 |
| Fri 00 | 0 | 0.0 | 185 ms | 0 |
| Fri 02 | 0 | 0.0 | 147 ms | 0 |
| Fri 04 | 0 | 0.0 | 229 ms | 0 |
| Fri 07 | 0 | 0.0 | 204 ms | 0 |
| Fri 09 | 0 | 0.0 | 197 ms | 0 |
| Fri 11 | 0 | 0.0 | 219 ms | 0 |
| Fri 13 | 0 | 0.0 | 108 ms | 0 |
| Fri 15 | 0 | 0.0 | 159 ms | 0 |
| Fri 16 | 0 | 0.0 | 401 ms | 0 |
| Fri 18 | 0 | 0.0 | 191 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 6 days of data so far, so the 90-day numbers fill in over time.
No outages on record for ORO yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when ORO goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send ORO alerts to Slack, Discord or a webhook — free.
ORO, at oroagents.com, is one of the AI services we monitor. ORO builds high-fidelity simulation environments grounded in real data to teach AI the tacit knowledge required to run safe and profitable autonomous businesses.
ORO publishes an official status page at status.oroagents.com; when we can read it, its incident level is folded into the status shown here.
Common problems for AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 6 days of checks. No public incidents logged since monitoring began 6 days ago.
Response time over the last 24 hours: 195 ms average, 108–401 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public ORO incident since monitoring began 6 days ago.
From our own checks: 100% over 6 days of checks.
195 ms on average over the last 24 hours (108–401 ms).
Yes, at https://status.oroagents.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report ORO here at once, the problem is on ORO's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with ORO. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.