asn.dev

Observed topology

AS214941 UPCELL TELEKOMUNIKASYON LIMITED SIRKETI

Unclassified RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS214941: 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
AS34984Superonline Iletisim Hizmetleri A.S.MobileIPv46
AS9121Turk Telekomunikasyon Anonim SirketiMobileIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS218391MRS BILISIM VE TELEKOMUNIKASYON HIZMETLERI LIMITED SIRKETIUnclassifiedIPv4406
AS41683Earth Telekomunikasyon Bilisim Internet ArGe Yaz. Hiz.Tic. Ltd. StiUnclassifiedIPv4177
AS211961HEDEF GLOBAL BILISIM TEKNOLOJILERI SANAYI TICARET LIMITED SIRKETIUnclassifiedIPv41

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS9121Turk Telekomunikasyon Anonim SirketiMobileIPv4437
AS218391MRS BILISIM VE TELEKOMUNIKASYON HIZMETLERI LIMITED SIRKETIUnclassifiedIPv4406
AS41683Earth Telekomunikasyon Bilisim Internet ArGe Yaz. Hiz.Tic. Ltd. StiUnclassifiedIPv4177
AS12735TurkNet Iletisim Hizmetleri A.S.UnclassifiedIPv4143
AS34984Superonline Iletisim Hizmetleri A.S.MobileIPv411
AS211961HEDEF GLOBAL BILISIM TEKNOLOJILERI SANAYI TICARET LIMITED SIRKETIUnclassifiedIPv41

Provenance

Where this comes from

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