Observed topology
AS49100 IR-THR-PTE
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS49100: 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 AS49100 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS39074 | Sepanta Communication Development Co. Ltd | Unclassified | IPv4 IPv6 | 3,988 |
| AS1756 | Shiraz Hamyar Co. | Unclassified | IPv4 | 3,661 |
| AS34918 | Pishgaman Toseeh Ertebatat Company (Private Joint Stock) | Unclassified | IPv4 | 3,299 |
| AS48359 | Hesabgar Pardaz Gharb PJSC | Unclassified | IPv4 IPv6 | 3,285 |
| AS56503 | PJSC "Badr Rayan Jonoob" | Unclassified | IPv4 | 2,639 |
| AS44208 | Farahoosh Dena PLC | Unclassified | IPv4 | 2,524 |
| AS201540 | Pishgaman Toseeh Fanavari Etelaat Va Ertebatat Jonoub (Joint Stock Company) | Unclassified | IPv4 IPv6 | 1,654 |
| AS201150 | Didehban Net Company PJS | Unclassified | IPv4 | 1,336 |
| AS44090 | Enteghal Dadeh Mahan Co. PJSC | Unclassified | IPv4 | 1,145 |
| AS39650 | Atrin Information & Communications Technology Company PJS | Unclassified | IPv4 IPv6 | 969 |
Adjacency
Adjacent networks
Every AS seen directly next to AS49100 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS43754 | Asiatech Data Transmission company | Unclassified | IPv4 IPv6 | 34,179 |
| AS202251 | Padiz-Daderesan-Company | Unclassified | IPv4 | 6,618 |
| AS34918 | Pishgaman Toseeh Ertebatat Company (Private Joint Stock) | Unclassified | IPv4 IPv6 | 5,546 |
| AS39074 | Sepanta Communication Development Co. Ltd | Unclassified | IPv4 IPv6 | 4,530 |
| AS1756 | Shiraz Hamyar Co. | Unclassified | IPv4 | 3,661 |
| AS48359 | Hesabgar Pardaz Gharb PJSC | Unclassified | IPv4 IPv6 | 3,649 |
| AS56503 | PJSC "Badr Rayan Jonoob" | Unclassified | IPv4 | 2,699 |
| AS44208 | Farahoosh Dena PLC | Unclassified | IPv4 | 2,524 |
| AS206388 | Gostaresh Ertebat Azin Kia Company PJSC | Unclassified | IPv4 IPv6 | 1,755 |
| AS201540 | Pishgaman Toseeh Fanavari Etelaat Va Ertebatat Jonoub (Joint Stock Company) | Unclassified | IPv4 IPv6 | 1,656 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-23 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.15M 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.