asn.dev

Observed topology

AS215563 LUKE-IT

Hosting RIPE

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

Transit

Upstream networks

All 11

Networks observed carrying traffic for AS215563: 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
AS44592SkyLink Data Center BVHostingIPv4 IPv6130
AS6939Hurricane Electric LLCTransitIPv698
AS197071active 1 GmbHUnclassifiedIPv439
AS47272HYEHOST LLCHostingIPv638
AS197477Moritz Mantel trading as NerdscaveUnclassifiedIPv4 IPv624
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv64
AS24482SG.GSHostingIPv4 IPv63
AS401753BIXCE IncUnclassifiedIPv4 IPv63
AS56662Marcin GondekUnclassifiedIPv62
AS57821Nonattached Network e.V.UnclassifiedIPv62

All 11 upstreams →

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS44592SkyLink Data Center BVHostingIPv4 IPv6130
AS6939Hurricane Electric LLCTransitIPv698
AS197071active 1 GmbHUnclassifiedIPv439
AS47272HYEHOST LLCHostingIPv638
AS197477Moritz Mantel trading as NerdscaveUnclassifiedIPv4 IPv624
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv64
AS24482SG.GSHostingIPv4 IPv63
AS401753BIXCE IncUnclassifiedIPv4 IPv63
AS56662Marcin GondekUnclassifiedIPv62
AS57821Nonattached Network e.V.UnclassifiedIPv62

All 11 adjacent →

Provenance

Where this comes from

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