Persona 장애 기록

1. 2026년 7월 23일 오후 8:03 UTCinvestigating

   20:36 UTC로, 비-US 데이터베이스 검증의 하위 세트는 높은 연결 문제를 경험하고있다. 우리는 적극적으로 문제를 조사하고 있습니다.

2. 2026년 7월 23일 오후 8:14 UTCmonitoring

   으로 21:02 UTC, 우리는 재생율을보고있다. 모니터링은 계속됩니다.

3. 2026년 7월 23일 오후 8:34 UTCresolved

   20:36 UTC와 21:02 UTC 사이, 우리는 비 미국 데이터베이스 검증의 하위 집합에 영향을 미치는 높은 연결 문제 경험. 이것은 이제 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 23일 오후 2:33 UTCinvestigating

   우리는 현재 EU 지역에서 문서 및 정부 ID 검증에 영향을 미치는 높은 응답 시간을 투자하고 있습니다. 문제는 대략 10:45 UTC에서 시작되었습니다.

2. 2026년 7월 23일 오후 5:54 UTCmonitoring

   우리는 EU 지역에서 부분 복구를보고 있으며 용량이 향상되었습니다. 우리는 상황을 모니터링하고 있습니다.

3. 2026년 7월 23일 오후 10:43 UTCresolved

   10:45am UTC - 16:35pm UTC 사이, 그리고 다시 사이에 18:25 UTC - 18:50 UTC, 우리는 EU 지역에서 문서와 정부 ID 검증에 영향을 미치는 높은 응답 시간을 경험. 문제가 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 21일 오후 3:08 UTCinvestigating

   우리는 현재 미국 지역의 높은 응답 시간을 투자하고 있으며 문서 및 정부 ID 검증에 영향을 미칩니다. 업데이트가 곧 시작됩니다.

2. 2026년 7월 21일 오후 5:08 UTCmonitoring

   12:50과 16:30 UTC (7 월 21 일) 사이, 우리는 미국 지역에 정부 ID 및 문서 검증을 통해 높은 응답 시간을 보았다. 이것은 현재 감시되고 있습니다. 수정은 19:15 UTC (7 월 21 일)에 적용되었으며 모니터링은 진행 중입니다.

3. 2026년 7월 22일 오후 12:49 UTCresolved

   수정은 19:15 UTC (7 월 21 일)에 적용됩니다. 문제가 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 6일 오후 4:24 UTCresolved

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

2. 2026년 7월 6일 오후 4:24 UTCinvestigating

   We are investigating latencies for Government ID verifications.

1. 2026년 7월 6일 오후 4:22 UTCresolved

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

2. 2026년 7월 6일 오후 4:22 UTCinvestigating

   We are investigating elevated latencies for Government ID verifications.

1. 2026년 7월 1일 오후 2:19 UTCidentified

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

2. 2026년 7월 1일 오후 2:41 UTCmonitoring

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

3. 2026년 7월 1일 오후 3:16 UTCresolved

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

1. 2026년 6월 22일 오후 7: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. 2026년 6월 22일 오후 7:30 UTCidentified

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

3. 2026년 6월 22일 오후 7:34 UTCmonitoring

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

4. 2026년 6월 22일 오후 7: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. 2026년 6월 18일 오후 3: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. 2026년 6월 18일 오후 4: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. 2026년 6월 18일 오후 4: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. 2026년 6월 16일 오전 7: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. 2026년 6월 16일 오전 8: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. 2026년 6월 10일 오전 4: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. 2026년 6월 10일 오전 6: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. 2026년 6월 10일 오전 7: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. 2026년 4월 27일 오후 11: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. 2026년 4월 27일 오후 11:49 UTCresolved

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

1. 2026년 4월 21일 오후 10:14 UTCinvestigating

   Customers are experiencing elevated 400 error response codes.

2. 2026년 4월 21일 오후 11:10 UTCmonitoring

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

3. 2026년 4월 21일 오후 11:48 UTCresolved

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

1. 2026년 4월 2일 오전 4: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. 2026년 3월 26일 오후 11: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. 2026년 3월 26일 오후 11:54 UTCmonitoring

   Verification latency has improved following mitigation efforts.

3. 2026년 3월 27일 오전 12: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. 2026년 3월 24일 오후 6: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. 2026년 3월 24일 오후 6: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. 2026년 3월 22일 오전 2: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. 2026년 3월 22일 오전 2: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. 2026년 3월 19일 오후 10: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. 2026년 3월 19일 오후 10: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. 2026년 3월 19일 오후 11: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. 2026년 3월 11일 오후 9: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. 2026년 3월 4일 오후 2: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. 2026년 3월 4일 오후 2:52 UTCidentified

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

1. 2026년 2월 20일 오후 10: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. 2026년 2월 20일 오후 10:35 UTCresolved

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