Vendor Status Watch

← all vendors

IPVanish status history

Current state: operational — “All Systems Operational” per https://ipvanish.statuspage.io (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

9incidents, last 30 days
39incidents, last 90 days
53incidents on record
Incidents per week, last 12 weeks:

How long do IPVanish incidents last?

5.2 hmedian incident duration49 measured
24.7 h90th percentile1 in 10 ran longer
13.5 hmedian, major/critical only9 incidents

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)

StartedIncidentStatusImpactDuration
2026-09-12 21:16 UTCPotential Service Impactresolvedminor2 h 55 min
2026-09-07 13:57 UTCBucharest City, Romaniaresolvedminor6 h 50 min
2026-09-04 07:00 UTCChicago US Maintenance Part-2maintenancenone4 h 14 min (approx.)
2026-09-02 17:52 UTCSan Jose, Costa Ricaresolvedminor2 h 28 min
2026-09-02 17:13 UTCLAS- Las Vegas, USAresolvedminor20 h 23 min
2026-08-31 12:00 UTCBucharest City, Romaniaresolvedminor1 h 16 min
2026-08-29 01:04 UTCService impacting situation, Kansas Cityresolvedminor8 h 07 min
2026-08-24 22:59 UTCSingapore, Kathmandu - Virtual Nepal, Phnom Penh - Virtual Cambodia, and Dubai United Arab Emiratesresolvednone1 h 45 min
2026-08-23 03:31 UTCOpenVPN and IKEv2resolvednone1 h 47 min
2026-08-14 13:50 UTCOslo, Norwayresolvedminor26 h 13 min
2026-08-13 12:18 UTCPhoenix, United Statesresolvedminor33 h 23 min
2026-08-06 19:14 UTCMinneapolis, USAresolvedminor1 h 34 min
2026-08-05 07:58 UTCVancouver and Calgary Canadaresolvedminor2 h 31 min
2026-07-31 05:03 UTCDetroit, USresolvedmaintenance3 h 07 min
2026-07-19 03:04 UTCBuenos Aires, Argentinaresolvedminor11 h 12 min
2026-07-19 03:02 UTCSantiago, Chileresolvedminor11 h 13 min
2026-07-19 03:01 UTCMontevideo, Uruguayresolvedminor11 h 14 min
2026-07-19 02:59 UTCSao Paulo, Brazilresolvedminor11 h 15 min
2026-07-18 04:03 UTCSantiago, Chileresolvedmajor11 h 57 min
2026-07-18 02:31 UTCMontevideo, Uruguayresolvedmajor13 h 29 min
2026-07-18 02:30 UTCSao Paulo, Brazilresolvedmajor13 h 31 min
2026-07-18 02:27 UTCBuenos Aires, Argentinaresolvedmajor13 h 35 min
2026-07-14 12:36 UTCIstanbul, Turkey & Yerevan, Armeniaresolvedminor4 h 29 min
2026-07-10 14:25 UTCKUL - Kuala Lumpur, Malaysiaresolvedminor1 h 08 min
2026-07-10 02:34 UTCTallinn, Estoniaresolvedminor11 h 22 min
2026-07-07 19:32 UTCBogota, Colombiaresolvedminor5 h 03 min
2026-07-06 10:52 UTCZagreb, Croatiaresolvedminor1 h 44 min
2026-07-06 02:44 UTCVancouver, Canadaresolvedminor21 h 49 min
2026-07-02 18:21 UTCPhoenix, USAresolvedminor2 d 19 h
2026-07-02 16:09 UTCIslamabad, Pakistanresolvedminor4 h 51 min
2026-07-01 22:42 UTCWe are currently investigating a service impacting issue with Riga, Latviaresolvedminor5 h 13 min
2026-06-30 16:36 UTCDenver, USAresolvednone3 h 13 min
2026-06-30 10:53 UTCSydney, Australiaresolvedminor2 h 35 min
2026-06-29 18:03 UTCWireGuard issueresolvednone1 h 52 min
2026-06-29 14:03 UTCMarseille, Franceresolvedminor54 min
2026-06-24 23:38 UTCDetroit, United Statesresolvednone14 h 19 min
2026-06-24 18:23 UTCDetroit, USresolvedminor2 h 25 min
2026-06-23 22:38 UTCMiami, Florida US and Virtual Locations in Cayman Islands, Venezuela, Belize, Jamaica, Bahamas, Papua New Guinea, Trinidad and Tobago, Dominican Republic, Nicaragua, and Hondurasresolvedmajor7 h 00 min
2026-06-22 00:22 UTCVancouver, Canadaresolvedminor46 h 12 min
2026-06-14 01:00 UTCLuxembourgresolvednone4 h 32 min
2026-06-13 21:50 UTCVancouver, Canadaresolvedminor2 d 4 h
2026-06-12 04:15 UTCService impacting situation for Calgary, Canadaresolvedminor43 min
2026-06-02 11:29 UTCJohannesburg, South Africaresolvedminor3 h 10 min
2026-05-29 23:39 UTCKuala Lumpur, Malaysiaresolvedmajor4 h 10 min
2026-05-27 13:00 UTCJohannesburg, South Africaresolvedmajor1 h 04 min
2026-05-26 01:26 UTCBeirut, Lebanonresolvednone1 h 50 min
2026-05-21 06:32 UTCCharlotte, USresolvedmajor15 h 57 min
2026-05-19 21:07 UTCHelsinki, Finlandresolvedminor24 h 42 min
2026-05-12 00:25 UTCStockholm Swedenresolvedmaintenance3 d 14 h
2026-05-10 17:22 UTCOpenVPN Connectionsresolvednone4 h 39 min
2026-05-08 03:24 UTCInfrastructureresolvedmajor14 h 03 min
2026-05-06 22:55 UTC[Tallinn Estonia]resolvednone15 h 09 min
2026-05-05 02:03 UTCService impacting situation for Sofia, Bulgariaresolvedmaintenance6 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
}