asn.dev

Observed topology

AS209990 DIYAAELDIN-MOUSTAFA-TRADING-AS-KARMUZ

Unclassified RIPE

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

Transit

Upstream networks

All 17

Networks observed carrying traffic for AS209990: 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 IPv6235
AS211588Innovation Harbor B.V.UnclassifiedIPv4 IPv6129
AS8283Netwerkvereniging ColoclueUnclassifiedIPv4 IPv689
AS34927iFog GmbHHostingIPv4 IPv683
AS24482SG.GSHostingIPv4 IPv610
AS37989DCS1 Pte. Ltd.HostingIPv4 IPv610
AS58057Securebit AGUnclassifiedIPv610
AS52025ParadoxNetworks LimitedUnclassifiedIPv64
AS56630Melbikomas UABHostingIPv62
AS205794JINZE YANGUnclassifiedIPv62

All 17 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS207740Youssef HamedUnclassifiedIPv62

Adjacency

Adjacent networks

All 18

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6235
AS211588Innovation Harbor B.V.UnclassifiedIPv4 IPv6131
AS8283Netwerkvereniging ColoclueUnclassifiedIPv4 IPv689
AS34927iFog GmbHHostingIPv4 IPv683
AS24482SG.GSHostingIPv4 IPv610
AS37989DCS1 Pte. Ltd.HostingIPv4 IPv610
AS58057Securebit AGUnclassifiedIPv610
AS52025ParadoxNetworks LimitedUnclassifiedIPv64
AS56630Melbikomas UABHostingIPv62
AS205794JINZE YANGUnclassifiedIPv62

All 18 adjacent →

Provenance

Where this comes from

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