Persona Outage History
25 incidents recorded over the last 365 days, 25 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.
Every Recorded Persona Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Jul 23, 2026 | Subset of non-US database verifications are experiencing elevated connectivity issuesBetween 20:36 UTC and 21:02 UTC, we experienced elevated connectivity issues affecting a subset of non-US database verifications. This is now resolved. | 30 min | Resolved |
| Jul 23, 2026 | Elevated Latency on Document and Government ID verifications (EU)Between 10:45am UTC - 16:35pm UTC, and then again between 18:25 UTC - 18:50 UTC, we experienced elevated response times affecting document and government ID verifications in the EU region. The issue is now resolved. | 8h 9m | Resolved |
| Jul 21, 2026 | Elevated Latency on Document verifications and Government ID verificationA fix was applied at 19:15 UTC (July 21st). The issue is now resolved. | 21h 41m | Resolved |
| Jul 6, 2026 | Elevated latency for Government ID verificationsThe issue has been resolved and latencies have returned to normal. | -38 min | Resolved |
| Jul 6, 2026 | Elevated latency for Government ID verificationsThe issue has been resolved and latencies have returned to normal. | -96 min | Resolved |
| Jul 1, 2026 | Missing verification images on DashboardThe issue impacting Verification images on the Dashboard is now resolved. | 56 min | Resolved |
| Jun 22, 2026 | Case Status - Not UpdatingIncident Resolved: Case Status update via workflows and dashboards are fully functional after a brief disruption between 18:30 and 19:20 UTC. All automated case updates have caught up. Please manually update the status… | 35 min | Resolved |
| Jun 18, 2026 | Errors with AAMVA verificationsBetween 15:07 UTC and 16:31 UTC, AAMVA verifications were unavailable due to an issue originating from AAMVA's source network. Services have been fully restored as of 16:31 UTC. We are expecting a Root Cause Analysis… | 42 min | Resolved |
| Jun 16, 2026 | Elevated workflow run errorsFrom 07:12 AM UTC to 07:38 AM UTC, we saw elevated workflow execution errors. During this window, Inquiry completion rates for legacy US tenants fell to zero. We identified the cause and applied mitigations; services… | -7 min | Resolved |
| Jun 10, 2026 | Increased latency for verificationsBetween 03:05 and 05:53 UTC (June 10th), we saw elevated response times across government ID and selfie verifications in the US region, caused by a degradation in Google Cloud Storage. This is now resolved. | 2h 3m | Resolved |
| Apr 27, 2026 | Selfie and Government ID Elevated LatencyCorrection the issue was between 21:40 UTC - 22:22 UTC | -128 min | Resolved |
| Apr 21, 2026 | Elevated External API ErrorsBetween 19:00 UTC and 22:12 UTC, customers intermittently saw elevated 400 error API responses. The issue is now resolved. | 1h 33m | Resolved |
| Apr 2, 2026 | Slightly elevated workflow run errors for some customersOn April 2, 2026 between 2:50 am and 3:32 am UTC, a small number of customers may have experienced slightly elevated response times and an approximately 10% increase in workflow run errors. This is now resolved. | -31 min | Resolved |
| Mar 26, 2026 | Degraded Performance for VerificationsResolved – Clarification Earlier, we notified you of a potential increase in verification latency. The increase was briefly impacting p95 and should not have been noticeable for the majority of customers. This… | 22 min | Resolved |
| Mar 24, 2026 | Increased 500 Errors on Inquiry and Verify EndpointsBetween 20:30 UTC, March 23th and 14:26 UTC, March 24th, we had an issue affecting the `/inquiry` and `/verify` endpoints, which were returning 500 errors for some requests. This is related to a recent change introduced… | -221 min | Resolved |
| Mar 22, 2026 | Elevated Workflow completion time on US LegacyBetween 12:01 am and 12:15am UTC, we saw degraded performance with Workflows on our US1 region. Workflow completion times were elevated during this period. This is now resolved. | -106 min | Resolved |
| Mar 19, 2026 | Increased latencyWe experienced elevated latency in our workflows product between 22:36 UTC and 23:15 PM UTC in the US region. This is now resolved. | 1h 37m | Resolved |
| Mar 11, 2026 | [CORRECTION] All systems fully operationalAt 21:06 UTC today we pushed an incorrect status page update as a result of an internal training exercise. We are not currently experiencing any issues and apologize for the additional noise this may have created. | -23 min | Resolved |
| Mar 4, 2026 | Degraded performance in US LegacyBetween **Mar 4, 2026 14:09 UTC** - **Mar 4, 2026 14:21 UTC,** Persona identified evaluated response times with the API in **US Legacy**. | -37 min | Resolved |
| Feb 20, 2026 | Elevated workflow latencyAs of 22:25 PM we have seen performance return to normal for impacted workflows. | 0 min | Resolved |
| Feb 15, 2026 | Elevated workflow latencyBetween 9:50 PM UTC and 10:55 PM UTC, we saw elevated latency across workflows. This is now resolved. | 38 min | Resolved |
| Feb 6, 2026 | Intermittent errorsThis issue has been resolved | -24 min | Resolved |
| Feb 4, 2026 | Degraded performanceWe are fully operational, the incident has been closed. | 1h 41m | Resolved |
| Jan 30, 2026 | Tagging System ErrorsThe issue causing tagging errors within Inquiries has been resolved, and functionality has returned to normal. Thank you for your patience while we worked to restore full service. | 54 min | Resolved |
| Jan 28, 2026 | Degraded Performance for VerificationsThe issue causing increased verification latency has been resolved, and system performance has returned to normal levels. Thank you for your patience while we worked to restore full service. | 19h 15m | Resolved |
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 Persona 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 Persona 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 Persona 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 Persona outage in this window ran 21h 41m, against a mean recovery of 4h 2m. If you depend on Persona 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.