bgpreport

Network · data from 2026-11-12

AS267804 AS267804 - MORAN DOLORES GRACIELA

Registry name: AS267804 - MORAN DOLORES GRACIELA, AR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS267804, 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.172.110.0/23 Invalid: maxLength Nonecovered by 45.172.108.0/22 1 0%low visibility 2
45.172.108.0/24 Valid RIR databaseLACNIC 670 100% 67
45.172.110.0/24 Valid RIR databaseLACNIC 670 100% 67
45.172.111.0/24 Valid RIR databaseLACNIC 670 100% 67
45.172.109.0/24 Valid RIR databaseLACNIC 668 99% 67

AS-SET

AS267804 isn't in PeeringDB, where networks name their 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 4 are in fix.csv.

  • ROA: maxLength1
  • Route object: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: maxLength45.172.110.0/23ROA 45.172.108.0/22 AS267804 has maxLength 22; the route is a /23. Raise the maxLength, or add a ROA for 45.172.110.0/23.1 of 673
Route object: none45.172.110.0/23No route object for it. A route object for 45.172.108.0/22 with origin AS267804 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267804 in the RIR database for the space.1 of 673

Route objects not announced

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

45.172.108.0/22LACNICValid
2803:7fa0::/32LACNICValid

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.