asn.dev

Observed topology

AS34718 TPSUZ-AS "IST TELEKOM" JV LLC

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS34718: 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
AS28910"Uzbektelekom" Joint Stock CompanyUnclassifiedIPv4 IPv61,256

Transit

Downstream networks

All 30

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

ASNetworkTypeFamiliesPaths seen
AS43647"SERVERCORE CIS" FE LLCUnclassifiedIPv41,212
AS35682BEST INTERNET SOLUTION XKUnclassifiedIPv4801
AS43533OOO "Gals Telecom"ResidentialIPv4732
AS215028ITGLOBALCOM U LLCUnclassifiedIPv4494
AS39032"IST TELEKOM" JV LLCUnclassifiedIPv4442
AS47141Lit-Tel LLCUnclassifiedIPv4378
AS49424New Line Solutions LLCUnclassifiedIPv4256
AS210519ToshTeleQabul MChJUnclassifiedIPv4256
AS197661LLC ONE-NETUnclassifiedIPv4191
AS202436Century Dynamics LLCUnclassifiedIPv4189

All 30 downstreams →

Adjacency

Adjacent networks

All 31

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

ASNetworkTypeFamiliesPaths seen
AS28910"Uzbektelekom" Joint Stock CompanyUnclassifiedIPv4 IPv67,821
AS43647"SERVERCORE CIS" FE LLCUnclassifiedIPv41,212
AS35682BEST INTERNET SOLUTION XKUnclassifiedIPv4801
AS43533OOO "Gals Telecom"ResidentialIPv4732
AS215028ITGLOBALCOM U LLCUnclassifiedIPv4494
AS39032"IST TELEKOM" JV LLCUnclassifiedIPv4442
AS47141Lit-Tel LLCUnclassifiedIPv4378
AS49424New Line Solutions LLCUnclassifiedIPv4256
AS210519ToshTeleQabul MChJUnclassifiedIPv4256
AS197661LLC ONE-NETUnclassifiedIPv4191

All 31 adjacent →

Provenance

Where this comes from

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