asn.dev

Observed topology

AS25085 DMITRY-AS

Unclassified RIPE Network Services

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS25085: 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
AS31898Oracle CorporationHostingIPv6130
AS53667FranTech SolutionsHostingIPv672
AS44324MoeDove LLCResidentialIPv665
AS49962ALUE LTDUnclassifiedIPv637
AS17433Hytron Network Services LimitedResidentialIPv635
AS357084b42 UGUnclassifiedIPv61
AS37989DCS1 Pte. Ltd.HostingIPv61
AS58057Securebit AGUnclassifiedIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS49962ALUE LTDUnclassifiedIPv632
AS56367ALUE LTDUnclassifiedIPv632

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS31898Oracle CorporationHostingIPv6130
AS44324MoeDove LLCResidentialIPv6129
AS53667FranTech SolutionsHostingIPv672
AS49962ALUE LTDUnclassifiedIPv669
AS17433Hytron Network Services LimitedResidentialIPv635
AS56367ALUE LTDUnclassifiedIPv632
AS357084b42 UGUnclassifiedIPv61
AS37989DCS1 Pte. Ltd.HostingIPv61
AS58057Securebit AGUnclassifiedIPv61

Provenance

Where this comes from

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