Observed topology
AS6697 BELPAK-AS BELPAK
Residential APNIC
Transit
Upstream networks
Networks observed carrying traffic for AS6697: 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 |
|---|---|---|---|---|
| AS12389 | PJSC Rostelecom | Residential | IPv4 IPv6 | 4,566 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 1,583 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 1,464 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 IPv6 | 1,101 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 894 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 674 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 614 |
| AS8359 | MTS PJSC | Mobile | IPv4 IPv6 | 332 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 230 |
| AS34019 | Hivane Association | Unclassified | IPv4 IPv6 | 229 |
Transit
Downstream networks
Networks for which AS6697 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS25106 | Mobile TeleSystems JLLC | Unclassified | IPv4 IPv6 | 12,395 |
| AS42772 | Unitary enterprise A1 | Unclassified | IPv4 | 1,540 |
| AS28849 | JSC GLOBALONEBEL | Unclassified | IPv4 | 628 |
| AS209881 | LLC "Vash internet partner" | Unclassified | IPv4 IPv6 | 471 |
| AS50334 | Join stock Grodno Regional Techno Commercial Centre GARANT | Unclassified | IPv4 | 434 |
| AS50593 | "T1-Group" LLC | Unclassified | IPv4 | 372 |
| AS60367 | "Seti Plus" Ltd. | Unclassified | IPv4 | 305 |
| AS49243 | The state institution "The Main Economic Office" of the Administrative Affairs Office of the President of the Republic of Belarus | Unclassified | IPv4 | 248 |
| AS50929 | Company with additional Liability "Advanced Technology" | Residential | IPv4 | 248 |
| AS31143 | COSMOS TV JLLC | Unclassified | IPv4 IPv6 | 161 |
Adjacency
Adjacent networks
Every AS seen directly next to AS6697 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS25106 | Mobile TeleSystems JLLC | Unclassified | IPv4 IPv6 | 12,538 |
| AS12389 | PJSC Rostelecom | Residential | IPv4 IPv6 | 7,092 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 IPv6 | 5,886 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 3,849 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 3,267 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 2,098 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 1,597 |
| AS42772 | Unitary enterprise A1 | Unclassified | IPv4 | 1,540 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 IPv6 | 1,322 |
| AS28849 | JSC GLOBALONEBEL | Unclassified | IPv4 | 1,084 |
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.