bgpreport

Network · data from 2026-11-12

AS267488 andre luiz silva dos santos informatica

Registry name: AS267488 - Pronet Construcoes LTDA, BR · PeeringDB

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

Announced routes

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

181.191.152.0/22 Valid Other IRR onlyALTDB, RADB 672 100% 67
181.191.152.0/23 Valid Other IRR onlyALTDB 670 100% 67
181.191.154.0/23 Valid Other IRR onlyALTDB 670 100% 67
2804:4240::/32 Valid Other IRR onlyALTDB, RADB 634 100% 67
2804:4240::/33 Valid Other IRR onlyALTDB 634 100% 67
2804:4240::/34 Valid Other IRR onlyALTDB 634 100% 67
2804:4240:4000::/34 Valid Other IRR onlyALTDB 634 100% 67
2804:4240:8000::/33 Valid Other IRR onlyALTDB 634 100% 67
2804:4240:8000::/34 Valid Other IRR onlyALTDB 634 100% 67
2804:4240:c000::/34 Valid Other IRR onlyALTDB 634 100% 67

AS-SET

AS267488'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 16 are in fix.csv.

  • Route object: RIR10
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
Route object: RIR181.191.152.0/22Route object only in ALTDB, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR181.191.152.0/23Route object only in ALTDB. Add it in the RIR database for the space.670 of 673
Route object: RIR181.191.154.0/23Route object only in ALTDB. Add it in the RIR database for the space.670 of 673
Route object: RIR2804:4240::/32Route object only in ALTDB, RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:4240::/33Route object only in ALTDB. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:4240::/34Route object only in ALTDB. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:4240:4000::/34Route object only in ALTDB. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:4240:8000::/33Route object only in ALTDB. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:4240:8000::/34Route object only in ALTDB. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:4240:c000::/34Route object only in ALTDB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

181.191.152.0/24ALTDBValid
181.191.153.0/24ALTDBValid
181.191.154.0/24ALTDBValid
181.191.155.0/24ALTDBValid
186.251.92.0/22RADBNo ROA
2804:4108::/32RADBNo 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.