bgpreport

Network · data from 2026-11-12

AS5719 SUNYSB - State University of New York at Stony Brook

Registry name: SUNYSB - State University of New York at Stony Brook, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS5719, 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.
2620:101::/46 Valid None 635 100% 67
129.49.0.0/16 Valid Other IRR onlyRADB 673 100% 68
130.245.0.0/16 Valid Other IRR onlyRADB 673 100% 68
192.12.89.0/24 Valid Other IRR onlyRADB 673 100% 68
192.12.90.0/24 Valid Other IRR onlyRADB 673 100% 68
192.42.55.0/24 Valid Other IRR onlyRADB 673 100% 68
2620:10d:1000::/44 Valid Other IRR onlyRADB 635 100% 68
129.49.0.0/17 Valid Other IRR onlyRADB 40 6%low visibility 28
129.49.128.0/17 Valid Other IRR onlyRADB 40 6%low visibility 28
130.245.0.0/17 Valid Other IRR onlyRADB 40 6%low visibility 28
130.245.128.0/17 Valid Other IRR onlyRADB 40 6%low visibility 28

AS-SET

AS5719 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.

  • Route object: none1
  • Route object: RIR10
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: none2620:101::/46No route object for it. Add a route object with origin AS5719 in the RIR database for the space.635 of 636
Route object: RIR129.49.0.0/16Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR130.245.0.0/16Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR192.12.89.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR192.12.90.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR192.42.55.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR2620:10d:1000::/44Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR129.49.0.0/17Route object only in RADB. Add it in the RIR database for the space.40 of 673
Route object: RIR129.49.128.0/17Route object only in RADB. Add it in the RIR database for the space.40 of 673
Route object: RIR130.245.0.0/17Route object only in RADB. Add it in the RIR database for the space.40 of 673
Route object: RIR130.245.128.0/17Route object only in RADB. Add it in the RIR database for the space.40 of 673

Route objects not announced

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

129.49.4.0/24RADBValid
199.109.44.0/22RADBValid

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.