bgpreport

Network · data from 2026-11-12

AS270431 AS270431 - J Riva Junior Eletronics ME

Registry name: AS270431 - J Riva Junior Eletronics ME, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS270431, 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.
190.115.84.0/24 Valid Nonecovered by 190.115.84.0/23 93 14% 33
190.115.85.0/24 Valid Nonecovered by 190.115.84.0/23 93 14% 33
190.115.84.0/22 Valid Other IRR onlyALTDB, NTTCOM, RADB 672 100% 67
190.115.84.0/23 Valid Other IRR onlyRADB 672 100% 67
190.115.86.0/23 Valid Other IRR onlyRADB 672 100% 67
2804:6be0::/32 Valid Other IRR onlyALTDB, NTTCOM, RADB 633 100% 67
190.115.86.0/24 Valid Other IRR onlyRADB 93 14% 33
190.115.87.0/24 Valid Other IRR onlyRADB 93 14% 33

AS-SET

AS270431 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 11 are in fix.csv.

  • Route object: none2
  • Route object: RIR6
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
Route object: none190.115.84.0/24No route object for it. A route object for 190.115.84.0/23 with origin AS270431 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270431 in the RIR database for the space.93 of 673
Route object: none190.115.85.0/24No route object for it. A route object for 190.115.84.0/23 with origin AS270431 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270431 in the RIR database for the space.93 of 673
Route object: RIR190.115.84.0/22Route object only in ALTDB, NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR190.115.84.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR190.115.86.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR2804:6be0::/32Route object only in ALTDB, NTTCOM, RADB. Add it in the RIR database for the space.633 of 636
Route object: RIR190.115.86.0/24Route object only in RADB. Add it in the RIR database for the space.93 of 673
Route object: RIR190.115.87.0/24Route object only in RADB. Add it in the RIR database for the space.93 of 673

Route objects not announced

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

2804:6be0:700::/40RADBValid
2804:6be0:800::/40RADBValid
2804:6be0:900::/40RADBValid

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.