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.
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 | 252 |
| AS206226 | Little Orbit Inc. | Unclassified | IPv4 IPv6 | 250 |
| AS401323 | LayerByte LLC | Unclassified | IPv4 IPv6 | 95 |
| AS402259 | ZT Enterprises LLC | Unclassified | IPv4 IPv6 | 95 |
| AS401502 | Falcon (America) LLC | Unclassified | IPv4 IPv6 | 92 |
| AS214757 | Jakub Krsa | Unclassified | IPv4 IPv6 | 56 |
| AS214371 | Gijs van de Sande | Hosting | IPv4 IPv6 | 41 |
| AS219187 | Tangtech Internet Services LLC | Unclassified | IPv6 | 35 |
| AS216078 | Liam Kremer | Hosting | IPv6 | 21 |
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 | 894 |
| AS208111 | Falcon FZE LLC | Unclassified | IPv4 IPv6 | 252 |
| AS206226 | Little Orbit Inc. | Unclassified | IPv4 IPv6 | 250 |
| AS214757 | Jakub Krsa | Unclassified | IPv4 IPv6 | 109 |
| AS6204 | INTERKVM HOST SRL | Unclassified | IPv4 IPv6 | 106 |
| AS401323 | LayerByte LLC | Unclassified | IPv4 IPv6 | 95 |
| AS402259 | ZT Enterprises LLC | Unclassified | IPv4 IPv6 | 95 |
| AS401502 | Falcon (America) LLC | Unclassified | IPv4 IPv6 | 92 |
| AS214371 | Gijs van de Sande | Hosting | IPv4 IPv6 | 66 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 53 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-05 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 73.57M 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.