Tipalti incident

Two-Factor Authentication (2FA) SMS Delivery Issues

Minor Resolved View vendor source →

Tipalti experienced a minor incident on May 22, 2025 affecting Tipalti Hub, lasting 2h 7m. The incident has been resolved; the full update timeline is below.

Started
May 22, 2025, 06:52 PM UTC
Resolved
May 22, 2025, 08:59 PM UTC
Duration
2h 7m
Detected by Pingoru
May 22, 2025, 06:52 PM UTC

Affected components

Tipalti Hub

Update timeline

  1. investigating May 22, 2025, 06:52 PM UTC

    We are currently investigating an issue with our two-factor authentication (2FA) provider that is preventing SMS verification codes from being delivered. This is affecting users who have not previously saved their session (i.e., “Remember this device for 30 days” was not selected). Users with an active saved session are not impacted and can continue logging in normally. We are actively working with our 2FA provider to resolve the issue. In the meantime, affected users are advised to wait and try again later. We appreciate your patience and will provide updates here hourly until issue is resolved. Tipalti Support

  2. investigating May 22, 2025, 07:55 PM UTC

    We are continuing to work with our two-factor authentication (2FA) provider to resolve an issue that is preventing SMS verification codes from being delivered. This is affecting users who have not previously saved their session (i.e., did not select “Remember this device for 30 days”). Users with an active saved session remain unaffected and can log in as usual. Our teams are actively working on a resolution. We will share the next update within one hour. Thank you for your continued patience. Tipalti Support

  3. investigating May 22, 2025, 08:49 PM UTC

    We are continuing to investigate this issue.

  4. monitoring May 22, 2025, 08:52 PM UTC

    The issue preventing SMS verification codes from being delivered has been resolved. Affected users should now be able to receive 2FA codes and log in successfully. We are actively monitoring the system to ensure continued stability. Thank you for your patience while we worked to resolve this.

  5. monitoring May 22, 2025, 08:58 PM UTC

    We are continuing to monitor for any further issues.

  6. resolved May 22, 2025, 08:59 PM UTC

    This incident has been resolved.