bgpreport

Network · data from 2026-11-12

AS5772 AS5772 - Unisys Brasil Ltda.

Registry name: AS5772 - Unisys Brasil Ltda., BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS5772, 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.
189.45.248.0/21 No ROA Other origin only 647 96% 67
189.45.248.0/22 No ROA Other origin only 644 96% 67
189.45.251.0/26 No ROA None 3 0%low visibility 3
200.220.0.0/19 No ROA Other IRR onlyRADB 671 100% 66
200.220.64.0/18 No ROA Other IRR onlyRADB 671 100% 66
200.220.32.0/19 No ROA Other IRR onlyRADB 2 0%low visibility 2

AS-SET

AS5772 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 13 are in fix.csv.

  • ROA: none6
  • Route object: none3
  • Route object: RIR3
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none189.45.248.0/21No ROA covers it. Add a ROA for AS5772, maxLength 21.647 of 673
Route object: none189.45.248.0/21Route objects for it name AS198949. Add a route object with origin AS5772 in the RIR database for the space.647 of 673
ROA: none189.45.248.0/22No ROA covers it. Add a ROA for AS5772, maxLength 22.644 of 673
Route object: none189.45.248.0/22Route objects for it name AS52925. Add a route object with origin AS5772 in the RIR database for the space.644 of 673
ROA: none189.45.251.0/26No ROA covers it. Add a ROA for AS5772, maxLength 26.3 of 673
Route object: none189.45.251.0/26No route object for it. Add a route object with origin AS5772 in the RIR database for the space.3 of 673
ROA: none200.220.0.0/19No ROA covers it. Add a ROA for AS5772, maxLength 19.671 of 673
Route object: RIR200.220.0.0/19Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none200.220.64.0/18No ROA covers it. Add a ROA for AS5772, maxLength 18.671 of 673
Route object: RIR200.220.64.0/18Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none200.220.32.0/19No ROA covers it. Add a ROA for AS5772, maxLength 19.2 of 673
Route object: RIR200.220.32.0/19Route object only in RADB. Add it in the RIR database for the space.2 of 673

Route objects not announced

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

200.220.0.0/17RADBNo 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.