CLASSIC

Classic Communications
Data as of 2026-08-23
GLEIF verified
LEI
54930010FN7RJVZJYR27
Registered name
CLASSIC
Jurisdiction
Ultimate parent
No parent on file in GLEIF
Cluster stats
Netblocks6 · 460 IPv4 addresses
IPv6 1 prefix (largest 2a00:2381:cab4::/56)
Registered in United States (2) · Hong Kong (1) · KW (1) · Poland (1)
All fragments 165 blocks across 52 clusters
Cluster ID227000952
RegistryAPNIC
Owner jurisdictionLU
Customersfind customers using this network →
Evidence & provenance ?
Attribution GLEIF legal-entity match
Legal identityLEI 54930010FN7RJVZJYR27
Shared handles clustered on 16 shared RIR contact/maintainer handles
Registry names 5 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works · report an issue

Footprint over time

7 weekly snapshots · JSON
6 -442 netblocks since 2026-07-05
2026-07-05 peak 448 2026-08-23

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
205.201.64.0/24 Classic Communications ARIN ASSIGNMENT ● high
207.254.224.0/25 Classic Communications ARIN ASSIGNMENT ● high
61.239.252.112/30 CLASSIC APNIC ASSIGNED NON-PORTABLE ● low
85.128.119.56/29 CLASSIC RIPE ASSIGNED PA ● low
195.39.140.64/26 CLASSIC-NET RIPE ASSIGNED PA ● low
2a00:2381:cab4::/56 CLASSIC-ENTERPRISES RIPE ASSIGNED ● low

IPv6 ranges (1)

Network trust

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

These blocks are registered to Classic Communications 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:2381:cab4::/56 /56 authorized for AS2856 — British Telecommunications Limited

NIC Handles

ABUSE6997-ARIN AC2009-AP AUIO-ARIN BTNET-MNT C00735163 C00928742 CEBRI CH134-AP CH134-AP DUMY-RIPE DUMY-RIPE MAINT-HK-CTI +4 more