Persona kesinti geçmişi

1. 23 Temmuz 2026 20:03 UTCinvestigating

   20:36 UTC olarak, non-US veritabanı doğrulamalarının bir alt kümesi yüksek bağlantı sorunları yaşıyor. Sorunu aktif olarak araştırıyoruz.

2. 23 Temmuz 2026 20:14 UTCmonitoring

   21:02 UTC olarak, hız kurtarma görüyoruz. İzleme devam ediyor.

3. 23 Temmuz 2026 20:34 UTCresolved

   20:36 UTC ve 21:02 UTC arasında, ABD olmayan veri doğrulamalarının bir alt kümesini etkileyen yüksek bağlantı sorunları yaşadık. Bu şimdi çözüldü.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 23 Temmuz 2026 14:33 UTCinvestigating

   Şu anda AB bölgesinde belge ve hükümet kimlik doğrulamalarını etkileyen yüksek yanıt süreleri araştırıyoruz. Sorun yaklaşık 10:45 UTC'de başladı.

2. 23 Temmuz 2026 17:54 UTCmonitoring

   AB bölgesinde kısmi iyileşme görüyoruz ve kapasite gelişmiştir. Durumu izlemeye devam ediyoruz.

3. 23 Temmuz 2026 22:43 UTCresolved

   10:45am UTC - 16:35pm UTC ve sonra 18:25 UTC - 18:50 UTC arasında, AB bölgesinde belge ve hükümet kimlik doğrulamalarını etkileyen zamanları yaşadık. Sorun şu anda çözüldü.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 21 Temmuz 2026 15:08 UTCinvestigating

   Şu anda ABD bölgesinde yüksek tepki süreleri araştırıyoruz, belge ve hükümet kimlik doğrulamalarını etkiliyoruz. Yakında bir güncelleme yayınlayacağız.

2. 21 Temmuz 2026 17:08 UTCmonitoring

   12:50 ve 16:30 UTC ( 21 Temmuz), ABD bölgesinde hükümet kimlik ve belge doğrulamalarında yüksek tepki süreleri gördük. Bu şimdi izleniyor. Bir düzeltme 19:15 UTC ( 21 Temmuz), ve izleme devam etmektedir.

3. 22 Temmuz 2026 12:49 UTCresolved

   Bir düzeltme 19:15 UTC'de uygulandı ( 21 Temmuz). Sorun şu anda çözüldü.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 6 Temmuz 2026 16:24 UTCresolved

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

2. 6 Temmuz 2026 16:24 UTCinvestigating

   We are investigating latencies for Government ID verifications.

1. 6 Temmuz 2026 16:22 UTCresolved

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

2. 6 Temmuz 2026 16:22 UTCinvestigating

   We are investigating elevated latencies for Government ID verifications.

1. 1 Temmuz 2026 14:19 UTCidentified

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

2. 1 Temmuz 2026 14:41 UTCmonitoring

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

3. 1 Temmuz 2026 15:16 UTCresolved

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

1. 22 Haziran 2026 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 Haziran 2026 19:30 UTCidentified

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

3. 22 Haziran 2026 19:34 UTCmonitoring

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

4. 22 Haziran 2026 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 Haziran 2026 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 Haziran 2026 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 Haziran 2026 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 Haziran 2026 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 Haziran 2026 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 Haziran 2026 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 Haziran 2026 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 Haziran 2026 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 Nisan 2026 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 Nisan 2026 23:49 UTCresolved

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

1. 21 Nisan 2026 22:14 UTCinvestigating

   Customers are experiencing elevated 400 error response codes.

2. 21 Nisan 2026 23:10 UTCmonitoring

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

3. 21 Nisan 2026 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 Nisan 2026 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 Mart 2026 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 Mart 2026 23:54 UTCmonitoring

   Verification latency has improved following mitigation efforts.

3. 27 Mart 2026 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 Mart 2026 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 Mart 2026 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 Mart 2026 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 Mart 2026 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 Mart 2026 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 Mart 2026 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 Mart 2026 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 Mart 2026 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 Mart 2026 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 Mart 2026 14:52 UTCidentified

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

1. 20 Şubat 2026 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 Şubat 2026 22:35 UTCresolved

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