asn.dev

Observed topology

AS210036 RAYHAANNET Rayhaan Ahmad Jaufeerally

Unclassified RIPE Enterprise

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

Transit

Upstream networks

All 21

Networks observed carrying traffic for AS210036: 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 IPv6116
AS57118CommunityRack.org VereinUnclassifiedIPv4 IPv698
AS8758Iway AGResidentialIPv4 IPv644
AS8298IPng Networks GmbHHostingIPv616
AS24482SG.GSHostingIPv4 IPv64
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv64
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv63
AS48185team.blue NVUnclassifiedIPv4 IPv63
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv63
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv62

All 21 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS210617Philipp KernUnclassifiedIPv4 IPv673
AS210400Pierre BourdonUnclassifiedIPv639

Adjacency

Adjacent networks

All 26

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

ASNetworkTypeFamiliesPaths seen
AS57118CommunityRack.org VereinUnclassifiedIPv4 IPv6168
AS6939Hurricane Electric LLCTransitIPv4 IPv6130
AS210617Philipp KernUnclassifiedIPv4 IPv673
AS8758Iway AGResidentialIPv4 IPv644
AS210400Pierre BourdonUnclassifiedIPv639
AS8298IPng Networks GmbHHostingIPv616
AS24482SG.GSHostingIPv4 IPv66
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv66
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv66
AS48185team.blue NVUnclassifiedIPv4 IPv65

All 26 adjacent →

Provenance

Where this comes from

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