Fingerprint Outage History

32 incidents recorded over the last 365 days, 32 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Fingerprint status100.00% uptime history

Every Recorded Fingerprint Incident

Fingerprint incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 26, 2026Sign-ups and onboarding are currently not available229h 45mResolved
Oct 20, 2026Ingress sealed results encoding issues370h 32mResolved
Oct 16, 2026Increased Latency on Management API470h 21mResolved
Oct 9, 2026Ingress endpoint degradations630h 35mResolved
Oct 5, 2026Delayed Dashboard & Analytics Data733h 48mResolved
Sep 28, 2026Ingress endpoint degradations906h 32mResolved
Sep 25, 2026Ingress endpoint degradations978h 24mResolved
Sep 23, 2026Degradation in the dashboard1015h 23mResolved
Sep 21, 2026Degraded search API1065h 54mResolved
Sep 17, 2026Webhooks Degradation 1179h 58mResolved
Sep 16, 2026Ingress endpoint degradations1204h 11mResolved
Sep 15, 2026Observed Increased Latency for Events1207h 32mResolved
Sep 11, 2026Visitor API and Search Event API degradation1323h 38mResolved
Sep 9, 2026Ingress endpoint degredation1355h 42mResolved
Sep 8, 2026Ingress endpoint degredation1375h 7mResolved
Sep 1, 2026Flow worker deployments failing1549h 38mResolved
Sep 1, 2026Ingress endpoint degredation 1551h 30mResolved
Sep 1, 2026Smart Signals Degraded for Mobile SDK Clients1553h 2mResolved
Aug 31, 2026Ingress endpoint degradation1468h 33mResolved
Aug 28, 2026Ingress endpoint degradation1547h 18mResolved
Aug 25, 2026Investigating increased Latency and Errors in the Server API1613h 8mResolved
Aug 25, 2026Management API Database Migration1h 0mResolved
Aug 24, 2026Increased Latency and Error Rates in US-East-11641h 9mResolved
Aug 21, 2026Throttling issues in the Database layer1705h 39mResolved
Aug 14, 2026Sign-ups failing at Management API1879h 32mResolved
Aug 6, 2026We are experiencing issues with our Dashboard2075h 22mResolved
Jul 28, 2026Bot Detection False Positives Affecting Some Identifications1536h 24mResolved
Jul 9, 2026Summary Emails Service Degradation1994h 18mResolved
Jul 6, 2026Degraded Search API Performance2067h 50mResolved
Jun 26, 2026Degraded Search API performance1593h 30mResolved
Jun 21, 2026Management API - Intermittent failures1712h 49mResolved
Jun 1, 2026Dashboard Data Latency2184h 43mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Fingerprint incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Fingerprint Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Fingerprint acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Fingerprint outage in this window ran 91d, against a mean recovery of 54d 7h. If you depend on Fingerprint in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.