Privy Outage History

Privy is up right now

Privy had 4 outages in the last 2 years — averaging 0.2 incidents per month.

There were 4 Privy outages since May 29, 2025. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.privy.com

Minor November 18, 2025

Dashboard Intermittent Availability

Detected by Pingoru
Nov 18, 2025, 03:23 PM UTC
Resolved
Nov 18, 2025, 03:23 PM UTC
Duration
Timeline · 1 update
  1. monitoring Nov 18, 2025, 03:23 PM UTC

    Nov 18, 10:23 EST Resolved - This incident has been resolved. Nov 18, 09:23 EST Update - The ongoing issues with Privy Landing Pages and Embedded Forms have been traced to an issue with one of our vendors, Cloudflare. We’re monitoring the issue, but you can also view their incident here: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7 Nov 18, 08:55 EST Update - Access to the Privy dashboard has stabilized. We are monitoring intermittent performance for landing pages and embedded forms. Nov 18, 08:28 EST Update - A fix is in place and we are continuing to monitor service performance. Nov 18, 07:59 EST Identified - Access to Privy’s dashboard is experiencing intermittent unavailability. We’ve identified the issue and are working with a vendor to resolve it. We do not believe this is impacting scheduled or sent emails or sms.

Read the full incident report →

Minor May 30, 2025

Email links are not working

Detected by Pingoru
May 30, 2025, 12:25 AM UTC
Resolved
May 30, 2025, 12:25 AM UTC
Duration
Timeline · 1 update
  1. monitoring May 30, 2025, 12:25 AM UTC

    May 29, 20:25 EDT Resolved - Issue resolved. Email redirect links are now working normally. May 29, 20:15 EDT Monitoring - We're actively working on a fix. Email redirect links will be restored gradually. May 29, 16:24 EDT Update - Our engineers have identified the problem with link redirection and are working on a solution May 29, 14:39 EDT Investigating - We're receiving reports that link redirection is resulting in "not found" errors. Our engineering team is investing this issue.

Read the full incident report →