Is there an Privy outage?
Privy status: Systems Active
Last checked: 9 minutes ago
Get notified about any outages, downtime or incidents for Privy and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: 9 minutes ago
Get notified about any outages, downtime or incidents for Privy and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Privy.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowOutlogger tracks the status of these components for Xero:
| Component | Status |
|---|---|
| Dashboard | Active |
| Platform | Active |
| Privy Convert | Active |
| Signup Integrations | Active |
| Website Campaigns | Active |
| Privy Email | Active |
| Email Infrastructure | Active |
| Email Sending | Active |
| Privy Text | Active |
| Text Sending | Active |
View the latest incidents for Privy and check for official updates:
Description: This incident has been resolved.
Status: Resolved
Impact: None | Started At: Aug. 21, 2019, 8:34 p.m.
Description: From about 3:21 pm eastern time to 3:34pm, the Dashboard and API were temporarily down due to a long-running database migration that was holding an exclusive lock. The long-running transaction was manually killed early to free up waiting transactions. Service resumed after said transaction was killed.
Status: Resolved
Impact: Major | Started At: Aug. 9, 2019, 7:21 a.m.
Description: From about 3:21 pm eastern time to 3:34pm, the Dashboard and API were temporarily down due to a long-running database migration that was holding an exclusive lock. The long-running transaction was manually killed early to free up waiting transactions. Service resumed after said transaction was killed.
Status: Resolved
Impact: Major | Started At: Aug. 9, 2019, 7:21 a.m.
Description: From about 3:11pm eastern time to 3:30pm, a database failed and a standby automatically recovered service. Background jobs and email sending was delayed by up to 30 minutes but has since recovered.
Status: Resolved
Impact: None | Started At: July 26, 2019, 8:36 p.m.
Description: From about 3:11pm eastern time to 3:30pm, a database failed and a standby automatically recovered service. Background jobs and email sending was delayed by up to 30 minutes but has since recovered.
Status: Resolved
Impact: None | Started At: July 26, 2019, 8:36 p.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.
