Observed topology
AS197324 BGP43 Vladyslav Koba
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS197324: 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.
Transit
Downstream networks
Networks for which AS197324 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS202396 | Zeng Yukai | Unclassified | IPv6 | 74 |
| AS218444 | Muhammet Eren Karaman | Unclassified | IPv6 | 39 |
| AS219310 | EMIRASLAN EMIRASLANOV | Unclassified | IPv6 | 37 |
| AS219378 | ZHANG XIYUAN | Unclassified | IPv6 | 33 |
| AS152135 | Cubiscomm Signal Sales, Inc. | Unclassified | IPv4 | 7 |
| AS214507 | SIA "Puces datorsistemas" | Unclassified | IPv4 IPv6 | 6 |
| AS208068 | Ludwig Moritz Hodiamont | Unclassified | IPv6 | 4 |
| AS218165 | Markus Reich | Unclassified | IPv6 | 4 |
| AS403147 | UG | Unclassified | IPv6 | 4 |
| AS201028 | Vexura UG (Haftungsbeschraenkt) | Unclassified | IPv6 | 3 |
Adjacency
Adjacent networks
Every AS seen directly next to AS197324 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS11967 | Hop179 OU | Unclassified | IPv4 IPv6 | 151 |
| AS218569 | Viktor Nesmeianov | Unclassified | IPv4 IPv6 | 88 |
| AS202396 | Zeng Yukai | Unclassified | IPv6 | 74 |
| AS215828 | Tizian Maxime Weigt trading as "TMW Global Networks" | Hosting | IPv4 IPv6 | 62 |
| AS218444 | Muhammet Eren Karaman | Unclassified | IPv6 | 39 |
| AS219310 | EMIRASLAN EMIRASLANOV | Unclassified | IPv6 | 37 |
| AS219378 | ZHANG XIYUAN | Unclassified | IPv6 | 33 |
| AS205941 | Lungu Stefan Gabriel | Unclassified | IPv6 | 31 |
| AS152135 | Cubiscomm Signal Sales, Inc. | Unclassified | IPv4 | 7 |
| AS214507 | SIA "Puces datorsistemas" | Unclassified | IPv4 IPv6 | 6 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-13 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.40M 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.