bgpreport

Network · data from 2026-11-12

AS268712 AS268712 - DIEGO RIBEIRO NEVES

Registry name: AS268712 - DIEGO RIBEIRO NEVES, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS268712, 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.171.96.0/24 No ROA Nonecovered by 45.171.96.0/23 662 98% 67
45.171.97.0/24 No ROA Other IRR onlyALTDB 666 99% 66
45.171.98.0/24 No ROA Other IRR onlyRADB 665 99% 67
45.171.99.0/24 No ROA Other IRR onlyALTDB, RADB 664 99% 67
2804:5998:c000::/34 No ROA Other IRR onlyRADB 633 100% 67
2804:5998:8000::/34 No ROA Other IRR onlyRADB 631 99% 67

AS-SET

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

  • ROA: none6
  • Route object: none1
  • Route object: RIR5
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none45.171.96.0/24No ROA covers it. Add a ROA for AS268712, maxLength 24.662 of 673
Route object: none45.171.96.0/24No route object for it. A route object for 45.171.96.0/23 with origin AS268712 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268712 in the RIR database for the space.662 of 673
ROA: none45.171.97.0/24No ROA covers it. Add a ROA for AS268712, maxLength 24.666 of 673
Route object: RIR45.171.97.0/24Route object only in ALTDB. Add it in the RIR database for the space.666 of 673
ROA: none45.171.98.0/24No ROA covers it. Add a ROA for AS268712, maxLength 24.665 of 673
Route object: RIR45.171.98.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673
ROA: none45.171.99.0/24No ROA covers it. Add a ROA for AS268712, maxLength 24.664 of 673
Route object: RIR45.171.99.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.664 of 673
ROA: none2804:5998:c000::/34No ROA covers it. Add a ROA for AS268712, maxLength 34.633 of 636
Route object: RIR2804:5998:c000::/34Route object only in RADB. Add it in the RIR database for the space.633 of 636
ROA: none2804:5998:8000::/34No ROA covers it. Add a ROA for AS268712, maxLength 34.631 of 636
Route object: RIR2804:5998:8000::/34Route object only in RADB. Add it in the RIR database for the space.631 of 636

Route objects not announced

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

45.171.96.0/22RADBNo ROA
45.171.96.0/23RADBNo ROA
45.171.98.0/23RADBNo ROA
2804:5998::/32RADBNo ROA
2804:5998::/33RADBNo ROA
2804:5998:8000::/33RADBNo 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.