asn.dev

Observed topology

AS29527 ASTUTIUM-AS Astutium Limited

Unclassified RIPE

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

Transit

Upstream networks

All 21

Networks observed carrying traffic for AS29527: 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
AS60800Netwise Hosting LtdHostingIPv4304
AS6939Hurricane Electric LLCTransitIPv4 IPv6139
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv634
AS50304Blix Solutions ASUnclassifiedIPv4 IPv624
AS33891Core-Backbone GmbHHostingIPv422
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv612
AS24482SG.GSHostingIPv4 IPv612
AS48185team.blue NVUnclassifiedIPv4 IPv612
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv612
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv612

All 21 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS34623Astutium LimitedHostingIPv4 IPv694

Adjacency

Adjacent networks

All 22

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

ASNetworkTypeFamiliesPaths seen
AS60800Netwise Hosting LtdHostingIPv4332
AS6939Hurricane Electric LLCTransitIPv4 IPv6176
AS34623Astutium LimitedHostingIPv4 IPv694
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv638
AS50304Blix Solutions ASUnclassifiedIPv4 IPv628
AS33891Core-Backbone GmbHHostingIPv424
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv614
AS24482SG.GSHostingIPv4 IPv614
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv614
AS48185team.blue NVUnclassifiedIPv4 IPv613

All 22 adjacent →

Provenance

Where this comes from

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