Observed topology
AS48434 TEBYAN
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS48434: 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 AS48434 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS212216 | Netafraz Iranian Ltd. | Unclassified | IPv4 | 360 |
| AS49099 | Tadbir Pardaz IT Group LTD | Unclassified | IPv4 | 244 |
| AS214751 | Rahpooyan Pardazesh Gostar Sahra CO. PJS | Unclassified | IPv4 | 120 |
| AS210650 | Sarmayeh & Danesh Brokerage Co. | Unclassified | IPv4 | 61 |
| AS47603 | Zirsakht Pishro Abr Damavand Private Joint Stock Company | Unclassified | IPv4 | 60 |
| AS204955 | Vista Samaneh ASA Company (PJS) | Unclassified | IPv4 | 60 |
| AS215700 | Mabna Financial Data Processing PJS | Unclassified | IPv4 | 59 |
Adjacency
Adjacent networks
Every AS seen directly next to AS48434 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS12880 | Iran Information Technology Company PJSC | Residential | IPv4 | 2,292 |
| AS212216 | Netafraz Iranian Ltd. | Unclassified | IPv4 | 360 |
| AS49099 | Tadbir Pardaz IT Group LTD | Unclassified | IPv4 | 244 |
| AS214751 | Rahpooyan Pardazesh Gostar Sahra CO. PJS | Unclassified | IPv4 | 120 |
| AS210650 | Sarmayeh & Danesh Brokerage Co. | Unclassified | IPv4 | 61 |
| AS47603 | Zirsakht Pishro Abr Damavand Private Joint Stock Company | Unclassified | IPv4 | 60 |
| AS204955 | Vista Samaneh ASA Company (PJS) | Unclassified | IPv4 | 60 |
| AS215700 | Mabna Financial Data Processing PJS | Unclassified | IPv4 | 59 |
| AS6736 | Institute for Research in Fundamental Sciences | Education | IPv4 | 58 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-22 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.12M 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.