Skip to main content

AS29527

ASTUTIUM-AS

Astutium Limited

Registry

Authoritative registration data

AS number
29527
Name
ASTUTIUM-AS
Organisation
Astutium Limited
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

11

IPv6 prefixes

1

Total announced

12

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS29527
217.148.32.0/20 IPv4 /20 not checked
83.243.96.0/21 IPv4 /21 not checked
95.128.48.0/21 IPv4 /21 not checked
194.150.120.0/22 IPv4 /22 not checked
80.76.212.0/22 IPv4 /22 not checked
80.76.216.0/22 IPv4 /22 not checked
91.227.124.0/22 IPv4 /22 not checked
193.108.221.0/24 IPv4 /24 not checked
193.203.20.0/24 IPv4 /24 not checked
193.203.21.0/24 IPv4 /24 not checked
193.84.0.0/24 IPv4 /24 not checked
2001:4bf0:1::/48 IPv6 /48 not checked

No rows match “”.

Showing of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

No Internet Exchange memberships found

The exchange directory has no current membership records for this AS.

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS29527 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

42 networks seen before AS29527 in AS paths

No rows match “”.

Showing of

Observed downstreams

1 networks seen after AS29527 in AS paths

Observed downstreams
Families
AS34623 464 699
v4 v6

No rows match “”.

Showing of

Uncertain adjacencies

37 adjacencies that may be an artefact of collector peering

No rows match “”.

Showing of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.