bgpreport

Network · data from 2026-11-12

AS27818 Cotesma

Registry name: AS27818 - Cotesma, AR · PeeringDB

75IPv4 routes 100.0% RPKI valid · 1.3% with a route object
18IPv6 routes 100.0% RPKI valid · 94.4% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 75 with no route object for this origin
5Low visibility seen by under 10% of full-table peers
8Route objects not announced registered with origin AS27818, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS27818, 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.

201.220.161.0/24 Valid Nonecovered by 201.220.160.0/19 673 100% 67
131.161.152.0/24 Valid Nonecovered by 131.161.152.0/22 672 100% 66
131.161.153.0/24 Valid Nonecovered by 131.161.152.0/22 672 100% 66
131.161.154.0/24 Valid Nonecovered by 131.161.152.0/22 672 100% 67
131.161.155.0/24 Valid Nonecovered by 131.161.152.0/22 672 100% 67
181.114.128.0/24 Valid Nonecovered by 181.114.128.0/20 672 100% 66
181.114.129.0/24 Valid Nonecovered by 181.114.128.0/20 672 100% 66
181.114.130.0/24 Valid Nonecovered by 181.114.128.0/20 672 100% 66
181.114.131.0/24 Valid Nonecovered by 181.114.128.0/20 672 100% 66
181.114.132.0/24 Valid Nonecovered by 181.114.128.0/20 672 100% 66
181.114.133.0/24 Valid Nonecovered by 181.114.128.0/20 672 100% 66
181.114.134.0/24 Valid Nonecovered by 181.114.128.0/20 672 100% 66
181.114.135.0/24 Valid Nonecovered by 181.114.128.0/20 672 100% 66
181.114.136.0/24 Valid Nonecovered by 181.114.128.0/20 672 100% 66
181.114.137.0/24 Valid Nonecovered by 181.114.128.0/20 672 100% 66
181.114.138.0/24 Valid Nonecovered by 181.114.128.0/20 672 100% 66
181.114.139.0/24 Valid Nonecovered by 181.114.128.0/20 672 100% 66
181.114.140.0/24 Valid Nonecovered by 181.114.128.0/20 672 100% 66
181.114.141.0/24 Valid Nonecovered by 181.114.128.0/20 672 100% 66
181.114.142.0/24 Valid Nonecovered by 181.114.128.0/20 672 100% 66
181.114.143.0/24 Valid Nonecovered by 181.114.128.0/20 672 100% 66
181.114.144.0/24 Valid Nonecovered by 181.114.144.0/21 672 100% 66
181.114.145.0/24 Valid Nonecovered by 181.114.144.0/21 672 100% 66
181.114.146.0/24 Valid Nonecovered by 181.114.144.0/21 672 100% 66
181.114.147.0/24 Valid Nonecovered by 181.114.144.0/21 672 100% 66
181.114.148.0/24 Valid Nonecovered by 181.114.144.0/21 672 100% 66
181.114.149.0/24 Valid Nonecovered by 181.114.144.0/21 672 100% 66
181.114.150.0/24 Valid Nonecovered by 181.114.144.0/21 672 100% 66
181.114.151.0/24 Valid Nonecovered by 181.114.144.0/21 672 100% 66
181.114.152.0/24 Valid Nonecovered by 181.114.128.0/19 672 100% 67
181.114.153.0/24 Valid Nonecovered by 181.114.128.0/19 672 100% 67
181.114.154.0/24 Valid Nonecovered by 181.114.128.0/19 672 100% 67
181.114.158.0/24 Valid Nonecovered by 181.114.128.0/19 672 100% 67
181.114.159.0/24 Valid Nonecovered by 181.114.128.0/19 672 100% 67
201.220.160.0/24 Valid Nonecovered by 201.220.160.0/19 672 100% 66
201.220.164.0/24 Valid Nonecovered by 201.220.160.0/19 672 100% 66
201.220.165.0/24 Valid Nonecovered by 201.220.160.0/19 672 100% 66
201.220.168.0/24 Valid Nonecovered by 201.220.160.0/19 672 100% 66
201.220.170.0/24 Valid Nonecovered by 201.220.160.0/19 672 100% 66
201.220.171.0/24 Valid Nonecovered by 201.220.160.0/19 672 100% 66
201.220.172.0/24 Valid Nonecovered by 201.220.160.0/19 672 100% 66
201.220.173.0/24 Valid Nonecovered by 201.220.160.0/19 672 100% 66
201.220.174.0/24 Valid Nonecovered by 201.220.160.0/19 672 100% 66
201.220.175.0/24 Valid Nonecovered by 201.220.160.0/19 672 100% 66
201.220.176.0/24 Valid Nonecovered by 201.220.160.0/19 672 100% 66
201.220.177.0/24 Valid Nonecovered by 201.220.160.0/19 672 100% 66
201.220.186.0/23 Valid Nonecovered by 201.220.160.0/19 672 100% 66
201.220.187.0/24 Valid Nonecovered by 201.220.160.0/19 672 100% 66
201.220.188.0/22 Valid Nonecovered by 201.220.160.0/19 672 100% 66
201.220.188.0/24 Valid Nonecovered by 201.220.160.0/19 672 100% 66
201.220.189.0/24 Valid Nonecovered by 201.220.160.0/19 672 100% 66
201.220.190.0/24 Valid Nonecovered by 201.220.160.0/19 672 100% 66
201.220.191.0/24 Valid Nonecovered by 201.220.160.0/19 672 100% 66
181.114.155.0/24 Valid Nonecovered by 181.114.128.0/19 671 100% 66
181.114.156.0/24 Valid Nonecovered by 181.114.128.0/19 671 100% 66
181.114.157.0/24 Valid Nonecovered by 181.114.128.0/19 671 100% 66
201.220.186.0/24 Valid Nonecovered by 201.220.160.0/19 667 99% 66
201.220.162.0/24 Valid Nonecovered by 201.220.160.0/19 666 99% 66
201.220.163.0/24 Valid Nonecovered by 201.220.160.0/19 666 99% 66
201.220.166.0/24 Valid Nonecovered by 201.220.160.0/19 666 99% 66
201.220.167.0/24 Valid Nonecovered by 201.220.160.0/19 666 99% 66
201.220.178.0/24 Valid Nonecovered by 201.220.160.0/19 666 99% 66
201.220.179.0/24 Valid Nonecovered by 201.220.160.0/19 666 99% 66
201.220.180.0/24 Valid Nonecovered by 201.220.160.0/19 666 99% 66
201.220.181.0/24 Valid Nonecovered by 201.220.160.0/19 666 99% 66
201.220.182.0/24 Valid Nonecovered by 201.220.160.0/19 666 99% 66
201.220.183.0/24 Valid Nonecovered by 201.220.160.0/19 666 99% 66
201.220.184.0/24 Valid Nonecovered by 201.220.160.0/19 666 99% 66
201.220.185.0/24 Valid Nonecovered by 201.220.160.0/19 666 99% 66
2803:3380:1003::/48 Valid Nonecovered by 2803:3380:1000::/40 633 100% 69
181.114.136.0/22 Valid Nonecovered by 181.114.128.0/20 8 1%low visibility 6
201.220.168.0/21 Valid Nonecovered by 201.220.160.0/19 8 1%low visibility 6
201.220.180.0/22 Valid Nonecovered by 201.220.160.0/19 8 1%low visibility 6
201.220.184.0/22 Valid Nonecovered by 201.220.160.0/19 8 1%low visibility 6
201.220.169.0/24 Valid Nonecovered by 201.220.160.0/19 3 0%low visibility 3
200.47.43.0/24 Valid RIR databaseLACNIC 671 100% 66
2803:3380:fe00::/40 Valid RIR databaseLACNIC 636 100% 67
2803:3380:ff00::/40 Valid RIR databaseLACNIC 636 100% 67
2803:3380:1100::/40 Valid RIR databaseLACNIC 633 100% 69
2803:3380:1200::/40 Valid RIR databaseLACNIC 633 100% 69
2803:3380:2000::/36 Valid RIR databaseLACNIC 633 100% 69
2803:3380:3000::/36 Valid RIR databaseLACNIC 633 100% 69
2803:3380:4000::/36 Valid RIR databaseLACNIC 633 100% 69
2803:3380:5000::/36 Valid RIR databaseLACNIC 633 100% 69
2803:3380:6000::/36 Valid RIR databaseLACNIC 633 100% 69
2803:3380:7000::/36 Valid RIR databaseLACNIC 633 100% 69
2803:3380:8000::/36 Valid RIR databaseLACNIC 633 100% 69
2803:3380:9000::/36 Valid RIR databaseLACNIC 633 100% 69
2803:3380:a000::/36 Valid RIR databaseLACNIC 633 100% 69
2803:3380:b000::/36 Valid RIR databaseLACNIC 633 100% 69
2803:3380:c000::/36 Valid RIR databaseLACNIC 633 100% 69
2803:3380:d000::/36 Valid RIR databaseLACNIC 633 100% 69
2803:3380:e000::/36 Valid RIR databaseLACNIC 633 100% 69

