Historial de interrupciones de Persona

1. July 23, 2026 at 8:03 PM UTCinvestigating

   A partir de las 20:36 UTC, un subconjunto de verificaciones de bases de datos no estadounidenses están experimentando problemas elevados de conectividad. Estamos investigando activamente la cuestión.

2. July 23, 2026 at 8:14 PM UTCmonitoring

   A partir de las 21:02 UTC, estamos viendo recuperación de tasa. La vigilancia está en curso.

3. July 23, 2026 at 8:34 PM UTCresolved

   Entre 20:36 UTC y 21:02 UTC, experimentamos problemas elevados de conectividad que afectan a un subconjunto de verificaciones de bases de datos no estadounidenses. Esto ya está resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 23, 2026 at 2:33 PM UTCinvestigating

   Actualmente estamos investigando tiempos elevados de respuesta que afectan las verificaciones de documentos y de identificación gubernamental en la región de la UE. La cuestión comenzó aproximadamente a las 10:45 UTC.

2. July 23, 2026 at 5:54 PM UTCmonitoring

   Estamos viendo la recuperación parcial en la región de la UE, y la capacidad ha mejorado. Seguimos vigilando la situación.

3. July 23, 2026 at 10:43 PM UTCresolved

   Entre las 10:45am UTC - 16:35pm UTC, y luego entre 18:25 UTC - 18:50 UTC, experimentamos tiempos elevados de respuesta que afectan las verificaciones de documentos y de identificación del gobierno en la región de la UE. La cuestión se resuelve ahora.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 21, 2026 at 3:08 PM UTCinvestigating

   Actualmente estamos investigando tiempos elevados de respuesta en la región de Estados Unidos, impactando documentos y verificaciones de identificación del gobierno. Publicaremos una actualización pronto.

2. July 21, 2026 at 5:08 PM UTCmonitoring

   Entre las 12:50 y las 16:30 UTC (21 de julio), vimos tiempos elevados de respuesta a través del ID del gobierno y verificaciones de documentos en la región de Estados Unidos. Esto está siendo monitoreado ahora. Se aplicó una solución a las 19:15 UTC (21 de julio), y la vigilancia está en curso.

3. July 22, 2026 at 12:49 PM UTCresolved

   Se aplicó una solución a las 19:15 UTC (21 de julio). La cuestión se resuelve ahora.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 6, 2026 at 4:24 PM UTCresolved

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

2. July 6, 2026 at 4:24 PM UTCinvestigating

   We are investigating latencies for Government ID verifications.

1. July 6, 2026 at 4:22 PM UTCresolved

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

2. July 6, 2026 at 4:22 PM UTCinvestigating

   We are investigating elevated latencies for Government ID verifications.

1. July 1, 2026 at 2:19 PM UTCidentified

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

2. July 1, 2026 at 2:41 PM UTCmonitoring

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

3. July 1, 2026 at 3:16 PM UTCresolved

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

1. June 22, 2026 at 7:12 PM UTCinvestigating

   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.

2. June 22, 2026 at 7:30 PM UTCidentified

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

3. June 22, 2026 at 7:34 PM UTCmonitoring

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

4. June 22, 2026 at 7:48 PM UTCresolved

   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.

1. June 18, 2026 at 3:48 PM UTCinvestigating

   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.

2. June 18, 2026 at 4:38 PM UTCinvestigating

   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.

3. June 18, 2026 at 4:53 PM UTCresolved

   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.

1. June 16, 2026 at 7:45 AM UTCinvestigating

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

2. June 16, 2026 at 8:19 AM UTCresolved

   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.

1. June 10, 2026 at 4:27 AM UTCinvestigating

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

2. June 10, 2026 at 6:06 AM UTCidentified

   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.

3. June 10, 2026 at 7:02 AM UTCresolved

   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.

1. April 27, 2026 at 11:47 PM UTCresolved

   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.

2. April 27, 2026 at 11:49 PM UTCresolved

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

1. April 21, 2026 at 10:14 PM UTCinvestigating

   Customers are experiencing elevated 400 error response codes.

2. April 21, 2026 at 11:10 PM UTCmonitoring

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

3. April 21, 2026 at 11:48 PM UTCresolved

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

1. April 2, 2026 at 4:03 AM UTCresolved

   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.

1. March 26, 2026 at 11:38 PM UTCinvestigating

   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.

2. March 26, 2026 at 11:54 PM UTCmonitoring

   Verification latency has improved following mitigation efforts.

3. March 27, 2026 at 12:00 AM UTCresolved

   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.

1. March 24, 2026 at 6:07 PM UTCidentified

   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.

2. March 24, 2026 at 6:07 PM UTCresolved

   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.

1. March 22, 2026 at 2:01 AM UTCidentified

   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.

2. March 22, 2026 at 2:01 AM UTCresolved

   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.

1. March 19, 2026 at 10:11 PM UTCinvestigating

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

2. March 19, 2026 at 10:50 PM UTCmonitoring

   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.

3. March 19, 2026 at 11:49 PM UTCresolved

   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.

1. March 11, 2026 at 9:29 PM UTCresolved

   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.

1. March 4, 2026 at 2:52 PM UTCresolved

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

2. March 4, 2026 at 2:52 PM UTCidentified

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

1. February 20, 2026 at 10:34 PM UTCmonitoring

   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.

2. February 20, 2026 at 10:35 PM UTCresolved

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