asn.dev

Observed topology

AS203118 EZERDI Ezerdi LLC

Hosting RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS203118: 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
AS12389PJSC RostelecomResidentialIPv470
AS60764Telecom Samara LLCUnclassifiedIPv4 IPv641
AS3216PJSC "Vimpelcom"MobileIPv437
AS51028Zummer LLCUnclassifiedIPv45
AS24482SG.GSHostingIPv4 IPv63
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv4 IPv63
AS37721Virtual Technologies & SolutionsResidentialIPv42
AS49673Truenetwork LLCUnclassifiedIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS39735"Permtelecom" LtdUnclassifiedIPv4171
AS57842UralKonnektServis LLCUnclassifiedIPv4 IPv6149
AS6874Perm National Research Polytechnic UniversityEducationIPv415

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS39735"Permtelecom" LtdUnclassifiedIPv4182
AS60764Telecom Samara LLCUnclassifiedIPv4 IPv6180
AS57842UralKonnektServis LLCUnclassifiedIPv4 IPv6156
AS12389PJSC RostelecomResidentialIPv4137
AS3216PJSC "Vimpelcom"MobileIPv4126
AS51028Zummer LLCUnclassifiedIPv442
AS6874Perm National Research Polytechnic UniversityEducationIPv415
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv4 IPv614
AS37721Virtual Technologies & SolutionsResidentialIPv412
AS24482SG.GSHostingIPv4 IPv63

All 11 adjacent →

Provenance

Where this comes from

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