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 26 min ago. Last stored result reached it in 587 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 14 | 0 | 0.0 | 469 ms | 0 |
| Mon 16 | 0 | 0.0 | 366 ms | 0 |
| Mon 18 | 0 | 0.0 | 363 ms | 0 |
| Mon 20 | 0 | 0.0 | 438 ms | 0 |
| Mon 22 | 0 | 0.0 | 349 ms | 0 |
| Tue 00 | 0 | 0.0 | 410 ms | 0 |
| Tue 02 | 0 | 0.0 | 380 ms | 0 |
| Tue 04 | 0 | 0.0 | 483 ms | 0 |
| Tue 07 | 0 | 0.0 | 396 ms | 0 |
| Tue 09 | 0 | 0.0 | 523 ms | 0 |
| Tue 11 | 0 | 0.0 | 135 ms | 0 |
| Tue 13 | 0 | 0.0 | 328 ms | 0 |
| Tue 15 | 0 | 0.0 | 650 ms | 0 |
| Tue 17 | 0 | 0.0 | 307 ms | 0 |
| Tue 20 | 0 | 0.0 | 309 ms | 0 |
| Tue 22 | 0 | 0.0 | 494 ms | 0 |
| Wed 00 | 0 | 0.0 | 510 ms | 0 |
| Wed 02 | 0 | 0.0 | 300 ms | 0 |
| Wed 05 | 0 | 0.0 | 320 ms | 0 |
| Wed 07 | 0 | 0.0 | 569 ms | 0 |
| Wed 09 | 0 | 0.0 | 312 ms | 0 |
| Wed 11 | 0 | 0.0 | 335 ms | 0 |
| Wed 14 | 0 | 0.0 | 377 ms | 0 |
| Wed 16 | 0 | 0.0 | 377 ms | 0 |
| Wed 18 | 0 | 0.0 | 347 ms | 0 |
| Wed 20 | 0 | 0.0 | 382 ms | 0 |
| Wed 22 | 0 | 0.0 | 532 ms | 0 |
| Thu 00 | 0 | 0.0 | 439 ms | 0 |
| Thu 02 | 0 | 0.0 | 232 ms | 0 |
| Thu 04 | 0 | 0.0 | 342 ms | 0 |
| Thu 07 | 0 | 0.0 | 618 ms | 0 |
| Thu 09 | 0 | 0.0 | 369 ms | 0 |
| Thu 11 | 0 | 0.0 | 579 ms | 0 |
| Thu 13 | 0 | 0.0 | 319 ms | 0 |
| Thu 15 | 0 | 0.0 | 307 ms | 0 |
| Thu 17 | 0 | 0.0 | 404 ms | 0 |
| Thu 19 | 0 | 0.0 | 551 ms | 0 |
| Thu 21 | 0 | 0.0 | 243 ms | 0 |
| Thu 23 | 0 | 0.0 | 367 ms | 0 |
| Fri 01 | 0 | 0.0 | 499 ms | 0 |
| Fri 03 | 0 | 0.0 | 432 ms | 0 |
| Fri 05 | 0 | 0.0 | 501 ms | 0 |
| Fri 07 | 0 | 0.0 | 326 ms | 0 |
| Fri 09 | 0 | 0.0 | 454 ms | 0 |
| Fri 10 | 0 | 0.0 | 557 ms | 0 |
| Fri 12 | 0 | 0.0 | 528 ms | 0 |
| Fri 14 | 0 | 0.0 | 433 ms | 0 |
| Fri 16 | 0 | 0.0 | 587 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 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Orum 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 Orum goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Orum alerts to Slack, Discord or a webhook — free.
We track Orum (orum.com) as part of the AI group. Built on 1 billion real sales calls, Orum's AI cold calling software gives every rep AI agents that find numbers, dial, and coach. See it in action.
Orum publishes an official status page at status.orum.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 452 ms average, 243–587 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Orum incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
452 ms on average over the last 24 hours (243–587 ms).
Yes, at https://status.orum.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 Orum here at once, the problem is on Orum'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 Orum. 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.