Privy Outage History

11 incidents recorded over the last 365 days, 8 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Privy status99.72% uptime history

Every Recorded Privy Incident

Privy incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 27, 2026Privy Dashboard IssuesThis incident has been resolved.4h 50mResolved
Oct 21, 2026Database MaintenanceThe scheduled maintenance has been completed.1h 0mScheduled
Oct 19, 2026Privy Displays Offline for Shopify StoresPrivy Popups and Embedded forms are operating correctly.7h 13mResolved
Oct 18, 2026Investigating dashboard issuesWe're consolidating this incident with https://status.privy.com/incidents/sj8sw3b7yz8l - further updates will be made in that incident2h 53mResolved
Oct 17, 2026Privy Displays OutageThis incident has been resolved. All Privy Displays are online.28h 56mResolved
Sep 30, 2026Site Timeouts for some usersThis incident has been resolved.1h 59mResolved
Sep 24, 2026Landing page SSL errorThis incident has been resolved.35h 53mResolved
May 2, 2026Database MaintenanceThe scheduled maintenance has been completed.1h 0mScheduled
Apr 30, 2026Database Scheduled MaintenanceThe maintenance has been completed.2h 0mScheduled
Feb 23, 2026Degraded Dashboard Access Affecting Selected Regions: UKPrivy services are back up and running. If you continue to experience trouble accessing Privy's Dashboard please reach out to support@privy.com. Thank you for your patience as we resolved these issues.25h 33mResolved
Nov 18, 2025Dashboard Intermittent AvailabilityThis incident has been resolved.2h 23mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Privy incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Privy Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Privy acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Privy outage in this window ran 1d 11h, against a mean recovery of 10h 20m. If you depend on Privy in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.