bgpreport

Network · data from 2026-11-12

AS11816 SetarNet

Registry name: AS11816 - SERVICIO DI TELECOMUNICACION DI ARUBA (SETAR) N.V., AW · PeeringDB

122IPv4 routes 98.4% RPKI valid · 93.4% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
2No ROA 8 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
16Route objects not announced registered with origin AS11816, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS11816, 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.229.2.0/23 No ROA None 672 100% 67
201.229.88.0/23 No ROA None 672 100% 67
186.189.28.0/23 Valid Nonecovered by 186.189.28.0/22 672 100% 67
186.189.30.0/23 Valid Nonecovered by 186.189.28.0/22 672 100% 67
186.189.48.0/23 Valid Nonecovered by 186.189.48.0/22 672 100% 67
186.189.50.0/23 Valid Nonecovered by 186.189.48.0/22 672 100% 67
186.189.52.0/23 Valid Nonecovered by 186.189.52.0/22 672 100% 67
186.189.54.0/23 Valid Nonecovered by 186.189.52.0/22 671 100% 67
181.41.0.0/23 Valid RIR databaseLACNIC 672 100% 67
181.41.2.0/23 Valid RIR databaseLACNIC 672 100% 67
181.41.4.0/23 Valid RIR databaseLACNIC 672 100% 67
181.41.8.0/23 Valid RIR databaseLACNIC 672 100% 67
181.41.20.0/23 Valid RIR databaseLACNIC 672 100% 67
181.41.22.0/23 Valid RIR databaseLACNIC 672 100% 67
181.41.26.0/23 Valid RIR databaseLACNIC 672 100% 67
181.41.28.0/23 Valid RIR databaseLACNIC 672 100% 67
181.41.30.0/23 Valid RIR databaseLACNIC 672 100% 67
181.41.32.0/23 Valid RIR databaseLACNIC 672 100% 67
181.41.34.0/23 Valid RIR databaseLACNIC 672 100% 67
181.41.36.0/22 Valid RIR databaseLACNIC 672 100% 67
181.41.40.0/22 Valid RIR databaseLACNIC 672 100% 67
181.41.44.0/23 Valid RIR databaseLACNIC 672 100% 67
181.41.46.0/23 Valid RIR databaseLACNIC 672 100% 67
181.41.50.0/23 Valid RIR databaseLACNIC 672 100% 67
181.41.52.0/23 Valid RIR databaseLACNIC 672 100% 67
181.41.54.0/23 Valid RIR databaseLACNIC 672 100% 67
181.41.56.0/23 Valid RIR databaseLACNIC 672 100% 67
181.41.58.0/23 Valid RIR databaseLACNIC 672 100% 67
181.41.60.0/23 Valid RIR databaseLACNIC 672 100% 67
181.41.62.0/23 Valid RIR databaseLACNIC 672 100% 67
186.159.100.0/24 Valid RIR databaseLACNIC 672 100% 67
186.189.6.0/23 Valid RIR databaseLACNIC 672 100% 67
186.189.8.0/23 Valid RIR databaseLACNIC 672 100% 67
186.189.12.0/23 Valid RIR databaseLACNIC 672 100% 67
186.189.14.0/23 Valid RIR databaseLACNIC 672 100% 67
186.189.16.0/23 Valid RIR databaseLACNIC 672 100% 67
186.189.18.0/23 Valid RIR databaseLACNIC 672 100% 67
186.189.22.0/23 Valid RIR databaseLACNIC 672 100% 67
186.189.24.0/23 Valid RIR databaseLACNIC 672 100% 67
186.189.26.0/23 Valid RIR databaseLACNIC 672 100% 67
186.189.32.0/23 Valid RIR databaseLACNIC 672 100% 67
186.189.34.0/23 Valid RIR databaseLACNIC 672 100% 67
186.189.36.0/23 Valid RIR databaseLACNIC 672 100% 67
186.189.38.0/23 Valid RIR databaseLACNIC 672 100% 67
186.189.42.0/23 Valid RIR databaseLACNIC 672 100% 67
186.189.58.0/23 Valid RIR databaseLACNIC 672 100% 67
186.189.60.0/23 Valid RIR databaseLACNIC 672 100% 67
186.189.128.0/23 Valid RIR databaseLACNIC 672 100% 67
186.189.130.0/23 Valid RIR databaseLACNIC 672 100% 67
186.189.134.0/23 Valid RIR databaseLACNIC 672 100% 67
186.189.138.0/23 Valid RIR databaseLACNIC 672 100% 67
186.189.140.0/23 Valid RIR databaseLACNIC 672 100% 67
186.189.142.0/23 Valid RIR databaseLACNIC 672 100% 67
186.189.144.0/23 Valid RIR databaseLACNIC 672 100% 67
186.189.146.0/23 Valid RIR databaseLACNIC 672 100% 67
186.189.148.0/23 Valid RIR databaseLACNIC 672 100% 67
186.189.150.0/23 Valid RIR databaseLACNIC 672 100% 67
186.189.152.0/23 Valid RIR databaseLACNIC 672 100% 67
186.189.154.0/23 Valid RIR databaseLACNIC 672 100% 67
186.189.156.0/23 Valid RIR databaseLACNIC 672 100% 67
186.189.158.0/23 Valid RIR databaseLACNIC 672 100% 67
186.189.160.0/23 Valid RIR databaseLACNIC 672 100% 67
186.189.164.0/23 Valid RIR databaseLACNIC 672 100% 67
186.189.166.0/23 Valid RIR databaseLACNIC 672 100% 67
186.189.168.0/23 Valid RIR databaseLACNIC 672 100% 67
186.189.170.0/23 Valid RIR databaseLACNIC 672 100% 67
186.189.174.0/23 Valid RIR databaseLACNIC 672 100% 67
186.189.176.0/23 Valid RIR databaseLACNIC 672 100% 67
186.189.178.0/23 Valid RIR databaseLACNIC 672 100% 67
186.189.180.0/23 Valid RIR databaseLACNIC 672 100% 67
186.189.182.0/23 Valid RIR databaseLACNIC 672 100% 67
186.189.184.0/23 Valid RIR databaseLACNIC 672 100% 67
186.189.186.0/23 Valid RIR databaseLACNIC 672 100% 67
186.189.188.0/23 Valid RIR databaseLACNIC 672 100% 67
186.189.190.0/23 Valid RIR databaseLACNIC 672 100% 67
201.229.0.0/23 Valid RIR databaseLACNIC 672 100% 67
201.229.4.0/23 Valid RIR databaseLACNIC 672 100% 67
201.229.6.0/23 Valid RIR databaseLACNIC 672 100% 67
201.229.8.0/23 Valid RIR databaseLACNIC 672 100% 67
201.229.12.0/23 Valid RIR databaseLACNIC 672 100% 67
201.229.16.0/21 Valid RIR databaseLACNIC 672 100% 67
201.229.24.0/21 Valid RIR databaseLACNIC 672 100% 67
201.229.32.0/21 Valid RIR databaseLACNIC 672 100% 67
201.229.40.0/21 Valid RIR databaseLACNIC 672 100% 67
201.229.48.0/23 Valid RIR databaseLACNIC 672 100% 67
201.229.50.0/23 Valid RIR databaseLACNIC 672 100% 67
201.229.52.0/23 Valid RIR databaseLACNIC 672 100% 67
201.229.54.0/23 Valid RIR databaseLACNIC 672 100% 67
201.229.60.0/23 Valid RIR databaseLACNIC 672 100% 67
201.229.62.0/23 Valid RIR databaseLACNIC 672 100% 67
201.229.64.0/23 Valid RIR databaseLACNIC 672 100% 67
201.229.66.0/23 Valid RIR databaseLACNIC 672 100% 67
201.229.68.0/23 Valid RIR databaseLACNIC 672 100% 67
201.229.70.0/23 Valid RIR databaseLACNIC 672 100% 67
201.229.72.0/23 Valid RIR databaseLACNIC 672 100% 67
201.229.74.0/23 Valid RIR databaseLACNIC 672 100% 67
201.229.76.0/23 Valid RIR databaseLACNIC 672 100% 67
201.229.78.0/23 Valid RIR databaseLACNIC 672 100% 67
201.229.80.0/23 Valid RIR databaseLACNIC 672 100% 67
201.229.82.0/23 Valid RIR databaseLACNIC 672 100% 67
201.229.84.0/23 Valid RIR databaseLACNIC 672 100% 67
201.229.86.0/23 Valid RIR databaseLACNIC 672 100% 67
201.229.92.0/23 Valid RIR databaseLACNIC 672 100% 67
201.229.94.0/23 Valid RIR databaseLACNIC 672 100% 67
201.229.96.0/23 Valid RIR databaseLACNIC 672 100% 67
201.229.98.0/23 Valid RIR databaseLACNIC 672 100% 67
201.229.100.0/23 Valid RIR databaseLACNIC 672 100% 67
201.229.102.0/23 Valid RIR databaseLACNIC 672 100% 67
201.229.104.0/23 Valid RIR databaseLACNIC 672 100% 67
201.229.108.0/23 Valid RIR databaseLACNIC 672 100% 67
201.229.110.0/23 Valid RIR databaseLACNIC 672 100% 67
201.229.112.0/23 Valid RIR databaseLACNIC 672 100% 67
201.229.114.0/23 Valid RIR databaseLACNIC 672 100% 67
201.229.118.0/23 Valid RIR databaseLACNIC 672 100% 67
201.229.122.0/23 Valid RIR databaseLACNIC 672 100% 67
186.189.0.0/23 Valid RIR databaseLACNIC 671 100% 67
186.189.44.0/23 Valid RIR databaseLACNIC 671 100% 67
186.189.46.0/23 Valid RIR databaseLACNIC 671 100% 67
186.189.62.0/23 Valid RIR databaseLACNIC 671 100% 67
186.189.56.0/23 Valid RIR databaseLACNIC 670 100% 67
186.189.162.0/23 Valid RIR databaseLACNIC 669 99% 67
186.189.172.0/23 Valid RIR databaseLACNIC 669 99% 67
2800:ad0::/32 Valid RIR databaseLACNIC 635 100% 67

