bgpreport

Network · data from 2026-11-12

AS61572 AS61572 - CONTROLADORIA-GERAL DA UNIAO

Registry name: AS61572 - CONTROLADORIA-GERAL DA UNIAO, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS61572, 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.
138.117.134.100/30 No ROA Nonecovered by 138.117.134.0/24 2 0%low visibility 2
138.117.134.0/24 No ROA Other IRR onlyRADB 672 100% 66
138.117.132.0/23 No ROA Other IRR onlyRADB, TC 670 100% 66
2801:80:3280::/42 No ROA Other IRR onlyRADB 636 100% 67
2801:80:3200::/48 No ROA Other IRR onlyRADB 634 100% 67

AS-SET

AS61572 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 16 are in fix.csv.

  • ROA: none5
  • Route object: none1
  • Route object: RIR4
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none138.117.134.100/30No ROA covers it. Add a ROA for AS61572, maxLength 30.2 of 673
Route object: none138.117.134.100/30No route object for it. A route object for 138.117.134.0/24 with origin AS61572 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS61572 in the RIR database for the space.2 of 673
ROA: none138.117.134.0/24No ROA covers it. Add a ROA for AS61572, maxLength 24.672 of 673
Route object: RIR138.117.134.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none138.117.132.0/23No ROA covers it. Add a ROA for AS61572, maxLength 23.670 of 673
Route object: RIR138.117.132.0/23Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
ROA: none2801:80:3280::/42No ROA covers it. Add a ROA for AS61572, maxLength 42.636 of 636
Route object: RIR2801:80:3280::/42Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none2801:80:3200::/48No ROA covers it. Add a ROA for AS61572, maxLength 48.634 of 636
Route object: RIR2801:80:3200::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

138.117.132.0/22RADBNo ROA
138.117.135.0/24RADB, TCNo ROA
2801:80:3200::/40RADBNo ROA
2801:80:3200::/64RADBNo ROA
2801:80:328e::/48RADBNo ROA
2801:80:32b2::/48RADBNo 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.