Observed topology

AS6536 CITYNET - CityNet

Residential ARIN Cable/DSL/ISP

Upstreams 4 carry this network

Downstreams 5 this network carries

Adjacent (IPv4) 9

Adjacent (IPv6) 2

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS6536: 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
AS6461	Zayo Bandwidth	Transit	IPv4 IPv6	125
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	85
AS3356	Level 3 Parent, LLC	Transit	IPv4	80
AS174	Cogent Communications, LLC	Transit	IPv4	46

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS13418	Fort Wayne Newspapers, Inc.	Unclassified	IPv4	58
AS20235	Mylan Pharmaceuticals Inc.	Unclassified	IPv4	58
AS32721	WesBanco Bank, Inc.	Unclassified	IPv4	57
AS46590	City of Charleston	Unclassified	IPv4	16
AS395209	MicroLogic, Inc.	Unclassified	IPv4	15

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS6461	Zayo Bandwidth	Transit	IPv4 IPv6	290
AS3356	Level 3 Parent, LLC	Transit	IPv4	90
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	85
AS174	Cogent Communications, LLC	Transit	IPv4	75
AS13418	Fort Wayne Newspapers, Inc.	Unclassified	IPv4	58
AS20235	Mylan Pharmaceuticals Inc.	Unclassified	IPv4	58
AS32721	WesBanco Bank, Inc.	Unclassified	IPv4	57
AS46590	City of Charleston	Unclassified	IPv4	16
AS395209	MicroLogic, Inc.	Unclassified	IPv4	15

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.