Observed topology
AS12880 DCI-AS Iran Information Technology Company PJSC
Residential RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS12880: 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 |
|---|---|---|---|---|
| AS49666 | Telecommunication Infrastructure Company | Unclassified | IPv4 IPv6 | 3,860 |
Transit
Downstream networks
Networks for which AS12880 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS42337 | Respina Networks & Beyond PJSC | Unclassified | IPv4 IPv6 | 44,077 |
| AS48434 | Tebyan-e-Noor Cultural-Artistic Institute | Unclassified | IPv4 | 1,374 |
| AS60148 | Iran Information Technology Company PJSC | Unclassified | IPv4 IPv6 | 1,090 |
| AS24631 | Tose'h Fanavari Ertebabat Pasargad Arian Co. PJS | Unclassified | IPv4 | 1,017 |
| AS200370 | Farzanegan Pars Communications Company PJS | Unclassified | IPv4 IPv6 | 1,008 |
| AS59441 | NOAVARAN SHABAKEH SABZ MEHREGAN (Ltd.) | Hosting | IPv4 IPv6 | 671 |
| AS58224 | Iran Telecommunication Company PJS | Unclassified | IPv4 | 476 |
| AS57292 | ICT Research Institute (Iran Telecommunications Research Center "ITRC") | Unclassified | IPv4 | 298 |
| AS202735 | Communication Regulatory Authority | Unclassified | IPv4 | 241 |
| AS34592 | Iranian Presidential Administration | Unclassified | IPv4 | 180 |
Adjacency
Adjacent networks
Every AS seen directly next to AS12880 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS49666 | Telecommunication Infrastructure Company | Unclassified | IPv4 IPv6 | 139,676 |
| AS42337 | Respina Networks & Beyond PJSC | Unclassified | IPv4 IPv6 | 113,983 |
| AS202251 | Padiz-Daderesan-Company | Unclassified | IPv4 | 9,471 |
| AS200370 | Farzanegan Pars Communications Company PJS | Unclassified | IPv4 IPv6 | 2,630 |
| AS48434 | Tebyan-e-Noor Cultural-Artistic Institute | Unclassified | IPv4 | 2,334 |
| AS205207 | Padiz Dadeh Resan PJSC | Unclassified | IPv4 | 1,879 |
| AS24631 | Tose'h Fanavari Ertebabat Pasargad Arian Co. PJS | Unclassified | IPv4 | 1,373 |
| AS60148 | Iran Information Technology Company PJSC | Unclassified | IPv4 IPv6 | 1,150 |
| AS59441 | NOAVARAN SHABAKEH SABZ MEHREGAN (Ltd.) | Hosting | IPv4 IPv6 | 671 |
| AS58224 | Iran Telecommunication Company PJS | Unclassified | IPv4 | 476 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-06 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.00M 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.