Observed topology
AS41051 FREETRANSIT Openfactory GmbH
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS41051: 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 |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv6 | 19 |
| AS9002 | RETN Limited | Unclassified | IPv6 | 3 |
| AS39351 | 31173 Services AB | VPN | IPv6 | 3 |
| AS49585 | CoreRoute UG (haftungsbeschraenkt) | Unclassified | IPv6 | 2 |
| AS3333 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv6 | 1 |
| AS17639 | Converge ICT Solutions Inc. | Unclassified | IPv6 | 1 |
| AS24482 | SG.GS | Hosting | IPv6 | 1 |
| AS29632 | Netassist International EOOD | Unclassified | IPv6 | 1 |
| AS42708 | Glesys Sweden AB | Unclassified | IPv6 | 1 |
| AS48185 | team.blue NV | Unclassified | IPv6 | 1 |
Transit
Downstream networks
Networks for which AS41051 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS218346 | Nariman Mammadov | Unclassified | IPv6 | 423 |
| AS47509 | Wai-Wah Tang | Unclassified | IPv6 | 216 |
| AS207852 | Yonghan Ching | Unclassified | IPv6 | 186 |
| AS213368 | Marco Ciotola | Unclassified | IPv6 | 144 |
| AS203991 | Hainan Jinzhao Biotechnology Co. Ltd. | Unclassified | IPv4 IPv6 | 123 |
| AS219367 | Andreas Fornberg | Unclassified | IPv6 | 121 |
| AS208223 | SHU-HAO TUNG | Unclassified | IPv6 | 117 |
| AS214242 | Jiaxing Xing | Unclassified | IPv6 | 110 |
| AS212237 | Changgong Zhang | Unclassified | IPv4 IPv6 | 102 |
| AS211237 | Urban Suhadolnik | Unclassified | IPv4 IPv6 | 96 |
Adjacency
Adjacent networks
Every AS seen directly next to AS41051 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 2,125 |
| AS39351 | 31173 Services AB | VPN | IPv4 IPv6 | 950 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 560 |
| AS218346 | Nariman Mammadov | Unclassified | IPv6 | 423 |
| AS215510 | Internet Service GmbH | Residential | IPv4 IPv6 | 290 |
| AS49585 | CoreRoute UG (haftungsbeschraenkt) | Unclassified | IPv4 IPv6 | 269 |
| AS47509 | Wai-Wah Tang | Unclassified | IPv6 | 216 |
| AS207852 | Yonghan Ching | Unclassified | IPv6 | 186 |
| AS213368 | Marco Ciotola | Unclassified | IPv6 | 144 |
| AS203991 | Hainan Jinzhao Biotechnology Co. Ltd. | Unclassified | IPv4 IPv6 | 123 |
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.