bgpreport

Network · data from 2026-11-12

AS20044 AS20044 - S/A ESTADO DE MINAS

Registry name: AS20044 - S/A ESTADO DE MINAS, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS20044, 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.188.176.10/32 No ROA Nonecovered by 200.188.176.0/24 3 0%low visibility 3
200.188.176.0/30 No ROA Nonecovered by 200.188.176.0/24 2 0%low visibility 2
200.188.176.0/20 No ROA Other IRR onlyRADB 668 99% 66
200.188.177.0/24 No ROA Other IRR onlyRADB 668 99% 66
200.188.179.0/24 No ROA Other IRR onlyRADB 668 99% 66
200.188.180.0/24 No ROA Other IRR onlyRADB 668 99% 66
200.188.181.0/24 No ROA Other IRR onlyRADB 668 99% 66
200.188.182.0/24 No ROA Other IRR onlyRADB 668 99% 66
200.188.183.0/24 No ROA Other IRR onlyRADB 668 99% 66
200.188.184.0/24 No ROA Other IRR onlyRADB 668 99% 66
200.188.185.0/24 No ROA Other IRR onlyRADB 668 99% 66
200.188.186.0/24 No ROA Other IRR onlyRADB 668 99% 66
200.188.189.0/24 No ROA Other IRR onlyRADB 668 99% 66
200.188.190.0/24 No ROA Other IRR onlyRADB 668 99% 66
200.188.191.0/24 No ROA Other IRR onlyRADB 668 99% 66
200.188.178.0/24 No ROA Other IRR onlyRADB 667 99% 66
2804:564::/32 No ROA Other IRR onlyRADB 631 99% 69

AS-SET

AS20044 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 37 are in fix.csv.

  • ROA: none17
  • Route object: none2
  • Route object: RIR15
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none200.188.176.10/32No ROA covers it. Add a ROA for AS20044, maxLength 32.3 of 673
Route object: none200.188.176.10/32No route object for it. A route object for 200.188.176.0/24 with origin AS20044 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS20044 in the RIR database for the space.3 of 673
ROA: none200.188.176.0/30No ROA covers it. Add a ROA for AS20044, maxLength 30.2 of 673
Route object: none200.188.176.0/30No route object for it. A route object for 200.188.176.0/24 with origin AS20044 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS20044 in the RIR database for the space.2 of 673
ROA: none200.188.176.0/20No ROA covers it. Add a ROA for AS20044, maxLength 20.668 of 673
Route object: RIR200.188.176.0/20Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none200.188.177.0/24No ROA covers it. Add a ROA for AS20044, maxLength 24.668 of 673
Route object: RIR200.188.177.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none200.188.179.0/24No ROA covers it. Add a ROA for AS20044, maxLength 24.668 of 673
Route object: RIR200.188.179.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none200.188.180.0/24No ROA covers it. Add a ROA for AS20044, maxLength 24.668 of 673
Route object: RIR200.188.180.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none200.188.181.0/24No ROA covers it. Add a ROA for AS20044, maxLength 24.668 of 673
Route object: RIR200.188.181.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none200.188.182.0/24No ROA covers it. Add a ROA for AS20044, maxLength 24.668 of 673
Route object: RIR200.188.182.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none200.188.183.0/24No ROA covers it. Add a ROA for AS20044, maxLength 24.668 of 673
Route object: RIR200.188.183.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none200.188.184.0/24No ROA covers it. Add a ROA for AS20044, maxLength 24.668 of 673
Route object: RIR200.188.184.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none200.188.185.0/24No ROA covers it. Add a ROA for AS20044, maxLength 24.668 of 673
Route object: RIR200.188.185.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none200.188.186.0/24No ROA covers it. Add a ROA for AS20044, maxLength 24.668 of 673
Route object: RIR200.188.186.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none200.188.189.0/24No ROA covers it. Add a ROA for AS20044, maxLength 24.668 of 673
Route object: RIR200.188.189.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none200.188.190.0/24No ROA covers it. Add a ROA for AS20044, maxLength 24.668 of 673
Route object: RIR200.188.190.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none200.188.191.0/24No ROA covers it. Add a ROA for AS20044, maxLength 24.668 of 673
Route object: RIR200.188.191.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none200.188.178.0/24No ROA covers it. Add a ROA for AS20044, maxLength 24.667 of 673
Route object: RIR200.188.178.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none2804:564::/32No ROA covers it. Add a ROA for AS20044, maxLength 32.631 of 636
Route object: RIR2804:564::/32Route object only in RADB. Add it in the RIR database for the space.631 of 636

Route objects not announced

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

200.188.176.0/24RADBNo ROA
200.188.187.0/24RADBNo ROA
200.188.188.0/24RADBNo 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.