bgpreport

Network · data from 2026-11-12

AS204527 BJNIP bejuno GmbH

Registry name: BJNIP bejuno GmbH, DE · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS204527, 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.
210.93.220.0/24 No ROA Other IRR onlyRADB 672 100% 67
2403:8300:e01::/48 No ROA RIR databaseAPNIC, RADB 634 100% 70
2403:8300:e06::/47 No ROA RIR databaseAPNIC, RADB 634 100% 70
2403:8300:e0c::/46 No ROA RIR databaseAPNIC, RADB 634 100% 70
2a07:db01:40::/42 Valid None 631 99% 70
185.130.6.0/24 Valid Other IRR onlyRADB 668 99% 66
2a07:db01:1::/48 Valid Other IRR onlyRADB 634 100% 70
185.130.7.0/24 Valid RIR databaseRIPE 673 100% 66
2a07:db01:4::/48 Valid RIR databaseRIPE 634 100% 69

AS-SET

AS204527 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: none1
  • Route object: RIR3
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none210.93.220.0/24No ROA covers it. Add a ROA for AS204527, maxLength 24.672 of 673
Route object: RIR210.93.220.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none2403:8300:e01::/48No ROA covers it. Add a ROA for AS204527, maxLength 48.634 of 636
ROA: none2403:8300:e06::/47No ROA covers it. Add a ROA for AS204527, maxLength 47.634 of 636
ROA: none2403:8300:e0c::/46No ROA covers it. Add a ROA for AS204527, maxLength 46.634 of 636
Route object: none2a07:db01:40::/42No route object for it. Add a route object with origin AS204527 in the RIR database for the space.631 of 636
Route object: RIR185.130.6.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR2a07:db01:1::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

185.130.5.0/24RIPEValid
2403:8300:e00::/48APNICNo ROA
2403:8300:e02::/48APNICNo ROA
2403:8300:e03::/48APNICNo ROA
2403:8300:e04::/47APNICNo ROA
2403:8300:e08::/46APNICNo ROA
2a07:db01::/48RIPEValid
2a07:db01:3::/48RIPEValid

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.