Proof incident

Identity verification and credential analysis problems

Critical Resolved View vendor source →

Proof experienced a critical incident on June 12, 2025 affecting Notarize Consumer App (iOS) and Proof Consumer (Web) and 1 more component, lasting 2h 30m. The incident has been resolved; the full update timeline is below.

Started
Jun 12, 2025, 06:17 PM UTC
Resolved
Jun 12, 2025, 08:48 PM UTC
Duration
2h 30m
Detected by Pingoru
Jun 12, 2025, 06:17 PM UTC

Affected components

Notarize Consumer App (iOS)Proof Consumer (Web)Notarize Consumer App (Android)Proof Real EstateNotary Platform

Update timeline

  1. investigating Jun 12, 2025, 06:17 PM UTC

    Proof platform is experiencing problems with Identity verification and credential analysis functionality, due to a major cloud vendor outage. We are assessing the impact and mitigation strategies.

  2. investigating Jun 12, 2025, 06:36 PM UTC

    We are confirming a widespread impact due to Google Cloud outage, which some of our vendors depend on. This manifests as a high error rate for signers trying to pass ID verification before entering a meeting. We are failing over retail traffic to another vendor who is not affected, however business and real estate workflows will continue to be impacted.

  3. identified Jun 12, 2025, 07:28 PM UTC

    Google Cloud confirmed the outage and is working on recovery. Meanwhile, Proof enabled a partial workaround. Retail and some real estate signers should be able to pass Identity verification when using US driver's license and opting for a mobile workflow.

  4. identified Jun 12, 2025, 08:06 PM UTC

    We are receiving updates that Google Cloud is recovering globally. Our primary IDV vendor is still down in the US region; we will send another update when this changes. US driver's license and mobile flow workaround remains available for retail and some real estate signers.

  5. monitoring Jun 12, 2025, 08:29 PM UTC

    We are observing recovery, ID verification flows are being handled by our primary IDV vendor normally.

  6. resolved Jun 12, 2025, 08:48 PM UTC

    This incident has been resolved.