bgpreport

Network · data from 2026-11-12

AS3755 NYSERNET3-AS - NYSERNet

Registry name: NYSERNET3-AS - NYSERNet, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS3755, 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.
137.238.240.0/20 No ROA Other IRR onlyRADB 671 100% 68
192.77.173.0/24 Valid Other IRR onlyRADB 671 100% 68
199.109.84.0/24 Valid Other IRR onlyRADB 671 100% 68
199.110.240.0/20 Valid Other IRR onlyRADB 671 100% 68
2620:f:2::/48 Valid Other IRR onlyRADB 635 100% 69
2620:f:6::/48 Valid Other IRR onlyRADB 609 96% 69

AS-SET

AS3755 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 8 are in fix.csv.

  • ROA: none1
  • Route object: RIR6
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none137.238.240.0/20No ROA covers it. Add a ROA for AS3755, maxLength 20.671 of 673
Route object: RIR137.238.240.0/20Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR192.77.173.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR199.109.84.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR199.110.240.0/20Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR2620:f:2::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2620:f:6::/48Route object only in RADB. Add it in the RIR database for the space.609 of 636

Route objects not announced

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

199.109.64.0/24RADBValid

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.