bgpreport

Network · data from 2026-11-12

AS53856 NJIX - NJ IX

Registry name: NJIX - NJ IX, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS53856, 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.
91.223.133.0/24 No ROA RIR databaseRIPE 671 100% 68
23.168.192.0/24 Valid Other origin only 671 100% 67
45.224.252.0/22 Valid Other IRR onlyALTDB 671 100% 68
142.202.118.0/23 Valid Other IRR onlyALTDB 671 100% 68
23.174.112.0/24 Valid RIR databaseARIN 671 100% 68
45.170.12.0/22 Valid RIR databaseALTDB, LACNIC 671 100% 68
46.173.64.0/22 Valid RIR databaseRIPE 671 100% 68
46.173.68.0/22 Valid RIR databaseRIPE 671 100% 68
46.173.72.0/22 Valid RIR databaseRIPE 671 100% 68
46.173.76.0/22 Valid RIR databaseRIPE 671 100% 68
46.173.80.0/22 Valid RIR databaseRIPE 671 100% 68
46.173.84.0/22 Valid RIR databaseRIPE 671 100% 68
46.173.88.0/22 Valid RIR databaseRIPE 671 100% 68
46.173.92.0/22 Valid RIR databaseRIPE 671 100% 68
91.222.220.0/22 Valid RIR databaseRIPE 671 100% 68
91.242.73.0/24 Valid RIR databaseRIPE 671 100% 68
93.157.28.0/23 Valid RIR databaseRIPE 671 100% 68
94.131.64.0/22 Valid RIR databaseRIPE 671 100% 68
94.131.72.0/21 Valid RIR databaseRIPE 671 100% 68
95.164.24.0/22 Valid RIR databaseRIPE 671 100% 68
95.164.28.0/22 Valid RIR databaseRIPE 671 100% 68
95.164.78.0/23 Valid RIR databaseRIPE 671 100% 68
95.164.96.0/21 Valid RIR databaseRIPE 671 100% 68
95.164.104.0/21 Valid RIR databaseRIPE 671 100% 68
95.164.168.0/23 Valid RIR databaseRIPE 671 100% 68
95.164.240.0/22 Valid RIR databaseRIPE 671 100% 68
95.164.252.0/22 Valid RIR databaseRIPE 671 100% 68
194.145.117.0/24 Valid RIR databaseRIPE 671 100% 68

AS-SET

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

  • ROA: none1
  • Route object: none1
  • Route object: RIR2
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none91.223.133.0/24No ROA covers it. Add a ROA for AS53856, maxLength 24.671 of 673
Route object: none23.168.192.0/24Route objects for it name AS398436. Add a route object with origin AS53856 in the RIR database for the space.671 of 673
Route object: RIR45.224.252.0/22Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
Route object: RIR142.202.118.0/23Route object only in ALTDB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

45.41.12.0/22ARINInvalid: origin
45.86.16.0/22RIPEValid
94.131.0.0/21ALTDBNo ROA
94.131.128.0/18ALTDBNo ROA
94.131.224.0/21ALTDBNo ROA
94.131.232.0/21ALTDBNo ROA
95.164.70.0/24RIPEValid
2001:470:584::/48ARINValid

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.