bgpreport

Network · data from 2026-11-12

AS394755 CRHSC - City of Rock Hill SC

Registry name: CRHSC - City of Rock Hill SC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS394755, 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.

216.189.94.0/24 Invalid: origin None 25 4%low visibility 19
216.189.95.0/24 Invalid: origin None 25 4%low visibility 19
64.187.106.0/24 No ROA Other origin onlycovered by 64.187.106.0/23 673 100% 67
64.187.107.0/24 No ROA Other origin onlycovered by 64.187.106.0/23 673 100% 67

AS-SET

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

  • ROA: origin2
  • ROA: none2
  • Route object: none4
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin216.189.94.0/24ROAs covering it name AS8175, not AS394755. If AS394755 should announce it, add a ROA for AS394755.25 of 673
Route object: none216.189.94.0/24No route object for it. Add a route object with origin AS394755 in the RIR database for the space.25 of 673
ROA: origin216.189.95.0/24ROAs covering it name AS8175, not AS394755. If AS394755 should announce it, add a ROA for AS394755.25 of 673
Route object: none216.189.95.0/24No route object for it. Add a route object with origin AS394755 in the RIR database for the space.25 of 673
ROA: none64.187.106.0/24No ROA covers it. Add a ROA for AS394755, maxLength 24.673 of 673
Route object: none64.187.106.0/24Route objects for it name AS12180. A route object for 64.187.106.0/23 with origin AS394755 covers it (filters allowing more-specifics accept it). Add a route object with origin AS394755 in the RIR database for the space.673 of 673
ROA: none64.187.107.0/24No ROA covers it. Add a ROA for AS394755, maxLength 24.673 of 673
Route object: none64.187.107.0/24Route objects for it name AS12182. A route object for 64.187.106.0/23 with origin AS394755 covers it (filters allowing more-specifics accept it). Add a route object with origin AS394755 in the RIR database for the space.673 of 673

Route objects not announced

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

64.187.106.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.