asn.dev

Observed topology

AS202413 Pronkin Timofei

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS202413: 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.

No upstream observed. Typical for a tier-1 network that buys transit from nobody.

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS212743ETERNITY INTERNATIONAL LIMITEDUnclassifiedIPv4 IPv61,123
AS215103Sozonov Matvei AndreevichUnclassifiedIPv4120
AS219357Kochedykov Egor AleksandrovichUnclassifiedIPv4120
AS198685LUNAR HOSTING LTDUnclassifiedIPv4119
AS216150Nurmukan ZhantorinUnclassifiedIPv460
AS218914Datagio Systems Ltd.UnclassifiedIPv460

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS212743ETERNITY INTERNATIONAL LIMITEDUnclassifiedIPv4 IPv61,241
AS49581Ferdinand Zink trading as Tube-HostingHostingIPv41,081
AS62403PletX GmbHUnclassifiedIPv4 IPv6509
AS215730FZCOUnclassifiedIPv4122
AS215103Sozonov Matvei AndreevichUnclassifiedIPv4120
AS219357Kochedykov Egor AleksandrovichUnclassifiedIPv4120
AS198685LUNAR HOSTING LTDUnclassifiedIPv4119
AS216150Nurmukan ZhantorinUnclassifiedIPv460
AS218914Datagio Systems Ltd.UnclassifiedIPv460
AS207208MEVSPACE sp. z o.o.UnclassifiedIPv48

Provenance

Where this comes from

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