User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
fingerprint.com · Cloud & developer
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 55 min ago. Last stored result reached it in 167 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 03 | 0 | 0.0 | 217 ms | 0 |
| Tue 05 | 0 | 0.0 | 129 ms | 0 |
| Tue 07 | 0 | 0.0 | 199 ms | 0 |
| Tue 09 | 0 | 0.0 | 94 ms | 0 |
| Tue 11 | 0 | 0.0 | 264 ms | 0 |
| Tue 14 | 0 | 0.0 | 160 ms | 0 |
| Tue 16 | 0 | 0.0 | 185 ms | 0 |
| Tue 18 | 0 | 0.0 | 244 ms | 0 |
| Tue 20 | 0 | 0.0 | 249 ms | 0 |
| Tue 23 | 0 | 0.0 | 113 ms | 0 |
| Wed 01 | 0 | 0.0 | 233 ms | 0 |
| Wed 03 | 0 | 0.0 | 304 ms | 0 |
| Wed 05 | 0 | 0.0 | 206 ms | 0 |
| Wed 07 | 0 | 0.0 | 193 ms | 0 |
| Wed 08 | 0 | 0.0 | 84 ms | 0 |
| Wed 10 | 0 | 0.0 | 159 ms | 0 |
| Wed 12 | 0 | 0.0 | 275 ms | 0 |
| Wed 14 | 0 | 0.0 | 97 ms | 0 |
| Wed 16 | 0 | 0.0 | 251 ms | 0 |
| Wed 18 | 0 | 0.0 | 612 ms | 0 |
| Wed 21 | 0 | 0.0 | 466 ms | 0 |
| Wed 23 | 0 | 0.0 | 235 ms | 0 |
| Thu 01 | 0 | 0.0 | 130 ms | 0 |
| Thu 03 | 0 | 0.0 | 238 ms | 0 |
| Thu 05 | 0 | 0.0 | 239 ms | 0 |
| Thu 07 | 0 | 0.0 | 266 ms | 0 |
| Thu 09 | 0 | 0.0 | 226 ms | 0 |
| Thu 11 | 0 | 0.0 | 267 ms | 0 |
| Thu 13 | 0 | 0.0 | 246 ms | 0 |
| Thu 15 | 0 | 0.0 | 254 ms | 0 |
| Thu 17 | 0 | 0.0 | 345 ms | 0 |
| Thu 19 | 0 | 0.0 | 269 ms | 0 |
| Thu 21 | 0 | 0.0 | 228 ms | 0 |
| Fri 00 | 0 | 0.0 | 211 ms | 0 |
| Fri 02 | 0 | 0.0 | 147 ms | 0 |
| Fri 04 | 0 | 0.0 | 224 ms | 0 |
| Fri 06 | 0 | 0.0 | 314 ms | 0 |
| Fri 08 | 0 | 0.0 | 212 ms | 0 |
| Fri 09 | 0 | 0.0 | 95 ms | 0 |
| Fri 11 | 0 | 0.0 | 137 ms | 0 |
| Fri 12 | 0 | 0.0 | 262 ms | 0 |
| Fri 14 | 0 | 0.0 | 125 ms | 0 |
| Fri 16 | 0 | 0.0 | 264 ms | 0 |
| Fri 17 | 0 | 0.0 | 187 ms | 0 |
| Fri 19 | 0 | 0.0 | 207 ms | 0 |
| Fri 21 | 0 | 0.0 | 109 ms | 0 |
| Fri 23 | 0 | 0.0 | 236 ms | 0 |
| Sat 01 | 0 | 0.0 | 167 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 Fingerprint 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 Fingerprint goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Fingerprint alerts to Slack, Discord or a webhook — free.
Fingerprint, at fingerprint.com, is one of the Cloud & developer services we monitor. The Fingerprint device intelligence platform works across web and mobile applications to identify all visitors with industry-leading accuracy — even if they’re anonymous.
Fingerprint publishes an official status page at status.fingerprint.com; when we can read it, its incident level is folded into the status shown here.
Common problems for cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
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: 192 ms average, 95–314 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 Fingerprint incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
192 ms on average over the last 24 hours (95–314 ms).
Yes, at https://status.fingerprint.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report Fingerprint here at once, the problem is on Fingerprint'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 Fingerprint. 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.