{"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":"109.244.0.0/16","resource_type":"ipv4","page":"https://rirtracker.com/ip/109.244.0.0-109.244.255.255/","statistics_now":{"registry":"APNIC","status":"allocated (dated 2009-11-18)"},"current_holder":{"rir":"APNIC","org":null,"how":"APNIC's latest statistics and the latest transfer record"},"rdap_snapshots":[],"transfers":[{"id":54220,"date":"2017-08-03T19:00:00Z","type":"RESOURCE_TRANSFER","source_rir":"RIPE NCC","recipient_rir":"APNIC","source_org":"JSC Digital Network","recipient_org":null,"range":"109.244.0.0/16","log":"RIPE NCC"},{"id":125487,"date":"2017-08-03T04:40:55Z","type":"RESOURCE_TRANSFER","source_rir":"RIPE NCC","recipient_rir":"APNIC","source_org":"ru-dinet","recipient_org":"Tencent Cloud Computing (Beijing) Co., Ltd","range":"109.244.0.0/16","log":"APNIC"},{"id":48057,"date":"2015-05-15T19:00:00Z","type":"RESOURCE_TRANSFER","source_rir":"RIPE NCC","recipient_rir":"RIPE NCC","source_org":"Complex Prime LLC","recipient_org":"Digital Networks CJSC","range":"109.244.0.0/16","log":"RIPE NCC"}],"events":[{"event_id":"5442c34657f96f07","registry":"RIPE NCC","report_date":"2017-08-03","source":"transfers","raw_action":"TRANSFER","raw_line":null,"resource_type":"ipv4","resource":"109.244.0.0/16","start":"109.244.0.0","end":"109.244.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":"JSC Digital Network","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:21+00:00","page":"https://rirtracker.com/ip/109.244.0.0-109.244.255.255/#e-5442c34657f96f07","report_page":"https://rirtracker.com/ripe/reports/2017-08-03/","evidence_url":"https://rirtracker.com/api/v1/resources/ip/109.244.0.0-109.244.255.255.json","observed":"Transfer: JSC Digital Network (RIPE NCC) to (no name) (APNIC)","same_transfer_as":"1423e61cbe4f8e58","explanation":"The RIPE NCC's transfer log records a transfer from JSC Digital Network (RIPE NCC) to an unnamed organization (APNIC) on 2017-08-03 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-08-03 19:00 UTC, JSC Digital Network (RIPE NCC) to (no name) (APNIC); resources moved: 109.244.0.0/16"},{"type":"delegated_before","url":"https://ftp.ripe.net/pub/stats/ripencc/2017/delegated-ripencc-extended-20170802.bz2","retrieved_at":"2026-10-12T21:25:22+00:00","summary":"RIPE NCC delegated statistics 2017-08-02 (produced 2017-08-02T21:59:59+00:00), before the change: allocated (dated 2009-11-18)"},{"type":"delegated_after","url":"https://ftp.ripe.net/pub/stats/ripencc/2017/delegated-ripencc-extended-20170803.bz2","retrieved_at":"2026-10-12T21:25:25+00:00","summary":"RIPE NCC delegated statistics 2017-08-03 (produced 2017-08-03T21:59:59+00:00), after the change: not listed"}]},{"event_id":"1423e61cbe4f8e58","registry":"APNIC","report_date":"2017-08-03","source":"transfers","raw_action":"TRANSFER","raw_line":null,"resource_type":"ipv4","resource":"109.244.0.0/16","start":"109.244.0.0","end":"109.244.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":"ru-dinet","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:35+00:00","page":"https://rirtracker.com/ip/109.244.0.0-109.244.255.255/#e-1423e61cbe4f8e58","report_page":"https://rirtracker.com/apnic/reports/2017-08-03/","evidence_url":"https://rirtracker.com/api/v1/resources/ip/109.244.0.0-109.244.255.255.json","observed":"Transfer: ru-dinet (RIPE NCC) to Tencent Cloud Computing (Beijing) Co., Ltd (APNIC)","same_transfer_as":"5442c34657f96f07","explanation":"APNIC's transfer log records a transfer from ru-dinet (RIPE NCC) to Tencent Cloud Computing (Beijing) Co., Ltd (APNIC) on 2017-08-03 04:40 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-08-03 04:40 UTC, ru-dinet (RIPE NCC) to Tencent Cloud Computing (Beijing) Co., Ltd (APNIC); resources moved: 94.191.0.0/17, 109.244.0.0/16, 188.131.128.0/17"},{"type":"delegated_before","url":"https://ftp.apnic.net/stats/apnic/2017/delegated-apnic-extended-20170803.gz","retrieved_at":"2026-10-12T22:09:15+00:00","summary":"APNIC delegated statistics 2017-08-03, before the change: not listed"},{"type":"delegated_after","url":"https://ftp.apnic.net/stats/apnic/2017/delegated-apnic-extended-20170804.gz","retrieved_at":"2026-10-12T22:09:19+00:00","summary":"APNIC delegated statistics 2017-08-04, after the change: allocated (dated 2009-11-18)"}]},{"event_id":"96216301a4b65fd2","registry":"RIPE NCC","report_date":"2015-05-15","source":"transfers","raw_action":"TRANSFER","raw_line":null,"resource_type":"ipv4","resource":"109.244.0.0/16","start":"109.244.0.0","end":"109.244.255.255","classification":"INTRA_RIR_TRANSFER","classification_label":"Intra-RIPE NCC transfer","confidence":"CONFIRMED","source_rir":"RIPE NCC","recipient_rir":"RIPE NCC","source_organization":"Complex Prime LLC","recipient_organization":"Digital Networks CJSC","inventory_effect":"No effect on RIPE NCC applicant inventory","inventory_effect_code":"NO_EFFECT","provisional":false,"classifier_version":"1.4.0","classified_at":"2026-10-13T23:47:03+00:00","page":"https://rirtracker.com/ip/109.244.0.0-109.244.255.255/#e-96216301a4b65fd2","report_page":"https://rirtracker.com/ripe/reports/2015-05-15/","evidence_url":"https://rirtracker.com/api/v1/resources/ip/109.244.0.0-109.244.255.255.json","observed":"Transfer: Complex Prime LLC (RIPE NCC) to Digital Networks CJSC (RIPE NCC)","explanation":"The RIPE NCC's transfer log records a transfer from Complex Prime LLC (RIPE NCC) to Digital Networks CJSC (RIPE NCC) on 2015-05-15 19:00 UTC. The registration changed hands; it is not a new allocation from the RIPE NCC.","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 2015-05-15 19:00 UTC, Complex Prime LLC (RIPE NCC) to Digital Networks CJSC (RIPE NCC); resources moved: 109.244.0.0/16"},{"type":"delegated_before","url":"https://ftp.ripe.net/pub/stats/ripencc/2015/delegated-ripencc-extended-20150514.bz2","retrieved_at":"2026-10-12T20:32:48+00:00","summary":"RIPE NCC delegated statistics 2015-05-14 (produced 2015-05-14T21:59:59+00:00), before the change: allocated (dated 2009-11-18)"},{"type":"delegated_after","url":"https://ftp.ripe.net/pub/stats/ripencc/2015/delegated-ripencc-extended-20150515.bz2","retrieved_at":"2026-10-12T20:32:51+00:00","summary":"RIPE NCC delegated statistics 2015-05-15 (produced 2015-05-15T21:59:59+00:00), after the change: allocated (dated 2009-11-18)"}]}],"classification_history":{"5442c34657f96f07":[{"raw_change_id":53393,"classification_code":"INTER_RIR_TRANSFER_OUT","confidence":"CONFIRMED","classifier_version":"1.3.0","classified_at":"2026-10-13T02:43:05+00:00","current":0,"public_explanation":"The RIPE NCC's transfer log records a transfer from JSC Digital Network (RIPE NCC) to an unnamed organization (APNIC) on 2017-08-03 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":53393,"classification_code":"INTER_RIR_TRANSFER_OUT","confidence":"CONFIRMED","classifier_version":"1.3.1","classified_at":"2026-10-13T08:02:29+00:00","current":0,"public_explanation":"The RIPE NCC's transfer log records a transfer from JSC Digital Network (RIPE NCC) to an unnamed organization (APNIC) on 2017-08-03 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":53393,"classification_code":"INTER_RIR_TRANSFER_OUT","confidence":"CONFIRMED","classifier_version":"1.3.2","classified_at":"2026-10-13T14:44:43+00:00","current":0,"public_explanation":"The RIPE NCC's transfer log records a transfer from JSC Digital Network (RIPE NCC) to an unnamed organization (APNIC) on 2017-08-03 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":53393,"classification_code":"INTER_RIR_TRANSFER_OUT","confidence":"CONFIRMED","classifier_version":"1.4.0","classified_at":"2026-10-13T23:47:21+00:00","current":1,"public_explanation":"The RIPE NCC's transfer log records a transfer from JSC Digital Network (RIPE NCC) to an unnamed organization (APNIC) on 2017-08-03 19:00 UTC: it left the RIPE NCC for APNIC. It is not a new allocation and is not offered to RIPE NCC applicants."}],"1423e61cbe4f8e58":[{"raw_change_id":34833,"classification_code":"INTER_RIR_TRANSFER_IN","confidence":"CONFIRMED","classifier_version":"1.3.0","classified_at":"2026-10-13T02:35:31+00:00","current":0,"public_explanation":"APNIC's transfer log records a transfer from ru-dinet (RIPE NCC) to Tencent Cloud Computing (Beijing) Co., Ltd (APNIC) on 2017-08-03 04:40 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":34833,"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 ru-dinet (RIPE NCC) to Tencent Cloud Computing (Beijing) Co., Ltd (APNIC) on 2017-08-03 04:40 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":34833,"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 ru-dinet (RIPE NCC) to Tencent Cloud Computing (Beijing) Co., Ltd (APNIC) on 2017-08-03 04:40 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":34833,"classification_code":"INTER_RIR_TRANSFER_IN","confidence":"CONFIRMED","classifier_version":"1.4.0","classified_at":"2026-10-13T23:46:35+00:00","current":1,"public_explanation":"APNIC's transfer log records a transfer from ru-dinet (RIPE NCC) to Tencent Cloud Computing (Beijing) Co., Ltd (APNIC) on 2017-08-03 04:40 UTC: it came to APNIC from the RIPE NCC. It was already issued by another registry, so this is not a new issuance."}],"96216301a4b65fd2":[{"raw_change_id":47013,"classification_code":"INTRA_RIR_TRANSFER","confidence":"CONFIRMED","classifier_version":"1.3.0","classified_at":"2026-10-13T02:40:35+00:00","current":0,"public_explanation":"The RIPE NCC's transfer log records a transfer from Complex Prime LLC (RIPE NCC) to Digital Networks CJSC (RIPE NCC) on 2015-05-15 19:00 UTC. The registration changed hands; it is not a new allocation from the RIPE NCC."},{"raw_change_id":47013,"classification_code":"INTRA_RIR_TRANSFER","confidence":"CONFIRMED","classifier_version":"1.3.1","classified_at":"2026-10-13T08:02:14+00:00","current":0,"public_explanation":"The RIPE NCC's transfer log records a transfer from Complex Prime LLC (RIPE NCC) to Digital Networks CJSC (RIPE NCC) on 2015-05-15 19:00 UTC. The registration changed hands; it is not a new allocation from the RIPE NCC."},{"raw_change_id":47013,"classification_code":"INTRA_RIR_TRANSFER","confidence":"CONFIRMED","classifier_version":"1.3.2","classified_at":"2026-10-13T14:44:27+00:00","current":0,"public_explanation":"The RIPE NCC's transfer log records a transfer from Complex Prime LLC (RIPE NCC) to Digital Networks CJSC (RIPE NCC) on 2015-05-15 19:00 UTC. The registration changed hands; it is not a new allocation from the RIPE NCC."},{"raw_change_id":47013,"classification_code":"INTRA_RIR_TRANSFER","confidence":"CONFIRMED","classifier_version":"1.4.0","classified_at":"2026-10-13T23:47:03+00:00","current":1,"public_explanation":"The RIPE NCC's transfer log records a transfer from Complex Prime LLC (RIPE NCC) to Digital Networks CJSC (RIPE NCC) on 2015-05-15 19:00 UTC. The registration changed hands; it is not a new allocation from the RIPE NCC."}]},"arin_statistics_now":{"status":"not listed"}}