bgpreport

Network · data from 2026-11-12

AS11787 PACOURTS-AS - Supreme Court of Pennsylvania

Registry name: PACOURTS-AS - Supreme Court of Pennsylvania, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS11787, 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.8.33.0/24 No ROA Nonecovered by 198.8.32.0/21 672 100% 67
198.8.34.0/24 No ROA Nonecovered by 198.8.34.0/23 672 100% 67
198.8.35.0/24 No ROA Nonecovered by 198.8.34.0/23 672 100% 67
198.8.32.0/24 No ROA Other IRR onlyRADB 672 100% 67

AS-SET

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

  • ROA: none4
  • Route object: none3
  • Route object: RIR1
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none198.8.33.0/24No ROA covers it. Add a ROA for AS11787, maxLength 24.672 of 673
Route object: none198.8.33.0/24No route object for it. A route object for 198.8.32.0/21 with origin AS11787 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11787 in the RIR database for the space.672 of 673
ROA: none198.8.34.0/24No ROA covers it. Add a ROA for AS11787, maxLength 24.672 of 673
Route object: none198.8.34.0/24No route object for it. A route object for 198.8.34.0/23 with origin AS11787 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11787 in the RIR database for the space.672 of 673
ROA: none198.8.35.0/24No ROA covers it. Add a ROA for AS11787, maxLength 24.672 of 673
Route object: none198.8.35.0/24No route object for it. A route object for 198.8.34.0/23 with origin AS11787 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11787 in the RIR database for the space.672 of 673
ROA: none198.8.32.0/24No ROA covers it. Add a ROA for AS11787, maxLength 24.672 of 673
Route object: RIR198.8.32.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

198.8.32.0/20NTTCOMNo ROA
198.8.32.0/21NTTCOMNo ROA
198.8.34.0/23RADBNo ROA
198.8.40.0/22NTTCOMNo ROA
198.8.45.0/24NTTCOMNo ROA
198.8.46.0/23NTTCOMNo ROA
198.8.48.0/21NTTCOMNo ROA
198.8.56.0/24NTTCOMNo 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.