Latency-based triangulation
Rupt sends pings and measures response latency to check whether a connection’s timing is consistent with its reported location. These measurements help reveal VPN and proxy routing beyond known IP lists.
Advanced VPN and proxy detection beyond IP lists. Use latency triangulation and browser, locale, and location mismatches to uncover disguised connections.
IP location
London, GB
IP address
203.0.113.82
Advanced detection and triangulation
Detect VPNs and proxies beyond known IP lists. Rupt measures latency and cross-checks location, browser and locale signals to expose connections that misrepresent where they come from.
Location checked against measured latency.
Correlate ping timing with IP location, browser timezone and locale.
Rupt sends pings and measures response latency to check whether a connection’s timing is consistent with its reported location. These measurements help reveal VPN and proxy routing beyond known IP lists.
Compare browser timezone and locale signals with the connection’s reported location. Evaluate differences alongside the location and timing evidence to identify inconsistencies.
Combine IP geolocation, latency and browser signals to identify connections that misrepresent location, including proxy traffic from addresses that have not appeared on a blocklist.
VPN detection and IP geolocation
See how Rupt detects VPNs, proxies, and location mismatches with latency triangulation and browser signals. Walk through the results with our team.
Book a demoLocation and network signals
Identify the IP’s approximate city, region and country, and whether the connection uses a VPN, proxy, Tor or hosting network. Apply regional access rules and choose how to handle anonymized traffic.
01
Use the IP country to define where your product, content or transactions are available. Combine location with network signals when regional access needs additional verification.
02
Distinguish VPN, proxy, Tor and hosting signals. Apply different policies to anonymized connections and cloud traffic, with responses that fit your product and customers.
03
Cross-check reported location with latency, browser timezone and locale signals. Identify connections that may be disguising their location before granting access to a restricted region or action.
Detection to decision
Allow a familiar customer, verify an unfamiliar login, or enforce country restrictions. Connect detection results to your rules.
Meet the rules engineA customer opens your product on a device you recognize, through their usual privacy VPN. Your policy can allow the session and preserve the network evidence.
Network
VPN
Device
Recognized device
Allow
The customer carries on.
Applications
Use VPN and IP location signals for geofencing, account takeover protection, account sharing, and fraud ring detection.
Apply country rules using IP location, then add VPN and proxy signals when a connection needs closer scrutiny.
Explore policiesCombine VPN and device signals to verify unfamiliar logins before they reach a customer’s account.
Explore protectionRecognize devices when IPs change, then review account history for signs of possible shared access.
Explore sharingLink accounts through shared devices and networks, then use VPN and proxy evidence to review coordinated abuse.
Explore linked accountsA closer look
VPN detection and IP geolocation
See how advanced VPN and proxy detection fits your product. Explore your connections, location requirements, and access policies with our team.