Global Edge Network ActiveReal-Time Egress & Handshake Verification

Know your VPN works.Before your users do.

ExitProbe brings up real tunnels from global edge probes — WireGuard, OpenVPN, IKEv2, VLESS Reality, and Hysteria2 — proving egress IPs, handshake health, and latency in real time. Not a ping. Proof.

No credit card required8 protocols supportedZero false positivesAutonomous SLA alerts
exitprobe.com/dashboard/servers/nl-ams-prod-01
NL Flag

NL-AMS-PROD-01

Operational
Expected Exit IP: 185.102.24.1•Location: Amsterdam (Equinix AM3)•Interval: 60s•Throughput: 942 Mbps
Uptime Kuma Timeline (60 Intervals)99.98%(1,420 checks · Avg: 19ms)
24 hours ago Up Degraded Down No DataJust now

Telemetry Analytics & Visual Performance

RTT Latency (Min–Max Spread with Solid Avg and Dashed P95)Current Avg: 19ms

5-Protocol Live Matrix Breakdown

Edge Probe Engine
WGOperational
WireGuard
RTT:19ms
Next: probe-fra01 in ~8s
OVPNOperational
OpenVPN
RTT:38ms
Next: probe-ams02 in ~14s
VLESSOperational
VLESS Reality
RTT:24ms
Next: probe-fra01 in ~6s
HY2Operational
Hysteria 2
RTT:21ms
Next: probe-syd01 in ~10s

Real-Time Diagnostic Checks & Verification Logs

Showing last 5 checks
TimeProbe NodeProtocolResult StatusObserved Exit IPRTT LatencyDetails / Errors
18s ago
DE Flagprobe-fra01 (Frankfurt)
wireguardUp185.102.24.118.8msExit IP matched nominal pool (0 leaks detected)
42s ago
NL Flagprobe-ams02 (Amsterdam)
vlessUp185.102.24.123.4msExit IP matched nominal pool (0 leaks detected)
1m 05s ago
GB Flagprobe-lon01 (London)
openvpnUp185.102.24.137.9msExit IP matched nominal pool (0 leaks detected)
1m 32s ago
AU Flagprobe-syd02 (Sydney)
hysteriaUp185.102.24.120.8msExit IP matched nominal pool (0 leaks detected)
2m 10s ago
US Flagprobe-nyc03 (New York)
ikev2Up185.102.24.144.5msExit IP matched nominal pool (0 leaks detected)
Why ExitProbe

Built for VPN providers, not adapted for them

Generic uptime tools check that a host responds. ExitProbe checks that your service actually works — the way your users experience it.

01

Real tunnels, not pings

A host that answers ICMP can still have a completely broken tunnel. ExitProbe connects like a real client — full handshake, live session, actual traffic — then verifies the exit IP against what you expect.

handshakewireguard · 23 ms
tunnel routeup · default via wg0
expected exit ip185.102.24.1
observed exit ip185.102.24.1
verdict exit ip verified

Every check proves the whole path: handshake, route, and the IP the internet actually sees.

02

Eight protocols, one monitor

WireGuard, OpenVPN, IKEv2/IPSec, VLESS, Hysteria 2, Trojan, Shadowsocks and VMess — attach every tunnel type to a single monitor. Each protocol is checked independently, with its own status, latency and history.

WireGuard23 ms
OpenVPN41 ms
IKEv2 / IPSec37 ms
VLESS52 ms
Hysteria 248 ms
Trojan61 ms
Shadowsocks44 ms
VMessdown

One failing protocol never hides the seven that work — each tunnel gets its own verdict.

03

Regional truth, not averages

A protocol failing from one region never marks your whole server down. ExitProbe tracks every protocol from every probe separately, and tells you exactly where a problem is — and where it isn’t.

DE FlagFrankfurt23 ms
SG FlagSingapore88 ms
US FlagAshburn41 ms
JP FlagTokyounreachable

IKEv2 unreachable from Tokyo — still healthy from 3 other regions. Regional issue, not a global outage.

04

Incidents with full context

When something breaks, you get the exact protocol, probe and region — not “something is down”. Flapping is suppressed automatically, maintenance windows silence planned work, and escalations page you only if nobody acknowledges.

IKEv2 down · NL-AMS-012m ago
probe-TKY01 · 3 consecutive failures · unacknowledged
Acknowledgeescalates in 15m if unacked
Alerted viaEmailSlackDiscordTelegramWebhook
How it works

From config to certainty in three steps

01

Add your server

Paste a config or connection URI for any supported protocol, then assign it to global probes or your own private edge network.

02

We verify from everywhere

Probes bring up the real tunnel, run a live handshake and check the actual exit IP — on your schedule, down to 30 seconds.

03

You get proof, not noise

Dashboards, per-protocol incidents and alerts with full context. Flapping is suppressed; escalations only fire when it matters.

Live edge network

Checked from real places, right now

Every monitor is verified from our distributed probe fleet — or from private probes you run yourself, anywhere, with one install command.

0
Edge probes worldwide
0
Protocols supported
0s
Fastest check interval
0
Alert channels
Developer platform

Automate everything

Build on top of ExitProbe with a production-grade API — the same one our own dashboard runs on.

  • REST API v1 with scoped tokens
  • Prometheus metrics endpoint
  • SLA exports — CSV & PDF
  • HMAC-signed webhooks
  • Public status pages
Explore the platform
incident.created → your endpoint
POST /webhooks/exitprobe
X-ExitProbe-Signature: sha256=9f2c…
{
  "event": "incident.created",
  "monitor": "NL-AMS-01",
  "protocol": "ikev2",
  "probe": "probe-TKY01",
  "region": "Tokyo, JP",
  "status": "down",
  "opened_at": "2026-08-26T14:03:11Z"
}
Pricing

Simple plans that scale with your fleet

Start free. Upgrade when you need more monitors, faster checks, or your own private probes.

FAQ

Questions, answered

How is this different from a normal uptime ping?

A ping only proves the host is reachable. ExitProbe brings up the actual tunnel — WireGuard handshake, OpenVPN session, Hysteria connection — and verifies the exit IP seen from the internet. Your server can answer pings all day while its tunnel is silently broken; we catch that.

Do you store my VPN configs and private keys?

Configurations and connection URIs are stored encrypted (AES-256-GCM) and are only decrypted in memory at check time to bring up the tunnel. They are never exposed in logs or API responses.

Can I use my own probe locations?

Yes. Higher plans let you run private probes anywhere using our lightweight Go agent with a single install command — perfect for verifying your servers from the exact regions your users care about.

What happens when a server goes down?

An incident opens immediately, scoped to the exact protocol and probe that failed. Flapping is suppressed automatically, escalation policies can page you if nobody acknowledges, and alerts fire with full context.

Stop guessing. Start verifying.

Get started free — no credit card required.