Persona Identities Outage History

Persona Identities is up right now

Persona Identities had 26 outages in the last 2 years totaling 9h 6m of downtime — averaging 1.1 incidents per month.

There were 26 Persona Identities outages since October 24, 2025 totaling 9h 6m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.withpersona.com

Minor June 16, 2026

Elevated workflow run errors

Detected by Pingoru
Jun 16, 2026, 07:38 AM UTC
Resolved
Jun 16, 2026, 07:38 AM UTC
Duration
—
Affected: WorkflowsInquiries & Collections
Timeline · 2 updates
  1. investigating Jun 16, 2026, 07:45 AM UTC

    Status: Investigating We are investigating elevated workflow run failures in US Legacy. Our team is actively investigating the issue. We'll post an update soon. Affected components Workflows (Degraded performance)

  2. resolved Jun 16, 2026, 08:19 AM UTC

    Status: Resolved 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. Affected components Workflows (Operational) Inquiries & Collections (Operational)

Read the full incident report →

Minor June 10, 2026

Increased latency for verifications

Detected by Pingoru
Jun 10, 2026, 06:31 AM UTC
Resolved
Jun 10, 2026, 06:31 AM UTC
Duration
—
Affected: VerificationsInquiries & Collections
Timeline · 3 updates
  1. investigating Jun 10, 2026, 04:27 AM UTC

    Status: Investigating We're currently investigating elevated response times in the US region, impacting government ID and selfie verifications. We'll post an update soon. Affected components Verifications (Degraded performance) Inquiries & Collections (Degraded performance)

  2. identified Jun 10, 2026, 06:06 AM UTC

    Status: Identified 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. Affected components Verifications (Degraded performance) Inquiries & Collections (Degraded performance)

  3. resolved Jun 10, 2026, 06:31 AM UTC

    Status: Resolved 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. Affected components Verifications (Operational) Inquiries & Collections (Operational)

Read the full incident report →

Minor April 27, 2026

Selfie and Government ID Elevated Latency

Detected by Pingoru
Apr 27, 2026, 11:49 PM UTC
Resolved
Apr 27, 2026, 11:49 PM UTC
Duration
—
Affected: APIReportsWorkflowsWebhooksDashboardGraphVerificationsInquiries & CollectionsCases
Timeline · 2 updates
  1. resolved Apr 27, 2026, 09:39 PM UTC

    Status: 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. Affected components Workflows (Operational) Reports (Operational) Webhooks (Operational) Verifications (Operational) Dashboard (Operational) API (Operational) Cases (Operational) Inquiries & Collections (Operational) Graph (Operational)

  2. resolved Apr 27, 2026, 11:49 PM UTC

    Status: Resolved Correction the issue was between 21:40 UTC - 22:22 UTC Affected components Verifications (Operational) Reports (Operational) Webhooks (Operational) Dashboard (Operational) API (Operational) Inquiries & Collections (Operational) Workflows (Operational) Graph (Operational) Cases (Operational)

Read the full incident report →

Minor April 21, 2026

Elevated External API Errors

Detected by Pingoru
Apr 21, 2026, 11:48 PM UTC
Resolved
Apr 21, 2026, 11:48 PM UTC
Duration
—
Affected: API
Timeline · 3 updates
  1. investigating Apr 21, 2026, 10:14 PM UTC

    Status: Investigating Customers are experiencing elevated 400 error response codes. Affected components API (Degraded performance)

  2. monitoring Apr 21, 2026, 11:10 PM UTC

    Status: Monitoring Full rollback at 10:12 PM UTC resolved the issue. We are currently monitoring to confirm full resolution. Affected components API (Degraded performance)

  3. resolved Apr 21, 2026, 11:48 PM UTC

    Status: Resolved Between 19:00 UTC and 22:12 UTC, customers intermittently saw elevated 400 error API responses. The issue is now resolved. Affected components API (Operational)

Read the full incident report →

Minor March 27, 2026

