IKEv2 / IPSec monitoring
IPsec-based VPN, native on most OSes — actively verified from ExitProbe's distributed edge probes.
About IKEv2 / IPSec
IKEv2 is the modern IKE protocol paired with IPSec for data transfer. It is natively supported by iOS, macOS, Windows and Android, which makes it the default choice for mobile-first VPN deployments.
IKEv2 failures are notoriously subtle: MOBIKE roaming, rekey timers and NAT-T mismatches can keep a tunnel technically alive while degrading to an unusable state — exactly what active per-check verification catches.
How ExitProbe tests it
- 1ExitProbe negotiates a full IKEv2 / IPSec session from an edge probe using your EAP credentials.
- 2Confirms the CHILD_SA comes up, not just that the IKE handshake answers.
- 3Verifies the exit IP through the established security association.
- 4Flags degraded states where the session exists but traffic stops flowing.
Your credentials are stored encrypted (AES-256-GCM) and only decrypted in memory at check time on the probe running the test. They never appear in logs, API responses, or incident payloads.
Common questions
Yes — EAP-MSCHAPv2 credentials are the primary supported flow. Certificate-only machine auth profiles are validated for format at import time.
If it speaks standard IKEv2 with EAP (which strongSwan and most appliances do), yes. The check behaves like a normal remote client.
A tunnel that fails during rekey looks fine between checks and dies every few hours. Frequent active checks catch the pattern instead of hiding inside long gaps.
Monitor your IKEv2 / IPSec server today
Free plan included — real handshakes, exit IP verification, instant alerts.