Observed topology
AS6663 TTI-NET
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS6663: 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 |
|---|---|---|---|---|
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 | 432 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 386 |
| AS5405 | Inter.link GmbH | Unclassified | IPv4 IPv6 | 348 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 342 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 300 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 146 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 146 |
| AS3333 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv4 IPv6 | 50 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 50 |
| AS29504 | Freenet Liberec, z.s. | Unclassified | IPv4 IPv6 | 50 |
Transit
Downstream networks
Networks for which AS6663 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS48955 | Internet Resources Management SRL | Unclassified | IPv4 | 1,864 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 IPv6 | 1,524 |
| AS41496 | TV SAT 2002 SRL | Residential | IPv4 IPv6 | 1,134 |
| AS203680 | Araz Tech LLC | Unclassified | IPv4 IPv6 | 868 |
| AS49468 | MAGIT'ST SRL | Unclassified | IPv4 | 737 |
| AS211306 | Treadstone Business Development S.R.L. | Unclassified | IPv4 | 704 |
| AS41710 | MIIT LLC | Unclassified | IPv4 | 689 |
| AS212192 | INTELI TECH DEVELOPMENT SRL | Unclassified | IPv4 | 645 |
| AS13335 | Cloudflare, Inc. | Hosting | IPv4 IPv6 | 583 |
| AS49824 | PC "Astra-net" | Residential | IPv4 IPv6 | 580 |
Adjacency
Adjacent networks
Every AS seen directly next to AS6663 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 IPv6 | 15,792 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 9,189 |
| AS29049 | Delta Telecom Ltd | Residential | IPv4 IPv6 | 8,181 |
| AS5405 | Inter.link GmbH | Unclassified | IPv4 IPv6 | 5,912 |
| AS9121 | Turk Telekomunikasyon Anonim Sirketi | Mobile | IPv4 | 5,194 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 4,891 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 4,698 |
| AS42708 | Glesys AB | Unclassified | IPv4 IPv6 | 4,242 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 3,619 |
| AS202297 | Skylon Solutions Limited | Unclassified | IPv4 | 3,104 |
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.