HYPR incident

SMS Delivery Issues on Verizon Network

Notice Resolved View vendor source →

HYPR experienced a notice incident on January 14, 2026 affecting HYPR Affirm, lasting 1d. The incident has been resolved; the full update timeline is below.

Started
Jan 14, 2026, 07:51 PM UTC
Resolved
Jan 15, 2026, 08:16 PM UTC
Duration
1d
Detected by Pingoru
Jan 14, 2026, 07:51 PM UTC

Affected components

HYPR Affirm

Update timeline

  1. monitoring Jan 14, 2026, 07:51 PM UTC

    We have become aware of a potential service issue affecting Affirm workflows that include SMS or voice-based phone verification steps. Verizon has reported a network outage that may result in delayed or failed delivery of one-time passcodes (OTPs) sent to end users on the Verizon carrier network. As a result, some users may be unable to successfully complete Affirm Identity Verification workflows that rely on phone verification during this time. What you may experience: - Delayed or failed SMS or voice OTP delivery to Verizon numbers - Increased verification failures or user drop-off at the phone verification step What HYPR is doing: - Our team is actively monitoring the situation to track Verizon’s recovery progress. - We will provide updates as more information becomes available. What you can do: - If possible, consider temporarily disabling phone-based verification steps or enabling alternate verification methods within your workflows. - Advise impacted end users to retry their verification later. We apologize for any inconvenience this may cause and appreciate your patience while Verizon works to restore service. Please reach out to HYPR Support if you have any questions or need assistance adjusting your workflows.

  2. monitoring Jan 15, 2026, 05:12 AM UTC

    Verizon reports that their services have been restored and that devices still encountering issues should be restarted. If users continue to have issues with Affirm SMS messages after restarting their devices please reach out to our support team for further assistance.

  3. resolved Jan 15, 2026, 08:16 PM UTC

    This incident has been resolved.