asn.dev

Observed topology

AS395502 JCOLO

Unclassified ARIN NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS395502: 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 IPv6199
AS21559OSNETUnclassifiedIPv4 IPv664
AS6461Zayo BandwidthTransitIPv4 IPv650
AS20055Wholesail networks LLCResidentialIPv4 IPv621
AS11404Wave BroadbandResidentialIPv48
AS18895Nustream CommunicationsUnclassifiedIPv41
AS58057Securebit AGUnclassifiedIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS20940Akamai International B.V.HostingIPv4 IPv6102
AS34553PacketframeUnclassifiedIPv4 IPv6102
AS63293Facebook, Inc.HostingIPv4 IPv6102

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6501
AS34553PacketframeUnclassifiedIPv4 IPv6341
AS21559OSNETUnclassifiedIPv4 IPv6268
AS20940Akamai International B.V.HostingIPv4 IPv6102
AS63293Facebook, Inc.HostingIPv4 IPv6102
AS20055Wholesail networks LLCResidentialIPv4 IPv656
AS6461Zayo BandwidthTransitIPv4 IPv650
AS11404Wave BroadbandResidentialIPv412
AS18895Nustream CommunicationsUnclassifiedIPv41
AS58057Securebit AGUnclassifiedIPv61

Provenance

Where this comes from

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