Observed topology
AS213622 FALCON Falcon FZE LLC
Unclassified RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS213622: 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 |
|---|---|---|---|---|
| AS137409 | GSL Networks Pty LTD | Unclassified | IPv4 | 61 |
| AS6939 | Hurricane Electric LLC | Transit | IPv6 | 13 |
| AS174 | Cogent Communications, LLC | Transit | IPv6 | 10 |
| AS3257 | GTT Communications Inc. | Transit | IPv6 | 6 |
| AS6204 | INTERKVM HOST SRL | Unclassified | IPv6 | 1 |
| AS24482 | SG.GS | Hosting | IPv6 | 1 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv6 | 1 |
Transit
Downstream networks
Networks for which AS213622 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS208111 | Falcon FZE LLC | Unclassified | IPv4 IPv6 | 250 |
| AS206226 | Little Orbit Inc. | Unclassified | IPv4 IPv6 | 248 |
| AS216078 | Liam Kremer | Hosting | IPv4 IPv6 | 101 |
| AS401323 | LayerByte LLC | Unclassified | IPv4 IPv6 | 94 |
| AS402259 | ZT Enterprises LLC | Unclassified | IPv4 IPv6 | 94 |
| AS401502 | Falcon (America) LLC | Unclassified | IPv4 IPv6 | 91 |
| AS214371 | Gijs van de Sande | Hosting | IPv4 IPv6 | 53 |
| AS214757 | Jakub Krsa | Unclassified | IPv4 IPv6 | 53 |
| AS219187 | Tangtech Internet Services LLC | Unclassified | IPv6 | 34 |
Adjacency
Adjacent networks
Every AS seen directly next to AS213622 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS137409 | GSL Networks Pty LTD | Unclassified | IPv4 IPv6 | 925 |
| AS208111 | Falcon FZE LLC | Unclassified | IPv4 IPv6 | 250 |
| AS206226 | Little Orbit Inc. | Unclassified | IPv4 IPv6 | 248 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 199 |
| AS216078 | Liam Kremer | Hosting | IPv4 IPv6 | 189 |
| AS214757 | Jakub Krsa | Unclassified | IPv4 IPv6 | 107 |
| AS401323 | LayerByte LLC | Unclassified | IPv4 IPv6 | 94 |
| AS402259 | ZT Enterprises LLC | Unclassified | IPv4 IPv6 | 94 |
| AS6204 | INTERKVM HOST SRL | Unclassified | IPv4 IPv6 | 91 |
| AS401502 | Falcon (America) LLC | Unclassified | IPv4 IPv6 | 91 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-09 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.03M 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.