bgpreport

Network · data from 2026-11-12

AS20337 SUNYPOLY-ASN - SUNY Institute of Technology

Registry name: SUNYPOLY-ASN - SUNY Institute of Technology, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS20337, 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.

207.10.56.0/24 Invalid: origin None 2 0%low visibility 2
149.15.0.0/16 No ROA Other IRR onlyRADB 672 100% 67
150.156.0.0/16 No ROA Other IRR onlyRADB 672 100% 67
192.52.220.0/24 No ROA Other IRR onlyRADB 672 100% 67
204.29.215.0/24 No ROA Other IRR onlyRADB 672 100% 67

AS-SET

AS20337 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: origin1
  • ROA: none4
  • Route object: none1
  • Route object: RIR4
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: origin207.10.56.0/24ROAs covering it name AS7029, not AS20337. If AS20337 should announce it, add a ROA for AS20337.2 of 673
Route object: none207.10.56.0/24No route object for it. Add a route object with origin AS20337 in the RIR database for the space.2 of 673
ROA: none149.15.0.0/16No ROA covers it. Add a ROA for AS20337, maxLength 16.672 of 673
Route object: RIR149.15.0.0/16Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none150.156.0.0/16No ROA covers it. Add a ROA for AS20337, maxLength 16.672 of 673
Route object: RIR150.156.0.0/16Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none192.52.220.0/24No ROA covers it. Add a ROA for AS20337, maxLength 24.672 of 673
Route object: RIR192.52.220.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none204.29.215.0/24No ROA covers it. Add a ROA for AS20337, maxLength 24.672 of 673
Route object: RIR204.29.215.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

205.232.28.0/23ALTDB, RADBValid
205.232.28.0/24ALTDB, RADBValid
205.232.29.0/24ALTDB, RADBValid

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.