bgpreport

Network · data from 2026-11-12

AS264685 REDES DEL OESTE

Registry name: AS264685 - REDES DEL OESTE S.A, AR · PeeringDB

20IPv4 routes 55.0% RPKI valid · 60.0% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
9No ROA 8 with no route object for this origin
3Low visibility seen by under 10% of full-table peers
6Route objects not announced registered with origin AS264685, seen from no peer

Announced routes

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

38.51.30.0/23 No ROA Nonecovered by 38.51.28.0/22 670 100% 67
38.51.30.0/24 No ROA Nonecovered by 38.51.28.0/22 669 99% 67
38.51.31.0/24 No ROA Nonecovered by 38.51.28.0/22 669 99% 67
38.51.28.0/23 No ROA Nonecovered by 38.51.28.0/22 668 99% 67
38.51.29.0/24 No ROA Nonecovered by 38.51.28.0/22 668 99% 67
38.51.28.0/22 No ROA Other IRR onlyRADB 670 100% 67
38.4.144.0/21 No ROA Other IRR onlyRADB 669 99% 67
38.51.22.0/24 No ROA Other IRR onlyRADB 668 99% 67
38.51.28.0/24 No ROA Other IRR onlyRADB 1 0%low visibility 1
168.227.98.0/23 Valid Nonecovered by 168.227.96.0/22 670 100% 67
45.175.163.0/24 Valid Nonecovered by 45.175.162.0/23 669 99% 67
45.175.162.0/24 Valid Nonecovered by 45.175.162.0/23 1 0%low visibility 1
45.175.162.0/23 Valid Other IRR onlyRADB 671 100% 67
168.227.99.0/24 Valid Other IRR onlyRADB 671 100% 67
168.227.96.0/24 Valid Other IRR onlyRADB 669 99% 67
168.227.97.0/24 Valid Other IRR onlyRADB 669 99% 67
168.227.98.0/24 Valid Other IRR onlyRADB 1 0%low visibility 1
168.227.96.0/22 Valid RIR databaseALTDB, LACNIC, RADB 670 100% 67
168.227.96.0/23 Valid RIR databaseLACNIC 669 99% 67
181.174.238.0/24 Valid RIR databaseLACNIC, RADB 669 99% 67
2803:340::/32 Valid RIR databaseLACNIC, RADB 636 100% 67

AS-SET

PeeringDB's irr_as_set for AS264685: AS264685. 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 (AS264685 isn't in the set, or no route object for AS264685 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.

NameDatabaseASNsSets Route objectsAS264685 in itNot covered
AS264685 A single AS number, not a set: AS264685 (this network), 19 route objects.

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

  • ROA: none9
  • Route object: none8
  • Route object: RIR9
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none38.51.30.0/23No ROA covers it. Add a ROA for AS264685, maxLength 23.670 of 673
Route object: none38.51.30.0/23No route object for it. A route object for 38.51.28.0/22 with origin AS264685 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264685 in the RIR database for the space.670 of 673
ROA: none38.51.30.0/24No ROA covers it. Add a ROA for AS264685, maxLength 24.669 of 673
Route object: none38.51.30.0/24No route object for it. A route object for 38.51.28.0/22 with origin AS264685 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264685 in the RIR database for the space.669 of 673
ROA: none38.51.31.0/24No ROA covers it. Add a ROA for AS264685, maxLength 24.669 of 673
Route object: none38.51.31.0/24No route object for it. A route object for 38.51.28.0/22 with origin AS264685 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264685 in the RIR database for the space.669 of 673
ROA: none38.51.28.0/23No ROA covers it. Add a ROA for AS264685, maxLength 23.668 of 673
Route object: none38.51.28.0/23No route object for it. A route object for 38.51.28.0/22 with origin AS264685 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264685 in the RIR database for the space.668 of 673
ROA: none38.51.29.0/24No ROA covers it. Add a ROA for AS264685, maxLength 24.668 of 673
Route object: none38.51.29.0/24No route object for it. A route object for 38.51.28.0/22 with origin AS264685 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264685 in the RIR database for the space.668 of 673
ROA: none38.51.28.0/22No ROA covers it. Add a ROA for AS264685, maxLength 22.670 of 673
Route object: RIR38.51.28.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none38.4.144.0/21No ROA covers it. Add a ROA for AS264685, maxLength 21.669 of 673
Route object: RIR38.4.144.0/21Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none38.51.22.0/24No ROA covers it. Add a ROA for AS264685, maxLength 24.668 of 673
Route object: RIR38.51.22.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none38.51.28.0/24No ROA covers it. Add a ROA for AS264685, maxLength 24.1 of 673
Route object: RIR38.51.28.0/24Route object only in RADB. Add it in the RIR database for the space.1 of 673
Route object: none168.227.98.0/23No route object for it. A route object for 168.227.96.0/22 with origin AS264685 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264685 in the RIR database for the space.670 of 673
Route object: none45.175.163.0/24No route object for it. A route object for 45.175.162.0/23 with origin AS264685 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264685 in the RIR database for the space.669 of 673
Route object: none45.175.162.0/24No route object for it. A route object for 45.175.162.0/23 with origin AS264685 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264685 in the RIR database for the space.1 of 673
Route object: RIR45.175.162.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR168.227.99.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR168.227.96.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR168.227.97.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR168.227.98.0/24Route object only in RADB. Add it in the RIR database for the space.1 of 673

Route objects not announced

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

38.4.144.0/24RADBNo ROA
38.10.142.0/24RADBNo ROA
45.167.120.0/24RADBNo ROA
179.61.4.0/22RADBNo ROA
181.233.180.0/22RADBNo ROA
190.15.192.0/19RADBNo ROA

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.