bgpreport

Network · data from 2026-11-12

AS40539 PROHCI - Hosting Consulting, Inc

Registry name: PROHCI - Hosting Consulting, Inc, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS40539, 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.
208.91.204.0/24 No ROA Nonecovered by 208.91.204.0/22 672 100% 67
199.88.56.0/21 No ROA Other IRR onlyRADB 672 100% 67
208.78.92.0/22 No ROA Other IRR onlyRADB 672 100% 67
208.78.92.0/24 No ROA Other IRR onlyRADB 672 100% 67
208.91.204.0/22 No ROA Other IRR onlyRADB 672 100% 67
208.91.206.0/24 No ROA Other IRR onlyRADB 672 100% 67
208.91.207.0/24 No ROA Other IRR onlyRADB 672 100% 67

AS-SET

AS40539 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 14 are in fix.csv.

  • ROA: none7
  • Route object: none1
  • Route object: RIR6
ChangePrefix or setDetailFull-table peers
ROA: none208.91.204.0/24No ROA covers it. Add a ROA for AS40539, maxLength 24.672 of 673
Route object: none208.91.204.0/24No route object for it. A route object for 208.91.204.0/22 with origin AS40539 covers it (filters allowing more-specifics accept it). Add a route object with origin AS40539 in the RIR database for the space.672 of 673
ROA: none199.88.56.0/21No ROA covers it. Add a ROA for AS40539, maxLength 21.672 of 673
Route object: RIR199.88.56.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none208.78.92.0/22No ROA covers it. Add a ROA for AS40539, maxLength 22.672 of 673
Route object: RIR208.78.92.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none208.78.92.0/24No ROA covers it. Add a ROA for AS40539, maxLength 24.672 of 673
Route object: RIR208.78.92.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none208.91.204.0/22No ROA covers it. Add a ROA for AS40539, maxLength 22.672 of 673
Route object: RIR208.91.204.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none208.91.206.0/24No ROA covers it. Add a ROA for AS40539, maxLength 24.672 of 673
Route object: RIR208.91.206.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none208.91.207.0/24No ROA covers it. Add a ROA for AS40539, maxLength 24.672 of 673
Route object: RIR208.91.207.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

Every route object with origin AS40539 is announced.

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.