bgpreport

Network · data from 2026-11-12

AS19677 NJTRANSIT - NJTRANSIT

Registry name: NJTRANSIT - NJTRANSIT, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS19677, 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.
198.177.0.0/24 No ROA Nonecovered by 198.177.0.0/22 673 100% 67
198.177.1.0/24 No ROA Nonecovered by 198.177.0.0/22 673 100% 67
198.177.2.0/24 No ROA Nonecovered by 198.177.0.0/22 673 100% 67
198.177.3.0/24 No ROA Nonecovered by 198.177.0.0/22 673 100% 67
198.177.5.0/24 No ROA Nonecovered by 198.177.4.0/23 673 100% 67
50.148.174.0/24 Valid RIR databaseARIN 673 100% 67

AS-SET

AS19677 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: none5
  • Route object: none5
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none198.177.0.0/24No ROA covers it. Add a ROA for AS19677, maxLength 24.673 of 673
Route object: none198.177.0.0/24No route object for it. A route object for 198.177.0.0/22 with origin AS19677 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19677 in the RIR database for the space.673 of 673
ROA: none198.177.1.0/24No ROA covers it. Add a ROA for AS19677, maxLength 24.673 of 673
Route object: none198.177.1.0/24No route object for it. A route object for 198.177.0.0/22 with origin AS19677 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19677 in the RIR database for the space.673 of 673
ROA: none198.177.2.0/24No ROA covers it. Add a ROA for AS19677, maxLength 24.673 of 673
Route object: none198.177.2.0/24No route object for it. A route object for 198.177.0.0/22 with origin AS19677 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19677 in the RIR database for the space.673 of 673
ROA: none198.177.3.0/24No ROA covers it. Add a ROA for AS19677, maxLength 24.673 of 673
Route object: none198.177.3.0/24No route object for it. A route object for 198.177.0.0/22 with origin AS19677 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19677 in the RIR database for the space.673 of 673
ROA: none198.177.5.0/24No ROA covers it. Add a ROA for AS19677, maxLength 24.673 of 673
Route object: none198.177.5.0/24No route object for it. A route object for 198.177.4.0/23 with origin AS19677 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19677 in the RIR database for the space.673 of 673

Route objects not announced

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

198.177.0.0/22RADBNo ROA
198.177.4.0/23RADBNo ROA

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.