asn.dev

Observed topology

AS203493 YACOLO-AS Egor Timoshenko

Hosting RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS203493: 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
AS48858JSC "ER-Telecom Holding"UnclassifiedIPv4 IPv6250
AS35598INETCOM CARRIER LLCUnclassifiedIPv4171
AS39927E-Light-Telecom Ltd.UnclassifiedIPv470
AS62255BiMajLink d.o.o.UnclassifiedIPv427
AS13094JSC "ER-Telecom Holding"UnclassifiedIPv4 IPv618

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS207713GLOBAL INTERNET SOLUTIONS LLCHostingIPv4 IPv6452
AS218462NOTBAD HOSTING LTDUnclassifiedIPv459

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS48858JSC "ER-Telecom Holding"UnclassifiedIPv4 IPv6642
AS207713GLOBAL INTERNET SOLUTIONS LLCHostingIPv4 IPv6452
AS35598INETCOM CARRIER LLCUnclassifiedIPv4229
AS13094JSC "ER-Telecom Holding"UnclassifiedIPv4 IPv678
AS39927E-Light-Telecom Ltd.UnclassifiedIPv470
AS218462NOTBAD HOSTING LTDUnclassifiedIPv459
AS62255BiMajLink d.o.o.UnclassifiedIPv427
AS31500Global Network Management IncUnclassifiedIPv41

Provenance

Where this comes from

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