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 1 hr ago. Last stored result reached it in 247 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 20 | 0 | 0.0 | 79 ms | 0 |
| Mon 22 | 0 | 0.0 | 264 ms | 0 |
| Tue 00 | 0 | 0.0 | 213 ms | 0 |
| Tue 02 | 0 | 0.0 | 234 ms | 0 |
| Tue 04 | 0 | 0.0 | 73 ms | 0 |
| Tue 07 | 0 | 0.0 | 203 ms | 0 |
| Tue 09 | 0 | 0.0 | 246 ms | 0 |
| Tue 11 | 0 | 0.0 | 248 ms | 0 |
| Tue 13 | 0 | 0.0 | 176 ms | 0 |
| Tue 15 | 0 | 0.0 | 166 ms | 0 |
| Tue 17 | 0 | 0.0 | 234 ms | 0 |
| Tue 20 | 0 | 0.0 | 100 ms | 0 |
| Tue 22 | 0 | 0.0 | 90 ms | 0 |
| Wed 00 | 0 | 0.0 | 252 ms | 0 |
| Wed 02 | 0 | 0.0 | 242 ms | 0 |
| Wed 05 | 0 | 0.0 | 82 ms | 0 |
| Wed 07 | 0 | 0.0 | 200 ms | 0 |
| Wed 09 | 0 | 0.0 | 214 ms | 0 |
| Wed 11 | 0 | 0.0 | 207 ms | 0 |
| Wed 14 | 0 | 0.0 | 207 ms | 0 |
| Wed 16 | 0 | 0.0 | 195 ms | 0 |
| Wed 18 | 0 | 0.0 | 208 ms | 0 |
| Wed 20 | 0 | 0.0 | 168 ms | 0 |
| Wed 22 | 0 | 0.0 | 203 ms | 0 |
| Thu 00 | 0 | 0.0 | 45 ms | 0 |
| Thu 03 | 0 | 0.0 | 197 ms | 0 |
| Thu 05 | 0 | 0.0 | 240 ms | 0 |
| Thu 07 | 0 | 0.0 | 84 ms | 0 |
| Thu 09 | 0 | 0.0 | 178 ms | 0 |
| Thu 11 | 0 | 0.0 | 200 ms | 0 |
| Thu 13 | 0 | 0.0 | 120 ms | 0 |
| Thu 15 | 0 | 0.0 | 50 ms | 0 |
| Thu 17 | 0 | 0.0 | 242 ms | 0 |
| Thu 19 | 0 | 0.0 | 177 ms | 0 |
| Thu 21 | 0 | 0.0 | 237 ms | 0 |
| Fri 00 | 0 | 0.0 | 233 ms | 0 |
| Fri 02 | 0 | 0.0 | 319 ms | 0 |
| Fri 04 | 0 | 0.0 | 308 ms | 0 |
| Fri 06 | 0 | 0.0 | 260 ms | 0 |
| Fri 08 | 0 | 0.0 | 195 ms | 0 |
| Fri 10 | 0 | 0.0 | 217 ms | 0 |
| Fri 12 | 0 | 0.0 | 218 ms | 0 |
| Fri 14 | 0 | 0.0 | 221 ms | 0 |
| Fri 16 | 0 | 0.0 | 223 ms | 0 |
| Fri 17 | 0 | 0.0 | 205 ms | 0 |
| Fri 18 | 0 | 0.0 | 235 ms | 0 |
| Fri 20 | 0 | 0.0 | 104 ms | 0 |
| Fri 22 | 0 | 0.0 | 247 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 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Rossum 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 Rossum goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Rossum alerts to Slack, Discord or a webhook — free.
Rossum is listed in our AI category and checked at rossum.ai. Automate complex transactional workflows with Rossum’s AI document processing solution. Reduce manual tasks, increase accuracy, drive efficiency.
Rossum publishes an official status page at status.rossum.ai; 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 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 232 ms average, 104–339 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 Rossum incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
232 ms on average over the last 24 hours (104–339 ms).
Yes, at https://status.rossum.ai.
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 Rossum here at once, the problem is on Rossum'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 Rossum. 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.