asn.dev

Observed topology

AS19016 WCG-AS

Residential ARIN Cable/DSL/ISP

Upstreams 11 carry this network
Downstreams 3 this network carries
Adjacent (IPv4) 11
Adjacent (IPv6) 12
Upstream graph Who carries AS19016, and who carries them, drawn as a map up to the transit-free core. 3 exchanges Where AS19016 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 11

Networks observed carrying traffic for AS19016: 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
AS6461Zayo BandwidthTransitIPv4 IPv6377
AS174Cogent Communications, LLCTransitIPv4 IPv6270
AS6939Hurricane Electric LLCTransitIPv4 IPv6252
AS22652Videotron LteeResidentialIPv4 IPv641
AS24482SG.GSHostingIPv4 IPv622
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv622
AS852TELUS Communications Inc.ResidentialIPv4 IPv620
AS293ESnetUnclassifiedIPv419
AS35280F5 Networks SARLHostingIPv4 IPv618
AS1403EBOXResidentialIPv66

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS394081Westman Communications GroupResidentialIPv4232
AS396045Spliced Networks Inc.UnclassifiedIPv4 IPv691
AS394522Assiniboine CollegeUnclassifiedIPv61

Adjacency

Adjacent networks

All 14

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

ASNetworkTypeFamiliesPaths seen
AS6461Zayo BandwidthTransitIPv4 IPv6547
AS174Cogent Communications, LLCTransitIPv4 IPv6349
AS6939Hurricane Electric LLCTransitIPv4 IPv6295
AS394081Westman Communications GroupResidentialIPv4232
AS396045Spliced Networks Inc.UnclassifiedIPv4 IPv691
AS22652Videotron LteeResidentialIPv4 IPv652
AS24482SG.GSHostingIPv4 IPv628
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv628
AS293ESnetUnclassifiedIPv424
AS852TELUS Communications Inc.ResidentialIPv4 IPv620

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-26 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.