bgpreport

Network · data from 2026-11-12

AS265630 COMISSO DANTE ANIBAL

Registry name: AS265630 - COMISSO DANTE ANIBAL, AR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS265630, 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.
170.244.188.0/22 No ROA None 670 100% 67
181.81.246.0/24 Valid Nonecovered by 181.81.246.0/23 666 99% 67
181.81.247.0/24 Valid Nonecovered by 181.81.246.0/23 666 99% 67
45.195.32.0/20 Valid RIR databaseAFRINIC, RADB 669 99% 67
181.93.244.0/24 Valid RIR databaseLACNIC 666 99% 67
181.93.248.0/24 Valid RIR databaseLACNIC 666 99% 67
181.94.192.0/22 Valid RIR databaseLACNIC 666 99% 67

AS-SET

AS265630'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: none1
  • Route object: none3
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none170.244.188.0/22No ROA covers it. Add a ROA for AS265630, maxLength 22.670 of 673
Route object: none170.244.188.0/22No route object for it. Add a route object with origin AS265630 in the RIR database for the space.670 of 673
Route object: none181.81.246.0/24No route object for it. A route object for 181.81.246.0/23 with origin AS265630 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265630 in the RIR database for the space.666 of 673
Route object: none181.81.247.0/24No route object for it. A route object for 181.81.246.0/23 with origin AS265630 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265630 in the RIR database for the space.666 of 673

Route objects not announced

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

45.195.32.0/24AFRINIC, RADBValid
181.81.246.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.