Route 256

Data as of 2026-09-13
BGP inherited
This organisation
Netblocks8 · 9,728 IPv4 addresses
IPv6 1 prefix (largest 2604:cc00::/32)
Record ID242551420
RegistryARIN
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 5 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 (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
192.111.54.0/23 Route 256 ARIN DIRECT ALLOCATION ● low
199.16.184.0/21 Route 256 ARIN DIRECT ALLOCATION ● low
199.102.68.0/22 Route 256 ARIN DIRECT ALLOCATION ● low
204.11.32.0/22 Route 256 ARIN DIRECT ALLOCATION ● low
208.64.36.0/22 Route 256 ARIN DIRECT ALLOCATION ● low
208.79.208.0/21 Route 256 ARIN DIRECT ALLOCATION ● low
208.92.216.0/21 Route 256 ARIN DIRECT ALLOCATION ● low
2604:cc00::/32 Route 256 ARIN DIRECT ALLOCATION ● low

IPv6 ranges (1)

CIDR
2604:cc00::/32

Footprint over time

6 weekly snapshots · JSON
8 0 netblocks since 2026-08-09
2026-08-09 peak 8 2026-09-13

Network trust

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

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

2604:cc00::/32 /32 authorized for AS53292 — ManagedWay
208.79.208.0/21 /21 authorized for AS53292 — ManagedWay
199.16.184.0/21 /21 authorized for AS53292 — ManagedWay
208.92.216.0/21 /21 authorized for AS53292 — ManagedWay
199.102.68.0/22 /22 authorized for AS53292 — ManagedWay
208.64.36.0/22 /22 authorized for AS53292 — ManagedWay
204.11.32.0/22 /22 authorized for AS53292 — ManagedWay
192.111.54.0/23 /23 authorized for AS53292 — ManagedWay

NIC Handles

IPADM585-ARIN IPADM585-ARIN IPADM585-ARIN IPADM585-ARIN WFRM