Persona kesinti geçmişi

We are investigating latencies for Government ID verifications.

The issue has been resolved and latencies have returned to normal.

The issue has been resolved and latencies have returned to normal.

We are investigating elevated latencies for Government ID verifications.

We've identified an issue on the Dashboard impacting Verification images, causing them to load intermittently.

The issue impacting Verification images on the Dashboard has been fixed.

The issue impacting Verification images on the Dashboard is now resolved.

We're investigating an issue that is causing users to not able to update case status in the Persona platform. Issue is limited to cases that are assigned to case queues.

The root cause of the issue has been identified and we rolled out a fix at 19:20 UTC.

Case status can now be updated after the fix was implemented. We are currently monitoring to confirm full resolution.

Incident 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 of any cases modified during that specific timeframe.

Persona is currently investigating erroring AAMVA verifications. We are working directly with AAMVA to identify the root cause and will provide updates as we learn more.

We are continuing to investigate the ongoing AAMVA service outage. AAMVA verifications remain unavailable at this time. Our team is actively working to restore service and is in contact with AAMVA. We will provide another update in 30 minutes or sooner if the situation changes.

Between 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 (RCA) report directly from AAMVA. We will share further details as they become available. We apologize for any disruption this may have caused.

We are investigating elevated workflow run failures in US Legacy. Our team is actively investigating the issue. We'll post an update soon.

From 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 are stable and under active monitoring.

We're currently investigating elevated response times in the US region, impacting government ID and selfie verifications. We'll post an update soon.

We're currently monitoring elevated response times affecting government ID and selfie verifications in the US region. The delays are linked to a degradation in our cloud storage provider (Google Cloud Storage). We are monitoring GCS's status and will update as soon as we have more information.

Between 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.

On April 27, between 9:39 and 10:21 UTC, we experienced elevated latency affecting Selfie and Government ID verifications. The issue was mitigated by disabling and rolling back recent model changes that were contributing to the increased latency.

Correction the issue was between 21:40 UTC - 22:22 UTC

Customers are experiencing elevated 400 error response codes.

Full rollback at 10:12 PM UTC resolved the issue. We are currently monitoring to confirm full resolution.

Between 19:00 UTC and 22:12 UTC, customers intermittently saw elevated 400 error API responses. The issue is now resolved.

On 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.

Starting at 3:00 UTC, March 25, we are investigating an issue causing an increase in tail latencies for verifications. Our team is actively working to identify the root cause and restore normal performance. We will provide updates as more information becomes available.

Verification latency has improved following mitigation efforts.

Resolved – 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 notification was triggered prematurely in the spirit of transparency, we apologize for any confusion caused. All systems have been operating normally.

Since 20:30 UTC, March 23th, we have identified an issue affecting the `/inquiry` and `/verify` endpoints, which are returning 500 errors for some requests. This is related to a recent change introduced to improve security around redirect URI validation. We have identified the root cause and are actively working on a resolution.

Between 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 to improve security around redirect URI validation, which has now been disabled. Service has returned to normal and errors have ceased. We apologize for any disruption this may have caused.

Since 12:01 am UTC, we saw degraded performance with Workflows on our US1 region. Workflow completion times were elevated during this period. We've identified the cause and are working on resolving the issue.

Between 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.

**Acknowledge (investigating)** - We're currently investigating elevated response times with event-triggered workflows in the US region. We'll post an update soon.

We experienced elevated latency in our workflows product between 22:36 UTC - 23:15 PM UTC. We have returned to normal operating levels and are currently monitoring the situation.

We experienced elevated latency in our workflows product between 22:36 UTC and 23:15 PM UTC in the US region. This is now resolved.

At 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.

Between **Mar 4, 2026 14:09 UTC** - **Mar 4, 2026 14:21 UTC,** Persona identified evaluated response times with the API in **US Legacy**.

Persona has identified evaluated response times with the API in **US Legacy.**

Between 22:10 PM and 22:25 PM, we saw increased latency across a limited subset of workflows in our US region. A fix has been applied and we have seen performance return to normal for impacted workflows.

As of 22:25 PM we have seen performance return to normal for impacted workflows.

Since 9:50 PM UTC, we've seen elevated workflow latency. We'll post an update soon.

Starting 9:50 PM UTC, we saw increased latency across workflows. A fix has been applied. We're seeing improvement and continuing to monitor performance.

Between 9:50 PM UTC and 10:55 PM UTC, we saw elevated latency across workflows. This is now resolved.

This issue has been resolved

For approximately three minutes between 7:57 AM 2/6 UTC and 8:00 AM 2/6 UTC we saw intermittent spikes of 500 errors for a subset of US customers. Note: DE1 was not affected during this window.

We're experiencing a service outage as of 19:24 UTC. Our team is actively investigating the issue. We'll post an update soon

We've identified the issue and are working to restore service.

We are continuing to work on a fix. The dashboard is accessible and inquiries, verification, and workflows are intermittently being processed across all regions.

Functionality in DE region has been restored. We are working to restore full functionality in US region.

We are seeing degraded performance across DE and US regions. We are continuing to work to restore full functionality across all regions.

All transactions-based flow are fully functional across US and DE shards. We are working on restoring functionality for inquiry-based flows.

We are currently processing all transactions, inquiries, workflows and verification. We are continuing to monitor to ensure full functionality has been restored.

All functionality has been restored and we are fully operational. We are continuing to monitor.

We are fully operational, the incident has been closed.