Observed topology

AS399220 UPSTATE-FIBER-NETWORK

Unclassified ARIN

Upstreams 7 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 8

Adjacent (IPv6) 3

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS399220: 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
AS13536	FirstLight Fiber, Inc.	Residential	IPv4 IPv6	605
AS174	Cogent Communications, LLC	Transit	IPv4	320
AS3356	Level 3 Parent, LLC	Transit	IPv4 IPv6	143
AS46887	Crown Castle Fiber LLC	Unclassified	IPv4	120
AS11722	Slic Network Solutions, Inc	Residential	IPv4	36
AS7828	Northland Communications	Unclassified	IPv4	8
AS46414	GoNetSpeed	Unclassified	IPv4 IPv6	6

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS395685	Ontario Telephone Company Inc	Unclassified	IPv4	390

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS13536	FirstLight Fiber, Inc.	Residential	IPv4 IPv6	987
AS395685	Ontario Telephone Company Inc	Unclassified	IPv4	390
AS174	Cogent Communications, LLC	Transit	IPv4	320
AS3356	Level 3 Parent, LLC	Transit	IPv4 IPv6	143
AS46887	Crown Castle Fiber LLC	Unclassified	IPv4	120
AS11722	Slic Network Solutions, Inc	Residential	IPv4	44
AS7828	Northland Communications	Unclassified	IPv4	8
AS46414	GoNetSpeed	Unclassified	IPv4 IPv6	6

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-21 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.14M 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.