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 1 hr ago. Last stored result reached it in 50 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 21 | 0 | 0.0 | 72 ms | 0 |
| Mon 23 | 0 | 0.0 | 111 ms | 0 |
| Tue 01 | 0 | 0.0 | 76 ms | 0 |
| Tue 03 | 0 | 0.0 | 48 ms | 0 |
| Tue 05 | 0 | 0.0 | 234 ms | 0 |
| Tue 07 | 0 | 0.0 | 49 ms | 0 |
| Tue 10 | 0 | 0.0 | 34 ms | 0 |
| Tue 12 | 0 | 0.0 | 116 ms | 0 |
| Tue 14 | 0 | 0.0 | 52 ms | 0 |
| Tue 16 | 0 | 0.0 | 107 ms | 0 |
| Tue 17 | 0 | 0.0 | 77 ms | 0 |
| Tue 20 | 0 | 0.0 | 92 ms | 0 |
| Tue 22 | 0 | 0.0 | 67 ms | 0 |
| Wed 00 | 0 | 0.0 | 87 ms | 0 |
| Wed 02 | 0 | 0.0 | 39 ms | 0 |
| Wed 05 | 0 | 0.0 | 88 ms | 0 |
| Wed 07 | 0 | 0.0 | 92 ms | 0 |
| Wed 09 | 0 | 0.0 | 100 ms | 0 |
| Wed 11 | 0 | 0.0 | 267 ms | 0 |
| Wed 13 | 0 | 0.0 | 121 ms | 0 |
| Wed 15 | 0 | 0.0 | 79 ms | 0 |
| Wed 18 | 0 | 0.0 | 69 ms | 0 |
| Wed 20 | 0 | 0.0 | 240 ms | 0 |
| Wed 22 | 0 | 0.0 | 65 ms | 0 |
| Thu 00 | 0 | 0.0 | 61 ms | 0 |
| Thu 02 | 0 | 0.0 | 44 ms | 0 |
| Thu 04 | 0 | 0.0 | 69 ms | 0 |
| Thu 06 | 0 | 0.0 | 59 ms | 0 |
| Thu 08 | 0 | 0.0 | 37 ms | 0 |
| Thu 10 | 0 | 0.0 | 22 ms | 0 |
| Thu 11 | 0 | 0.0 | 95 ms | 0 |
| Thu 13 | 0 | 0.0 | 116 ms | 0 |
| Thu 15 | 0 | 0.0 | 25 ms | 0 |
| Thu 17 | 0 | 0.0 | 143 ms | 0 |
| Thu 19 | 0 | 0.0 | 51 ms | 0 |
| Thu 22 | 0 | 0.0 | 117 ms | 0 |
| Fri 00 | 0 | 0.0 | 61 ms | 0 |
| Fri 02 | 0 | 0.0 | 126 ms | 0 |
| Fri 04 | 0 | 0.0 | 40 ms | 0 |
| Fri 06 | 0 | 0.0 | 98 ms | 0 |
| Fri 08 | 0 | 0.0 | 111 ms | 0 |
| Fri 10 | 0 | 0.0 | 39 ms | 0 |
| Fri 12 | 0 | 0.0 | 43 ms | 0 |
| Fri 14 | 0 | 0.0 | 55 ms | 0 |
| Fri 16 | 0 | 0.0 | 139 ms | 0 |
| Fri 18 | 0 | 0.0 | 187 ms | 0 |
| Fri 19 | 0 | 0.0 | 37 ms | 0 |
| Fri 20 | 0 | 0.0 | 50 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 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for AiSDR 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 AiSDR goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send AiSDR alerts to Slack, Discord or a webhook — free.
We track AiSDR (aisdr.com) as part of the Money group. AiSDR finds in-market buyers using real-time signals, then reaches out with messages that sound like your best rep wrote them. Pay $1.50 per person prospected.
AiSDR publishes an official status page at status.aisdr.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 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 87 ms average, 37–187 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public AiSDR incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
87 ms on average over the last 24 hours (37–187 ms).
Yes, at https://status.aisdr.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 AiSDR here at once, the problem is on AiSDR'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 AiSDR. 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.