Observed topology

AS40128 MUSFIBERNET - Morristown Utility Systems

Unclassified ARIN Cable/DSL/ISP

Upstreams 5 carry this network

Downstreams 6 this network carries

Adjacent (IPv4) 11

Adjacent (IPv6) 0

Upstream graph Who carries AS40128, and who carries them, drawn as a map up to the transit-free core. 2 exchanges Where AS40128 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS40128: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.

AS	Network	Type	Families	Paths seen
AS2914	NTT America, Inc.	Transit	IPv4	331
AS6939	Hurricane Electric LLC	Transit	IPv4	79
AS14016	Capcon Networks	Unclassified	IPv4	45
AS24482	SG.GS	Hosting	IPv4	8
AS37721	Virtual Technologies & Solutions	Residential	IPv4	8

Transit

Downstream networks

inferred

Networks for which AS40128 was observed as the last hop before the origin, meaning it appears to provide them transit.

AS	Network	Type	Families	Paths seen
AS36367	Alchemy Global Networks, LLC	Unclassified	IPv4	118
AS398854	Ultranet, LLC	Unclassified	IPv4	118
AS62923	Lakeway Publishers, Inc.	Unclassified	IPv4	59
AS402547	J	Unclassified	IPv4	59
AS40798	Wallace Hardware Co., Inc.	Unclassified	IPv4	58
AS55024	Walters State Community College	Unclassified	IPv4	6

Adjacency

Adjacent networks

All 11

Every AS seen directly next to AS40128 in a routing path, in either direction.

AS	Network	Type	Families	Paths seen
AS2914	NTT America, Inc.	Transit	IPv4	625
AS14016	Capcon Networks	Unclassified	IPv4	169
AS36367	Alchemy Global Networks, LLC	Unclassified	IPv4	118
AS398854	Ultranet, LLC	Unclassified	IPv4	118
AS6939	Hurricane Electric LLC	Transit	IPv4	79
AS62923	Lakeway Publishers, Inc.	Unclassified	IPv4	59
AS402547	J	Unclassified	IPv4	59
AS40798	Wallace Hardware Co., Inc.	Unclassified	IPv4	58
AS24482	SG.GS	Hosting	IPv4	8
AS37721	Virtual Technologies & Solutions	Residential	IPv4	8

All 11 adjacent →

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-08 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.00M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you. Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.

Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.