asn.dev

Observed topology

AS22995 BARR-XPLR-ASN

Unclassified ARIN

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

Transit

Upstream networks

All 20

Networks observed carrying traffic for AS22995: 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
AS3356Level 3 Parent, LLCTransitIPv4 IPv62,507
AS6939Hurricane Electric LLCTransitIPv4 IPv62,274
AS6461Zayo BandwidthTransitIPv4 IPv61,754
AS3257GTT Communications Inc.TransitIPv4 IPv61,036
AS22652Videotron LteeResidentialIPv4 IPv6252
AS2914NTT America, Inc.TransitIPv4250
AS24482SG.GSHostingIPv4 IPv6151
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv6141
AS852TELUS Communications Inc.ResidentialIPv4 IPv6132
AS34927iFog GmbHHostingIPv4117

All 20 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS30028Xplore Inc.UnclassifiedIPv4575
AS32100Xplore Inc.UnclassifiedIPv4 IPv6561
AS40473Xplore Inc.ResidentialIPv4385
AS3367Xplore Inc.ResidentialIPv4 IPv665

Adjacency

Adjacent networks

All 24

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv63,309
AS3356Level 3 Parent, LLCTransitIPv4 IPv62,895
AS6461Zayo BandwidthTransitIPv4 IPv62,076
AS3257GTT Communications Inc.TransitIPv4 IPv61,226
AS30028Xplore Inc.UnclassifiedIPv41,036
AS32100Xplore Inc.UnclassifiedIPv4 IPv6561
AS40473Xplore Inc.ResidentialIPv4385
AS22652Videotron LteeResidentialIPv4 IPv6289
AS2914NTT America, Inc.TransitIPv4250
AS24482SG.GSHostingIPv4 IPv6167

All 24 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.