asn.dev

Observed topology

AS215577 LUC-AS

Unclassified RIPE Educational/Research

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS215577: 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
AS211588Innovation Harbor B.V.UnclassifiedIPv687
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv63
AS17639Converge ICT Solutions Inc.UnclassifiedIPv63
AS24482SG.GSHostingIPv63
AS34019Hivane AssociationUnclassifiedIPv63
AS48185team.blue NVUnclassifiedIPv63
AS48362Stadtwerke FeldkirchResidentialIPv63
AS50300CustodianDC LimitedUnclassifiedIPv63
AS213241TECHIT.BE SRLResidentialIPv63

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS197919Noah van der AaUnclassifiedIPv638

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS211588Innovation Harbor B.V.UnclassifiedIPv6120
AS197919Noah van der AaUnclassifiedIPv638
AS213241TECHIT.BE SRLResidentialIPv65
AS24482SG.GSHostingIPv64
AS34019Hivane AssociationUnclassifiedIPv64
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv63
AS17639Converge ICT Solutions Inc.UnclassifiedIPv63
AS48185team.blue NVUnclassifiedIPv63
AS48362Stadtwerke FeldkirchResidentialIPv63
AS50300CustodianDC LimitedUnclassifiedIPv63

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.