bgpreport

Network · data from 2026-11-12

AS22252 AS22252 - The City of New York

Registry name: AS22252 - The City of New York, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS22252, 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.
161.185.7.0/24 Valid Nonecovered by 161.185.0.0/17 673 100% 67
161.185.152.0/23 Valid Nonecovered by 161.185.0.0/16 673 100% 67
161.185.208.0/23 Valid Nonecovered by 161.185.0.0/16 673 100% 67
161.185.224.0/23 Valid Nonecovered by 161.185.0.0/16 673 100% 67
157.188.0.0/16 Valid Other IRR onlyRADB 673 100% 67
157.188.0.0/18 Valid Other IRR onlyRADB 673 100% 67
157.188.12.0/23 Valid Other IRR onlyRADB 673 100% 67
157.188.128.0/19 Valid Other IRR onlyRADB 673 100% 67
157.188.192.0/20 Valid Other IRR onlyRADB 673 100% 67
157.188.208.0/20 Valid Other IRR onlyRADB 673 100% 67
161.185.0.0/16 Valid Other IRR onlyRADB 673 100% 67
161.185.0.0/17 Valid Other IRR onlyRADB 673 100% 67
161.185.4.0/24 Valid Other IRR onlyRADB 673 100% 67
161.185.30.0/23 Valid Other IRR onlyRADB 673 100% 67
161.185.32.0/20 Valid Other IRR onlyRADB 673 100% 67
161.185.150.0/23 Valid Other IRR onlyRADB 673 100% 67
161.185.151.0/24 Valid Other IRR onlyRADB 673 100% 67
161.185.160.0/24 Valid Other IRR onlyRADB 673 100% 67
161.185.161.0/24 Valid Other IRR onlyRADB 673 100% 67
161.185.182.0/24 Valid Other IRR onlyRADB 673 100% 67
167.153.0.0/16 Valid Other IRR onlyRADB 673 100% 67
167.153.0.0/17 Valid Other IRR onlyRADB 673 100% 67
167.153.128.0/17 Valid Other IRR onlyRADB 673 100% 67

AS-SET

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

  • Route object: none4
  • Route object: RIR19
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
Route object: none161.185.7.0/24No route object for it. A route object for 161.185.0.0/17 with origin AS22252 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22252 in the RIR database for the space.673 of 673
Route object: none161.185.152.0/23No route object for it. A route object for 161.185.0.0/16 with origin AS22252 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22252 in the RIR database for the space.673 of 673
Route object: none161.185.208.0/23No route object for it. A route object for 161.185.0.0/16 with origin AS22252 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22252 in the RIR database for the space.673 of 673
Route object: none161.185.224.0/23No route object for it. A route object for 161.185.0.0/16 with origin AS22252 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22252 in the RIR database for the space.673 of 673
Route object: RIR157.188.0.0/16Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR157.188.0.0/18Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR157.188.12.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR157.188.128.0/19Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR157.188.192.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR157.188.208.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR161.185.0.0/16Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR161.185.0.0/17Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR161.185.4.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR161.185.30.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR161.185.32.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR161.185.150.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR161.185.151.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR161.185.160.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR161.185.161.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR161.185.182.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR167.153.0.0/16Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR167.153.0.0/17Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR167.153.128.0/17Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

157.188.252.0/22RADBValid
167.153.150.0/24RADBValid
167.153.193.0/24ARINValid
167.153.196.0/24ARINValid
167.153.198.0/24ARINValid
2001:19a0::/32RADBValid

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.