AS-SET

AS27818's PeeringDB record names no AS-SET.

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 83 are in fix.csv.

  • Route object: none75
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
Route object: none201.220.161.0/24No route object for it. A route object for 201.220.160.0/19 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.673 of 673
Route object: none131.161.152.0/24No route object for it. A route object for 131.161.152.0/22 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.672 of 673
Route object: none131.161.153.0/24No route object for it. A route object for 131.161.152.0/22 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.672 of 673
Route object: none131.161.154.0/24No route object for it. A route object for 131.161.152.0/22 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.672 of 673
Route object: none131.161.155.0/24No route object for it. A route object for 131.161.152.0/22 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.672 of 673
Route object: none181.114.128.0/24No route object for it. A route object for 181.114.128.0/20 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.672 of 673
Route object: none181.114.129.0/24No route object for it. A route object for 181.114.128.0/20 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.672 of 673
Route object: none181.114.130.0/24No route object for it. A route object for 181.114.128.0/20 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.672 of 673
Route object: none181.114.131.0/24No route object for it. A route object for 181.114.128.0/20 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.672 of 673
Route object: none181.114.132.0/24No route object for it. A route object for 181.114.128.0/20 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.672 of 673
Route object: none181.114.133.0/24No route object for it. A route object for 181.114.128.0/20 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.672 of 673
Route object: none181.114.134.0/24No route object for it. A route object for 181.114.128.0/20 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.672 of 673
Route object: none181.114.135.0/24No route object for it. A route object for 181.114.128.0/20 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.672 of 673
Route object: none181.114.136.0/24No route object for it. A route object for 181.114.128.0/20 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.672 of 673
Route object: none181.114.137.0/24No route object for it. A route object for 181.114.128.0/20 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.672 of 673
Route object: none181.114.138.0/24No route object for it. A route object for 181.114.128.0/20 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.672 of 673
Route object: none181.114.139.0/24No route object for it. A route object for 181.114.128.0/20 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.672 of 673
Route object: none181.114.140.0/24No route object for it. A route object for 181.114.128.0/20 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.672 of 673
Route object: none181.114.141.0/24No route object for it. A route object for 181.114.128.0/20 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.672 of 673
Route object: none181.114.142.0/24No route object for it. A route object for 181.114.128.0/20 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.672 of 673
Route object: none181.114.143.0/24No route object for it. A route object for 181.114.128.0/20 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.672 of 673
Route object: none181.114.144.0/24No route object for it. A route object for 181.114.144.0/21 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.672 of 673
Route object: none181.114.145.0/24No route object for it. A route object for 181.114.144.0/21 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.672 of 673
Route object: none181.114.146.0/24No route object for it. A route object for 181.114.144.0/21 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.672 of 673
Route object: none181.114.147.0/24No route object for it. A route object for 181.114.144.0/21 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.672 of 673
Route object: none181.114.148.0/24No route object for it. A route object for 181.114.144.0/21 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.672 of 673
Route object: none181.114.149.0/24No route object for it. A route object for 181.114.144.0/21 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.672 of 673
Route object: none181.114.150.0/24No route object for it. A route object for 181.114.144.0/21 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.672 of 673
Route object: none181.114.151.0/24No route object for it. A route object for 181.114.144.0/21 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.672 of 673
Route object: none181.114.152.0/24No route object for it. A route object for 181.114.128.0/19 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.672 of 673
Route object: none181.114.153.0/24No route object for it. A route object for 181.114.128.0/19 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.672 of 673
Route object: none181.114.154.0/24No route object for it. A route object for 181.114.128.0/19 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.672 of 673
Route object: none181.114.158.0/24No route object for it. A route object for 181.114.128.0/19 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.672 of 673
Route object: none181.114.159.0/24No route object for it. A route object for 181.114.128.0/19 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.672 of 673
Route object: none201.220.160.0/24No route object for it. A route object for 201.220.160.0/19 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.672 of 673
Route object: none201.220.164.0/24No route object for it. A route object for 201.220.160.0/19 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.672 of 673
Route object: none201.220.165.0/24No route object for it. A route object for 201.220.160.0/19 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.672 of 673
Route object: none201.220.168.0/24No route object for it. A route object for 201.220.160.0/19 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.672 of 673
Route object: none201.220.170.0/24No route object for it. A route object for 201.220.160.0/19 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.672 of 673
Route object: none201.220.171.0/24No route object for it. A route object for 201.220.160.0/19 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.672 of 673
Route object: none201.220.172.0/24No route object for it. A route object for 201.220.160.0/19 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.672 of 673
Route object: none201.220.173.0/24No route object for it. A route object for 201.220.160.0/19 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.672 of 673
Route object: none201.220.174.0/24No route object for it. A route object for 201.220.160.0/19 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.672 of 673
Route object: none201.220.175.0/24No route object for it. A route object for 201.220.160.0/19 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.672 of 673
Route object: none201.220.176.0/24No route object for it. A route object for 201.220.160.0/19 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.672 of 673
Route object: none201.220.177.0/24No route object for it. A route object for 201.220.160.0/19 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.672 of 673
Route object: none201.220.186.0/23No route object for it. A route object for 201.220.160.0/19 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.672 of 673
Route object: none201.220.187.0/24No route object for it. A route object for 201.220.160.0/19 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.672 of 673
Route object: none201.220.188.0/22No route object for it. A route object for 201.220.160.0/19 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.672 of 673
Route object: none201.220.188.0/24No route object for it. A route object for 201.220.160.0/19 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.672 of 673
Route object: none201.220.189.0/24No route object for it. A route object for 201.220.160.0/19 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.672 of 673
Route object: none201.220.190.0/24No route object for it. A route object for 201.220.160.0/19 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.672 of 673
Route object: none201.220.191.0/24No route object for it. A route object for 201.220.160.0/19 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.672 of 673
Route object: none181.114.155.0/24No route object for it. A route object for 181.114.128.0/19 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.671 of 673
Route object: none181.114.156.0/24No route object for it. A route object for 181.114.128.0/19 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.671 of 673
Route object: none181.114.157.0/24No route object for it. A route object for 181.114.128.0/19 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.671 of 673
Route object: none201.220.186.0/24No route object for it. A route object for 201.220.160.0/19 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.667 of 673
Route object: none201.220.162.0/24No route object for it. A route object for 201.220.160.0/19 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.666 of 673
Route object: none201.220.163.0/24No route object for it. A route object for 201.220.160.0/19 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.666 of 673
Route object: none201.220.166.0/24No route object for it. A route object for 201.220.160.0/19 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.666 of 673
Route object: none201.220.167.0/24No route object for it. A route object for 201.220.160.0/19 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.666 of 673
Route object: none201.220.178.0/24No route object for it. A route object for 201.220.160.0/19 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.666 of 673
Route object: none201.220.179.0/24No route object for it. A route object for 201.220.160.0/19 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.666 of 673
Route object: none201.220.180.0/24No route object for it. A route object for 201.220.160.0/19 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.666 of 673
Route object: none201.220.181.0/24No route object for it. A route object for 201.220.160.0/19 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.666 of 673
Route object: none201.220.182.0/24No route object for it. A route object for 201.220.160.0/19 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.666 of 673
Route object: none201.220.183.0/24No route object for it. A route object for 201.220.160.0/19 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.666 of 673
Route object: none201.220.184.0/24No route object for it. A route object for 201.220.160.0/19 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.666 of 673
Route object: none201.220.185.0/24No route object for it. A route object for 201.220.160.0/19 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.666 of 673
Route object: none2803:3380:1003::/48No route object for it. A route object for 2803:3380:1000::/40 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.633 of 636
Route object: none181.114.136.0/22No route object for it. A route object for 181.114.128.0/20 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.8 of 673
Route object: none201.220.168.0/21No route object for it. A route object for 201.220.160.0/19 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.8 of 673
Route object: none201.220.180.0/22No route object for it. A route object for 201.220.160.0/19 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.8 of 673
Route object: none201.220.184.0/22No route object for it. A route object for 201.220.160.0/19 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.8 of 673
Route object: none201.220.169.0/24No route object for it. A route object for 201.220.160.0/19 with origin AS27818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27818 in the RIR database for the space.3 of 673

Route objects not announced

Route objects with origin AS27818 whose prefix no peer sees AS27818 announce. Many are kept on purpose (backup routes, space announced only in some places).

131.161.152.0/22LACNICValid
181.114.128.0/19LACNICValid
181.114.128.0/20RADBValid
181.114.144.0/21RADBValid
201.220.160.0/19LACNICValid
2803:3380:1000::/36LACNICValid
2803:3380:1000::/40LACNICValid
2803:3380:f000::/36LACNICValid

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.