asn.dev

Observed topology

AS25846 US-CLOUDNIUM-01

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS25846: 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
AS397423Tier.Net Technologies LLCHostingIPv4 IPv6432
AS174Cogent Communications, LLCTransitIPv494
AS19108OptimumUnclassifiedIPv470
AS5650Frontier Communications of America, Inc.ResidentialIPv49

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS402069Moneta Solutions, IncUnclassifiedIPv4 IPv6347
AS401043MJF Ventures LLCUnclassifiedIPv4228
AS402094SRJK LLCUnclassifiedIPv4 IPv690

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS397423Tier.Net Technologies LLCHostingIPv4 IPv61,097
AS402069Moneta Solutions, IncUnclassifiedIPv4 IPv6347
AS401043MJF Ventures LLCUnclassifiedIPv4228
AS174Cogent Communications, LLCTransitIPv494
AS402094SRJK LLCUnclassifiedIPv4 IPv690
AS19108OptimumUnclassifiedIPv470
AS5650Frontier Communications of America, Inc.ResidentialIPv49

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-18 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.