User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Money
Is Rupt down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → rupt.dev—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
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.
Live outage map
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.
What's broken
Recent reports
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.
Our checks
Reaching it
Last checked 11 min ago. Last stored result reached it in 88 ms.
Official status
All clear
No active incidents in the official feed Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 14 | 0 | 0.0 | 84 ms | 0 |
| Mon 16 | 0 | 0.0 | 90 ms | 0 |
| Mon 18 | 0 | 0.0 | 119 ms | 0 |
| Mon 20 | 0 | 0.0 | 204 ms | 0 |
| Mon 22 | 0 | 0.0 | 133 ms | 0 |
| Tue 00 | 0 | 0.0 | 107 ms | 0 |
| Tue 02 | 0 | 0.0 | 112 ms | 0 |
| Tue 04 | 0 | 0.0 | 216 ms | 0 |
| Tue 07 | 0 | 0.0 | 71 ms | 0 |
| Tue 09 | 0 | 0.0 | 97 ms | 0 |
| Tue 11 | 0 | 0.0 | 112 ms | 0 |
| Tue 13 | 0 | 0.0 | 66 ms | 0 |
| Tue 15 | 0 | 0.0 | 81 ms | 0 |
| Tue 17 | 0 | 0.0 | 87 ms | 0 |
| Tue 20 | 0 | 0.0 | 130 ms | 0 |
| Tue 22 | 0 | 0.0 | 87 ms | 0 |
| Wed 00 | 0 | 0.0 | 202 ms | 0 |
| Wed 02 | 0 | 0.0 | 106 ms | 0 |
| Wed 05 | 0 | 0.0 | 121 ms | 0 |
| Wed 07 | 0 | 0.0 | 83 ms | 0 |
| Wed 09 | 0 | 0.0 | 121 ms | 0 |
| Wed 11 | 0 | 0.0 | 114 ms | 0 |
| Wed 14 | 0 | 0.0 | 87 ms | 0 |
| Wed 16 | 0 | 0.0 | 156 ms | 0 |
| Wed 18 | 0 | 0.0 | 220 ms | 0 |
| Wed 20 | 0 | 0.0 | 89 ms | 0 |
| Wed 22 | 0 | 0.0 | 75 ms | 0 |
| Thu 00 | 0 | 0.0 | 146 ms | 0 |
| Thu 03 | 0 | 0.0 | 112 ms | 0 |
| Thu 05 | 0 | 0.0 | 77 ms | 0 |
| Thu 07 | 0 | 0.0 | 73 ms | 0 |
| Thu 09 | 0 | 0.0 | 101 ms | 0 |
| Thu 11 | 0 | 0.0 | 58 ms | 0 |
| Thu 13 | 0 | 0.0 | 66 ms | 0 |
| Thu 15 | 0 | 0.0 | 74 ms | 0 |
| Thu 17 | 0 | 0.0 | 89 ms | 0 |
| Thu 19 | 0 | 0.0 | 132 ms | 0 |
| Thu 21 | 0 | 0.0 | 62 ms | 0 |
| Thu 23 | 0 | 0.0 | 110 ms | 0 |
| Fri 01 | 0 | 0.0 | 101 ms | 0 |
| Fri 03 | 0 | 0.0 | 70 ms | 0 |
| Fri 05 | 0 | 0.0 | 231 ms | 0 |
| Fri 08 | 0 | 0.0 | 44 ms | 0 |
| Fri 10 | 0 | 0.0 | 107 ms | 0 |
| Fri 11 | 0 | 0.0 | 90 ms | 0 |
| Fri 13 | 0 | 0.0 | 111 ms | 0 |
| Fri 15 | 0 | 0.0 | 63 ms | 0 |
| Fri 17 | 0 | 0.0 | 88 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
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.
Embed this status: free live Rupt badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for Rupt yet. Outages of 10 minutes or more get their own page here.
Having trouble with Rupt?
One report per service every 10 minutes from this network. No account.
Follow Rupt
Get an email when Rupt goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Rupt alerts to Slack, Discord or a webhook — free.
About Rupt
Rupt, at rupt.dev, is one of the Money services we monitor. Rupt helps you know which users and agents you can trust — and prevent fraud and abuse. From signup to payment, detect account sharing, account takeover, fake accounts, bots, and other abuse with minimal developer effort.
Rupt publishes an official status page at status.rupt.dev; 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 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 101 ms average, 44–231 ms range across 12 successful checks.
Questions
Is Rupt down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Rupt last down?
We have not recorded a public Rupt incident since monitoring began 8 days ago.
What is Rupt's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Rupt respond?
101 ms on average over the last 24 hours (44–231 ms).
Does Rupt have an official status page?
Yes, at https://status.rupt.dev.
Rupt not working for me but the status is fine. What now?
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 Rupt here at once, the problem is on Rupt'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 Rupt. 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.