This tool builds a fully navigable 3D model of everything data crosses on a trip across the public internet — the devices and infrastructure that are normally invisible every time you load a webpage. Orbit and zoom through the scene, click any device — from your own laptop to the destination data center's database server — and an info panel explains what it is, what it does, how it connects to the rest of the path, and its role in internet communication. Then run a live simulation — Ping, DNS Lookup, HTTP Request, HTTPS Request, or Traceroute — and watch a glowing packet animate hop by hop along the actual logical path, with a live log of every hop and its round-trip timing.
• User premises — a user computer that plugs into a LAN switch (which uplinks to the Wi-Fi router/home gateway performing NAT), matching how a real network with more than one wired device is actually wired. • Access network — the cable/fiber modem (ONT), the ISP's shared last-mile access network, and the ISP's carrier-grade edge router. • Internet core with real redundancy — an Internet Exchange Point (IXP) for settlement-free peering AND a separate Tier-1 transit provider router for paid backup capacity, a long-haul backbone fiber link, and a BGP-speaking core router that forwards traffic between autonomous systems. • Naming infrastructure — a DNS server representing the recursive resolver and authoritative name server chain that turns domain names into IP addresses. • Destination data center — the destination ISP/transit router, a CDN edge cache, a perimeter firewall, a load balancer distributing across two redundant web servers, an application server, and a database server, all housed inside a cloud data center. • Five animated simulations — Ping (ICMP), DNS Lookup, HTTP Request, HTTPS Request, and Traceroute — each following the real logical hop sequence with a live simulation log and an on-screen hop-by-hop caption. • A large, collapsible 2D schematic diagram of the full topology, cross-highlighting with the 3D view in both directions. • A built-in Learning Hub with an 11-stage guided tour of how a request crosses the internet, a networking glossary, and a knowledge quiz.
When you load a webpage, your browser first needs an IP address for the domain — a DNS lookup traverses your ISP's resolver, and if not cached, out to root servers, top-level-domain servers, and finally the domain's authoritative name server, which returns the answer.
On the way out, your computer's request first goes to the LAN switch it's physically plugged into, which uplinks to the Wi-Fi router — the router performs Network Address Translation (NAT) to swap your private LAN address for your ISP-assigned public IP. The packet passes through your modem onto the ISP's shared access network, then to the ISP's edge router, which consults its routing table (built from BGP, the Border Gateway Protocol) to pick the next hop toward the destination network — typically choosing between a settlement-free peering path at an Internet Exchange Point and a paid transit-provider path, whichever offers the best route.
From there, traffic travels across long-haul backbone fiber — sometimes under an ocean — to reach the destination network's own edge router. Many real-world requests are answered right there by a CDN edge cache without ever reaching the origin; on a cache miss, the request continues to the data center perimeter, where a firewall inspects the traffic, a load balancer distributes it to one of the (redundant) web servers, and — for dynamic requests — an application server executes business logic and a database server returns any stored data. The response then retraces the entire path back to your device.
• Ping (ICMP) — sends an echo request along the access-and-core path to the destination network's edge and back, measuring round-trip time. • DNS Lookup — animates the resolver chain resolving a domain name to an IP address before any connection is made. • HTTP Request — follows the full path through the CDN edge, firewall, load balancer, and web/app/database tiers and back, with each hop's description noting the request travels as plaintext. • HTTPS Request — follows the identical path, but each hop's description notes the payload is TLS-encrypted end to end. • Traceroute — a one-way animation that pauses at every intermediate router, mirroring how real traceroute discovers the path using TTL-limited probes and ICMP Time Exceeded replies.
Every simulation shows a live on-screen caption in the 3D view itself — the current hop number, the From → To node pair, and a real protocol-accurate description — in addition to the full scrollable log in the side rail.
It renders a complete, navigable 3D model of the path data takes across the public internet — from a user’s computer through a LAN switch, Wi-Fi router, ISP access network, an ISP edge router with both a peering and a transit path, backbone fiber, DNS infrastructure, a CDN edge cache, and into a destination data center’s firewall, load balancer, redundant web servers, application server, and database. Every device is clickable for a full explanation, and you can run animated Ping, DNS Lookup, HTTP/HTTPS Request, and Traceroute simulations that move a glowing packet hop by hop along the real logical path, with a live on-screen description of each hop.
On any real network with more than one wired device, each device plugs into a switch, and the switch uplinks to the router over a single Ethernet connection — the router does not have a dedicated port for every device in the building. This tool models that real wiring order: the computer connects to the LAN switch, which connects to the Wi-Fi router/home gateway, which performs NAT and reaches the modem.
Real ISPs typically reach the rest of the internet two ways: a settlement-free peering connection at an Internet Exchange Point, and a paid connection to a Tier-1/Tier-2 transit provider that guarantees reachability to anywhere. BGP continuously selects the best available path between the two, and having both is what keeps a network reachable even if one exchange point or peering relationship goes down.
A Content Delivery Network edge cache sits geographically close to users and stores copies of origin content. On a cache hit it answers directly, without ever reaching the destination data center; only a cache miss continues on to the firewall, load balancer, and web tier. In real-world traffic this is usually the first stop after leaving the internet core — most requests today never reach the origin server at all.
Both simulations follow the identical physical and logical path — LAN switch, router, modem, ISP network, IXP, backbone, CDN, destination firewall, load balancer, web/app/database tiers — but the HTTPS simulation’s hop captions note that the payload is TLS-encrypted at every intermediate hop, while the HTTP simulation’s captions note that the payload is plaintext and visible to any intermediate network it crosses.
Ping only reports whether the final destination responded and how long the round trip took. Traceroute reveals every individual router hop in between by sending probes with increasing TTL values and recording the ICMP Time Exceeded reply from each hop — the simulation animates the packet visiting and pausing briefly at each intermediate router so you can see the actual path structure.
It is an educational 3D visualization, not a packet-level network simulator or protocol analyzer. Its purpose is to make normally-invisible internet infrastructure and request flows tangible and explorable for learning — the hop sequences, device roles, and protocol behavior described match how the real internet works, but no live network traffic is generated or captured.