Network · data from 2026-11-12
AS20712 Andrews & Arnold Ltd
Registry name: AS20712 Andrews & Arnold Ltd, GB · PeeringDB
89IPv4 routes
85.4% RPKI valid · 95.5% with a route object
21IPv6 routes
85.7% RPKI valid · 66.7% with a route object
0RPKI invalid
0 origin · 0 maxLength
16No ROA
11 with no route object for this origin
1Low visibility
seen by under 10% of full-table peers
23Route objects not announced
registered with origin AS20712, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS20712, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
| 44.30.117.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 44.31.91.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 44.31.166.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 44.31.241.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 44.32.156.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 91.242.172.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 93.187.168.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 188.191.132.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 192.67.4.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 194.60.203.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 194.70.3.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 192.150.92.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 91.208.66.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 2001:678:3c4::/48 | No ROA | RIR databaseRIPE | 636 100% |
| 2001:67c:2a4c::/48 | No ROA | RIR databaseRIPE | 636 100% |
| 2001:67c:2e80::/48 | No ROA | RIR databaseRIPE | 636 100% |
| 90.155.0.0/22 | Valid | Nonecovered by 90.155.0.0/21 | 673 100% |
| 90.155.62.0/24 | Valid | Nonecovered by 90.155.0.0/18 | 673 100% |
| 90.155.67.0/24 | Valid | Nonecovered by 90.155.64.0/19 | 673 100% |
| 2001:8b0::/34 | Valid | Nonecovered by 2001:8b0::/32 | 636 100% |
| 2001:8b0::/48 | Valid | Nonecovered by 2001:8b0::/32 | 636 100% |
| 2001:8b0:1::/48 | Valid | Nonecovered by 2001:8b0::/32 | 636 100% |
| 2001:8b0:4000::/36 | Valid | Nonecovered by 2001:8b0::/32 | 636 100% |
| 2001:8b6:1::/48 | Valid | Nonecovered by 2001:8b6::/32 | 635 100% |
| 2001:8b6:2::/48 | Valid | Nonecovered by 2001:8b6::/32 | 635 100% |
| 2001:8b6:3::/48 | Valid | Nonecovered by 2001:8b6::/32 | 635 100% |
| 217.169.19.0/24 | Valid | Nonecovered by 217.169.0.0/19 | 0 0%low visibility |
| 5.172.160.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 51.146.73.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 51.194.130.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 81.2.64.0/18 | Valid | RIR databaseRIPE | 673 100% |
| 81.187.0.0/16 | Valid | RIR databaseRIPE | 673 100% |
| 81.187.30.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 87.232.230.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 90.155.0.0/18 | Valid | RIR databaseRIPE | 673 100% |
| 90.155.0.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 90.155.4.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 90.155.53.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 90.155.64.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 90.155.96.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 91.190.97.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.190.105.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.200.61.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.240.176.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.244.239.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.116.12.0/22 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 94.116.32.0/22 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 94.116.196.0/22 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 109.205.152.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 109.205.156.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 176.110.118.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 176.123.222.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 178.211.150.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 178.238.144.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 185.6.132.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 188.220.10.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 188.220.192.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 188.220.206.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 188.220.217.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 188.221.11.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 188.221.23.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 188.221.98.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 188.221.189.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 194.4.172.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 194.62.124.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.169.0.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 45.88.21.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.88.23.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.89.37.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.89.39.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.92.3.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.129.89.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.129.91.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.134.249.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.134.251.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.135.9.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.135.11.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.136.217.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.136.219.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.138.77.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.138.79.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.139.33.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.139.35.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.139.229.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.139.231.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.140.69.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.140.71.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.140.134.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.140.215.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.141.49.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.141.51.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.142.205.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.142.207.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.144.157.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.144.159.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.116.152.0/22 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 94.116.184.0/22 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 94.116.236.0/22 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 94.194.88.0/22 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 2001:678:c40::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2001:67c:2bc::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2001:67c:1270::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2001:67c:2058::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2001:67c:2a40::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2001:8b0::/32 | Valid | RIR databaseRIPE | 636 100% |
| 2001:8b0:1628::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a00:8e00:1::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a03:3a40:2000::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a05:6346:200::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a11:f2c0:ffc9::/48 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS20712: AS-AA. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS20712 isn't in the set, or no route object for AS20712 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS20712 in it | Not covered |
|---|---|---|---|---|---|
| AS-AA | RIPElists itself further down | 41 | 8 | Yes | 0 |
Fix list
The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 55 are in fix.csv.
- ROA: none16
- Route object: none11
- Route object: RIR5
- Route object: not announced23
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 44.30.117.0/24 | No ROA covers it. Add a ROA for AS20712, maxLength 24. |
| Route object: RIR | 44.30.117.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 44.31.91.0/24 | No ROA covers it. Add a ROA for AS20712, maxLength 24. |
| Route object: RIR | 44.31.91.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 44.31.166.0/24 | No ROA covers it. Add a ROA for AS20712, maxLength 24. |
| Route object: RIR | 44.31.166.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 44.31.241.0/24 | No ROA covers it. Add a ROA for AS20712, maxLength 24. |
| Route object: RIR | 44.31.241.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 44.32.156.0/24 | No ROA covers it. Add a ROA for AS20712, maxLength 24. |
| Route object: RIR | 44.32.156.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 91.242.172.0/24 | No ROA covers it. Add a ROA for AS20712, maxLength 24. |
| ROA: none | 93.187.168.0/24 | No ROA covers it. Add a ROA for AS20712, maxLength 24. |
| ROA: none | 188.191.132.0/22 | No ROA covers it. Add a ROA for AS20712, maxLength 22. |
| ROA: none | 192.67.4.0/24 | No ROA covers it. Add a ROA for AS20712, maxLength 24. |
| ROA: none | 194.60.203.0/24 | No ROA covers it. Add a ROA for AS20712, maxLength 24. |
| ROA: none | 194.70.3.0/24 | No ROA covers it. Add a ROA for AS20712, maxLength 24. |
| ROA: none | 192.150.92.0/24 | No ROA covers it. Add a ROA for AS20712, maxLength 24. |
| ROA: none | 91.208.66.0/24 | No ROA covers it. Add a ROA for AS20712, maxLength 24. |
| ROA: none | 2001:678:3c4::/48 | No ROA covers it. Add a ROA for AS20712, maxLength 48. |
| ROA: none | 2001:67c:2a4c::/48 | No ROA covers it. Add a ROA for AS20712, maxLength 48. |
| ROA: none | 2001:67c:2e80::/48 | No ROA covers it. Add a ROA for AS20712, maxLength 48. |
| Route object: none | 90.155.0.0/22 | No route object for it. A route object for 90.155.0.0/21 with origin AS20712 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20712 in the RIR database for the space. |
| Route object: none | 90.155.62.0/24 | No route object for it. A route object for 90.155.0.0/18 with origin AS20712 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20712 in the RIR database for the space. |
| Route object: none | 90.155.67.0/24 | No route object for it. A route object for 90.155.64.0/19 with origin AS20712 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20712 in the RIR database for the space. |
| Route object: none | 2001:8b0::/34 | No route object for it. A route object for 2001:8b0::/32 with origin AS20712 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20712 in the RIR database for the space. |
| Route object: none | 2001:8b0::/48 | No route object for it. A route object for 2001:8b0::/32 with origin AS20712 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20712 in the RIR database for the space. |
| Route object: none | 2001:8b0:1::/48 | No route object for it. A route object for 2001:8b0::/32 with origin AS20712 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20712 in the RIR database for the space. |
| Route object: none | 2001:8b0:4000::/36 | No route object for it. A route object for 2001:8b0::/32 with origin AS20712 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20712 in the RIR database for the space. |
| Route object: none | 2001:8b6:1::/48 | No route object for it. A route object for 2001:8b6::/32 with origin AS20712 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20712 in the RIR database for the space. |
| Route object: none | 2001:8b6:2::/48 | No route object for it. A route object for 2001:8b6::/32 with origin AS20712 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20712 in the RIR database for the space. |
| Route object: none | 2001:8b6:3::/48 | No route object for it. A route object for 2001:8b6::/32 with origin AS20712 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20712 in the RIR database for the space. |
| Route object: none | 217.169.19.0/24 | No route object for it. A route object for 217.169.0.0/19 with origin AS20712 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20712 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS20712 whose prefix no peer sees AS20712 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 44.32.187.0/24 | RADB | No ROA |
| 81.187.0.0/19 | RIPE | Valid |
| 81.187.32.0/21 | RIPE | Valid |
| 81.187.40.0/23 | RIPE | Valid |
| 81.187.43.0/24 | RIPE | Valid |
| 81.187.44.0/22 | RIPE | Valid |
| 81.187.48.0/20 | RIPE | Valid |
| 81.187.64.0/19 | RIPE | Valid |
| 81.187.96.0/24 | RIPE | Valid |
| 81.187.97.0/24 | RIPE | Valid |
| 81.187.112.0/20 | RIPE | Valid |
| 81.187.128.0/17 | RIPE | Valid |
| 90.155.0.0/21 | RIPE | Valid |
| 90.155.1.0/24 | RIPE | Valid |
| 90.155.16.0/20 | RIPE | Valid |
| 90.155.42.0/24 | RIPE | Valid |
| 90.155.71.0/24 | RIPE | Valid |
| 91.194.69.0/24 | RIPE | No ROA |
| 176.122.246.0/24 | RIPE | No ROA |
| 185.238.117.0/24 | RIPE | Invalid: origin |
| 212.134.228.0/24 | RIPE | Invalid: origin |
| 2001:8b6::/32 | RIPE | Valid |
| 2a06:a005:1720::/44 | RIPE | Invalid: origin |
Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.