Byte Virt JP

ByteVirtJP
Data as of 2026-08-30
Registry
Cluster stats
Netblocks8 · 768 IPv4 addresses
IPv6 6 prefixes (largest 2a0c:9a40:8aa1::/48)
Cluster ID233086620
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution Registry record
Shared handles clustered on 3 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works · report an issue

Footprint over time

10 weekly snapshots · JSON
8 +1 netblocks since 2026-07-05
2026-07-05 peak 8 2026-08-30

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
69.8.128.0/24 ByteVirtJP RIPE ASSIGNED PA ● low
69.8.130.0/23 ByteVirtJP RIPE ASSIGNED PA ● low
2a0c:9a40:8aa1::/48 ByteVirtJP RIPE ASSIGNED ● low
2a12:bec0:164::/48 ByteVirtJP RIPE ASSIGNED ● low
2a12:bec0:165::/48 ByteVirtJP RIPE ASSIGNED ● low
2a12:bec0:166::/48 ByteVirtJP RIPE ASSIGNED ● low
2a12:bec0:167::/48 ByteVirtJP RIPE ASSIGNED ● low
2a12:bec0:689::/48 ByteVirtJP RIPE ASSIGNED ● low

IPv6 ranges (6)

Network trust

what's this?
RPKI hygiene: C how networks compare →
50.0% of checked blocks have valid RPKI ROA coverage (4 of 8)
Possible discrepancies (1)

These blocks are registered to ByteVirtJP 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.

2a12:bec0:166::/48 /48 authorized for AS199707 — HONGKONG XING TONG HUI TECHNOLOGY CO., LIMITED

NIC Handles

BYTEVIRT-MNT DUMY-RIPE DUMY-RIPE