BKNIX

Data as of 2026-11-08
Handle
This organisation
Netblocks18
IPv6 9 prefixes (largest 2001:df5:b881:1::1/128)
Also registered under this name 44 netblocks across 7 separate records
Record ID265738692
RegistryPEERINGDB
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution RIR handle
Shared handles clustered on 1 shared RIR contact/maintainer handle
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works · report an issue

IP Ranges (18)

⬇ export CSV
CIDR Org name Registry Status Confidence
203.159.67.1/32 BKNIX PEERINGDB ASSIGNED ● high
203.159.67.2/32 BKNIX PEERINGDB ASSIGNED ● high
203.159.67.3/32 BKNIX PEERINGDB ASSIGNED ● high
203.159.68.1/32 BKNIX PEERINGDB ASSIGNED ● high
203.159.68.2/32 BKNIX PEERINGDB ASSIGNED ● high
203.159.68.3/32 BKNIX PEERINGDB ASSIGNED ● high
203.159.68.4/32 BKNIX PEERINGDB ASSIGNED ● high
203.159.68.5/32 BKNIX PEERINGDB ASSIGNED ● high
203.159.68.7/32 BKNIX PEERINGDB ASSIGNED ● high
2001:df5:b881::1/128 BKNIX PEERINGDB ASSIGNED ● high
2001:df5:b881::2/128 BKNIX PEERINGDB ASSIGNED ● high
2001:df5:b881::3/128 BKNIX PEERINGDB ASSIGNED ● high
2001:df5:b881::4/128 BKNIX PEERINGDB ASSIGNED ● high
2001:df5:b881::5/128 BKNIX PEERINGDB ASSIGNED ● high
2001:df5:b881::7/128 BKNIX PEERINGDB ASSIGNED ● high
2001:df5:b881:1::1/128 BKNIX PEERINGDB ASSIGNED ● high
2001:df5:b881:1::2/128 BKNIX PEERINGDB ASSIGNED ● high
2001:df5:b881:1::3/128 BKNIX PEERINGDB ASSIGNED ● high

IPv6 ranges (9)

Footprint over time

20 weekly snapshots · JSON
18 0 netblocks since 2026-07-05
2026-07-05 peak 18 2026-11-08

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (18 of 18)
No discrepancies found among checked blocks.

NIC Handles

AS63528