AS-SET

AS11816'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 26 are in fix.csv.

  • ROA: none2
  • Route object: none8
  • Route object: not announced16
ChangePrefix or setDetailFull-table peers
ROA: none201.229.2.0/23No ROA covers it. Add a ROA for AS11816, maxLength 23.672 of 673
Route object: none201.229.2.0/23No route object for it. Add a route object with origin AS11816 in the RIR database for the space.672 of 673
ROA: none201.229.88.0/23No ROA covers it. Add a ROA for AS11816, maxLength 23.672 of 673
Route object: none201.229.88.0/23No route object for it. Add a route object with origin AS11816 in the RIR database for the space.672 of 673
Route object: none186.189.28.0/23No route object for it. A route object for 186.189.28.0/22 with origin AS11816 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11816 in the RIR database for the space.672 of 673
Route object: none186.189.30.0/23No route object for it. A route object for 186.189.28.0/22 with origin AS11816 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11816 in the RIR database for the space.672 of 673
Route object: none186.189.48.0/23No route object for it. A route object for 186.189.48.0/22 with origin AS11816 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11816 in the RIR database for the space.672 of 673
Route object: none186.189.50.0/23No route object for it. A route object for 186.189.48.0/22 with origin AS11816 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11816 in the RIR database for the space.672 of 673
Route object: none186.189.52.0/23No route object for it. A route object for 186.189.52.0/22 with origin AS11816 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11816 in the RIR database for the space.672 of 673
Route object: none186.189.54.0/23No route object for it. A route object for 186.189.52.0/22 with origin AS11816 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11816 in the RIR database for the space.671 of 673

Route objects not announced

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

181.41.6.0/23LACNICValid
181.41.24.0/23LACNICValid
186.189.2.0/23LACNICValid
186.189.4.0/23LACNICValid
186.189.28.0/22LACNICValid
186.189.48.0/22LACNICValid
186.189.52.0/22LACNICValid
186.189.132.0/23LACNICValid
186.189.136.0/23LACNICValid
201.229.10.0/23LACNICValid
201.229.14.0/23LACNICValid
201.229.90.0/23LACNICValid
201.229.106.0/23LACNICValid
201.229.120.0/23LACNICValid
201.229.124.0/23LACNICValid
201.229.126.0/23LACNICValid

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.