Observed topology
AS58224 TCI Iran Telecommunication Company PJS
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS58224: 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 |
|---|---|---|---|---|
| AS48159 | Telecommunication Infrastructure Company | Unclassified | IPv4 IPv6 | 64,986 |
| AS49666 | Telecommunication Infrastructure Company | Unclassified | IPv4 | 8,069 |
| AS12880 | Iran Information Technology Company PJSC | Residential | IPv4 | 487 |
| AS60148 | Iran Information Technology Company PJSC | Unclassified | IPv4 | 61 |
Transit
Downstream networks
Networks for which AS58224 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS9147 | Homaye Jahan Nama Co. ( Private Joint Stock) | Unclassified | IPv4 | 1,050 |
| AS29079 | IRNA | Unclassified | IPv4 | 854 |
| AS59962 | Shiraz University | Unclassified | IPv4 | 694 |
| AS5542 | Ministry of Health, Treatment and Medical Education | Unclassified | IPv4 | 610 |
| AS8868 | Khallagh Borhan Market Development for Creative Industries Co | Unclassified | IPv4 | 549 |
| AS57457 | Asan Pardakht Persian Co. LTD | Unclassified | IPv4 | 427 |
| AS21419 | PISHTAZE E JADID INFORMATION COMPANY (Ltd.) | Unclassified | IPv4 | 366 |
| AS51241 | Islamic Republic of Iran Post PJSC | Unclassified | IPv4 | 366 |
| AS60014 | Abramad Technological Infrastructures Development Company PJS | Unclassified | IPv4 | 343 |
| AS41061 | Iran Zamin Bank PJSC | Unclassified | IPv4 | 305 |
Adjacency
Adjacent networks
Every AS seen directly next to AS58224 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS48159 | Telecommunication Infrastructure Company | Unclassified | IPv4 IPv6 | 77,442 |
| AS49666 | Telecommunication Infrastructure Company | Unclassified | IPv4 | 9,593 |
| AS9147 | Homaye Jahan Nama Co. ( Private Joint Stock) | Unclassified | IPv4 | 1,050 |
| AS29079 | IRNA | Unclassified | IPv4 | 854 |
| AS59962 | Shiraz University | Unclassified | IPv4 | 694 |
| AS5542 | Ministry of Health, Treatment and Medical Education | Unclassified | IPv4 | 610 |
| AS8868 | Khallagh Borhan Market Development for Creative Industries Co | Unclassified | IPv4 | 549 |
| AS12880 | Iran Information Technology Company PJSC | Residential | IPv4 | 487 |
| AS57457 | Asan Pardakht Persian Co. LTD | Unclassified | IPv4 | 427 |
| AS21419 | PISHTAZE E JADID INFORMATION COMPANY (Ltd.) | Unclassified | IPv4 | 366 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-01 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.48M 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.