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 5 min ago. Last stored result reached it in 865 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 14 | 0 | 0.0 | 790 ms | 0 |
| Mon 16 | 0 | 0.0 | 1488 ms | 0 |
| Mon 18 | 0 | 0.0 | 969 ms | 0 |
| Mon 20 | 0 | 0.0 | 851 ms | 0 |
| Mon 22 | 0 | 0.0 | 897 ms | 0 |
| Tue 00 | 0 | 0.0 | 799 ms | 0 |
| Tue 02 | 0 | 0.0 | 701 ms | 0 |
| Tue 04 | 0 | 0.0 | 889 ms | 0 |
| Tue 07 | 0 | 0.0 | 656 ms | 0 |
| Tue 09 | 0 | 0.0 | 873 ms | 0 |
| Tue 11 | 0 | 0.0 | 816 ms | 0 |
| Tue 13 | 0 | 0.0 | 827 ms | 0 |
| Tue 15 | 0 | 0.0 | 881 ms | 0 |
| Tue 17 | 0 | 0.0 | 758 ms | 0 |
| Tue 20 | 0 | 0.0 | 747 ms | 0 |
| Tue 22 | 0 | 0.0 | 618 ms | 0 |
| Wed 00 | 0 | 0.0 | 905 ms | 0 |
| Wed 02 | 0 | 0.0 | 825 ms | 0 |
| Wed 05 | 0 | 0.0 | 770 ms | 0 |
| Wed 07 | 0 | 0.0 | 762 ms | 0 |
| Wed 09 | 0 | 0.0 | 841 ms | 0 |
| Wed 11 | 0 | 0.0 | 757 ms | 0 |
| Wed 14 | 0 | 0.0 | 836 ms | 0 |
| Wed 16 | 0 | 0.0 | 900 ms | 0 |
| Wed 18 | 0 | 0.0 | 794 ms | 0 |
| Wed 20 | 0 | 0.0 | 949 ms | 0 |
| Wed 22 | 0 | 0.0 | 856 ms | 0 |
| Thu 00 | 0 | 0.0 | 833 ms | 0 |
| Thu 03 | 0 | 0.0 | 772 ms | 0 |
| Thu 05 | 0 | 0.0 | 950 ms | 0 |
| Thu 07 | 0 | 0.0 | 828 ms | 0 |
| Thu 09 | 0 | 0.0 | 815 ms | 0 |
| Thu 11 | 0 | 0.0 | 769 ms | 0 |
| Thu 13 | 0 | 0.0 | 745 ms | 0 |
| Thu 15 | 0 | 0.0 | 817 ms | 0 |
| Thu 17 | 0 | 0.0 | 1056 ms | 0 |
| Thu 19 | 0 | 0.0 | 964 ms | 0 |
| Thu 21 | 0 | 0.0 | 908 ms | 0 |
| Thu 23 | 0 | 0.0 | 750 ms | 0 |
| Fri 01 | 0 | 0.0 | 842 ms | 0 |
| Fri 03 | 0 | 0.0 | 862 ms | 0 |
| Fri 05 | 0 | 0.0 | 892 ms | 0 |
| Fri 07 | 0 | 0.0 | 479 ms | 0 |
| Fri 09 | 0 | 0.0 | 759 ms | 0 |
| Fri 11 | 0 | 0.0 | 753 ms | 0 |
| Fri 13 | 0 | 0.0 | 831 ms | 0 |
| Fri 15 | 0 | 0.0 | 980 ms | 0 |
| Fri 17 | 0 | 0.0 | 865 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 ryd 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 ryd goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send ryd alerts to Slack, Discord or a webhook — free.
We track ryd (fleet.ryd.one) as part of the Money group. Tanken. Laden. Waschen. ryd fleet ist das Payment-Betriebssystem für Flotten. Optimieren Sie Ihren Fuhrpark. 100% Abdeckung. 100% Digital.
ryd publishes an official status page at status.ryd.one; when we can read it, its incident level is folded into the status shown here.
Common problems for money services: login and two-factor problems, payments or transfers failing, and app errors.
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: 797 ms average, 230–980 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 ryd incident since monitoring began 6 days ago.
From our own checks: 100% over 6 days of checks.
797 ms on average over the last 24 hours (230–980 ms).
Yes, at https://status.ryd.one.
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 ryd here at once, the problem is on ryd'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 ryd. 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.