Observed topology
AS34718 TPSUZ-AS EAST TELECOM ISP ET,TPS,EVO
Unclassified RIPE Cable/DSL/ISP
Transit
Upstream networks
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.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS28910 | "Uzbektelekom" Joint Stock Company | Unclassified | IPv4 IPv6 | 1,311 |
Transit
Downstream networks
Networks for which AS34718 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS43647 | "SERVERCORE CIS" FE LLC | Unclassified | IPv4 | 1,249 |
| AS35682 | BEST INTERNET SOLUTION XK | Unclassified | IPv4 | 814 |
| AS43533 | OOO "Gals Telecom" | Residential | IPv4 | 756 |
| AS215028 | ITGLOBALCOM U LLC | Unclassified | IPv4 | 585 |
| AS39032 | "IST TELEKOM" JV LLC | Unclassified | IPv4 | 449 |
| AS47141 | Lit-Tel LLC | Unclassified | IPv4 | 378 |
| AS49424 | New Line Solutions LLC | Unclassified | IPv4 | 260 |
| AS210519 | ToshTeleQabul MChJ | Unclassified | IPv4 | 260 |
| AS197661 | LLC ONE-NET | Unclassified | IPv4 | 195 |
| AS202436 | Century Dynamics LLC | Unclassified | IPv4 | 194 |
Adjacency
Adjacent networks
Every AS seen directly next to AS34718 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS28910 | "Uzbektelekom" Joint Stock Company | Unclassified | IPv4 IPv6 | 8,169 |
| AS43647 | "SERVERCORE CIS" FE LLC | Unclassified | IPv4 | 1,249 |
| AS35682 | BEST INTERNET SOLUTION XK | Unclassified | IPv4 | 814 |
| AS43533 | OOO "Gals Telecom" | Residential | IPv4 | 756 |
| AS215028 | ITGLOBALCOM U LLC | Unclassified | IPv4 | 585 |
| AS39032 | "IST TELEKOM" JV LLC | Unclassified | IPv4 | 449 |
| AS47141 | Lit-Tel LLC | Unclassified | IPv4 | 378 |
| AS49424 | New Line Solutions LLC | Unclassified | IPv4 | 260 |
| AS210519 | ToshTeleQabul MChJ | Unclassified | IPv4 | 260 |
| AS197661 | LLC ONE-NET | Unclassified | IPv4 | 195 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-26 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.14M 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.