User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
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 57 min ago. Last stored result reached it in 101 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 15 | 0 | 0.0 | 99 ms | 0 |
| Mon 17 | 0 | 0.0 | 127 ms | 0 |
| Mon 19 | 0 | 0.0 | 212 ms | 0 |
| Mon 21 | 0 | 0.0 | 257 ms | 0 |
| Mon 23 | 0 | 0.0 | 186 ms | 0 |
| Tue 01 | 0 | 0.0 | 78 ms | 0 |
| Tue 04 | 0 | 0.0 | 63 ms | 0 |
| Tue 06 | 0 | 0.0 | 91 ms | 0 |
| Tue 08 | 0 | 0.0 | 66 ms | 0 |
| Tue 10 | 0 | 0.0 | 56 ms | 0 |
| Tue 12 | 0 | 0.0 | 88 ms | 0 |
| Tue 14 | 0 | 0.0 | 131 ms | 0 |
| Tue 17 | 0 | 0.0 | 118 ms | 0 |
| Tue 19 | 0 | 0.0 | 48 ms | 0 |
| Tue 21 | 0 | 0.0 | 98 ms | 0 |
| Tue 23 | 0 | 0.0 | 124 ms | 0 |
| Wed 02 | 0 | 0.0 | 108 ms | 0 |
| Wed 04 | 0 | 0.0 | 84 ms | 0 |
| Wed 06 | 0 | 0.0 | 157 ms | 0 |
| Wed 08 | 0 | 0.0 | 74 ms | 0 |
| Wed 11 | 0 | 0.0 | 85 ms | 0 |
| Wed 13 | 0 | 0.0 | 169 ms | 0 |
| Wed 15 | 0 | 0.0 | 156 ms | 0 |
| Wed 17 | 0 | 0.0 | 141 ms | 0 |
| Wed 19 | 0 | 0.0 | 159 ms | 0 |
| Wed 21 | 0 | 0.0 | 124 ms | 0 |
| Wed 23 | 0 | 0.0 | 138 ms | 0 |
| Thu 02 | 0 | 0.0 | 259 ms | 0 |
| Thu 04 | 0 | 0.0 | 64 ms | 0 |
| Thu 06 | 0 | 0.0 | 109 ms | 0 |
| Thu 08 | 0 | 0.0 | 106 ms | 0 |
| Thu 10 | 0 | 0.0 | 137 ms | 0 |
| Thu 12 | 0 | 0.0 | 49 ms | 0 |
| Thu 14 | 0 | 0.0 | 74 ms | 0 |
| Thu 16 | 0 | 0.0 | 217 ms | 0 |
| Thu 18 | 0 | 0.0 | 135 ms | 0 |
| Thu 20 | 0 | 0.0 | 114 ms | 0 |
| Thu 22 | 0 | 0.0 | 66 ms | 0 |
| Fri 00 | 0 | 0.0 | 76 ms | 0 |
| Fri 02 | 0 | 0.0 | 145 ms | 0 |
| Fri 04 | 0 | 0.0 | 113 ms | 0 |
| Fri 05 | 0 | 0.0 | 91 ms | 0 |
| Fri 08 | 0 | 0.0 | 52 ms | 0 |
| Fri 10 | 0 | 0.0 | 66 ms | 0 |
| Fri 11 | 0 | 0.0 | 49 ms | 0 |
| Fri 13 | 0 | 0.0 | 123 ms | 0 |
| Fri 15 | 0 | 0.0 | 168 ms | 0 |
| Fri 17 | 0 | 0.0 | 101 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 Ripio 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 Ripio goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Ripio alerts to Slack, Discord or a webhook — free.
We track Ripio (ripio.com) as part of the Cloud & developer group. Desarrollá las economías on-chain con Ripio: stablecoins en moneda local, rampas instantáneas e infraestructura white-label para empresas en Latinoamérica.
Ripio publishes an official status page at status.ripio.com; when we can read it, its incident level is folded into the status shown here.
Common problems for cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
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: 96 ms average, 26–168 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 Ripio incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
96 ms on average over the last 24 hours (26–168 ms).
Yes, at https://status.ripio.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report Ripio here at once, the problem is on Ripio'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 Ripio. 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.