TUPLENET-V6-20241223
Data as of 2026-07-26
BGP inherited
Cluster stats
| Netblocks | 2 |
| IPv6 | 2 prefixes (largest 2406:840:fea0::/48) |
| All fragments | 4 blocks across 2 clusters |
| Cluster ID | 213877900 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| 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 | |
IP Ranges (2)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 2406:840:fea0::/48 | TUPLENET-V6-20241223 | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 2406:840:fea1::/48 | TUPLENET-V6-20241223 | APNIC | ASSIGNED NON-PORTABLE | ● low |
IPv6 ranges (2)
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(2 of 2)
RPKI-inferred operator
TupleTech Corporation
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
AT1888-AP
MAINT-NBDHM-CN
WC2257-AP
WC2257-AP