IPVanish
Documents
| Document | Verified | Changed | Evidence |
|---|---|---|---|
| Trust center | snapshot | ||
| Privacy policy | snapshot | ||
| Terms | snapshot | ||
| Security page | snapshot | ||
| Status page statuspage | snapshot | ||
| Security advisories | snapshot |
Subprocessors
None extracted.
Service status
none Ongoing since : Toronto Maintenance
none Ongoing since : Helsinki Maintenance Updates
none Ongoing since : Taipa Macao Maintenance Updates
none Ongoing since : San Jose (US) Maintenance Updates
none Ongoing since : Helsinki Maintenance Updates
none Ongoing since : Minneapolis USA Maintenance Updates Group 1
none Ongoing since : Minneapolis USA Maintenance Updates Group 2
none Ongoing since : Prague Czech Republic Maintenance
none Ongoing since : Prague Czech Republic Maintenance
- 19 incidents in 29 days
- 1 major or critical
- 6 days typical time to resolve
- 49 min longest major
| Began | Incident | Impact | Lasted |
|---|---|---|---|
| Toronto Maintenance | none | ongoing | |
| Tirana, Albania | minor | 19 h 51 min | |
| Queretaro, Mexico | major | 49 min | |
| Helsinki Maintenance Updates | none | ongoing | |
| CHI - Chicago, Illinois - United States | none | 2 h 55 min | |
| Taipa Macao Maintenance Updates | none | ongoing | |
| Hong Kong Maintenance Updates | none | 5 days | |
| Vancouver Maintenance Updates | none | 6 days |
As IPVanish's status page reports its own incidents (scheduled maintenance left out), read every few hours since (evidence)
Changes
None since tracking began.