asn.dev

Observed topology

AS34837 IRANET-IPM

Unclassified APNIC

Upstreams 1 carry this network
Downstreams 8 this network carries
Adjacent (IPv4) 9
Adjacent (IPv6) 0
Upstream graph Who carries AS34837, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS34837 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS34837: 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.

ASNetworkTypeFamiliesPaths seen
AS6736Institute for Research in Fundamental SciencesEducationIPv41,200

Transit

Downstream networks

inferred

Networks for which AS34837 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS15611Iranian Research Organization for Science & TechnologyUnclassifiedIPv4414
AS31175Securities and Exchange OrganizationUnclassifiedIPv4119
AS208651Shahr Bank PJSCUnclassifiedIPv4116
AS57241Maskan BankUnclassifiedIPv4104
AS51460Sina BankUnclassifiedIPv487
AS203694Beh Pardakht Melat Co PJSUnclassifiedIPv459
AS219019Etebarsanji Iran PJSCUnclassifiedIPv459
AS42915Engeneering Designing and Supply the parts of Iran Khodro PJSCUnclassifiedIPv435

Adjacency

Adjacent networks

observed

Every AS seen directly next to AS34837 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS6736Institute for Research in Fundamental SciencesEducationIPv42,193
AS15611Iranian Research Organization for Science & TechnologyUnclassifiedIPv4414
AS31175Securities and Exchange OrganizationUnclassifiedIPv4119
AS208651Shahr Bank PJSCUnclassifiedIPv4116
AS57241Maskan BankUnclassifiedIPv4104
AS51460Sina BankUnclassifiedIPv487
AS203694Beh Pardakht Melat Co PJSUnclassifiedIPv459
AS219019Etebarsanji Iran PJSCUnclassifiedIPv459
AS42915Engeneering Designing and Supply the parts of Iran Khodro PJSCUnclassifiedIPv435

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-25 12:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.17M 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.