{"classifier_version":"1.4.0","documentation":"https://rirtracker.com/api/","disclaimer":"This site independently analyzes publicly available Internet number-resource records. It is not affiliated with or endorsed by ARIN, the RIPE NCC, APNIC, LACNIC, AFRINIC, the Number Resource Organization (NRO), or any other Regional Internet Registry. Classifications and hold-expiration dates are evidence-based interpretations and do not constitute confirmation that a resource is available for issuance or transfer.","resource":"132.232.0.0/16","resource_type":"ipv4","page":"https://rirtracker.com/ip/132.232.0.0-132.232.255.255/","statistics_now":{"registry":"APNIC","status":"allocated (dated 1989-03-23)"},"current_holder":{"rir":"APNIC","org":null,"how":"APNIC's latest statistics and the latest transfer record"},"rdap_snapshots":[],"transfers":[{"id":55345,"date":"2017-11-14T19:00:00Z","type":"RESOURCE_TRANSFER","source_rir":"RIPE NCC","recipient_rir":"APNIC","source_org":"Legaco Network B.V","recipient_org":null,"range":"132.232.0.0/16","log":"RIPE NCC"},{"id":125586,"date":"2017-11-14T05:01:32Z","type":"RESOURCE_TRANSFER","source_rir":"RIPE NCC","recipient_rir":"APNIC","source_org":"ORG-LNB4-RIPE","recipient_org":"Tencent Cloud Computing (Beijing) Co., Ltd","range":"132.232.0.0/16","log":"APNIC"}],"events":[{"event_id":"660091685c245ed8","registry":"RIPE NCC","report_date":"2017-11-14","source":"transfers","raw_action":"TRANSFER","raw_line":null,"resource_type":"ipv4","resource":"132.232.0.0/16","start":"132.232.0.0","end":"132.232.255.255","classification":"INTER_RIR_TRANSFER_OUT","classification_label":"Inter-RIR transfer out of the RIPE NCC","confidence":"CONFIRMED","source_rir":"RIPE NCC","recipient_rir":"APNIC","source_organization":"Legaco Network B.V","recipient_organization":null,"inventory_effect":"Transferred out of RIPE NCC administration; not offered to RIPE NCC applicants","inventory_effect_code":"TRANSFER_OUT","provisional":false,"classifier_version":"1.4.0","classified_at":"2026-10-13T23:47:24+00:00","page":"https://rirtracker.com/ip/132.232.0.0-132.232.255.255/#e-660091685c245ed8","report_page":"https://rirtracker.com/ripe/reports/2017-11-14/","evidence_url":"https://rirtracker.com/api/v1/resources/ip/132.232.0.0-132.232.255.255.json","observed":"Transfer: Legaco Network B.V (RIPE NCC) to (no name) (APNIC)","same_transfer_as":"2c0c7e94b1b90045","explanation":"The RIPE NCC's transfer log records a transfer from Legaco Network B.V (RIPE NCC) to an unnamed organization (APNIC) on 2017-11-14 19:00 UTC: it left the RIPE NCC for APNIC. It is not a new allocation and is not offered to RIPE NCC applicants.","evidence":[{"type":"transfer","url":"https://ftp.ripe.net/pub/stats/ripencc/transfers/transfers_latest.json","retrieved_at":"2026-10-13T21:49:37+00:00","summary":"Transfer log: RESOURCE_TRANSFER on 2017-11-14 19:00 UTC, Legaco Network B.V (RIPE NCC) to (no name) (APNIC); resources moved: 132.232.0.0/16"},{"type":"delegated_before","url":"https://ftp.ripe.net/pub/stats/ripencc/2017/delegated-ripencc-extended-20171113.bz2","retrieved_at":"2026-10-12T21:32:12+00:00","summary":"RIPE NCC delegated statistics 2017-11-13 (produced 2017-11-13T22:59:59+00:00), before the change: assigned (dated 1989-03-23)"},{"type":"delegated_after","url":"https://ftp.ripe.net/pub/stats/ripencc/2017/delegated-ripencc-extended-20171114.bz2","retrieved_at":"2026-10-12T21:32:31+00:00","summary":"RIPE NCC delegated statistics 2017-11-14 (produced 2017-11-14T22:59:59+00:00), after the change: not listed"}]},{"event_id":"2c0c7e94b1b90045","registry":"APNIC","report_date":"2017-11-14","source":"transfers","raw_action":"TRANSFER","raw_line":null,"resource_type":"ipv4","resource":"132.232.0.0/16","start":"132.232.0.0","end":"132.232.255.255","classification":"INTER_RIR_TRANSFER_IN","classification_label":"Inter-RIR transfer into APNIC","confidence":"CONFIRMED","source_rir":"RIPE NCC","recipient_rir":"APNIC","source_organization":"ORG-LNB4-RIPE","recipient_organization":"Tencent Cloud Computing (Beijing) Co., Ltd","inventory_effect":"Transferred into APNIC administration; not a new issuance","inventory_effect_code":"TRANSFER_IN","provisional":false,"classifier_version":"1.4.0","classified_at":"2026-10-13T23:46:36+00:00","page":"https://rirtracker.com/ip/132.232.0.0-132.232.255.255/#e-2c0c7e94b1b90045","report_page":"https://rirtracker.com/apnic/reports/2017-11-14/","evidence_url":"https://rirtracker.com/api/v1/resources/ip/132.232.0.0-132.232.255.255.json","observed":"Transfer: ORG-LNB4-RIPE (RIPE NCC) to Tencent Cloud Computing (Beijing) Co., Ltd (APNIC)","same_transfer_as":"660091685c245ed8","explanation":"APNIC's transfer log records a transfer from ORG-LNB4-RIPE (RIPE NCC) to Tencent Cloud Computing (Beijing) Co., Ltd (APNIC) on 2017-11-14 05:01 UTC: it came to APNIC from the RIPE NCC. It was already issued by another registry, so this is not a new issuance.","evidence":[{"type":"transfer","url":"https://ftp.apnic.net/stats/apnic/transfers/transfers_latest.json","retrieved_at":"2026-10-13T18:17:16+00:00","summary":"Transfer log: RESOURCE_TRANSFER on 2017-11-14 05:01 UTC, ORG-LNB4-RIPE (RIPE NCC) to Tencent Cloud Computing (Beijing) Co., Ltd (APNIC); resources moved: 132.232.0.0/16"},{"type":"delegated_before","url":"https://ftp.apnic.net/stats/apnic/2017/delegated-apnic-extended-20171114.gz","retrieved_at":"2026-10-12T22:16:06+00:00","summary":"APNIC delegated statistics 2017-11-14, before the change: not listed"},{"type":"delegated_after","url":"https://ftp.apnic.net/stats/apnic/2017/delegated-apnic-extended-20171115.gz","retrieved_at":"2026-10-12T22:16:17+00:00","summary":"APNIC delegated statistics 2017-11-15, after the change: allocated (dated 1989-03-23)"}]}],"classification_history":{"660091685c245ed8":[{"raw_change_id":54555,"classification_code":"INTER_RIR_TRANSFER_OUT","confidence":"CONFIRMED","classifier_version":"1.3.0","classified_at":"2026-10-13T02:43:36+00:00","current":0,"public_explanation":"The RIPE NCC's transfer log records a transfer from Legaco Network B.V (RIPE NCC) to an unnamed organization (APNIC) on 2017-11-14 19:00 UTC: it left the RIPE NCC for APNIC. It is not a new allocation and is not offered to RIPE NCC applicants."},{"raw_change_id":54555,"classification_code":"INTER_RIR_TRANSFER_OUT","confidence":"CONFIRMED","classifier_version":"1.3.1","classified_at":"2026-10-13T08:02:32+00:00","current":0,"public_explanation":"The RIPE NCC's transfer log records a transfer from Legaco Network B.V (RIPE NCC) to an unnamed organization (APNIC) on 2017-11-14 19:00 UTC: it left the RIPE NCC for APNIC. It is not a new allocation and is not offered to RIPE NCC applicants."},{"raw_change_id":54555,"classification_code":"INTER_RIR_TRANSFER_OUT","confidence":"CONFIRMED","classifier_version":"1.3.2","classified_at":"2026-10-13T14:44:46+00:00","current":0,"public_explanation":"The RIPE NCC's transfer log records a transfer from Legaco Network B.V (RIPE NCC) to an unnamed organization (APNIC) on 2017-11-14 19:00 UTC: it left the RIPE NCC for APNIC. It is not a new allocation and is not offered to RIPE NCC applicants."},{"raw_change_id":54555,"classification_code":"INTER_RIR_TRANSFER_OUT","confidence":"CONFIRMED","classifier_version":"1.4.0","classified_at":"2026-10-13T23:47:24+00:00","current":1,"public_explanation":"The RIPE NCC's transfer log records a transfer from Legaco Network B.V (RIPE NCC) to an unnamed organization (APNIC) on 2017-11-14 19:00 UTC: it left the RIPE NCC for APNIC. It is not a new allocation and is not offered to RIPE NCC applicants."}],"2c0c7e94b1b90045":[{"raw_change_id":35030,"classification_code":"INTER_RIR_TRANSFER_IN","confidence":"CONFIRMED","classifier_version":"1.3.0","classified_at":"2026-10-13T02:35:37+00:00","current":0,"public_explanation":"APNIC's transfer log records a transfer from ORG-LNB4-RIPE (RIPE NCC) to Tencent Cloud Computing (Beijing) Co., Ltd (APNIC) on 2017-11-14 05:01 UTC: it came to APNIC from the RIPE NCC. It was already issued by another registry, so this is not a new issuance."},{"raw_change_id":35030,"classification_code":"INTER_RIR_TRANSFER_IN","confidence":"CONFIRMED","classifier_version":"1.3.1","classified_at":"2026-10-13T08:01:51+00:00","current":0,"public_explanation":"APNIC's transfer log records a transfer from ORG-LNB4-RIPE (RIPE NCC) to Tencent Cloud Computing (Beijing) Co., Ltd (APNIC) on 2017-11-14 05:01 UTC: it came to APNIC from the RIPE NCC. It was already issued by another registry, so this is not a new issuance."},{"raw_change_id":35030,"classification_code":"INTER_RIR_TRANSFER_IN","confidence":"CONFIRMED","classifier_version":"1.3.2","classified_at":"2026-10-13T14:44:01+00:00","current":0,"public_explanation":"APNIC's transfer log records a transfer from ORG-LNB4-RIPE (RIPE NCC) to Tencent Cloud Computing (Beijing) Co., Ltd (APNIC) on 2017-11-14 05:01 UTC: it came to APNIC from the RIPE NCC. It was already issued by another registry, so this is not a new issuance."},{"raw_change_id":35030,"classification_code":"INTER_RIR_TRANSFER_IN","confidence":"CONFIRMED","classifier_version":"1.4.0","classified_at":"2026-10-13T23:46:36+00:00","current":1,"public_explanation":"APNIC's transfer log records a transfer from ORG-LNB4-RIPE (RIPE NCC) to Tencent Cloud Computing (Beijing) Co., Ltd (APNIC) on 2017-11-14 05:01 UTC: it came to APNIC from the RIPE NCC. It was already issued by another registry, so this is not a new issuance."}]},"arin_statistics_now":{"status":"not listed"}}