Degraded Performance for Verifications

Detected by Pingoru
Mar 27, 2026, 12:00 AM UTC
Resolved
Mar 27, 2026, 12:00 AM UTC
Duration
—
Affected: Verifications
Timeline · 3 updates
  1. investigating Mar 06, 2026, 04:00 AM UTC

    Status: Investigating 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. Affected components Verifications (Degraded performance)

  2. monitoring Mar 26, 2026, 11:54 PM UTC

    Status: Monitoring Verification latency has improved following mitigation efforts. Affected components Verifications (Operational)

  3. resolved Mar 27, 2026, 12:00 AM UTC

    Status: Resolved 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. Affected components Verifications (Operational)

Read the full incident report →

Minor March 19, 2026

Increased latency

Detected by Pingoru
Mar 19, 2026, 11:49 PM UTC
Resolved
Mar 19, 2026, 11:49 PM UTC
Duration
—
Affected: Workflows
Timeline · 3 updates
  1. investigating Mar 19, 2026, 10:11 PM UTC

    Status: Investigating Acknowledge (investigating) - We're currently investigating elevated response times with event-triggered workflows in the US region. We'll post an update soon. Affected components Workflows (Degraded performance)

  2. monitoring Mar 19, 2026, 10:50 PM UTC

    Status: Monitoring 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. Affected components Workflows (Degraded performance)

  3. resolved Mar 19, 2026, 11:49 PM UTC

    Status: Resolved 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. Affected components Workflows (Operational)

Read the full incident report →

Minor February 20, 2026

Elevated workflow latency

Detected by Pingoru
Feb 20, 2026, 10:35 PM UTC
Resolved
Feb 20, 2026, 10:35 PM UTC
Duration
—
Timeline · 2 updates
  1. monitoring Feb 20, 2026, 10:34 PM UTC

    Status: Monitoring 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. resolved Feb 20, 2026, 10:35 PM UTC

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

Read the full incident report →

Minor January 30, 2026

Tagging System Errors

Detected by Pingoru
Jan 30, 2026, 03:03 PM UTC
Resolved
Jan 30, 2026, 03:03 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating Jan 30, 2026, 02:09 PM UTC

    Status: Investigating We are currently investigating an issue causing errors in our tagging system. Our team is actively working to identify the root cause and assess impact. We will provide updates as more information becomes available.

  2. identified Jan 30, 2026, 02:16 PM UTC

    Status: Identified We have identified the issue causing errors in our Tagging system. This issue occurs only when applying or updating Tags within Inquiries. Our team is actively working on a fix and will provide updates as progress is made.

  3. monitoring Jan 30, 2026, 02:23 PM UTC

    Status: Monitoring We have implemented a fix for the issue causing Tagging errors within Inquiries and are seeing improved behavior. The team is monitoring the system closely to ensure continued stability.

  4. resolved Jan 30, 2026, 03:03 PM UTC

    Status: Resolved The issue causing tagging errors within Inquiries has been resolved, and functionality has returned to normal. Thank you for your patience while we worked to restore full service.

Read the full incident report →

Minor January 28, 2026

Increased workflow errors

Detected by Pingoru
Jan 28, 2026, 07:57 PM UTC
Resolved
Jan 28, 2026, 07:57 PM UTC
Duration
—
Timeline · 3 updates
  1. investigating Jan 27, 2026, 08:58 PM UTC

    Status: Investigating On January 27, 2026, we detected an increase in errors affecting Persona Workflows between 18:10–20:40 UTC. Our team is investigating and will provide updates as they become available.

  2. monitoring Jan 27, 2026, 09:25 PM UTC

    Status: Monitoring Error rates for Persona Workflows have returned to normal levels, and the system is recovering. We are continuing to monitor to ensure full stability.

  3. resolved Jan 28, 2026, 07:57 PM UTC

    Status: Resolved The increase in errors affecting Persona Workflows has been fully resolved. The service is stable and operating normally.

Read the full incident report →