Observed topology
AS206621 ITKARKAS-AS
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS206621: 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 |
|---|---|---|---|---|
| AS44600 | "GIGATRANS UKRAINE", LLC | Unclassified | IPv4 | 153 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 24 |
| AS6939 | Hurricane Electric LLC | Transit | IPv6 | 19 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 | 6 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 4 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 3 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 3 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 | 3 |
| AS29632 | Netassist International EOOD | Unclassified | IPv6 | 2 |
Transit
Downstream networks
Networks for which AS206621 was observed as the last hop before the origin, meaning it appears to provide them transit.
Adjacency
Adjacent networks
Every AS seen directly next to AS206621 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS44600 | "GIGATRANS UKRAINE", LLC | Unclassified | IPv4 | 871 |
| AS51993 | LLC Telekompaniya Region | Residential | IPv4 | 783 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 167 |
| AS43384 | State University of Intelligent Technologies and Telecommunications | Unclassified | IPv4 | 129 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 | 22 |
| AS6939 | Hurricane Electric LLC | Transit | IPv6 | 19 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 17 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 17 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 | 8 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 6 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-25 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.18M 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.