Network Pulse — Complete Guide

Real-time network diagnostics and connection health monitoring from your browser.

How to Use

  1. Navigate to Network Pulse. Tests start automatically on page load.
  2. Wait for all metrics to populate (approximately 10-15 seconds).
  3. Review the stats cards, graph visualization, and AI security insights.
  4. Click Refresh Scan to re-run all tests.

Metrics Explained

Public IP Address

The external IP address that websites and servers see when your device connects. Useful for verifying VPN tunnels (if IP changes after connecting to VPN), proxy configurations, and DNS-based geo-restrictions.

Nearest Edge Server

Identifies which data center (PoP) is serving your requests. Supports 35+ global locations across Vercel, Cloudflare, and Google Cloud edge networks. If it shows an unexpected location, your traffic may be routing through a proxy or VPN.

Latency (RTT)

Measured using application-layer HTTP ping (not ICMP). Reflects real end-to-end round-trip time including DNS, TLS, and HTTP overhead — what users actually experience.

Benchmarks: <50ms Excellent · 50–100ms Good · 100–200ms Fair · >200ms Poor

Jitter

Response time variance between consecutive requests. High jitter indicates unstable connections — critical for VoIP, video conferencing, and real-time applications.

Benchmarks: <15ms Stable · 15-30ms Acceptable · >30ms Unstable

Packet Loss

HTTP request failure rate — tracks failed or timed-out requests vs. total. Even 1% loss can cause noticeable impact on TCP performance.

Benchmarks: 0% Ideal · <1% Acceptable · >2% Investigate

Path MTU Discovery (PMTUD)

Uses a client-side binary search (576–1500 bytes) to find the maximum payload your path supports. 1500 bytes = standard Ethernet. 1492 bytes = PPPoE overhead. <1400 bytes = VPN/tunnel encapsulation. Lower values may cause fragmentation and performance issues.

AI Security Insights

After all metrics are collected, the AI analysis panel generates a posture assessment and actionable recommendations based on the results:

  • Packet loss detected → Inspect physical cables, switch ports, duplex mismatches
  • High jitter → Enable QoS/prioritization, check bandwidth saturation
  • High latency → Check for routing inefficiencies or VPN overhead
  • MTU restriction → Verify VPN tunnel MTU settings, check for fragmentation
  • No issues → Regular monitoring recommended
Open Network Pulse →