Observed topology
AS41881 Fanava-AS Fanava Group
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS41881: 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 AS41881 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS62442 | Dade Samane Fanava Company (PJS) | Unclassified | IPv4 IPv6 | 2,299 |
| AS48551 | Sindad Network Technology PJSC | Unclassified | IPv4 | 2,098 |
| AS202391 | Cooperative Afra ertebatat-e-sabet-e Rasa Co | Unclassified | IPv4 | 1,621 |
| AS202468 | Noyan Abr Arvan Co. ( Private Joint Stock) | Unclassified | IPv4 | 1,104 |
| AS204203 | Atrin Information & Communications Technology Company PJS | Unclassified | IPv4 | 493 |
| AS43395 | Pooya Parto Qeshm Cooperative Company | Unclassified | IPv4 | 310 |
| AS44932 | Fannavaran-e Idea Pardaz-e Saba PJSC | Hosting | IPv4 | 276 |
| AS39571 | Sadad Informatics Corporation PJSC | Unclassified | IPv4 | 244 |
| AS213732 | Peyman Ertebatat Pouya Company (Ltd) | Unclassified | IPv4 | 244 |
| AS219142 | Avrin Telecom Industry Development Company (Private Joint Stock) | Unclassified | IPv4 | 184 |
Adjacency
Adjacent networks
Every AS seen directly next to AS41881 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS43754 | Asiatech Data Transmission company | Unclassified | IPv4 IPv6 | 14,960 |
| AS62442 | Dade Samane Fanava Company (PJS) | Unclassified | IPv4 IPv6 | 3,463 |
| AS204203 | Atrin Information & Communications Technology Company PJS | Unclassified | IPv4 | 2,516 |
| AS48551 | Sindad Network Technology PJSC | Unclassified | IPv4 | 2,159 |
| AS202391 | Cooperative Afra ertebatat-e-sabet-e Rasa Co | Unclassified | IPv4 | 1,682 |
| AS42337 | Respina Networks & Beyond PJSC | Unclassified | IPv4 | 1,467 |
| AS202468 | Noyan Abr Arvan Co. ( Private Joint Stock) | Unclassified | IPv4 | 1,104 |
| AS43395 | Pooya Parto Qeshm Cooperative Company | Unclassified | IPv4 | 310 |
| AS44932 | Fannavaran-e Idea Pardaz-e Saba PJSC | Hosting | IPv4 | 276 |
| AS12880 | Iran Information Technology Company PJSC | Residential | IPv4 | 244 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-14 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.46M 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.