bgpreport

Network · data from 2026-11-12

AS3847 NYC-REGIONAL - ENV

Registry name: NYC-REGIONAL - ENV, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS3847, 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.
63.236.68.0/24 No ROA None 672 100% 67
65.117.166.0/24 No ROA None 672 100% 67
199.165.204.0/24 No ROA RIR databaseARIN 672 100% 67
199.165.205.0/24 No ROA RIR databaseARIN 672 100% 67
216.71.117.0/24 No ROA RIR databaseARIN 671 100% 67

AS-SET

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

  • ROA: none5
  • Route object: none2
ChangePrefix or setDetailFull-table peers
ROA: none63.236.68.0/24No ROA covers it. Add a ROA for AS3847, maxLength 24.672 of 673
Route object: none63.236.68.0/24No route object for it. Add a route object with origin AS3847 in the RIR database for the space.672 of 673
ROA: none65.117.166.0/24No ROA covers it. Add a ROA for AS3847, maxLength 24.672 of 673
Route object: none65.117.166.0/24No route object for it. Add a route object with origin AS3847 in the RIR database for the space.672 of 673
ROA: none199.165.204.0/24No ROA covers it. Add a ROA for AS3847, maxLength 24.672 of 673
ROA: none199.165.205.0/24No ROA covers it. Add a ROA for AS3847, maxLength 24.672 of 673
ROA: none216.71.117.0/24No ROA covers it. Add a ROA for AS3847, maxLength 24.671 of 673

Route objects not announced

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