TIMORNET-ID
Data as of 2026-09-27
Handle
Limited data: only 2 ranges found registered
under this exact name. This may not reflect the organisation's full internet footprint — many companies'
web and cloud infrastructure is hosted under a third-party provider's own registration rather than their own.
This organisation
| Netblocks | 2 · 512 IPv4 addresses |
| IPv6 | 1 prefix (largest 2405:ee40::/32) |
| Record ID | 245620136 |
| Registry | APNIC |
| Customers | see who runs inside this network → |
Evidence & provenance ?
| Attribution | RIR handle |
| Shared handles | clustered on 3 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 |
|---|---|---|---|---|
| 103.149.178.0/23 | TIMORNET-ID | APNIC | ALLOCATED PORTABLE | ● low |
| 2405:ee40::/32 | TIMORNET-ID | APNIC | ALLOCATED PORTABLE | ● low |
IPv6 ranges (1)
| CIDR |
|---|
| 2405:ee40::/32 |
Other domains hosted in this network
what's this?Network trust
what's this?
RPKI hygiene: C
how networks compare →
50.0%
of checked blocks have valid RPKI ROA coverage
(1 of 2)
RPKI-inferred operator
PT. KUPANG INTERMEDIA
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
MNT-APJII-ID
VGLR1-AP
VGLR1-AP