FAA Fiber Cut Disrupted Thousands of Flights. Where the Failure Chain Could Have Been Interrupted A severed backup fiber line and a failed primary communications circuit disrupted air travel across the Northeast US for hours. The sequence shows why physical route visibility matters—and BWI Airport offers a separate, real-world example of what that visibility looks…
Start reading
Join us close to our headquarters in Maryland for a private small-group luncheon for higher-education IT, network, and infrastructure professionals. Managing campus inside plant and outside plant infrastructure gets more complicated as networks grow, buildings change, and new infrastructure is added. That’s why Graphical Networks is hosting a private Lunch & Learn focused on campus…
Start readingPractical guidance for managing power, cooling, racks, cabling, capacity, and infrastructure documentation Data centers rarely become difficult to manage because of one major mistake. Usually, complexity builds gradually. More equipment gets added. Rack densities increase. Power and cooling requirements change. Cable pathways fill up. Temporary fixes become permanent. Documentation falls behind, and important information ends…
Start reading
netTerrain 10.2 is live. 10.2 introduces depth-aware rack and cabinet modeling, Butterfly Layout automation for manhole diagrams, easier circuit editing, direct strand-to-strand fusing, and improvements to IPAM, imports, link editing, device identification, table navigation, security, and PDF export. These updates help you document physical infrastructure, connectivity, fiber, and IP resources more accurately as your environment…
Start reading
Graphical Networks will exhibit at DCF Trends 2026, taking place August 4–6, 2026, at the Hyatt Regency in Reston, Virginia. Stop by Booth #14 to see how netTerrain DCIM software helps data center teams document infrastructure, manage capacity, track assets and connectivity, and maintain a dependable system of record. As data centers grow in size,…
Start reading
Most network teams don’t say: “We have an undocumented network knowledge problem.” They say: “Ask the person who installed it.” “It should be in the old Visio diagram.” “There’s a spreadsheet somewhere.” “Someone on the fiber team knows.” This “system” may work for a while—until that person is unavailable, retires, or leaves the organization. Then…
Start reading