asn.dev

Observed topology

AS39526 MAO Mohammad Ali Obeidat

Hosting RIPE

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

Transit

Upstream networks

All 22

Networks observed carrying traffic for AS39526: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv627
AS8849Melbikomas UABHostingIPv418
AS9002RETN LimitedUnclassifiedIPv4 IPv615
AS1299Arelion Sweden ABTransitIPv49
AS3257GTT Communications Inc.TransitIPv4 IPv64
AS50304Blix Solutions ASUnclassifiedIPv4 IPv64
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv62
AS24482SG.GSHostingIPv4 IPv62
AS29632Netassist International EOODUnclassifiedIPv62
AS48185team.blue NVUnclassifiedIPv4 IPv62

All 22 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS20473The Constant Company, LLCHostingIPv43

Adjacency

Adjacent networks

All 23

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv630
AS8849Melbikomas UABHostingIPv418
AS9002RETN LimitedUnclassifiedIPv4 IPv615
AS1299Arelion Sweden ABTransitIPv49
AS3257GTT Communications Inc.TransitIPv4 IPv64
AS50304Blix Solutions ASUnclassifiedIPv4 IPv64
AS20473The Constant Company, LLCHostingIPv43
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv62
AS24482SG.GSHostingIPv4 IPv62
AS29632Netassist International EOODUnclassifiedIPv62

All 23 adjacent →

Provenance

Where this comes from

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