Observed topology
AS206375 NETSPEED NETSPEED INTERNET A.S.
Residential RIPE Cable/DSL/ISP
Transit
Upstream networks
Networks observed carrying traffic for AS206375: 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 |
|---|---|---|---|---|
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 585 |
| AS9121 | Turk Telekomunikasyon Anonim Sirketi | Mobile | IPv4 IPv6 | 492 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 429 |
| AS44901 | Belcloud LTD | Hosting | IPv4 | 264 |
| AS6939 | Hurricane Electric LLC | Transit | IPv6 | 260 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 151 |
| AS4849 | S3 Company Ltd | Hosting | IPv4 | 88 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 | 66 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 59 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 IPv6 | 59 |
Transit
Downstream networks
Networks for which AS206375 was observed as the last hop before the origin, meaning it appears to provide them transit.
Adjacency
Adjacent networks
Every AS seen directly next to AS206375 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS9121 | Turk Telekomunikasyon Anonim Sirketi | Mobile | IPv4 IPv6 | 1,119 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 585 |
| AS206119 | Veganet Teknolojileri ve Hizmetleri LTD STI | Unclassified | IPv4 | 522 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 429 |
| AS44901 | Belcloud LTD | Hosting | IPv4 | 264 |
| AS6939 | Hurricane Electric LLC | Transit | IPv6 | 260 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 151 |
| AS4849 | S3 Company Ltd | Hosting | IPv4 | 88 |
| AS21245 | MEDIANOVA INTERNET HIZMETLERI VE TICARET ANONIM SIRKETI | Hosting | IPv4 | 84 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 | 66 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-11 10:00 UTC by route-views2,rrc00, as seen from 74 BGP vantage points across 73.24M 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.