bgpreport

Network · data from 2026-11-12

AS11872 SYRACUSE-UNIVERSITY - Syracuse University

Registry name: SYRACUSE-UNIVERSITY - Syracuse University, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS11872, 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.
149.119.6.0/24 No ROA Other IRR onlyRADB 671 100% 68
149.119.7.0/24 No ROA Other IRR onlyRADB 671 100% 68
2620:4e::/48 No ROA RIR databaseARIN, RADB 635 100% 68
128.230.60.0/24 Valid Nonecovered by 128.230.32.0/19 672 100% 67
128.230.0.0/18 Valid Other IRR onlyRADB 31 5%low visibility 25
128.230.64.0/18 Valid Other IRR onlyRADB 31 5%low visibility 25
128.230.128.0/18 Valid Other IRR onlyRADB 31 5%low visibility 25
128.230.192.0/18 Valid Other IRR onlyRADB 31 5%low visibility 25
128.230.0.0/16 Valid RIR databaseARIN 672 100% 67
74.80.186.0/24 Valid RIR databaseARIN 671 100% 67

AS-SET

AS11872 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 20 are in fix.csv.

  • ROA: none3
  • Route object: none1
  • Route object: RIR6
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
ROA: none149.119.6.0/24No ROA covers it. Add a ROA for AS11872, maxLength 24.671 of 673
Route object: RIR149.119.6.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none149.119.7.0/24No ROA covers it. Add a ROA for AS11872, maxLength 24.671 of 673
Route object: RIR149.119.7.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none2620:4e::/48No ROA covers it. Add a ROA for AS11872, maxLength 48.635 of 636
Route object: none128.230.60.0/24No route object for it. A route object for 128.230.32.0/19 with origin AS11872 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11872 in the RIR database for the space.672 of 673
Route object: RIR128.230.0.0/18Route object only in RADB. Add it in the RIR database for the space.31 of 673
Route object: RIR128.230.64.0/18Route object only in RADB. Add it in the RIR database for the space.31 of 673
Route object: RIR128.230.128.0/18Route object only in RADB. Add it in the RIR database for the space.31 of 673
Route object: RIR128.230.192.0/18Route object only in RADB. Add it in the RIR database for the space.31 of 673

Route objects not announced

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

128.230.0.0/17RADBValid
128.230.0.0/19RADBValid
128.230.32.0/19RADBValid
128.230.64.0/19RADBValid
128.230.96.0/19RADBValid
128.230.128.0/17RADBValid
128.230.128.0/19RADBValid
128.230.160.0/19RADBValid
128.230.192.0/19RADBValid
128.230.224.0/19RADBValid

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.