asn.dev

Observed topology

AS3856 PCH-AS

Unclassified ARIN Educational/Research

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

Transit

Upstream networks

All 52

Networks observed carrying traffic for AS3856: 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
AS2914NTT America, Inc.TransitIPv4 IPv68
AS6939Hurricane Electric LLCTransitIPv4 IPv66
AS1403EBOXResidentialIPv4 IPv64
AS22652Videotron LteeResidentialIPv4 IPv63
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv63
AS34927iFog GmbHHostingIPv4 IPv63
AS57463NetIX Communications JSCUnclassifiedIPv4 IPv63
AS58057Securebit AGUnclassifiedIPv4 IPv63
AS852TELUS Communications Inc.ResidentialIPv4 IPv62
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv62

All 52 upstreams →

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 52

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

ASNetworkTypeFamiliesPaths seen
AS2914NTT America, Inc.TransitIPv4 IPv68
AS6939Hurricane Electric LLCTransitIPv4 IPv66
AS1403EBOXResidentialIPv4 IPv64
AS22652Videotron LteeResidentialIPv4 IPv63
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv63
AS34927iFog GmbHHostingIPv4 IPv63
AS57463NetIX Communications JSCUnclassifiedIPv4 IPv63
AS58057Securebit AGUnclassifiedIPv4 IPv63
AS852TELUS Communications Inc.ResidentialIPv4 IPv62
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv62

All 52 adjacent →

Provenance

Where this comes from

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