Observed topology
AS43754 ASIATECH Asiatech Data Transmission company
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS43754: 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 |
|---|---|---|---|---|
| AS41689 | Asiatech Data Transmission company | Unclassified | IPv4 IPv6 | 19,529 |
Transit
Downstream networks
Networks for which AS43754 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS50810 | Mobin Net Communication Company (Private Joint Stock) | Unclassified | IPv4 | 11,118 |
| AS48715 | Sefroyek Pardaz Engineering PJSC | Unclassified | IPv4 IPv6 | 4,061 |
| AS41881 | Fanava Group | Unclassified | IPv4 IPv6 | 3,349 |
| AS49100 | Pishgaman Toseeh Ertebatat Company (Private Joint Stock) | Unclassified | IPv4 IPv6 | 2,934 |
| AS44285 | Sefroyek Pardaz Engineering PJSC | Unclassified | IPv4 IPv6 | 2,408 |
| AS60077 | Asre Dadeha Asiatech | Unclassified | IPv4 IPv6 | 1,186 |
| AS210392 | Azarakhsh Ava-e Ahvaz Co | Unclassified | IPv4 | 838 |
| AS50057 | Parvaz System Information Technology Company (Ltd) | Unclassified | IPv4 IPv6 | 802 |
| AS39308 | ANDISHE SABZ KHAZAR CO. P.J.S. | Unclassified | IPv4 | 792 |
| AS44932 | Fannavaran-e Idea Pardaz-e Saba PJSC | Hosting | IPv4 IPv6 | 690 |
Adjacency
Adjacent networks
Every AS seen directly next to AS43754 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS41689 | Asiatech Data Transmission company | Unclassified | IPv4 IPv6 | 125,477 |
| AS49100 | Pishgaman Toseeh Ertebatat Company (Private Joint Stock) | Unclassified | IPv4 IPv6 | 30,843 |
| AS50810 | Mobin Net Communication Company (Private Joint Stock) | Unclassified | IPv4 | 17,362 |
| AS41881 | Fanava Group | Unclassified | IPv4 IPv6 | 14,841 |
| AS51074 | GOSTARESH-E-ERTEBATAT-E MABNA COMPANY (Private Joint Stock) | Unclassified | IPv4 IPv6 | 6,935 |
| AS211421 | Asiatech Data Transmission company | Unclassified | IPv4 IPv6 | 6,880 |
| AS48715 | Sefroyek Pardaz Engineering PJSC | Unclassified | IPv4 IPv6 | 4,153 |
| AS44285 | Sefroyek Pardaz Engineering PJSC | Unclassified | IPv4 IPv6 | 3,319 |
| AS213759 | Tose'eh Lian Yas Ertebat PJSC | Unclassified | IPv4 IPv6 | 3,133 |
| AS44400 | Ertebatat Sabet Parsian Co. PJS | Unclassified | IPv4 IPv6 | 1,787 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-10 10:00 UTC by route-views2,rrc00, as seen from 74 BGP vantage points across 71.97M 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.