asn.dev

Observed topology

AS25795 ARPNET - ARP NETWORKS, INC.

Unclassified ARIN NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS25795: 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
AS29838Atlantic Metro Communications II, Inc.HostingIPv4 IPv6500
AS396356Latitude.shHostingIPv4 IPv6240

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS36171Strasmore, Inc.UnclassifiedIPv481
AS201612nic.at GmbHUnclassifiedIPv4 IPv631
AS9559Plain Communications LtdUnclassifiedIPv428
AS25692AEGIS INFORMATION SYSTEMS INCUnclassifiedIPv428
AS402810TDDT,UnclassifiedIPv427
AS23646Clarinet Internet SolutionsUnclassifiedIPv416
AS204135LEMARIT GmbHUnclassifiedIPv4 IPv614
AS19044The Inner NetUnclassifiedIPv42

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS29838Atlantic Metro Communications II, Inc.HostingIPv4 IPv6711
AS396356Latitude.shHostingIPv4 IPv6254
AS36171Strasmore, Inc.UnclassifiedIPv481
AS201612nic.at GmbHUnclassifiedIPv4 IPv631
AS9559Plain Communications LtdUnclassifiedIPv428
AS25692AEGIS INFORMATION SYSTEMS INCUnclassifiedIPv428
AS402810TDDT,UnclassifiedIPv427
AS23646Clarinet Internet SolutionsUnclassifiedIPv416
AS204135LEMARIT GmbHUnclassifiedIPv4 IPv614
AS19044The Inner NetUnclassifiedIPv42

All 11 adjacent →

Provenance

Where this comes from

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