asn.dev

Observed topology

AS55256 NETSKOPE

Hosting ARIN Network Services

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

Transit

Upstream networks

All 116

Networks observed carrying traffic for AS55256: 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
AS1299Arelion Sweden ABTransitIPv48,581
AS174Cogent Communications, LLCTransitIPv44,695
AS6939Hurricane Electric LLCTransitIPv43,605
AS2914NTT America, Inc.TransitIPv42,226
AS9498BHARTI Airtel Ltd.MobileIPv42,049
AS7195EDGEUNO S.A.SUnclassifiedIPv41,976
AS3356Level 3 Parent, LLCTransitIPv41,736
AS3491PCCW Global (HK) Ltd.TransitIPv41,552
AS4826Vocus Connect International BackboneUnclassifiedIPv41,078
AS39386Saudi Telecom Company JSCUnclassifiedIPv4588

Transit

Downstream networks

inferred

Networks for which AS55256 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 116

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv48,581
AS174Cogent Communications, LLCTransitIPv44,695
AS6939Hurricane Electric LLCTransitIPv43,605
AS2914NTT America, Inc.TransitIPv42,226
AS9498BHARTI Airtel Ltd.MobileIPv42,049
AS7195EDGEUNO S.A.SUnclassifiedIPv41,976
AS3356Level 3 Parent, LLCTransitIPv41,736
AS3491PCCW Global (HK) Ltd.TransitIPv41,552
AS4826Vocus Connect International BackboneUnclassifiedIPv41,078
AS39386Saudi Telecom Company JSCUnclassifiedIPv4588

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.