Skip to main content

AS21267

Wavenet-AS21267

Wavenet offer a range of products from

Registry

Authoritative registration data

AS number
21267
Name
Wavenet-AS21267
Organisation
Wavenet offer a range of products from
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

63

IPv6 prefixes

1

Total announced

64

Announced prefixes

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

Prefixes announced by AS21267
195.26.32.0/19 IPv4 /19 RPKI valid
85.95.96.0/19 IPv4 /19 RPKI valid
217.145.128.0/20 IPv4 /20 not checked
80.87.16.0/20 IPv4 /20 not checked
91.143.64.0/20 IPv4 /20 not checked
93.115.176.0/20 IPv4 /20 RPKI valid
176.58.0.0/21 IPv4 /21 not checked
185.182.0.0/21 IPv4 /21 RPKI valid
188.94.16.0/21 IPv4 /21 RPKI valid
31.192.96.0/21 IPv4 /21 not checked
5.159.208.0/21 IPv4 /21 RPKI valid
5.39.176.0/21 IPv4 /21 not checked
80.74.240.0/21 IPv4 /21 not checked
80.74.248.0/21 IPv4 /21 not checked
87.236.128.0/21 IPv4 /21 not checked
88.151.152.0/21 IPv4 /21 not checked
89.38.120.0/21 IPv4 /21 RPKI valid
92.42.120.0/21 IPv4 /21 not checked
94.142.168.0/21 IPv4 /21 RPKI valid
95.129.64.0/21 IPv4 /21 RPKI valid
185.145.88.0/22 IPv4 /22 not checked
185.178.216.0/22 IPv4 /22 RPKI valid
185.182.200.0/22 IPv4 /22 not checked
185.204.212.0/22 IPv4 /22 RPKI valid
185.229.4.0/22 IPv4 /22 not checked
185.246.132.0/22 IPv4 /22 RPKI valid
185.247.200.0/22 IPv4 /22 not checked
185.248.252.0/22 IPv4 /22 not checked
185.52.144.0/22 IPv4 /22 RPKI valid
185.79.184.0/22 IPv4 /22 RPKI valid
185.90.0.0/22 IPv4 /22 not checked
185.94.204.0/22 IPv4 /22 RPKI valid
185.99.76.0/22 IPv4 /22 RPKI valid
212.11.68.0/22 IPv4 /22 not checked
212.11.72.0/22 IPv4 /22 not checked
45.132.108.0/22 IPv4 /22 not checked
45.137.44.0/22 IPv4 /22 RPKI valid
45.8.100.0/22 IPv4 /22 RPKI valid
45.88.60.0/22 IPv4 /22 not checked
5.181.72.0/22 IPv4 /22 RPKI valid
83.150.252.0/22 IPv4 /22 not checked
154.46.94.0/23 IPv4 /23 not checked
154.62.134.0/23 IPv4 /23 not checked
185.182.200.0/23 IPv4 /23 RPKI valid
195.88.8.0/23 IPv4 /23 not checked
185.178.218.0/24 IPv4 /24 not checked
185.178.219.0/24 IPv4 /24 RPKI valid
185.201.180.0/24 IPv4 /24 RPKI not found
185.210.163.0/24 IPv4 /24 RPKI not found
185.248.253.0/24 IPv4 /24 not checked
185.248.255.0/24 IPv4 /24 RPKI valid
188.94.19.0/24 IPv4 /24 not checked
188.94.21.0/24 IPv4 /24 not checked
193.24.13.0/24 IPv4 /24 not checked
193.24.3.0/24 IPv4 /24 not checked
193.24.31.0/24 IPv4 /24 RPKI valid
193.24.6.0/24 IPv4 /24 RPKI valid
217.156.133.0/24 IPv4 /24 not checked
217.156.156.0/24 IPv4 /24 not checked
217.156.209.0/24 IPv4 /24 RPKI not found
217.156.249.0/24 IPv4 /24 RPKI not found
217.163.68.0/24 IPv4 /24 RPKI not found
217.163.69.0/24 IPv4 /24 RPKI not found
2a00:f1c0::/32 IPv6 /32 RPKI valid

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS21267
Address families
LINX LON1: Main 50,000 Mbps IPv4 · IPv6
LINX LON2 20,000 Mbps IPv4 · IPv6
LINX Manchester 20,000 Mbps IPv4 · IPv6

No rows match “”.

Showing – of

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

Source:ripestat:asn-neighbours observed

Observed upstreams

45 networks seen before AS21267 in AS paths

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS21267 in AS paths

Observed downstreams
Families
AS29676 GRADWELL 229 3,836
v4

No rows match “”.

Showing – of

Uncertain adjacencies

17 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.