User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Money
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 19 min ago. Last stored result reached it in 60 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 14 | 0 | 0.0 | 82 ms | 0 |
| Mon 17 | 0 | 0.0 | 254 ms | 0 |
| Mon 19 | 0 | 0.0 | 200 ms | 0 |
| Mon 21 | 0 | 0.0 | 51 ms | 0 |
| Mon 23 | 0 | 0.0 | 67 ms | 0 |
| Tue 01 | 0 | 0.0 | 431 ms | 0 |
| Tue 03 | 0 | 0.0 | 219 ms | 0 |
| Tue 05 | 0 | 0.0 | 161 ms | 0 |
| Tue 07 | 0 | 0.0 | 72 ms | 0 |
| Tue 09 | 0 | 0.0 | 182 ms | 0 |
| Tue 12 | 0 | 0.0 | 49 ms | 0 |
| Tue 14 | 0 | 0.0 | 315 ms | 0 |
| Tue 16 | 0 | 0.0 | 73 ms | 0 |
| Tue 18 | 0 | 0.0 | 70 ms | 0 |
| Tue 21 | 0 | 0.0 | 91 ms | 0 |
| Tue 23 | 0 | 0.0 | 54 ms | 0 |
| Wed 01 | 0 | 0.0 | 57 ms | 0 |
| Wed 03 | 0 | 0.0 | 142 ms | 0 |
| Wed 06 | 0 | 0.0 | 52 ms | 0 |
| Wed 08 | 0 | 0.0 | 55 ms | 0 |
| Wed 10 | 0 | 0.0 | 368 ms | 0 |
| Wed 12 | 0 | 0.0 | 180 ms | 0 |
| Wed 14 | 0 | 0.0 | 89 ms | 0 |
| Wed 16 | 0 | 0.0 | 411 ms | 0 |
| Wed 19 | 0 | 0.0 | 237 ms | 0 |
| Wed 21 | 0 | 0.0 | 57 ms | 0 |
| Wed 23 | 0 | 0.0 | 131 ms | 0 |
| Thu 01 | 0 | 0.0 | 351 ms | 0 |
| Thu 03 | 0 | 0.0 | 49 ms | 0 |
| Thu 05 | 0 | 0.0 | 81 ms | 0 |
| Thu 07 | 0 | 0.0 | 932 ms | 0 |
| Thu 10 | 0 | 0.0 | 79 ms | 0 |
| Thu 12 | 0 | 0.0 | 48 ms | 0 |
| Thu 14 | 0 | 0.0 | 98 ms | 0 |
| Thu 16 | 0 | 0.0 | 106 ms | 0 |
| Thu 18 | 0 | 0.0 | 364 ms | 0 |
| Thu 20 | 0 | 0.0 | 92 ms | 0 |
| Thu 22 | 0 | 0.0 | 67 ms | 0 |
| Fri 00 | 0 | 0.0 | 84 ms | 0 |
| Fri 02 | 0 | 0.0 | 359 ms | 0 |
| Fri 04 | 0 | 0.0 | 93 ms | 0 |
| Fri 06 | 0 | 0.0 | 93 ms | 0 |
| Fri 08 | 0 | 0.0 | 63 ms | 0 |
| Fri 10 | 0 | 0.0 | 75 ms | 0 |
| Fri 12 | 0 | 0.0 | 231 ms | 0 |
| Fri 15 | 0 | 0.0 | 96 ms | 0 |
| Fri 17 | 0 | 0.0 | 270 ms | 0 |
| Fri 18 | 0 | 0.0 | 65 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 Rydoo 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 Rydoo goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Rydoo alerts to Slack, Discord or a webhook — free.
We track Rydoo (rydoo.com) as part of the Money group. Rydoo automates expense management and accounts payable for multinational finance teams. Two specialised products keeping every expense and invoice in policy.
Rydoo publishes an official status page at status.rydoo.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with money services: login and two-factor problems, payments or transfers failing, and app errors.
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: 127 ms average, 60–359 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 Rydoo incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
127 ms on average over the last 24 hours (60–359 ms).
Yes, at https://status.rydoo.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For money services, watch for login and two-factor problems, payments or transfers failing, and app errors. If many people report Rydoo here at once, the problem is on Rydoo'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 Rydoo. 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.