bgpreport

Network · data from 2026-11-12

AS2553 FSU-AS - Florida State University

Registry name: FSU-AS - Florida State University, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS2553, 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.
144.174.96.0/22 No ROA Nonecovered by 144.174.0.0/16 20 3%low visibility 18
128.186.0.0/16 No ROA Other IRR onlyRADB 666 99% 69
144.174.0.0/16 No ROA Other IRR onlyRADB 666 99% 69
146.201.0.0/17 No ROA Other IRR onlyALTDB 666 99% 69
146.201.128.0/18 No ROA Other IRR onlyALTDB 666 99% 68
146.201.192.0/18 No ROA Other IRR onlyALTDB 666 99% 69
192.80.53.0/24 No ROA Other IRR onlyRADB 666 99% 69
2607:f5d8:20::/48 No ROA RIR databaseARIN 17 3%low visibility 18

AS-SET

AS2553 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 15 are in fix.csv.

  • ROA: none8
  • Route object: none1
  • Route object: RIR6
ChangePrefix or setDetailFull-table peers
ROA: none144.174.96.0/22No ROA covers it. Add a ROA for AS2553, maxLength 22.20 of 673
Route object: none144.174.96.0/22No route object for it. A route object for 144.174.0.0/16 with origin AS2553 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2553 in the RIR database for the space.20 of 673
ROA: none128.186.0.0/16No ROA covers it. Add a ROA for AS2553, maxLength 16.666 of 673
Route object: RIR128.186.0.0/16Route object only in RADB. Add it in the RIR database for the space.666 of 673
ROA: none144.174.0.0/16No ROA covers it. Add a ROA for AS2553, maxLength 16.666 of 673
Route object: RIR144.174.0.0/16Route object only in RADB. Add it in the RIR database for the space.666 of 673
ROA: none146.201.0.0/17No ROA covers it. Add a ROA for AS2553, maxLength 17.666 of 673
Route object: RIR146.201.0.0/17Route object only in ALTDB. Add it in the RIR database for the space.666 of 673
ROA: none146.201.128.0/18No ROA covers it. Add a ROA for AS2553, maxLength 18.666 of 673
Route object: RIR146.201.128.0/18Route object only in ALTDB. Add it in the RIR database for the space.666 of 673
ROA: none146.201.192.0/18No ROA covers it. Add a ROA for AS2553, maxLength 18.666 of 673
Route object: RIR146.201.192.0/18Route object only in ALTDB. Add it in the RIR database for the space.666 of 673
ROA: none192.80.53.0/24No ROA covers it. Add a ROA for AS2553, maxLength 24.666 of 673
Route object: RIR192.80.53.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
ROA: none2607:f5d8:20::/48No ROA covers it. Add a ROA for AS2553, maxLength 48.17 of 636

Route objects not announced

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