AI NETOPS TELEMETRY SUITE
SMART AUTOMATED TRACEROUTE
Smart Automated Trace route tool 3D NOC
68 IXPs • MY IP: Scanning...
3D Pins:
Optimal Reroute Loss
Executive Network Telemetry Overview

Real-Time 3D Global Packet Routing & Autonomous System Path Analysis

1. Multi-Hop Geodesic Traceroute Mapping

Traditional command-line traceroute and mtr utilities output raw IP addresses and millisecond counters that obscure physical geography. The Smart Automated Trace route tool resolves target domains via RFC 8484 DNS-over-HTTPS (DoH), correlates intermediate Autonomous System Numbers (ASNs) against 68+ global Internet Exchange Points (IXPs), and projects parabolic optical routing arcs onto an interactive WebGL 3D Earth globe.

Network engineers can immediately distinguish whether elevated Round-Trip Time (RTT) is caused by physical submarine cable distance—such as the INDIGO-West link between Perth (WAIX) and Singapore (SGIX)—or suboptimal BGP path tromboning across continents.

2. Control-Plane vs. Data-Plane Telemetry

When diagnosing packet loss on high-capacity 100GbE core routers, operators must differentiate between ICMP Control-Plane Policing (CoPP) and genuine forwarding-plane congestion. If hop 2 displays 2% loss while hop 5 (the destination) reports 0.0% packet loss, the intermediate transit router is simply rate-limiting ICMP Time Exceeded generation on its management CPU while forwarding production TCP/QUIC traffic without interruption.

Our Hop-by-Hop Inspector highlights per-segment latency deltas, ingress/egress peering IPs, and direct links to PeeringDB and IANA RDAP WHOIS registries.

3. Integrated Multi-Page NetOps Ecosystem

Explore our dedicated multi-page engineering suite using the navigation bar above: launch the full-screen 9-in-1 Network Tools Hub for subnetting and port scanning, study submarine fiber physics in the BGP & Routing Academy, browse all 68+ international peering hubs in the Global IXP Directory, or review our NetOps Troubleshooting Playbooks.

Explore 68+ IXP Hubs → • Troubleshooting FAQ →
G ADS
Cloudflare Magic Transit — Global Anycast BGP Protection

Accelerate global packet routing with automated BGP failover & live MTR telemetry.

Deploy ↗
01 • Core Routing Mechanics

How 3D Visual Traceroute & BGP AS-Path Selection Work

Traditional traceroute operates by transmitting Internet Control Message Protocol (ICMP) Echo Request packets, User Datagram Protocol (UDP) probes, or Transmission Control Protocol (TCP) SYN segments with incrementally increasing Time-to-Live (TTL) header values. When a router along the forwarding path decrements the IP packet's TTL field to zero, it discards the packet and returns an ICMP Time Exceeded (Type 11, Code 0) message from its ingress interface IP address.

However, raw IP addresses only tell half the story. On the public Internet, packet forwarding between Tier-1 transit providers (such as Lumen/AS3356, Arelion/AS1299, Cogent/AS174, and NTT/AS2914) and regional networks (such as Telstra/AS1221 or Superloop/AS7545 in Australia) is governed by the Border Gateway Protocol (BGP-4). BGP routers select paths based on policy attributes—including LOCAL_PREF, AS_PATH length, MED (Multi-Exit Discriminator), and hot-potato routing—rather than purely shortest physical geographic distance.

By correlating each hop's IP address with its Autonomous System Number (ASN) and physical Internet Exchange Point (IXP) coordinates on a 3D sphere, network engineers can immediately spot trombone routing (for example, traffic between Perth and Singapore hair-pinning through Sydney or Los Angeles due to misconfigured BGP route announcements) and remediate peering policies.

02 • Latency & Optical Physics

Diagnosing Round-Trip Time (RTT), Jitter & Submarine Cable Delays

In silica fiber-optic cables, light propagates at approximately 200,000 kilometers per second (roughly two-thirds the speed of light in a vacuum due to the refractive index of glass, $n \approx 1.47$). This establishes a hard physical floor of roughly 1 millisecond of Round-Trip Time (RTT) per 100 kilometers of geodesic fiber distance, before accounting for submarine cable slack, optical erbium-doped fiber amplifiers (EDFAs), and router serialization queues.

When inspecting a multi-hop flow in our right-hand Hop-by-Hop Inspector, engineers evaluate three primary telemetry indicators:

03 • Integrated NetOps Utility Manual

Complete Reference Guide to the 9 Built-in Network Diagnostic Tools

Every utility in the Network Suite toolbar executes client-side calculations or queries live cryptographic DNS-over-HTTPS and IANA RDAP endpoints. Below is the engineering documentation for each module:

1. 📶 Multi-Probe Ping & Jitter Analyzer

