asn.dev

Observed topology

AS56584 InterEdge B.V.

Unclassified Spamhaus ASN-DROP RIPE

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

Transit

Upstream networks

inferred

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

No upstream observed. Typical for a tier-1 network that buys transit from nobody.

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS37451CONGO TELECOMResidentialIPv421
AS48635Your Hosting B.V.HostingIPv414
AS214279DASABO OUHostingIPv42
AS209179AfriCloud LLCUnclassifiedIPv41

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS34927iFog GmbHHostingIPv444
AS37451CONGO TELECOMResidentialIPv421
AS48635Your Hosting B.V.HostingIPv417
AS50629LWLcom GmbHUnclassifiedIPv4 IPv616
AS20764CJSC RASCOMUnclassifiedIPv411
AS6205HizliNet Teknoloji A.S.HostingIPv42
AS210464ANDREW KRISTULIResidentialIPv62
AS213900RS Computers L.L.CUnclassifiedIPv62
AS214279DASABO OUHostingIPv42
AS48925VibeGAMES B.V.HostingIPv41

All 12 adjacent →

Provenance

Where this comes from

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