asn.dev

Observed topology

AS64404 EVENTINFRA-AS

Unclassified RIPE

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

Transit

Upstream networks

All 19

Networks observed carrying traffic for AS64404: 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
AS49544i3D.net B.VUnclassifiedIPv4 IPv653
AS6939Hurricane Electric LLCTransitIPv4 IPv636
AS2914NTT America, Inc.TransitIPv4 IPv612
AS35133Eranium B.V.HostingIPv4 IPv65
AS9136Wobcom GmbHResidentialIPv4 IPv64
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv63
AS24482SG.GSHostingIPv4 IPv63
AS48185team.blue NVUnclassifiedIPv4 IPv63
AS58057Securebit AGUnclassifiedIPv4 IPv63
AS204092Association GRIFONUnclassifiedIPv4 IPv63

All 19 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS1101SURF B.V.UnclassifiedIPv4 IPv6580

Adjacency

Adjacent networks

All 23

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

ASNetworkTypeFamiliesPaths seen
AS1101SURF B.V.UnclassifiedIPv4 IPv6876
AS49544i3D.net B.VUnclassifiedIPv4 IPv6525
AS2914NTT America, Inc.TransitIPv4 IPv6169
AS6939Hurricane Electric LLCTransitIPv4 IPv6126
AS35133Eranium B.V.HostingIPv4 IPv688
AS9136Wobcom GmbHResidentialIPv4 IPv621
AS8434Telenor Sverige ABResidentialIPv420
AS50304Blix Solutions ASUnclassifiedIPv420
AS24482SG.GSHostingIPv4 IPv69
AS204092Association GRIFONUnclassifiedIPv4 IPv65

All 23 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.