User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Social
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 2 hr ago. Last stored result reached it in 208 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 01 | 0 | 0.0 | 104 ms | 0 |
| Tue 04 | 0 | 0.0 | 117 ms | 0 |
| Tue 06 | 0 | 0.0 | 108 ms | 0 |
| Tue 08 | 0 | 0.0 | 52 ms | 0 |
| Tue 10 | 0 | 0.0 | 74 ms | 0 |
| Tue 12 | 0 | 0.0 | 97 ms | 0 |
| Tue 14 | 0 | 0.0 | 110 ms | 0 |
| Tue 17 | 0 | 0.0 | 113 ms | 0 |
| Tue 19 | 0 | 0.0 | 79 ms | 0 |
| Tue 21 | 0 | 0.0 | 155 ms | 0 |
| Tue 23 | 0 | 0.0 | 160 ms | 0 |
| Wed 02 | 0 | 0.0 | 24 ms | 0 |
| Wed 04 | 0 | 0.0 | 45 ms | 0 |
| Wed 06 | 0 | 0.0 | 332 ms | 0 |
| Wed 08 | 0 | 0.0 | 55 ms | 0 |
| Wed 11 | 0 | 0.0 | 84 ms | 0 |
| Wed 13 | 0 | 0.0 | 435 ms | 0 |
| Wed 15 | 0 | 0.0 | 156 ms | 0 |
| Wed 17 | 0 | 0.0 | 210 ms | 0 |
| Wed 19 | 0 | 0.0 | 119 ms | 0 |
| Wed 21 | 0 | 0.0 | 529 ms | 0 |
| Thu 00 | 0 | 0.0 | 179 ms | 0 |
| Thu 02 | 0 | 0.0 | 129 ms | 0 |
| Thu 04 | 0 | 0.0 | 220 ms | 0 |
| Thu 06 | 0 | 0.0 | 124 ms | 0 |
| Thu 08 | 0 | 0.0 | 140 ms | 0 |
| Thu 10 | 0 | 0.0 | 52 ms | 0 |
| Thu 12 | 0 | 0.0 | 306 ms | 0 |
| Thu 14 | 0 | 0.0 | 135 ms | 0 |
| Thu 16 | 0 | 0.0 | 252 ms | 0 |
| Thu 18 | 0 | 0.0 | 126 ms | 0 |
| Thu 20 | 0 | 0.0 | 106 ms | 0 |
| Thu 22 | 0 | 0.0 | 175 ms | 0 |
| Fri 00 | 0 | 0.0 | 241 ms | 0 |
| Fri 03 | 0 | 0.0 | 70 ms | 0 |
| Fri 05 | 0 | 0.0 | 159 ms | 0 |
| Fri 07 | 0 | 0.0 | 60 ms | 0 |
| Fri 08 | 0 | 0.0 | 339 ms | 0 |
| Fri 10 | 0 | 0.0 | 91 ms | 0 |
| Fri 11 | 0 | 0.0 | 105 ms | 0 |
| Fri 13 | 0 | 0.0 | 96 ms | 0 |
| Fri 15 | 0 | 0.0 | 135 ms | 0 |
| Fri 17 | 0 | 0.0 | 634 ms | 0 |
| Fri 19 | 0 | 0.0 | 51 ms | 0 |
| Fri 21 | 0 | 0.0 | 86 ms | 0 |
| Fri 23 | 0 | 0.0 | 271 ms | 0 |
| Sat 01 | 0 | 0.0 | 133 ms | 0 |
| Sat 03 | 0 | 0.0 | 134 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 VaultCord 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 VaultCord goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send VaultCord alerts to Slack, Discord or a webhook — free.
VaultCord, at vaultcord.com, is one of the Social services we monitor. Securely back up your Discord server—channels, members, roles, messages & more. Block alts, VPNs, and bots. Custom verify pages. Try VaultCord free today!
VaultCord publishes an official status page at status.vaultcord.com; when we can read it, its incident level is folded into the status shown here.
Common problems for social services: feeds not loading, posts or messages not sending, and login loops.
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: 181 ms average, 51–634 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 VaultCord incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
181 ms on average over the last 24 hours (51–634 ms).
Yes, at https://status.vaultcord.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For social services, watch for feeds not loading, posts or messages not sending, and login loops. If many people report VaultCord here at once, the problem is on VaultCord'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 VaultCord. 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.