bgpreport

Network · data from 2026-11-12

AS267833 ONPOWER Internet

Registry name: AS267833 - CASELLES COSTA FACUNDO JAVIER (ONPOWER), AR · PeeringDB

11IPv4 routes 81.8% RPKI valid · 72.7% with a route object
0IPv6 routes
1RPKI invalid 0 origin · 1 maxLength
1No ROA 3 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS267833, seen from no peer

Announced routes

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

45.175.102.0/23 Invalid: maxLength Nonecovered by 45.175.100.0/22 1 0%low visibility 2
38.210.101.0/24 No ROA Other IRR onlyRADB 666 99% 67
216.28.240.0/24 Valid Nonecovered by 216.28.240.0/23 671 100% 67
216.28.241.0/24 Valid Nonecovered by 216.28.240.0/23 671 100% 67
216.28.240.0/23 Valid RIR databaseARIN 671 100% 67
45.175.100.0/22 Valid RIR databaseLACNIC 667 99% 67
177.184.89.0/24 Valid RIR databaseLACNIC 667 99% 67
45.175.101.0/24 Valid RIR databaseLACNIC 666 99% 67
45.175.102.0/24 Valid RIR databaseLACNIC 666 99% 67
45.175.103.0/24 Valid RIR databaseLACNIC 665 99% 67
45.175.100.0/24 Valid RIR databaseLACNIC 104 15% 41

AS-SET

AS267833'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 6 are in fix.csv.

  • ROA: maxLength1
  • ROA: none1
  • Route object: none3
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: maxLength45.175.102.0/23ROA 45.175.100.0/22 AS267833 has maxLength 22; the route is a /23. Raise the maxLength, or add a ROA for 45.175.102.0/23.1 of 673
Route object: none45.175.102.0/23No route object for it. A route object for 45.175.100.0/22 with origin AS267833 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267833 in the RIR database for the space.1 of 673
ROA: none38.210.101.0/24No ROA covers it. Add a ROA for AS267833, maxLength 24.666 of 673
Route object: RIR38.210.101.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
Route object: none216.28.240.0/24No route object for it. A route object for 216.28.240.0/23 with origin AS267833 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267833 in the RIR database for the space.671 of 673
Route object: none216.28.241.0/24No route object for it. A route object for 216.28.240.0/23 with origin AS267833 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267833 in the RIR database for the space.671 of 673

Route objects not announced

Every route object with origin AS267833 is announced.

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.