bgpreport

Network · data from 2026-11-12

AS270289 AS270289 - D F G LEITE - ME

Registry name: AS270289 - D F G LEITE - ME, BR · not in PeeringDB

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

Announced routes

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

2804:69c0::/34 No ROA Nonecovered by 2804:69c0::/32 635 100% 67
2804:69c0:4000::/34 No ROA Nonecovered by 2804:69c0::/32 635 100% 67
2804:69c0:4000::/40 No ROA Nonecovered by 2804:69c0::/32 635 100% 69
2804:69c0:8000::/34 No ROA Nonecovered by 2804:69c0::/32 635 100% 67
2804:69c0:c000::/34 No ROA Nonecovered by 2804:69c0::/32 635 100% 67
200.124.80.0/23 No ROA Other IRR onlyRADB 671 100% 66
200.124.83.0/24 No ROA Other IRR onlyRADB 670 100% 67
200.124.82.0/24 No ROA Other IRR onlyRADB 669 99% 66
2804:69c0::/32 No ROA Other IRR onlyRADB, TC 634 100% 67

AS-SET

AS270289 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 22 are in fix.csv.

  • ROA: none9
  • Route object: none5
  • Route object: RIR4
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none2804:69c0::/34No ROA covers it. Add a ROA for AS270289, maxLength 34.635 of 636
Route object: none2804:69c0::/34No route object for it. A route object for 2804:69c0::/32 with origin AS270289 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270289 in the RIR database for the space.635 of 636
ROA: none2804:69c0:4000::/34No ROA covers it. Add a ROA for AS270289, maxLength 34.635 of 636
Route object: none2804:69c0:4000::/34No route object for it. A route object for 2804:69c0::/32 with origin AS270289 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270289 in the RIR database for the space.635 of 636
ROA: none2804:69c0:4000::/40No ROA covers it. Add a ROA for AS270289, maxLength 40.635 of 636
Route object: none2804:69c0:4000::/40No route object for it. A route object for 2804:69c0::/32 with origin AS270289 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270289 in the RIR database for the space.635 of 636
ROA: none2804:69c0:8000::/34No ROA covers it. Add a ROA for AS270289, maxLength 34.635 of 636
Route object: none2804:69c0:8000::/34No route object for it. A route object for 2804:69c0::/32 with origin AS270289 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270289 in the RIR database for the space.635 of 636
ROA: none2804:69c0:c000::/34No ROA covers it. Add a ROA for AS270289, maxLength 34.635 of 636
Route object: none2804:69c0:c000::/34No route object for it. A route object for 2804:69c0::/32 with origin AS270289 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270289 in the RIR database for the space.635 of 636
ROA: none200.124.80.0/23No ROA covers it. Add a ROA for AS270289, maxLength 23.671 of 673
Route object: RIR200.124.80.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none200.124.83.0/24No ROA covers it. Add a ROA for AS270289, maxLength 24.670 of 673
Route object: RIR200.124.83.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none200.124.82.0/24No ROA covers it. Add a ROA for AS270289, maxLength 24.669 of 673
Route object: RIR200.124.82.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none2804:69c0::/32No ROA covers it. Add a ROA for AS270289, maxLength 32.634 of 636
Route object: RIR2804:69c0::/32Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

200.124.80.0/22RADB, TCNo ROA
200.124.80.0/24RADBNo ROA
200.124.81.0/24RADBNo ROA
200.124.82.0/23RADBNo 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.