asn.dev

Observed topology

AS213045 DED3L-NETWORK Alex Delporte

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS213045: 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
AS34927iFog GmbHHostingIPv6228
AS24482SG.GSHostingIPv66
AS37989DCS1 Pte. Ltd.HostingIPv66
AS57821Nonattached Network e.V.UnclassifiedIPv66
AS58057Securebit AGUnclassifiedIPv66
AS205794JINZE YANGUnclassifiedIPv66
AS29632Netassist International EOODUnclassifiedIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS215956Dennis de Houx trading as All In OneUnclassifiedIPv610

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS34927iFog GmbHHostingIPv6228
AS57821Nonattached Network e.V.UnclassifiedIPv610
AS215956Dennis de Houx trading as All In OneUnclassifiedIPv610
AS37989DCS1 Pte. Ltd.HostingIPv68
AS58057Securebit AGUnclassifiedIPv68
AS24482SG.GSHostingIPv66
AS205794JINZE YANGUnclassifiedIPv66
AS207292YANG HAOJINGUnclassifiedIPv62
AS29632Netassist International EOODUnclassifiedIPv61

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.