Measures sequential round-trip latency across 4, 8, or 12 probes, computing Minimum, Average, Maximum RTT, and Inter-Packet Jitter (mean deviation between consecutive probes). High jitter (>15 ms) degrades VoIP, WebRTC, and real-time telemetry streams even when average latency appears normal.

2. 🔌 TCP Service Port Scanner

Audits 18+ standard service ports across Web/TLS (80, 443, 8080, 8443), Remote Infrastructure (21 FTP, 22 SSH, 3389 RDP), Mail Relays (25, 465, 587, 993), and Databases (3306 MySQL, 5432 PostgreSQL, 6379 Redis, 27017 MongoDB) to verify firewall perimeter exposure.

3. 🔎 IP Lookup & ISP Intelligence

Resolves any hostname or IPv4/IPv6 address to its authoritative Autonomous System Number, ISP organization name, regional Internet registry (ARIN, RIPE, APNIC, LACNIC, AFRINIC), and local timezone offset.

4. 🌍 IP Geolocation & 3D Globe Pinning

Maps any IP address to its physical city, region, country code, international dialing prefix, and WGS84 latitude/longitude coordinates. Includes a one-click Fly to Location on 3D Globe action that plots the target directly on the interactive sphere.

5. 🏢 IANA RDAP ASN Lookup

Queries the official rdap.org/autnum/ registry for any Autonomous System Number (e.g., AS13335 Cloudflare, AS15169 Google, AS7545 TPG/WAIX) to inspect AS-block ranges, registrant entities, and administrative status flags.

6. 🔄 Reverse IP (DNS PTR) Lookup

Constructs the reversed-octet in-addr.arpa domain string for any IPv4 address and queries Cloudflare DNS-over-HTTPS for authoritative PTR (Type 12) records—essential for identifying router interface naming conventions (such as ae-2.r01.perth01.au.bb.gin.ntt.net).

7. 🖧 IEEE MAC Address OUI Vendor Lookup

Extracts the 24-bit Organizationally Unique Identifier (OUI) from any 48-bit Media Access Control address, identifies the hardware manufacturer (Cisco, Juniper, Apple, VMware, Ubiquiti, etc.), inspects the I/G (Unicast vs. Multicast) and U/L (Universal vs. Locally Administered) bits, and formats in IEEE colon and Cisco dotted-hex notation.

8. 🧮 IPv4 CIDR Subnet Calculator

Computes exact Network Address, Subnet Mask, ACL Wildcard Mask, Broadcast Address, Usable Host IP Range, and total addressable hosts for any prefix from /1 to /32 (including RFC 3021 /31 point-to-point router links), complete with a color-coded 32-bit binary bitmask visualizer.

9. 🔢 Multi-Base IP Address Converter

Performs bi-directional conversion between Dotted-Decimal IPv4 (103.1.168.1), Unsigned 32-bit Decimal Integer (1728161793), Hexadecimal (0x6701A801), Octal, 32-bit Dotted Binary, and Dual-Stack IPv4-Mapped IPv6 (::ffff:103.1.168.1) representations for firewall rules and raw socket programming.

04 • Frequently Asked Questions

Technical FAQ for Network Administrators & Security Analysts

Why does this tool use IANA RDAP instead of legacy Port-43 WHOIS?

Legacy WHOIS (RFC 3912) transmits unformatted plain text over unencrypted TCP port 43 and lacks standardized field schemas or internationalization. The Registration Data Access Protocol (RDAP, RFC 7480–7484) mandated by ICANN and Regional Internet Registries delivers structured JSON over HTTPS, enabling reliable parsing of CIDR netblocks, autonomous system numbers, registrar abuse contacts, and EPP status codes directly in the browser.

How can I trace routes from a custom city or my own live IP address?

You have three ways to customize your origin: (1) Click 🛡️ My IP and select Set as 3D Globe Origin to pin your live public egress IP; (2) Click 🌍 World in the Origin selector to pick from 68+ global IXPs or type any city/suburb on Earth into the OpenStreetMap Nominatim geocoder; or (3) Click the 🎯 icon and tap anywhere directly on the 3D Earth surface.

Can I ingest live MTR / Traceroute JSON from my own Linux routers or probes?

Yes. Click 🔌 API in the top control bar to connect a CORS-enabled REST API endpoint from your monitoring server (such as Prometheus, Telegraf, or a custom Python/Go MTR agent), or paste a custom JSON hop payload to render your private MPLS/BGP topology onto the 3D globe.

Is my IP lookup or diagnostic query history stored on external servers?

No. All DNS-over-HTTPS, RDAP WHOIS, and GeoIP lookups are executed directly from your web browser over encrypted HTTPS connections. Optional site preferences (such as your default Origin IXP hub) can be exported locally to a portable smart-traceroute-settings.json file.