VMess monitoring
V2Ray protocol, URI auto-detect — actively verified from ExitProbe's distributed edge probes.
About VMess
VMess is the classic V2Ray protocol. Share links encode a JSON payload in base64 containing the server, port, user ID (UUID), alteration id, network type and TLS settings.
Real-world VMess links are messy — numeric fields arrive as either JSON numbers or strings depending on which client generated them. A monitor that only handles one dialect silently breaks on half your fleet.
How ExitProbe tests it
- 1ExitProbe decodes the standard v2rayN base64(JSON) share-link format.
- 2Tolerant parsing accepts numeric fields as both numbers and strings.
- 3Establishes a real VMess session through an Xray-compatible core and verifies the exit IP with live traffic.
- 4Reports per-region handshake health so CDN-fronted nodes can be tuned per market.
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
The v2rayN standard: vmess:// followed by base64-encoded JSON. If your panel emits this (nearly all do), it just works.
Yes — net, path, host and serviceName fields from the JSON payload are honoured exactly like a desktop client would.
Yes. Attach any combination of protocols to one monitor and see each tunnel’s health independently on the same page.
Monitor your VMess server today
Free plan included — real handshakes, exit IP verification, instant alerts.