bgpreport

Network · data from 2026-11-12

AS28616 AS28616 - Emp. de Informatica e Informacao do Mun. BH/SA

Registry name: AS28616 - Emp. de Informatica e Informacao do Mun. BH/SA, BR · not in PeeringDB

8IPv4 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
9No ROA 1 with no route object for this origin
3Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS28616, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS28616, 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.
201.54.208.0/24 No ROA Nonecovered by 201.54.208.0/21 17 3%low visibility 9
201.54.208.0/21 No ROA Other IRR onlyRADB 672 100% 66
201.54.216.0/24 No ROA Other IRR onlyRADB 672 100% 66
201.54.223.0/24 No ROA Other IRR onlyRADB 672 100% 66
201.54.208.0/20 No ROA Other IRR onlyRADB 668 99% 66
201.54.216.0/21 No ROA Other IRR onlyRADB 666 99% 66
2801:a0::/32 No ROA Other IRR onlyRADB 626 98% 67
201.54.220.0/24 No ROA Other IRR onlyRADB 17 3%low visibility 9
201.54.221.0/24 No ROA Other IRR onlyRADB 17 3%low visibility 9

AS-SET

AS28616 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 18 are in fix.csv.

  • ROA: none9
  • Route object: none1
  • Route object: RIR8
ChangePrefix or setDetailFull-table peers
ROA: none201.54.208.0/24No ROA covers it. Add a ROA for AS28616, maxLength 24.17 of 673
Route object: none201.54.208.0/24No route object for it. A route object for 201.54.208.0/21 with origin AS28616 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28616 in the RIR database for the space.17 of 673
ROA: none201.54.208.0/21No ROA covers it. Add a ROA for AS28616, maxLength 21.672 of 673
Route object: RIR201.54.208.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none201.54.216.0/24No ROA covers it. Add a ROA for AS28616, maxLength 24.672 of 673
Route object: RIR201.54.216.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none201.54.223.0/24No ROA covers it. Add a ROA for AS28616, maxLength 24.672 of 673
Route object: RIR201.54.223.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none201.54.208.0/20No ROA covers it. Add a ROA for AS28616, maxLength 20.668 of 673
Route object: RIR201.54.208.0/20Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none201.54.216.0/21No ROA covers it. Add a ROA for AS28616, maxLength 21.666 of 673
Route object: RIR201.54.216.0/21Route object only in RADB. Add it in the RIR database for the space.666 of 673
ROA: none2801:a0::/32No ROA covers it. Add a ROA for AS28616, maxLength 32.626 of 636
Route object: RIR2801:a0::/32Route object only in RADB. Add it in the RIR database for the space.626 of 636
ROA: none201.54.220.0/24No ROA covers it. Add a ROA for AS28616, maxLength 24.17 of 673
Route object: RIR201.54.220.0/24Route object only in RADB. Add it in the RIR database for the space.17 of 673
ROA: none201.54.221.0/24No ROA covers it. Add a ROA for AS28616, maxLength 24.17 of 673
Route object: RIR201.54.221.0/24Route object only in RADB. Add it in the RIR database for the space.17 of 673

Route objects not announced

Every route object with origin AS28616 is announced.

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.