FingerprintJS had 23 outages in the last 2 years totaling 57h 24m of downtime — averaging 0.9 incidents per month.
There were 23 FingerprintJS outages since July 3, 2025 totaling 57h 24m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently experiencing a data ingestion delay that is affecting dashboards. There is no data loss as a result of this issue. Our team is working to restore normal operations.
All regions have been restored, and services are operating normally.
We’re currently observing elevated error rates and higher-than-normal latency in our US region for our Ingress endpoint. Our engineers are investigating.
Services started to come back online. We are monitoring the services to ensure their health
Server API performance in Global (US) is currently degraded. We're investigating the cause and working on remediation.
Server API performance has fully recovered. We will continue to monitor the situation.
A small number of trial customers experienced issues loading identification data on the Dashboard Identification page. The incident lasted approximately 20 hours. Identification services were not affected at any point. The fix was deployed on April 24, 2026. We are monitoring for full recovery.
We have observed a small percentage of requests to Identification and Server API failing. Our engineers have identified the root cause and begun remediation.
Issues have been resolved, and we will continue to monitor.
We are currently investigating an issue affecting the Public Management API. The dashboard and identification services are not impacted. We will provide an update as soon as we have more information.
The issue has been resolved and the team is monitoring to confirm stability. All services are operating as expected.
JS Agent CDN recovered
JS Agent CDN currently returns 403 for a portion of requests which makes JS Agent unavailable. We are working on a fix.
The issue has been resolved.
We are currently investigating an issue causing degradation in the creation of new accounts. Identification services for existing customers are operating normally and are not affected. Our engineering team is actively working to identify the root cause and implement a fix. We will provide further updates as more information becomes
Resolved — Account Creation Degradation The issue causing degradation in the creation of new accounts has been resolved. All services are now operating normally. Identification services for existing customers were not impacted during the incident. We will continue to monitor the system to ensure ongoing stability.
We experienced a brief period of increased error rates and timeouts on the Ingress endpoint in the EU region. The issue lasted for approximately one minute and has since been resolved. All systems are currently operating normally.
System is stable
Sealed Client Results feature does not work for certain customers due to an internal issue. https://dev.fingerprint.com/docs/sealed-client-results We are working on a fix
The issue has been resolved
We’re currently experiencing an issue affecting the Fingerprint Portal. Login is temporarily unavailable, and some portal actions may not work as expected. All identification services and related APIs remain fully operational and are not affected.
The issue with the Fingerprint Portal has been resolved.
We are currently experiencing degraded performance on our custom subdomains infrastructure. A small subset of requests may see increased latency or intermittent errors. This is likely caused by service interruptions from Cloudflare. Our core API endpoints remain fully operational.
The incident impacting custom subdomains infrastructure has been resolved. Cloudflare has mitigated their underlying issue and our traffic, error rates, and latency for custom subdomains have returned to normal levels. Our core API endpoints were unaffected throughout. We will continue to monitor, but no further impact is expected.
We are currently investigating an issue with our event storage system, at this time our Server API is impacted as well as certain dashboard capabilities such as search, CSV export.
We have rolled back the change that triggered the incident and have fully recovered.
Identification - Global (US) recovered
Dashboard recovered
Majority of our services in the US region are currently being impacted by an underlying issue with a vendor that we are actively investigating.
We are now fully back to normal operation.
We are investigating increased error rates for a small percentage of traffic to our identification service. We are investigating the issue now.
We have issued a fix for all regions, all systems are operational.
Very small % of requests for a small subset of customers might occasionally experience failed identification requests. We are investigating the problem.
We have implemented a fix and will be monitoring to confirm resolution. The issue occurred between 09:00 UTC to 16:00 UTC on Oct 7, 2025 and impacted less than 0.0012% of requests
From September 23rd 22:45 UTC to October 1st 20:31 UTC the "Update Event" method for our Server API in all regions accepted updates but inconsistently applied the updates to one of our backend databases. No update data has been lost, and all records of updates were maintained. However, updates were not applied successfully to one of our databases, this results in the update not being visible on the event when queried via our server API, dashboard, or CSV export functionality for events created in this timeframe. The underlying bug has been fixed as of October 1st 20:31 UTC, and we are working on backfilling the data. We will re-apply updates from this timeframe to the database that was inconsistent. We will update this status page as we make progress.
All event data backfill complete. All services operational.
We're currently observing increased latency in webhook processing in our US region. We’re actively working to resolve the issue.
All systems are operational at this time.
Due to an internal issue on our API gateway a small portion of requests in APS1 region (Asia) could fail with http code 500 for some customers. The issue took place between 5:43 and 5:44 UTC.
This issue was resolved.
We're currently observing increased latency and error rates in our US region. Our engineers are investigating the issue.
Services have stabilized, error rates have decreased and latency is back to normal. We will continue monitoring this.