Observed topology
AS6823 TR-3C1B-TELEKOM
Residential RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS6823: 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 |
|---|---|---|---|---|
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 200 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 190 |
| AS5405 | Inter.link GmbH | Unclassified | IPv4 | 180 |
| AS4849 | S3 Company Ltd | Hosting | IPv4 | 85 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 74 |
| AS6204 | INTERKVM HOST SRL | Unclassified | IPv4 | 71 |
| AS44901 | Belcloud LTD | Hosting | IPv4 | 38 |
| AS3333 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv4 IPv6 | 19 |
| AS9121 | Turk Telekomunikasyon Anonim Sirketi | Mobile | IPv4 | 19 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 19 |
Transit
Downstream networks
Networks for which AS6823 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS60847 | Karel Iletisim Hizmetleri A.S. | Unclassified | IPv4 | 502 |
| AS47894 | Veriteknik Bilisim Basin Ve Yayin Limited Sirketi | Unclassified | IPv4 | 490 |
| AS204647 | MIXNET TELEKOMUNIKASYON HIZMETLERI AS | Unclassified | IPv4 | 125 |
| AS8685 | Doruk Iletisim ve Otomasyon Sanayi ve Ticaret A.S. | Hosting | IPv4 | 48 |
| AS199099 | ERLION BILISIM LIMITED SIRKETI | Unclassified | IPv4 | 13 |
Adjacency
Adjacent networks
Every AS seen directly next to AS6823 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 556 |
| AS47894 | Veriteknik Bilisim Basin Ve Yayin Limited Sirketi | Unclassified | IPv4 | 549 |
| AS60847 | Karel Iletisim Hizmetleri A.S. | Unclassified | IPv4 | 502 |
| AS5405 | Inter.link GmbH | Unclassified | IPv4 | 460 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 254 |
| AS44901 | Belcloud LTD | Hosting | IPv4 | 161 |
| AS4849 | S3 Company Ltd | Hosting | IPv4 | 148 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 128 |
| AS204647 | MIXNET TELEKOMUNIKASYON HIZMETLERI AS | Unclassified | IPv4 | 125 |
| AS6204 | INTERKVM HOST SRL | Unclassified | IPv4 | 71 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-11 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.47M 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.