VEE TIME CORP.
VEETIME-TW
Cluster stats
| Netblocks | 20 |
| All fragments | 24 blocks across 2 clusters |
| Cluster ID | 194557818 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 6 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (20)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 121.254.64.0/19 | VEETIME-TW | APNIC | ALLOCATED NON-PORTABLE | ● low |
| 121.254.64.0/18 | VEETIME-TW | APNIC | ALLOCATED PORTABLE | ● low |
| 121.254.96.0/19 | VEETIME-TW | APNIC | ALLOCATED NON-PORTABLE | ● low |
| 121.254.112.0/20 | VEETIME-TW | APNIC | ALLOCATED NON-PORTABLE | ● low |
| 203.217.96.0/20 | VEETIME-TW | APNIC | ALLOCATED NON-PORTABLE | ● low |
| 203.217.96.0/19 | VEETIME-TW | APNIC | ALLOCATED PORTABLE | ● low |
| 203.217.112.0/20 | VEETIME-TW | APNIC | ALLOCATED NON-PORTABLE | ● low |
| 203.222.0.0/20 | VEETIME-TW | APNIC | ALLOCATED NON-PORTABLE | ● low |
| 203.222.0.0/19 | VEETIME-TW | APNIC | ALLOCATED PORTABLE | ● low |
| 203.222.1.0/24 | VEETIME-TW | APNIC | ALLOCATED NON-PORTABLE | ● low |
| 203.222.16.0/20 | VEETIME-TW | APNIC | ALLOCATED NON-PORTABLE | ● low |
| 210.209.128.0/20 | VEETIME-TW | APNIC | ALLOCATED NON-PORTABLE | ● low |
| 210.209.128.0/17 | VEETIME-TW | APNIC | ALLOCATED PORTABLE | ● low |
| 210.209.144.0/20 | VEETIME-TW | APNIC | ALLOCATED NON-PORTABLE | ● low |
| 210.209.160.0/20 | VEETIME-TW | APNIC | ALLOCATED NON-PORTABLE | ● low |
| 210.209.176.0/20 | VEETIME-TW | APNIC | ALLOCATED NON-PORTABLE | ● low |
| 210.209.192.0/20 | VEETIME-TW | APNIC | ALLOCATED NON-PORTABLE | ● low |
| 210.209.208.0/20 | VEETIME-TW | APNIC | ALLOCATED NON-PORTABLE | ● low |
| 210.209.224.0/20 | VEETIME-TW | APNIC | ALLOCATED NON-PORTABLE | ● low |
| 210.209.240.0/20 | VEETIME-TW | APNIC | ALLOCATED NON-PORTABLE | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(20 of 20)
Possible discrepancies (7)
These blocks are registered to VEETIME-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.209.128.0/17 /17 | authorized for AS4780 — Digital United Inc. |
| 121.254.64.0/18 /18 | authorized for AS4780 — Digital United Inc. |
| 121.254.64.0/19 /19 | authorized for AS4780 — Digital United Inc. |
| 203.217.96.0/19 /19 | authorized for AS4780 — Digital United Inc. |
| 203.222.0.0/19 /19 | authorized for AS4780 — Digital United Inc. |
| 203.222.0.0/20 /20 | authorized for AS4780 — Digital United Inc. |
| 203.222.16.0/20 /20 | authorized for AS4780 — Digital United Inc. |
NIC Handles
AT939-AP
FC634-AP
FC634-AP
MAINT-TW-TWNIC
VTCA1-AP
VTCA1-AP