TYCONET

BGP inherited
Cluster stats
Netblocks6
All fragments 7 blocks across 2 clusters
Cluster ID212496570
RegistryAPNIC
Customersfind 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

Footprint over time

4 weekly snapshots · JSON
6 0 netblocks since 2026-07-05
2026-07-05 peak 6 2026-07-19

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
124.30.22.48 – 124.30.22.71 TYCONET APNIC ASSIGNED NON-PORTABLE ● low
124.30.117.0 – 124.30.117.59 TYCONET APNIC ASSIGNED NON-PORTABLE ● low
221.134.70.20/30 TYCONET APNIC ASSIGNED NON-PORTABLE ● low
221.134.70.24/29 TYCONET APNIC ASSIGNED NON-PORTABLE ● low
221.134.89.144/29 TYCONET APNIC ASSIGNED NON-PORTABLE ● low
221.134.89.152/30 TYCONET APNIC ASSIGNED NON-PORTABLE ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “TYCONET” — 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.
  • TYCONET-CZ via T-Mobile Czech Republic a.s. sub-allocation

Network trust

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

NIC Handles

HS51-AP HS51-AP MAINT-IN-IRINN MAINT-IN-SIFY