TASC-TW
Data as of 2026-11-01
BGP inherited
This organisation
| Netblocks | 4 · 24,576 IPv4 addresses |
| Record ID | 261723346 |
| Registry | APNIC |
| Customers | see who runs inside this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 5 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
IP Ranges (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 210.208.0.0 – 210.208.95.255 | SAVECOM-TW | APNIC | ASSIGNED NON-PORTABLE | ● medium |
| 210.208.16.0/20 | SAVECOM-TW | APNIC | ASSIGNED NON-PORTABLE | ● medium |
| 210.208.33.0/25 | TASC-TW | APNIC | ASSIGNED NON-PORTABLE | ● medium |
| 210.208.33.128/25 | TASC-TW | APNIC | ASSIGNED NON-PORTABLE | ● medium |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
75.0%
of checked blocks have valid RPKI ROA coverage
(3 of 4)
Possible discrepancies (1)
These blocks are registered to TASC-TW 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.
| 210.208.16.0/20 /20 | authorized for AS7656 — SaveCom International Inc. |
NIC Handles
AT1530-AP
HC190-AP
HL1056-AP
MAINT-TW-SAVECOM
TWIX-AP