NO BKKB Jager Sentrum AS

NO-BKKB-Jager-Sentrum-AS
Data as of 2026-09-27
Registry
This organisation
Netblocks10
IPv6 4 prefixes (largest 2a00:14d8:471b::/48)
Also registered under this name 11 netblocks across 2 separate records
Record ID245864504
RegistryRIPE
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution Registry record
Shared handles clustered on 4 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works · report an issue

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
82.134.28.220/30 NO-BKKB-Jager-Sentrum-AS RIPE ASSIGNED PA ● low
82.134.39.88/30 NO-BKKB-Jager-Sentrum-AS RIPE ASSIGNED PA ● low
82.134.42.88/29 NO-BKKB-Jager-Sentrum-AS RIPE ASSIGNED PA ● low
85.200.224.96/30 NO-BKKB-Jager-Sentrum-AS RIPE ASSIGNED PA ● low
85.200.227.188/30 NO-BKKB-Jager-Sentrum-AS RIPE ASSIGNED PA ● low
85.200.241.76/30 NO-BKKB-Jager-Sentrum-AS RIPE ASSIGNED PA ● low
2a00:14d8:1001:2af::/64 NO-BKKB-Jager-Sentrum-AS RIPE ASSIGNED ● low
2a00:14d8:1001:72a::/64 NO-BKKB-Jager-Sentrum-AS RIPE ASSIGNED ● low
2a00:14d8:471b::/48 NO-BKKB-Jager-Sentrum-AS RIPE ASSIGNED ● low
2a00:14d8:50d9::/48 NO-BKKB-Jager-Sentrum-AS RIPE ASSIGNED ● low

IPv6 ranges (4)

Footprint over time

14 weekly snapshots · JSON
10 0 netblocks since 2026-07-05
2026-07-05 peak 10 2026-09-27

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (10 of 10)
Possible discrepancies (2)

These blocks are registered to NO BKKB Jager Sentrum AS but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.

2a00:14d8:471b::/48 /48 authorized for AS8542 — Eviny Fiber AS
2a00:14d8:50d9::/48 /48 authorized for AS8542 — Eviny Fiber AS

NIC Handles

BKKB-MNT DUMY-RIPE DUMY-RIPE LYSE-MNT