bgpreport

Network · data from 2026-11-12

AS200638 jh-computers-as JH-Computers GmbH

Registry name: jh-computers-as JH-Computers GmbH, DE · not in PeeringDB

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

Announced routes

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

2a13:3640:1:100::/56 Invalid: maxLength Nonecovered by 2a13:3640::/29 2 0%low visibility 1
185.26.86.0/24 Valid RIR databaseRIPE 673 100% 66
81.163.195.0/24 Valid RIR databaseRIPE 672 100% 66
2a13:3640::/29 Valid RIR databaseRIPE 633 100% 67

AS-SET

AS200638 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 2 are in fix.csv.

  • ROA: maxLength1
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: maxLength2a13:3640:1:100::/56ROA 2a13:3640::/29 AS200638 has maxLength 29; the route is a /56. Raise the maxLength, or add a ROA for 2a13:3640:1:100::/56.2 of 636
Route object: none2a13:3640:1:100::/56No route object for it. A route object for 2a13:3640::/29 with origin AS200638 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS200638 in the RIR database for the space.2 of 636

Route objects not announced

Every route object with origin AS200638 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.