BKNIX Route Servers

Data as of 2026-11-08
BGP inherited
This organisation
Netblocks8
IPv6 4 prefixes (largest 2001:df5:b881:1::6/128)
Record ID265720783
RegistryPEERINGDB
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
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 (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
203.159.67.6/32 BKNIX Route Servers PEERINGDB ASSIGNED ● high
203.159.67.7/32 BKNIX Route Servers PEERINGDB ASSIGNED ● high
203.159.68.68/32 BKNIX Route Servers PEERINGDB ASSIGNED ● high
203.159.68.69/32 BKNIX Route Servers PEERINGDB ASSIGNED ● high
2001:df5:b881::68/128 BKNIX Route Servers PEERINGDB ASSIGNED ● high
2001:df5:b881::69/128 BKNIX Route Servers PEERINGDB ASSIGNED ● high
2001:df5:b881:1::6/128 BKNIX Route Servers PEERINGDB ASSIGNED ● high
2001:df5:b881:1::7/128 BKNIX Route Servers PEERINGDB ASSIGNED ● high

IPv6 ranges (4)

Footprint over time

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

Network trust

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

NIC Handles

AS63529