Live / Priva / Incident
Priva: ALERT: Priva cloud incident occurred
Priva · priva.comMajor incidentResolved2026-10-28 13:26 UTC
Public — what happened
Summary
Priva reported a major incident beginning at 17:00 UTC on 2026-10-27, in which some users of Building Operator received a 500 error when trying to update or save settings. The company said only certain user accounts were affected, and those customers might be unable to apply configuration changes. Priva's technical team worked on the problem, and the incident was marked resolved at 13:26 on 2026-10-28. The text provided did not state a cause.
Affected
Priva Cloud Operator
Timeline
- Started — 2026-10-27 17:00 UTC
- Investigating — 2026-10-27 17:00 UTC
- Resolved — 2026-10-28 13:26 UTC · 20h 26m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Priva against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Priva: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Priva report →
More from Priva
Covered in The Squid’s Ink, Week 45, 2026, our weekly internet health report.