bgpreport

Network · data from 2026-11-12

AS270574 RRNET PROVEDOR

Registry name: AS270574 - RRNET PROVEDOR, BR · PeeringDB

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

Announced routes

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

200.26.240.0/23 No ROA Other IRR onlyRADB 671 100% 66
200.26.240.0/24 No ROA Other IRR onlyRADB 671 100% 66
200.26.241.0/24 No ROA Other IRR onlyRADB 671 100% 66
200.26.242.0/23 No ROA Other IRR onlyRADB 665 99% 67
200.26.242.0/24 No ROA Other IRR onlyRADB 665 99% 67
200.26.243.0/24 No ROA Other IRR onlyRADB 665 99% 67
2804:6e14::/33 No ROA Other IRR onlyRADB 631 99% 67
2804:6e14::/34 No ROA Other IRR onlyRADB 631 99% 67
2804:6e14:4000::/34 No ROA Other IRR onlyRADB 631 99% 67
2804:6e14:8000::/34 No ROA Other IRR onlyRADB 631 99% 67
2804:6e14:c000::/34 No ROA Other IRR onlyRADB 631 99% 67
2804:6e14:8000::/33 No ROA Other IRR onlyRADB 630 99% 67

AS-SET

AS270574'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 26 are in fix.csv.

  • ROA: none12
  • Route object: RIR12
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none200.26.240.0/23No ROA covers it. Add a ROA for AS270574, maxLength 23.671 of 673
Route object: RIR200.26.240.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none200.26.240.0/24No ROA covers it. Add a ROA for AS270574, maxLength 24.671 of 673
Route object: RIR200.26.240.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none200.26.241.0/24No ROA covers it. Add a ROA for AS270574, maxLength 24.671 of 673
Route object: RIR200.26.241.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none200.26.242.0/23No ROA covers it. Add a ROA for AS270574, maxLength 23.665 of 673
Route object: RIR200.26.242.0/23Route object only in RADB. Add it in the RIR database for the space.665 of 673
ROA: none200.26.242.0/24No ROA covers it. Add a ROA for AS270574, maxLength 24.665 of 673
Route object: RIR200.26.242.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673
ROA: none200.26.243.0/24No ROA covers it. Add a ROA for AS270574, maxLength 24.665 of 673
Route object: RIR200.26.243.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673
ROA: none2804:6e14::/33No ROA covers it. Add a ROA for AS270574, maxLength 33.631 of 636
Route object: RIR2804:6e14::/33Route object only in RADB. Add it in the RIR database for the space.631 of 636
ROA: none2804:6e14::/34No ROA covers it. Add a ROA for AS270574, maxLength 34.631 of 636
Route object: RIR2804:6e14::/34Route object only in RADB. Add it in the RIR database for the space.631 of 636
ROA: none2804:6e14:4000::/34No ROA covers it. Add a ROA for AS270574, maxLength 34.631 of 636
Route object: RIR2804:6e14:4000::/34Route object only in RADB. Add it in the RIR database for the space.631 of 636
ROA: none2804:6e14:8000::/34No ROA covers it. Add a ROA for AS270574, maxLength 34.631 of 636
Route object: RIR2804:6e14:8000::/34Route object only in RADB. Add it in the RIR database for the space.631 of 636
ROA: none2804:6e14:c000::/34No ROA covers it. Add a ROA for AS270574, maxLength 34.631 of 636
Route object: RIR2804:6e14:c000::/34Route object only in RADB. Add it in the RIR database for the space.631 of 636
ROA: none2804:6e14:8000::/33No ROA covers it. Add a ROA for AS270574, maxLength 33.630 of 636
Route object: RIR2804:6e14:8000::/33Route object only in RADB. Add it in the RIR database for the space.630 of 636

Route objects not announced

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

200.26.240.0/22TCNo ROA
2804:6e14::/32TCNo 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.