UCL-BD

Data as of 2026-07-26
Handle
Cluster stats
Netblocks6
IPv6 6 prefixes (largest 2405:9a40:1::/48)
Cluster ID213909177
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution RIR handle
Shared handles clustered on 4 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

5 weekly snapshots · JSON
6 0 netblocks since 2026-07-05
2026-07-05 peak 6 2026-07-26

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
2405:9a40::/48 UCL-BD APNIC ALLOCATED NON-PORTABLE ● low
2405:9a40:1::/48 UCL-BD APNIC ALLOCATED NON-PORTABLE ● low
2405:9a40:2::/48 UCL-BD APNIC ALLOCATED NON-PORTABLE ● low
2405:9a40:3::/48 UCL-BD APNIC ALLOCATED NON-PORTABLE ● low
2405:9a40:4::/48 UCL-BD APNIC ALLOCATED NON-PORTABLE ● low
2405:9a40:5::/48 UCL-BD APNIC ALLOCATED NON-PORTABLE ● low

IPv6 ranges (6)

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (6 of 6)
RPKI-inferred operator Unified Core Limited
Nearly all of this network's RPKI-covered space is cryptographically authorized for this single operator — the registered netname is likely one of its internal infrastructure labels.
No discrepancies found among checked blocks.

NIC Handles

AU227-AP MAINT-UNIFIED-BD UCL2-AP UCL2-AP