Post by Arthur Yee
Senior Network & Security Engineer | APAC Infrastructure Support | Cisco Meraki SD-WAN | FortiGate | Zscaler | Multi-Country Deployments
When I first got into networking, I started wondering how the Internet actually works behind the scenes. Playing around with tools like the Hurricane Electric BGP Toolkit and PeeringDB (https://www.peeringdb.com)completely changed the way I looked at it. Instead of being one giant cloud, the Internet is made up of thousands of independently operated networks, known as Autonomous Systems (ASes), that interconnect with one another. One of the coolest things I learned was that traffic can often take different routes depending on the direction. A request may travel along one path while the response returns via another. This phenomenon, known as asymmetric routing, is common on the Internet and can occur because routing decisions are made independently by different networks based on policies, costs, and business relationships. Looking at routing data can help identify where latency or routing changes are occurring and provides useful insight into how networks interact in the real world. PeeringDB is also widely used to learn about Internet exchange points (IXPs), peering locations, network operators, and interconnection information. I was surprised to see how much interconnection capacity can vary as well—some links operate at 10 Gbps, others at 100 Gbps, and many large networks now use 400 Gbps or higher-capacity connections. One thing that really stuck with me: complicated systems become a lot easier to understand when you explore real-world data and let your curiosity lead the way. A few nuances worth noting: routing data alone does not always reveal the exact cause of delays, since latency can also be affected by congestion, physical distance, server performance, or traffic engineering decisions. Also, PeeringDB information is generally self-reported by network operators, so details may occasionally be incomplete or outdated. #Networking #InternetInfrastructure #HurricaneBGPToolkit #Learning #Technology #NetworkEngineering #LookingBack