User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
foxpass.com · Cloud & developer
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what 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, and places with fewer than 3 reports are not shown. Updates every minute.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 560 ms · 2 min ago.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 05:00 | 0 | 0.0 | 155 ms | 0 |
| 05:15 | 0 | 0.0 | 691 ms | 0 |
| 05:30 | 0 | 0.0 | 921 ms | 0 |
| 05:45 | 0 | 0.0 | 205 ms | 0 |
| 06:00 | 0 | 0.0 | 656 ms | 0 |
| 06:15 | 0 | 0.0 | 473 ms | 0 |
| 06:30 | 0 | 0.0 | 539 ms | 0 |
| 06:45 | 0 | 0.0 | 213 ms | 0 |
| 07:00 | 0 | 0.0 | 380 ms | 0 |
| 07:15 | 0 | 0.0 | 352 ms | 0 |
| 07:30 | 0 | 0.0 | 376 ms | 0 |
| 07:45 | 0 | 0.0 | 196 ms | 0 |
| 08:00 | 0 | 0.0 | 837 ms | 0 |
| 08:15 | 0 | 0.0 | 403 ms | 0 |
| 08:30 | 0 | 0.0 | 688 ms | 0 |
| 08:45 | 0 | 0.0 | 587 ms | 0 |
| 09:00 | 0 | 0.0 | 355 ms | 0 |
| 09:15 | 0 | 0.0 | 268 ms | 0 |
| 09:30 | 0 | 0.0 | 155 ms | 0 |
| 09:45 | 0 | 0.0 | 213 ms | 0 |
| 10:00 | 0 | 0.0 | 192 ms | 0 |
| 10:15 | 0 | 0.0 | 205 ms | 0 |
| 10:30 | 0 | 0.0 | 544 ms | 0 |
| 10:45 | 0 | 0.0 | 165 ms | 0 |
| 11:00 | 0 | 0.0 | 495 ms | 0 |
| 11:15 | 0 | 0.0 | 401 ms | 0 |
| 11:30 | 0 | 0.0 | 226 ms | 0 |
| 11:45 | 0 | 0.0 | 539 ms | 0 |
| 12:00 | 0 | 0.0 | 250 ms | 0 |
| 12:15 | 0 | 0.0 | 494 ms | 0 |
| 12:30 | 0 | 0.0 | 662 ms | 0 |
| 12:45 | 0 | 0.0 | 321 ms | 0 |
| 13:00 | 0 | 0.0 | 478 ms | 0 |
| 13:15 | 0 | 0.0 | 776 ms | 0 |
| 13:30 | 0 | 0.0 | 499 ms | 0 |
| 13:45 | 0 | 0.0 | 342 ms | 0 |
| 14:00 | 0 | 0.0 | 187 ms | 0 |
| 14:15 | 0 | 0.0 | 400 ms | 0 |
| 14:30 | 0 | 0.0 | 583 ms | 0 |
| 14:45 | 0 | 0.0 | 1021 ms | 0 |
| 15:00 | 0 | 0.0 | 192 ms | 0 |
| 15:15 | 0 | 0.0 | 1021 ms | 0 |
| 15:30 | 0 | 0.0 | 511 ms | 0 |
| 15:45 | 0 | 0.0 | 338 ms | 0 |
| 16:00 | 0 | 0.0 | 254 ms | 0 |
| 16:15 | 0 | 0.0 | 726 ms | 0 |
| 16:30 | 0 | 0.0 | 405 ms | 0 |
| 16:45 | 0 | 0.0 | 528 ms | 0 |
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Foxpass 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 Foxpass goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Foxpass alerts to Slack, Discord or a webhook — free.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
If Foxpass is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on Foxpass's side.
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.