Persona driftsforstyrrelser

1. 23. juli 2026 kl. 20.03 UTCinvestigating

   Fra 20: 36 UTC, en delmængde af ikke-amerikanske database verifikationer oplever forhøjede forbindelsesproblemer. Vi undersøger aktivt spørgsmålet.

2. 23. juli 2026 kl. 20.14 UTCmonitoring

   Fra 21: 02 UTC, vi ser sats opsving. Overvågningen er i gang.

3. 23. juli 2026 kl. 20.34 UTCresolved

   Mellem 20: 36 UTC og 21: 02 UTC, vi oplevede forhøjede konnektivitet problemer påvirker en delmængde af ikke-amerikanske database verifikationer. Det er nu løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 23. juli 2026 kl. 14.33 UTCinvestigating

   Vi er i øjeblikket ved at undersøge forhøjede svartider, der påvirker dokument- og regeringsverifikationer i EU-regionen. Spørgsmålet begyndte omkring 10: 45 UTC.

2. 23. juli 2026 kl. 17.54 UTCmonitoring

   Vi oplever en delvis genopretning i EU-regionen, og kapaciteten er forbedret. Vi følger fortsat situationen.

3. 23. juli 2026 kl. 22.43 UTCresolved

   Mellem 10: 45am UTC - 16: 35pm UTC, og igen mellem 18: 25 UTC - 18: 50 UTC, oplevede vi forhøjede svartider, der påvirkede dokument- og regeringsverifikationer i EU-regionen. Spørgsmålet er nu løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 21. juli 2026 kl. 15.08 UTCinvestigating

   Vi undersøger lige nu forhøjede svartider i den amerikanske region. Vi sender snart en opdatering.

2. 21. juli 2026 kl. 17.08 UTCmonitoring

   Mellem 12: 50 og 16: 30 UTC (21. juli) så vi forhøjede svartider på tværs af regeringens ID og dokumentkontrol i den amerikanske region. Dette overvåges nu. Et fix blev anvendt kl 19: 15 UTC (21. juli), og overvågning er i gang.

3. 22. juli 2026 kl. 12.49 UTCresolved

   Et fix blev anvendt kl. 19.15 UTC (21. juli). Spørgsmålet er nu løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 6. juli 2026 kl. 16.24 UTCresolved

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

2. 6. juli 2026 kl. 16.24 UTCinvestigating

   We are investigating latencies for Government ID verifications.

1. 6. juli 2026 kl. 16.22 UTCresolved

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

2. 6. juli 2026 kl. 16.22 UTCinvestigating

   We are investigating elevated latencies for Government ID verifications.

1. 1. juli 2026 kl. 14.19 UTCidentified

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

2. 1. juli 2026 kl. 14.41 UTCmonitoring

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

3. 1. juli 2026 kl. 15.16 UTCresolved

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

1. 22. juni 2026 kl. 19.12 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. 22. juni 2026 kl. 19.30 UTCidentified

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

3. 22. juni 2026 kl. 19.34 UTCmonitoring

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

4. 22. juni 2026 kl. 19.48 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. 18. juni 2026 kl. 15.48 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. 18. juni 2026 kl. 16.38 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. 18. juni 2026 kl. 16.53 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. 16. juni 2026 kl. 07.45 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. 16. juni 2026 kl. 08.19 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. 10. juni 2026 kl. 04.27 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. 10. juni 2026 kl. 06.06 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. 10. juni 2026 kl. 07.02 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. 27. april 2026 kl. 23.47 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. 27. april 2026 kl. 23.49 UTCresolved

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

1. 21. april 2026 kl. 22.14 UTCinvestigating

   Customers are experiencing elevated 400 error response codes.

2. 21. april 2026 kl. 23.10 UTCmonitoring

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

3. 21. april 2026 kl. 23.48 UTCresolved

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

1. 2. april 2026 kl. 04.03 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. 26. marts 2026 kl. 23.38 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. 26. marts 2026 kl. 23.54 UTCmonitoring

   Verification latency has improved following mitigation efforts.

3. 27. marts 2026 kl. 00.00 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. 24. marts 2026 kl. 18.07 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. 24. marts 2026 kl. 18.07 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. 22. marts 2026 kl. 02.01 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. 22. marts 2026 kl. 02.01 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. 19. marts 2026 kl. 22.11 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. 19. marts 2026 kl. 22.50 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. 19. marts 2026 kl. 23.49 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. 11. marts 2026 kl. 21.29 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. 4. marts 2026 kl. 14.52 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. 4. marts 2026 kl. 14.52 UTCidentified

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

1. 20. februar 2026 kl. 22.34 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. 20. februar 2026 kl. 22.35 UTCresolved

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