asn.dev

Observed topology

AS30536 CCR-AS

Unclassified ARIN NSP

Upstreams 13 carry this network
Downstreams 2 this network carries
Adjacent (IPv4) 14
Adjacent (IPv6) 5
Upstream graph Who carries AS30536, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS30536 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 13

Networks observed carrying traffic for AS30536: 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.

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv62,557
AS14230ARK Data Centers LLCUnclassifiedIPv41,280
AS174Cogent Communications, LLCTransitIPv4 IPv6315
AS30058FDCservers.netUnclassifiedIPv4 IPv6278
AS3356Level 3 Parent, LLCTransitIPv4160
AS19366FibertownUnclassifiedIPv4118
AS60068Datacamp LimitedHostingIPv4 IPv691
AS5056Aureon Network ServicesResidentialIPv465
AS32425Pixel FactoryHostingIPv465
AS10796Charter Communications IncResidentialIPv462

All 13 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS206100Circle Computer Resources IncUnclassifiedIPv465
AS39946Chick-Fil-A, IncUnclassifiedIPv44

Adjacency

Adjacent networks

All 15

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv62,607
AS14230ARK Data Centers LLCUnclassifiedIPv41,280
AS174Cogent Communications, LLCTransitIPv4 IPv6330
AS30058FDCservers.netUnclassifiedIPv4 IPv6278
AS3356Level 3 Parent, LLCTransitIPv4160
AS19366FibertownUnclassifiedIPv4118
AS60068Datacamp LimitedHostingIPv4 IPv691
AS5056Aureon Network ServicesResidentialIPv465
AS32425Pixel FactoryHostingIPv465
AS206100Circle Computer Resources IncUnclassifiedIPv465

All 15 adjacent →

Provenance

Where this comes from

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