Observed topology
AS209604 TWO-E-TELEKOM
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS209604: 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 |
|---|---|---|---|---|
| AS16276 | OVH SAS | Hosting | IPv4 | 1,027 |
| AS201178 | Euronet Telekomunikasyon A.S. | Residential | IPv4 | 960 |
| AS23470 | ReliableSite.Net LLC | Hosting | IPv4 | 700 |
| AS135523 | Multinet Broadband | Unclassified | IPv4 | 231 |
| AS44901 | Belcloud LTD | Hosting | IPv4 | 192 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 188 |
| AS6206 | Netrouting B.V. | Hosting | IPv4 | 118 |
| AS13335 | Cloudflare, Inc. | Hosting | IPv4 | 65 |
| AS15612 | ServeCentric Ltd. | Unclassified | IPv4 | 60 |
| AS219384 | Satcore LLC | Unclassified | IPv4 | 59 |
Transit
Downstream networks
Networks for which AS209604 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS204223 | Serverplance Bilisim Ve Telekomunikasyon Hizm. Ltd. Sti. | Unclassified | IPv4 | 61 |
| AS215409 | Mucahid Selvi trading as Yaztek Yazilim Teknolojileri ve Bilgisayar Sisteml | Unclassified | IPv4 | 61 |
| AS212069 | Hostixo Internet Bilisim Yazilim Hizmetleri Tic. ve San. Ltd. Sti. | Unclassified | IPv4 | 60 |
Adjacency
Adjacent networks
Every AS seen directly next to AS209604 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS201178 | Euronet Telekomunikasyon A.S. | Residential | IPv4 | 1,142 |
| AS16276 | OVH SAS | Hosting | IPv4 | 1,027 |
| AS23470 | ReliableSite.Net LLC | Hosting | IPv4 | 700 |
| AS135523 | Multinet Broadband | Unclassified | IPv4 | 231 |
| AS44901 | Belcloud LTD | Hosting | IPv4 | 192 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 188 |
| AS6206 | Netrouting B.V. | Hosting | IPv4 | 118 |
| AS13335 | Cloudflare, Inc. | Hosting | IPv4 | 65 |
| AS204223 | Serverplance Bilisim Ve Telekomunikasyon Hizm. Ltd. Sti. | Unclassified | IPv4 | 61 |
| AS215409 | Mucahid Selvi trading as Yaztek Yazilim Teknolojileri ve Bilgisayar Sisteml | Unclassified | IPv4 | 61 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-17 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.18M 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.