bgpreport

Network · data from 2026-11-12

AS28601 AS28601 - UNIVERSIDADE DO ESTADO DE SANTA CATARINA

Registry name: AS28601 - UNIVERSIDADE DO ESTADO DE SANTA CATARINA, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS28601, 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.
179.97.96.0/21 No ROA Nonecovered by 179.97.96.0/20 671 100% 68
179.97.104.0/21 No ROA Nonecovered by 179.97.96.0/20 671 100% 68
2801:bc::/36 No ROA Nonecovered by 2801:bc::/32 636 100% 68
2801:bc:1000::/36 No ROA Nonecovered by 2801:bc::/32 636 100% 68
179.97.96.0/20 No ROA Other IRR onlyRADB 671 100% 68
2801:bc::/32 No ROA Other IRR onlyRADB 635 100% 70

AS-SET

AS28601 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 12 are in fix.csv.

  • ROA: none6
  • Route object: none4
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
ROA: none179.97.96.0/21No ROA covers it. Add a ROA for AS28601, maxLength 21.671 of 673
Route object: none179.97.96.0/21No route object for it. A route object for 179.97.96.0/20 with origin AS28601 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28601 in the RIR database for the space.671 of 673
ROA: none179.97.104.0/21No ROA covers it. Add a ROA for AS28601, maxLength 21.671 of 673
Route object: none179.97.104.0/21No route object for it. A route object for 179.97.96.0/20 with origin AS28601 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28601 in the RIR database for the space.671 of 673
ROA: none2801:bc::/36No ROA covers it. Add a ROA for AS28601, maxLength 36.636 of 636
Route object: none2801:bc::/36No route object for it. A route object for 2801:bc::/32 with origin AS28601 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28601 in the RIR database for the space.636 of 636
ROA: none2801:bc:1000::/36No ROA covers it. Add a ROA for AS28601, maxLength 36.636 of 636
Route object: none2801:bc:1000::/36No route object for it. A route object for 2801:bc::/32 with origin AS28601 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28601 in the RIR database for the space.636 of 636
ROA: none179.97.96.0/20No ROA covers it. Add a ROA for AS28601, maxLength 20.671 of 673
Route object: RIR179.97.96.0/20Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none2801:bc::/32No ROA covers it. Add a ROA for AS28601, maxLength 32.635 of 636
Route object: RIR2801:bc::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

Every route object with origin AS28601 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.