YTDS

BGP inherited
Cluster stats
Netblocks8
All fragments 9 blocks across 2 clusters
Cluster ID210165943
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 18 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-19

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
116.228.131.104/29 YTDS APNIC ASSIGNED NON-PORTABLE ● high
116.228.218.56/29 YTDS APNIC ASSIGNED NON-PORTABLE ● high
116.236.245.48/29 YTDS APNIC ASSIGNED NON-PORTABLE ● high
180.166.220.248/29 YTDS APNIC ASSIGNED NON-PORTABLE ● high
180.168.185.40/29 YTDS APNIC ASSIGNED NON-PORTABLE ● high
180.168.185.64/29 YTDS APNIC ASSIGNED NON-PORTABLE ● high
180.169.3.208/29 YTDS APNIC ASSIGNED NON-PORTABLE ● high
222.68.84.76/30 YTDS APNIC ASSIGNED NON-PORTABLE ● high

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “YTDS” — often per-country or per-system registrations of the same brand, occasionally a different organisation sharing the name. Not counted in this organisation's own footprint.
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own naming convention, not a direct registration.
  • YTDS-COM via CNCGROUP IP network of ShangHai IDC sub-allocation

Network trust

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

NIC Handles

AC1591-AP HB350-AP HB350-AP HB372-AP HB372-AP HB376-AP HB376-AP HB379-AP HB379-AP HB454-AP HB454-AP HB455-AP +6 more