User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
Is ORO down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → oroagents.com—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
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.
Live outage map
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.
What's broken
Recent reports
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.
Our checks
Reaching it
Last checked 33 min ago. Last stored result reached it in 229 ms.
Official status
All clear
No active incidents in the official feed Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 06:45 | 0 | 0.0 | 189 ms | 0 |
| 09:00 | 0 | 0.0 | 124 ms | 0 |
| 11:00 | 0 | 0.0 | 259 ms | 0 |
| 13:00 | 0 | 0.0 | 195 ms | 0 |
| 15:00 | 0 | 0.0 | 145 ms | 0 |
| 17:15 | 0 | 0.0 | 225 ms | 0 |
| 19:15 | 0 | 0.0 | 171 ms | 0 |
| 20:45 | 0 | 0.0 | 160 ms | 0 |
| 22:30 | 0 | 0.0 | 134 ms | 0 |
| 00:45 | 0 | 0.0 | 185 ms | 0 |
| 02:45 | 0 | 0.0 | 147 ms | 0 |
| 04:45 | 0 | 0.0 | 229 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
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.
Embed this status: free live ORO badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for ORO yet. Outages of 10 minutes or more get their own page here.
Having trouble with ORO?
One report per service every 10 minutes from this network. No account.
Follow ORO
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.
About ORO
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: 180 ms average, 124–259 ms range across 12 successful checks.
Questions
Is ORO down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was ORO last down?
We have not recorded a public ORO incident since monitoring began 6 days ago.
What is ORO's uptime?
From our own checks: 100% over 6 days of checks.
How fast does ORO respond?
180 ms on average over the last 24 hours (124–259 ms).
Does ORO have an official status page?
Yes, at https://status.oroagents.com.
ORO not working for me but the status is fine. What now?
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.