bgpreport

Network · data from 2026-11-12

AS29471 WebJanssen ISP ltd @ Co KG

Registry name: WebJanssen-DE WebJanssen ISP ltd & Co KG, DE · PeeringDB

3IPv4 routes 0.0% RPKI valid · 66.7% with a route object
0IPv6 routes
1RPKI invalid 1 origin · 0 maxLength
2No 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 AS29471, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS29471, 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.
195.158.54.0/24 Invalid: origin None 7 1%low visibility 7
195.140.208.0/22 No ROA RIR databaseRIPE 673 100% 66
195.225.208.0/22 No ROA RIR databaseRIPE 673 100% 66

AS-SET

AS29471's PeeringDB record names no 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 4 are in fix.csv.

  • ROA: origin1
  • ROA: none2
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: origin195.158.54.0/24ROAs covering it name AS8319, not AS29471. If AS29471 should announce it, add a ROA for AS29471.7 of 673
Route object: none195.158.54.0/24No route object for it. Add a route object with origin AS29471 in the RIR database for the space.7 of 673
ROA: none195.140.208.0/22No ROA covers it. Add a ROA for AS29471, maxLength 22.673 of 673
ROA: none195.225.208.0/22No ROA covers it. Add a ROA for AS29471, maxLength 22.673 of 673

Route objects not announced

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