Observed topology
AS3327 CITIC CITIC Telecom CPC Netherlands B.V.
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS3327: 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 | 565 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 489 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 307 |
| AS6453 | TATA COMMUNICATIONS (AMERICA) INC | Transit | IPv4 | 120 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 120 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 IPv6 | 95 |
| AS203790 | Strictera L.L.C-FZ | Unclassified | IPv4 | 59 |
| AS59692 | IQWeb FZ-LLC | Unclassified | IPv4 | 56 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 IPv6 | 42 |
| AS17639 | Converge ICT Solutions Inc. | Unclassified | IPv4 IPv6 | 41 |
Transit
Downstream networks
Networks for which AS3327 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS198068 | CLOUD.DOG OU | Unclassified | IPv4 IPv6 | 2,943 |
| AS4058 | CITIC Telecom International CPC Limited | Unclassified | IPv4 | 649 |
| AS48399 | Svyaz VSD LLC | Unclassified | IPv4 IPv6 | 474 |
| AS42300 | TOP CONNECT OU | Unclassified | IPv4 | 213 |
| AS61189 | Elkdata OU | Hosting | IPv4 IPv6 | 144 |
| AS50794 | Levira AS | Residential | IPv4 IPv6 | 124 |
| AS57873 | SONICTEST Ltd. | Unclassified | IPv4 | 118 |
| AS198966 | Fill Networks OU | Unclassified | IPv4 | 118 |
| AS200804 | OU NORTHSIDE SOLUTIONS | Unclassified | IPv4 | 118 |
| AS12976 | CITIC Telecom CPC Rus LLC | Unclassified | IPv4 IPv6 | 116 |
Adjacency
Adjacent networks
Every AS seen directly next to AS3327 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS198068 | CLOUD.DOG OU | Unclassified | IPv4 IPv6 | 2,943 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 1,935 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 1,185 |
| AS4058 | CITIC Telecom International CPC Limited | Unclassified | IPv4 | 761 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 678 |
| AS48399 | Svyaz VSD LLC | Unclassified | IPv4 IPv6 | 665 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 593 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 IPv6 | 277 |
| AS38001 | NewMedia Express Pte Ltd | Hosting | IPv4 IPv6 | 234 |
| AS50300 | CustodianDC Limited | Unclassified | IPv4 IPv6 | 233 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-20 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.16M 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.