Skip to main content

AS211431

AndrewA

-----BEGIN TOKEN-----fb3dc8f2bead78ba57ffd93034a325bb4ae0c810234c981b055735f8302957e6451bbe3029e8318d861b90d0b9b0ab9d880dfe9559cdc6d0b6b64074f15b8eb2-----END TOKEN-----

Registry

Authoritative registration data

AS number
211431
Name
AndrewA
Organisation
-----BEGIN TOKEN-----fb3dc8f2bead78ba57ffd93034a325bb4ae0c810234c981b055735f8302957e6451bbe3029e8318d861b90d0b9b0ab9d880dfe9559cdc6d0b6b64074f15b8eb2-----END TOKEN-----
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

9

Total announced

11

Announced prefixes

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

Prefixes announced by AS211431
44.30.205.0/24 IPv4 /24 RPKI not found
81.31.212.0/24 IPv4 /24 RPKI valid
2a05:dfc1:8100::/40 IPv6 /40 RPKI valid
2a06:a005:1720::/44 IPv6 /44 RPKI valid
2a06:a005:1790::/44 IPv6 /44 RPKI valid
2a06:a005:17b0::/44 IPv6 /44 not checked
2a06:a005:17c0::/44 IPv6 /44 RPKI valid
2a06:a005:17d0::/44 IPv6 /44 RPKI valid
2a13:9644:3000::/44 IPv6 /44 RPKI valid
2a13:9644:30f0::/44 IPv6 /44 RPKI valid
2a13:9644:30f1::/48 IPv6 /48 RPKI valid

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 AS211431 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS211431 in AS paths

Observed upstreams
Families
AS20473 AS-VULTR 194 1,257
v4 v6
AS13335 CLOUDFLARENET 172 359
v4 v6
AS20712 AS20712 126 157
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS211431 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

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.