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 41 min ago. Last stored result reached it in 94 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 20 | 0 | 0.0 | 235 ms | 0 |
| Tue 22 | 0 | 0.0 | 139 ms | 0 |
| Wed 00 | 0 | 0.0 | 122 ms | 0 |
| Wed 02 | 0 | 0.0 | 240 ms | 0 |
| Wed 05 | 0 | 0.0 | 126 ms | 0 |
| Wed 07 | 0 | 0.0 | 123 ms | 0 |
| Wed 09 | 0 | 0.0 | 189 ms | 0 |
| Wed 12 | 0 | 0.0 | 104 ms | 0 |
| Wed 14 | 0 | 0.0 | 149 ms | 0 |
| Wed 16 | 0 | 0.0 | 545 ms | 0 |
| Wed 18 | 0 | 0.0 | 315 ms | 0 |
| Wed 20 | 0 | 0.0 | 309 ms | 0 |
| Wed 22 | 0 | 0.0 | 209 ms | 0 |
| Thu 01 | 0 | 0.0 | 226 ms | 0 |
| Thu 03 | 0 | 0.0 | 197 ms | 0 |
| Thu 05 | 0 | 0.0 | 200 ms | 0 |
| Thu 07 | 0 | 0.0 | 179 ms | 0 |
| Thu 09 | 0 | 0.0 | 175 ms | 0 |
| Thu 11 | 0 | 0.0 | 121 ms | 0 |
| Thu 13 | 0 | 0.0 | 276 ms | 0 |
| Thu 15 | 0 | 0.0 | 193 ms | 0 |
| Thu 17 | 0 | 0.0 | 138 ms | 0 |
| Thu 19 | 0 | 0.0 | 240 ms | 0 |
| Thu 21 | 0 | 0.0 | 130 ms | 0 |
| Thu 23 | 0 | 0.0 | 175 ms | 0 |
| Fri 01 | 0 | 0.0 | 232 ms | 0 |
| Fri 03 | 0 | 0.0 | 114 ms | 0 |
| Fri 05 | 0 | 0.0 | 193 ms | 0 |
| Fri 07 | 0 | 0.0 | 217 ms | 0 |
| Fri 08 | 0 | 0.0 | 121 ms | 0 |
| Fri 10 | 0 | 0.0 | 109 ms | 0 |
| Fri 11 | 0 | 0.0 | 202 ms | 0 |
| Fri 13 | 0 | 0.0 | 164 ms | 0 |
| Fri 15 | 0 | 0.0 | 97 ms | 0 |
| Fri 17 | 0 | 0.0 | 226 ms | 0 |
| Fri 19 | 0 | 0.0 | 227 ms | 0 |
| Fri 20 | 0 | 0.0 | 121 ms | 0 |
| Fri 22 | 0 | 0.0 | 232 ms | 0 |
| Sat 00 | 0 | 0.0 | 130 ms | 0 |
| Sat 01 | 0 | 0.0 | 112 ms | 0 |
| Sat 03 | 0 | 0.0 | 171 ms | 0 |
| Sat 05 | 0 | 0.0 | 219 ms | 0 |
| Sat 07 | 0 | 0.0 | 158 ms | 0 |
| Sat 10 | 0 | 0.0 | 97 ms | 0 |
| Sat 12 | 0 | 0.0 | 174 ms | 0 |
| Sat 14 | 0 | 0.0 | 61 ms | 0 |
| Sat 17 | 0 | 0.0 | 171 ms | 0 |
| Sat 19 | 0 | 0.0 | 94 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 9 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Visp 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 Visp goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send confirmed down and recovery alerts to Slack, Discord or a webhook — free. Early warnings are part of Owner Alerts.
Visp, at visp.net, is one of the Money services we monitor. Visp.net provides complete ISP billing software and automation to streamline operations, control costs, save time, and grow your business.
Visp publishes an official status page at status.visp.net; 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 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 146 ms average, 61–232 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 Visp incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
146 ms on average over the last 24 hours (61–232 ms).
Yes, at https://status.visp.net.
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 Visp here at once, the problem is on Visp'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 Visp. 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.