Observed topology

AS59816 BLYNX

Unclassified ARIN

Upstreams 9 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 8

Adjacent (IPv6) 5

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS59816: 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
AS3356	Level 3 Parent, LLC	Transit	IPv4	389
AS39175	Connective Online Limited	Hosting	IPv4	120
AS39545	Fluidone Ltd.	Unclassified	IPv4	59
AS6939	Hurricane Electric LLC	Transit	IPv6	31
AS3257	GTT Communications Inc.	Transit	IPv4 IPv6	11
AS24482	SG.GS	Hosting	IPv4 IPv6	8
AS48185	team.blue NV	Unclassified	IPv4 IPv6	8
AS33891	Core-Backbone GmbH	Hosting	IPv4	7
AS50300	CustodianDC Limited	Unclassified	IPv6	1

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS215675	Perception TVCDN Ltd	Unclassified	IPv4	60

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS3356	Level 3 Parent, LLC	Transit	IPv4	449
AS39175	Connective Online Limited	Hosting	IPv4	121
AS215675	Perception TVCDN Ltd	Unclassified	IPv4	60
AS39545	Fluidone Ltd.	Unclassified	IPv4	59
AS6939	Hurricane Electric LLC	Transit	IPv6	31
AS3257	GTT Communications Inc.	Transit	IPv4 IPv6	12
AS24482	SG.GS	Hosting	IPv4 IPv6	8
AS48185	team.blue NV	Unclassified	IPv4 IPv6	8
AS33891	Core-Backbone GmbH	Hosting	IPv4	7
AS50300	CustodianDC Limited	Unclassified	IPv6	1

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.