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 44 min ago. Last stored result reached it in 266 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 03 | 0 | 0.0 | 329 ms | 0 |
| Mon 05 | 0 | 0.0 | 351 ms | 0 |
| Mon 07 | 0 | 0.0 | 114 ms | 0 |
| Mon 09 | 0 | 0.0 | 110 ms | 0 |
| Mon 11 | 0 | 0.0 | 119 ms | 0 |
| Mon 13 | 0 | 0.0 | 131 ms | 0 |
| Mon 15 | 0 | 0.0 | 125 ms | 0 |
| Mon 17 | 0 | 0.0 | 288 ms | 0 |
| Mon 20 | 0 | 0.0 | 313 ms | 0 |
| Mon 22 | 0 | 0.0 | 120 ms | 0 |
| Tue 00 | 0 | 0.0 | 227 ms | 0 |
| Tue 02 | 0 | 0.0 | 133 ms | 0 |
| Tue 04 | 0 | 0.0 | 314 ms | 0 |
| Tue 06 | 0 | 0.0 | 109 ms | 0 |
| Tue 08 | 0 | 0.0 | 368 ms | 0 |
| Tue 10 | 0 | 0.0 | 429 ms | 0 |
| Tue 12 | 0 | 0.0 | 326 ms | 0 |
| Tue 15 | 0 | 0.0 | 280 ms | 0 |
| Tue 17 | 0 | 0.0 | 333 ms | 0 |
| Tue 19 | 0 | 0.0 | 306 ms | 0 |
| Tue 22 | 0 | 0.0 | 225 ms | 0 |
| Wed 00 | 0 | 0.0 | 348 ms | 0 |
| Wed 02 | 0 | 0.0 | 299 ms | 0 |
| Wed 04 | 0 | 0.0 | 383 ms | 0 |
| Wed 06 | 0 | 0.0 | 322 ms | 0 |
| Wed 09 | 0 | 0.0 | 292 ms | 0 |
| Wed 11 | 0 | 0.0 | 298 ms | 0 |
| Wed 13 | 0 | 0.0 | 241 ms | 0 |
| Wed 15 | 0 | 0.0 | 299 ms | 0 |
| Wed 17 | 0 | 0.0 | 153 ms | 0 |
| Wed 20 | 0 | 0.0 | 399 ms | 0 |
| Wed 22 | 0 | 0.0 | 353 ms | 0 |
| Thu 00 | 0 | 0.0 | 347 ms | 0 |
| Thu 02 | 0 | 0.0 | 330 ms | 0 |
| Thu 04 | 0 | 0.0 | 290 ms | 0 |
| Thu 06 | 0 | 0.0 | 125 ms | 0 |
| Thu 08 | 0 | 0.0 | 283 ms | 0 |
| Thu 10 | 0 | 0.0 | 331 ms | 0 |
| Thu 12 | 0 | 0.0 | 302 ms | 0 |
| Thu 14 | 0 | 0.0 | 275 ms | 0 |
| Thu 17 | 0 | 0.0 | 208 ms | 0 |
| Thu 19 | 0 | 0.0 | 295 ms | 0 |
| Thu 21 | 0 | 0.0 | 151 ms | 0 |
| Thu 23 | 0 | 0.0 | 320 ms | 0 |
| Fri 01 | 0 | 0.0 | 290 ms | 0 |
| Fri 02 | 0 | 0.0 | 326 ms | 0 |
| Fri 04 | 0 | 0.0 | 312 ms | 0 |
| Fri 06 | 0 | 0.0 | 266 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 RamNode 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 RamNode goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send RamNode alerts to Slack, Discord or a webhook — free.
RamNode, at ramnode.com, is one of the Money services we monitor. RamNode Cloud VPS from $4/mo. KVM with NVMe, hourly billing, IPv4 included, and no surprise egress bills. 99.99% uptime across US and EU.
RamNode publishes an official status page at status.ramnode.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: 280 ms average, 151–331 ms range across 12 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public RamNode incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
280 ms on average over the last 24 hours (151–331 ms).
Yes, at https://status.ramnode.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 RamNode here at once, the problem is on RamNode'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 RamNode. 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.