Observed topology

AS3599 BINCNET

Hosting ARIN Content

Upstreams 7 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 8

Adjacent (IPv6) 4

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS3599: 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
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	475
AS13649	Flexential Colorado Corp.	Hosting	IPv4 IPv6	248
AS2914	NTT America, Inc.	Transit	IPv4 IPv6	97
AS174	Cogent Communications, LLC	Transit	IPv4 IPv6	84
AS8001	Cologix, Inc	Hosting	IPv4	57
AS6461	Zayo Bandwidth	Transit	IPv4	50
AS11796	Airstream Communications, LLC	Residential	IPv4	14

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS395446	Briggs & Stratton Corporation	Unclassified	IPv4	59

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	475
AS13649	Flexential Colorado Corp.	Hosting	IPv4 IPv6	248
AS2914	NTT America, Inc.	Transit	IPv4 IPv6	118
AS174	Cogent Communications, LLC	Transit	IPv4 IPv6	107
AS6461	Zayo Bandwidth	Transit	IPv4	65
AS395446	Briggs & Stratton Corporation	Unclassified	IPv4	59
AS8001	Cologix, Inc	Hosting	IPv4	57
AS11796	Airstream Communications, LLC	Residential	IPv4	14

Provenance

Where this comes from

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