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 13 min ago. Last stored result reached it in 210 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 17 | 0 | 0.0 | 259 ms | 0 |
| Tue 19 | 0 | 0.0 | 431 ms | 0 |
| Tue 22 | 0 | 0.0 | 161 ms | 0 |
| Wed 00 | 0 | 0.0 | 219 ms | 0 |
| Wed 02 | 0 | 0.0 | 381 ms | 0 |
| Wed 04 | 0 | 0.0 | 250 ms | 0 |
| Wed 07 | 0 | 0.0 | 463 ms | 0 |
| Wed 09 | 0 | 0.0 | 273 ms | 0 |
| Wed 11 | 0 | 0.0 | 246 ms | 0 |
| Wed 13 | 0 | 0.0 | 291 ms | 0 |
| Wed 15 | 0 | 0.0 | 216 ms | 0 |
| Wed 17 | 0 | 0.0 | 306 ms | 0 |
| Wed 20 | 0 | 0.0 | 293 ms | 0 |
| Wed 22 | 0 | 0.0 | 191 ms | 0 |
| Thu 00 | 0 | 0.0 | 249 ms | 0 |
| Thu 02 | 0 | 0.0 | 353 ms | 0 |
| Thu 04 | 0 | 0.0 | 270 ms | 0 |
| Thu 06 | 0 | 0.0 | 206 ms | 0 |
| Thu 08 | 0 | 0.0 | 252 ms | 0 |
| Thu 10 | 0 | 0.0 | 348 ms | 0 |
| Thu 12 | 0 | 0.0 | 192 ms | 0 |
| Thu 14 | 0 | 0.0 | 180 ms | 0 |
| Thu 17 | 0 | 0.0 | 335 ms | 0 |
| Thu 19 | 0 | 0.0 | 224 ms | 0 |
| Thu 21 | 0 | 0.0 | 234 ms | 0 |
| Thu 23 | 0 | 0.0 | 315 ms | 0 |
| Fri 01 | 0 | 0.0 | 252 ms | 0 |
| Fri 03 | 0 | 0.0 | 205 ms | 0 |
| Fri 05 | 0 | 0.0 | 281 ms | 0 |
| Fri 07 | 0 | 0.0 | 293 ms | 0 |
| Fri 09 | 0 | 0.0 | 214 ms | 0 |
| Fri 11 | 0 | 0.0 | 171 ms | 0 |
| Fri 13 | 0 | 0.0 | 213 ms | 0 |
| Fri 15 | 0 | 0.0 | 344 ms | 0 |
| Fri 17 | 0 | 0.0 | 345 ms | 0 |
| Fri 18 | 0 | 0.0 | 496 ms | 0 |
| Fri 19 | 0 | 0.0 | 223 ms | 0 |
| Fri 20 | 0 | 0.0 | 258 ms | 0 |
| Fri 22 | 0 | 0.0 | 232 ms | 0 |
| Sat 00 | 0 | 0.0 | 247 ms | 0 |
| Sat 02 | 0 | 0.0 | 183 ms | 0 |
| Sat 03 | 0 | 0.0 | 320 ms | 0 |
| Sat 05 | 0 | 0.0 | 264 ms | 0 |
| Sat 06 | 0 | 0.0 | 284 ms | 0 |
| Sat 08 | 0 | 0.0 | 285 ms | 0 |
| Sat 10 | 0 | 0.0 | 181 ms | 0 |
| Sat 12 | 0 | 0.0 | 175 ms | 0 |
| Sat 15 | 0 | 0.0 | 210 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 Infosec.exchange 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 Infosec.exchange goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Infosec.exchange alerts to Slack, Discord or a webhook — free.
We track Infosec.exchange (infosec.exchange) as part of the Money group. A Mastodon instance for info/cyber security-minded people.
Infosec.exchange publishes an official status page at status.infosec.exchange; when we can read it, its incident level is folded into the status shown here.
Typical issues with 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: 263 ms average, 175–496 ms range across 16 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Infosec.exchange incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
263 ms on average over the last 24 hours (175–496 ms).
Yes, at https://status.infosec.exchange.
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 Infosec.exchange here at once, the problem is on Infosec.exchange'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 Infosec.exchange. 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.