asn.dev

Observed topology

AS216392 NETCLOUDIFY SERGI GARCIA JIMENEZ

Hosting RIPE Content

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS216392: 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
AS49121Infinity Telecom, s.r.o.UnclassifiedIPv4 IPv6111
AS3257GTT Communications Inc.TransitIPv456
AS49600NEAR IP, S.L.HostingIPv4 IPv625
AS6939Hurricane Electric LLCTransitIPv416
AS1299Arelion Sweden ABTransitIPv64
AS29119AIRE NETWORKS DEL MEDITERRANEO SL UNIPERSONALUnclassifiedIPv4 IPv64

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS199143Indaleccius Broadcasting SLUnclassifiedIPv4147
AS213268QUARTIK SLUnclassifiedIPv461

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS49121Infinity Telecom, s.r.o.UnclassifiedIPv4 IPv6242
AS199143Indaleccius Broadcasting SLUnclassifiedIPv4147
AS3257GTT Communications Inc.TransitIPv485
AS213268QUARTIK SLUnclassifiedIPv461
AS6939Hurricane Electric LLCTransitIPv452
AS49600NEAR IP, S.L.HostingIPv4 IPv637
AS1299Arelion Sweden ABTransitIPv64
AS29119AIRE NETWORKS DEL MEDITERRANEO SL UNIPERSONALUnclassifiedIPv4 IPv64

Provenance

Where this comes from

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