IPVanish status history
Current state: operational — “All Systems Operational” per https://ipvanish.statuspage.io (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do IPVanish incidents last?
From 49 incidents with a vendor-posted start and resolve time. Longest on record: Phoenix, USA — 2.8 days (2026-07-02 18:21 UTC). Excluded, never estimated: 4 scheduled maintenance. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.
Incidents on record (53)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-09-12 21:16 UTC | Potential Service Impact | resolved | minor | 2 h 55 min |
| 2026-09-07 13:57 UTC | Bucharest City, Romania | resolved | minor | 6 h 50 min |
| 2026-09-04 07:00 UTC | Chicago US Maintenance Part-2 | maintenance | none | 4 h 14 min (approx.) |
| 2026-09-02 17:52 UTC | San Jose, Costa Rica | resolved | minor | 2 h 28 min |
| 2026-09-02 17:13 UTC | LAS- Las Vegas, USA | resolved | minor | 20 h 23 min |
| 2026-08-31 12:00 UTC | Bucharest City, Romania | resolved | minor | 1 h 16 min |
| 2026-08-29 01:04 UTC | Service impacting situation, Kansas City | resolved | minor | 8 h 07 min |
| 2026-08-24 22:59 UTC | Singapore, Kathmandu - Virtual Nepal, Phnom Penh - Virtual Cambodia, and Dubai United Arab Emirates | resolved | none | 1 h 45 min |
| 2026-08-23 03:31 UTC | OpenVPN and IKEv2 | resolved | none | 1 h 47 min |
| 2026-08-14 13:50 UTC | Oslo, Norway | resolved | minor | 26 h 13 min |
| 2026-08-13 12:18 UTC | Phoenix, United States | resolved | minor | 33 h 23 min |
| 2026-08-06 19:14 UTC | Minneapolis, USA | resolved | minor | 1 h 34 min |
| 2026-08-05 07:58 UTC | Vancouver and Calgary Canada | resolved | minor | 2 h 31 min |
| 2026-07-31 05:03 UTC | Detroit, US | resolved | maintenance | 3 h 07 min |
| 2026-07-19 03:04 UTC | Buenos Aires, Argentina | resolved | minor | 11 h 12 min |
| 2026-07-19 03:02 UTC | Santiago, Chile | resolved | minor | 11 h 13 min |
| 2026-07-19 03:01 UTC | Montevideo, Uruguay | resolved | minor | 11 h 14 min |
| 2026-07-19 02:59 UTC | Sao Paulo, Brazil | resolved | minor | 11 h 15 min |
| 2026-07-18 04:03 UTC | Santiago, Chile | resolved | major | 11 h 57 min |
| 2026-07-18 02:31 UTC | Montevideo, Uruguay | resolved | major | 13 h 29 min |
| 2026-07-18 02:30 UTC | Sao Paulo, Brazil | resolved | major | 13 h 31 min |
| 2026-07-18 02:27 UTC | Buenos Aires, Argentina | resolved | major | 13 h 35 min |
| 2026-07-14 12:36 UTC | Istanbul, Turkey & Yerevan, Armenia | resolved | minor | 4 h 29 min |
| 2026-07-10 14:25 UTC | KUL - Kuala Lumpur, Malaysia | resolved | minor | 1 h 08 min |
| 2026-07-10 02:34 UTC | Tallinn, Estonia | resolved | minor | 11 h 22 min |
| 2026-07-07 19:32 UTC | Bogota, Colombia | resolved | minor | 5 h 03 min |
| 2026-07-06 10:52 UTC | Zagreb, Croatia | resolved | minor | 1 h 44 min |
| 2026-07-06 02:44 UTC | Vancouver, Canada | resolved | minor | 21 h 49 min |
| 2026-07-02 18:21 UTC | Phoenix, USA | resolved | minor | 2 d 19 h |
| 2026-07-02 16:09 UTC | Islamabad, Pakistan | resolved | minor | 4 h 51 min |
| 2026-07-01 22:42 UTC | We are currently investigating a service impacting issue with Riga, Latvia | resolved | minor | 5 h 13 min |
| 2026-06-30 16:36 UTC | Denver, USA | resolved | none | 3 h 13 min |
| 2026-06-30 10:53 UTC | Sydney, Australia | resolved | minor | 2 h 35 min |
| 2026-06-29 18:03 UTC | WireGuard issue | resolved | none | 1 h 52 min |
| 2026-06-29 14:03 UTC | Marseille, France | resolved | minor | 54 min |
| 2026-06-24 23:38 UTC | Detroit, United States | resolved | none | 14 h 19 min |
| 2026-06-24 18:23 UTC | Detroit, US | resolved | minor | 2 h 25 min |
| 2026-06-23 22:38 UTC | Miami, Florida US and Virtual Locations in Cayman Islands, Venezuela, Belize, Jamaica, Bahamas, Papua New Guinea, Trinidad and Tobago, Dominican Republic, Nicaragua, and Honduras | resolved | major | 7 h 00 min |
| 2026-06-22 00:22 UTC | Vancouver, Canada | resolved | minor | 46 h 12 min |
| 2026-06-14 01:00 UTC | Luxembourg | resolved | none | 4 h 32 min |
| 2026-06-13 21:50 UTC | Vancouver, Canada | resolved | minor | 2 d 4 h |
| 2026-06-12 04:15 UTC | Service impacting situation for Calgary, Canada | resolved | minor | 43 min |
| 2026-06-02 11:29 UTC | Johannesburg, South Africa | resolved | minor | 3 h 10 min |
| 2026-05-29 23:39 UTC | Kuala Lumpur, Malaysia | resolved | major | 4 h 10 min |
| 2026-05-27 13:00 UTC | Johannesburg, South Africa | resolved | major | 1 h 04 min |
| 2026-05-26 01:26 UTC | Beirut, Lebanon | resolved | none | 1 h 50 min |
| 2026-05-21 06:32 UTC | Charlotte, US | resolved | major | 15 h 57 min |
| 2026-05-19 21:07 UTC | Helsinki, Finland | resolved | minor | 24 h 42 min |
| 2026-05-12 00:25 UTC | Stockholm Sweden | resolved | maintenance | 3 d 14 h |
| 2026-05-10 17:22 UTC | OpenVPN Connections | resolved | none | 4 h 39 min |
| 2026-05-08 03:24 UTC | Infrastructure | resolved | major | 14 h 03 min |
| 2026-05-06 22:55 UTC | [Tallinn Estonia] | resolved | none | 15 h 09 min |
| 2026-05-05 02:03 UTC | Service impacting situation for Sofia, Bulgaria | resolved | maintenance | 6 h 22 min |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch IPVanish with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"ipvanish"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}