{"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":"103.106.0.0/22","resource_type":"ipv4","page":"https://rirtracker.com/ip/103.106.0.0-103.106.3.255/","statistics_now":{"registry":"RIPE NCC","status":"allocated (dated 2017-12-15)"},"current_holder":{"rir":"RIPE NCC","org":"ORG-PHS8-RIPE","how":"The RIPE NCC's latest statistics and the latest transfer record"},"rdap_snapshots":[],"transfers":[{"id":129012,"date":"2023-11-29T20:29:36Z","type":"RESOURCE_TRANSFER","source_rir":"APNIC","recipient_rir":"RIPE NCC","source_org":"Parvez Mahmud","recipient_org":"ORG-PHS8-RIPE","range":"103.106.0.0/22","log":"APNIC"},{"id":100165,"date":"2023-11-29T19:00:00Z","type":"RESOURCE_TRANSFER","source_rir":"APNIC","recipient_rir":"RIPE NCC","source_org":null,"recipient_org":"WEISS HOSTING GROUP S.R.L.","range":"103.106.0.0/22","log":"RIPE NCC"}],"events":[{"event_id":"4e5808657d707db8","registry":"APNIC","report_date":"2023-11-30","source":"transfers","raw_action":"TRANSFER","raw_line":null,"resource_type":"ipv4","resource":"103.106.0.0/22","start":"103.106.0.0","end":"103.106.3.255","classification":"INTER_RIR_TRANSFER_OUT","classification_label":"Inter-RIR transfer out of APNIC","confidence":"CONFIRMED","source_rir":"APNIC","recipient_rir":"RIPE NCC","source_organization":"Parvez Mahmud","recipient_organization":"ORG-PHS8-RIPE","inventory_effect":"Transferred out of APNIC administration; not offered to APNIC applicants","inventory_effect_code":"TRANSFER_OUT","provisional":false,"classifier_version":"1.4.0","classified_at":"2026-10-13T23:46:49+00:00","page":"https://rirtracker.com/ip/103.106.0.0-103.106.3.255/#e-4e5808657d707db8","report_page":"https://rirtracker.com/apnic/reports/2023-11-30/","evidence_url":"https://rirtracker.com/api/v1/resources/ip/103.106.0.0-103.106.3.255.json","observed":"Transfer: Parvez Mahmud (APNIC) to ORG-PHS8-RIPE (RIPE NCC)","same_transfer_as":"a89a18af9be6c362","explanation":"APNIC's transfer log records a transfer from Parvez Mahmud (APNIC) to ORG-PHS8-RIPE (RIPE NCC) on 2023-11-29 20:29 UTC: it left APNIC for the RIPE NCC. It is not a new allocation and is not offered to APNIC applicants.","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 2023-11-29 20:29 UTC, Parvez Mahmud (APNIC) to ORG-PHS8-RIPE (RIPE NCC); resources moved: 103.106.0.0/22"},{"type":"delegated_before","url":"https://ftp.apnic.net/stats/apnic/2023/delegated-apnic-extended-20231130.gz","retrieved_at":"2026-10-13T00:55:13+00:00","summary":"APNIC delegated statistics 2023-11-30, before the change: allocated (dated 2017-12-15)"},{"type":"delegated_after","url":"https://ftp.apnic.net/stats/apnic/2023/delegated-apnic-extended-20231201.gz","retrieved_at":"2026-10-13T00:55:18+00:00","summary":"APNIC delegated statistics 2023-12-01, after the change: not listed"}]},{"event_id":"a89a18af9be6c362","registry":"RIPE NCC","report_date":"2023-11-29","source":"transfers","raw_action":"TRANSFER","raw_line":null,"resource_type":"ipv4","resource":"103.106.0.0/22","start":"103.106.0.0","end":"103.106.3.255","classification":"INTER_RIR_TRANSFER_IN","classification_label":"Inter-RIR transfer into the RIPE NCC","confidence":"CONFIRMED","source_rir":"APNIC","recipient_rir":"RIPE NCC","source_organization":null,"recipient_organization":"WEISS HOSTING GROUP S.R.L.","inventory_effect":"Transferred into RIPE NCC administration; not a new issuance","inventory_effect_code":"TRANSFER_IN","provisional":false,"classifier_version":"1.4.0","classified_at":"2026-10-13T23:49:46+00:00","page":"https://rirtracker.com/ip/103.106.0.0-103.106.3.255/#e-a89a18af9be6c362","report_page":"https://rirtracker.com/ripe/reports/2023-11-29/","evidence_url":"https://rirtracker.com/api/v1/resources/ip/103.106.0.0-103.106.3.255.json","observed":"Transfer: (no name) (APNIC) to WEISS HOSTING GROUP S.R.L. (RIPE NCC)","same_transfer_as":"4e5808657d707db8","explanation":"The RIPE NCC's transfer log records a transfer from an unnamed organization (APNIC) to WEISS HOSTING GROUP S.R.L. (RIPE NCC) on 2023-11-29 19:00 UTC: it came to the RIPE NCC from APNIC. It was already issued by another registry, so this is not a new issuance.","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 2023-11-29 19:00 UTC, (no name) (APNIC) to WEISS HOSTING GROUP S.R.L. (RIPE NCC); resources moved: 103.106.0.0/22"},{"type":"delegated_before","url":"https://ftp.ripe.net/pub/stats/ripencc/2023/delegated-ripencc-extended-20231128.bz2","retrieved_at":"2026-10-13T00:17:33+00:00","summary":"RIPE NCC delegated statistics 2023-11-28 (produced 2023-11-28T22:59:59+00:00), before the change: not listed"},{"type":"delegated_after","url":"https://ftp.ripe.net/pub/stats/ripencc/2023/delegated-ripencc-extended-20231129.bz2","retrieved_at":"2026-10-13T00:17:36+00:00","summary":"RIPE NCC delegated statistics 2023-11-29 (produced 2023-11-29T22:59:59+00:00), after the change: allocated (dated 2017-12-15)"}]},{"event_id":"97f7142bab8b6b28","registry":"APNIC","report_date":"2023-07-17","source":"statistics","raw_action":"ADDED","raw_line":null,"resource_type":"ipv4","resource":"103.106.0.0/22","start":"103.106.0.0","end":"103.106.3.255","classification":"RESTORED","classification_label":"Restored to the same holder","confidence":"STRONG_INFERENCE","source_rir":null,"recipient_rir":null,"source_organization":null,"recipient_organization":null,"inventory_effect":"No effect on APNIC applicant inventory","inventory_effect_code":"NO_EFFECT","provisional":false,"classifier_version":"1.4.0","classified_at":"2026-10-14T00:15:32+00:00","page":"https://rirtracker.com/ip/103.106.0.0-103.106.3.255/#e-97f7142bab8b6b28","report_page":"https://rirtracker.com/apnic/reports/2023-07-17/","evidence_url":"https://rirtracker.com/api/v1/resources/ip/103.106.0.0-103.106.3.255.json","observed":"103.106.0.0/22 reserved on 2023-07-17, allocated on 2023-07-18","explanation":"No transfer record matches. APNIC's statistics show it reserved on 2023-07-17 and allocated (dated 2017-12-15) on 2023-07-18. The tracker saw it removed from registration on 2023-04-17 (91 days earlier), and it is back with the same holder record it had before, so it went back to its previous holder rather than to a new one: most likely a suspension lifted, a reinstatement or a correction.","evidence":[{"type":"statistics_diff","url":"https://ftp.apnic.net/stats/apnic/2023/delegated-apnic-extended-20230718.gz","retrieved_at":"2026-10-13T00:44:42+00:00","summary":"Found by comparing APNIC's daily statistics: 103.106.0.0/22 reserved on 2023-07-17, allocated on 2023-07-18"},{"type":"delegated_before","url":"https://ftp.apnic.net/stats/apnic/2023/delegated-apnic-extended-20230717.gz","retrieved_at":"2026-10-13T00:44:38+00:00","summary":"APNIC delegated statistics 2023-07-17, before the change: reserved"},{"type":"delegated_after","url":"https://ftp.apnic.net/stats/apnic/2023/delegated-apnic-extended-20230718.gz","retrieved_at":"2026-10-13T00:44:42+00:00","summary":"APNIC delegated statistics 2023-07-18, after the change: allocated (dated 2017-12-15)"}]},{"event_id":"2accb7aecd509a8a","registry":"APNIC","report_date":"2023-04-17","source":"statistics","raw_action":"REMOVED","raw_line":null,"resource_type":"ipv4","resource":"103.106.0.0/22","start":"103.106.0.0","end":"103.106.3.255","classification":"REMOVED_REASON_UNKNOWN","classification_label":"Removed (return, revocation or reclamation not publicly distinguishable)","confidence":"STRONG_INFERENCE","source_rir":null,"recipient_rir":null,"source_organization":null,"recipient_organization":null,"inventory_effect":"Possible future reissue candidate after hold","inventory_effect_code":"HOLD_CANDIDATE","provisional":false,"classifier_version":"1.4.0","classified_at":"2026-10-14T00:15:10+00:00","page":"https://rirtracker.com/ip/103.106.0.0-103.106.3.255/#e-2accb7aecd509a8a","report_page":"https://rirtracker.com/apnic/reports/2023-04-17/","evidence_url":"https://rirtracker.com/api/v1/resources/ip/103.106.0.0-103.106.3.255.json","observed":"103.106.0.0/22 allocated on 2023-04-17, reserved on 2023-04-18","hold":{"hold_rule_source_url":"https://www.apnic.net/manage-ip/manage-resources/address-status","hold_rule_months":12,"estimated_hold_end":"2024-04-17","availability_statement":"Possible reissue candidate after this date; not confirmed available","hold_rule_observed":true},"explanation":"Removed from active registration. The tracker found it by comparing APNIC's daily statistics. APNIC's statistics show it allocated (dated 2017-12-15) on 2023-04-17 and reserved on 2023-04-18. Public sources do not distinguish a voluntary return, revocation, or reclamation. APNIC publishes no hold period, but its statistics have released returned IPv4 space a year after the removal or later since 2014, so the tracker estimates the hold ends on 2024-04-17. That is what APNIC has done, not a rule it states. This does not confirm availability.","evidence":[{"type":"statistics_diff","url":"https://ftp.apnic.net/stats/apnic/2023/delegated-apnic-extended-20230418.gz","retrieved_at":"2026-10-13T00:38:03+00:00","summary":"Found by comparing APNIC's daily statistics: 103.106.0.0/22 allocated on 2023-04-17, reserved on 2023-04-18"},{"type":"delegated_before","url":"https://ftp.apnic.net/stats/apnic/2023/delegated-apnic-extended-20230417.gz","retrieved_at":"2026-10-13T00:38:00+00:00","summary":"APNIC delegated statistics 2023-04-17, before the change: allocated (dated 2017-12-15)"},{"type":"delegated_after","url":"https://ftp.apnic.net/stats/apnic/2023/delegated-apnic-extended-20230418.gz","retrieved_at":"2026-10-13T00:38:03+00:00","summary":"APNIC delegated statistics 2023-04-18, after the change: reserved"}]},{"event_id":"b9d9a0179e4a3e41","registry":"APNIC","report_date":"2017-12-15","source":"statistics","raw_action":"ADDED","raw_line":null,"resource_type":"ipv4","resource":"103.106.0.0/22","start":"103.106.0.0","end":"103.106.3.255","classification":"APPARENT_NEW_ISSUANCE","classification_label":"Apparent new issuance","confidence":"STRONG_INFERENCE","source_rir":null,"recipient_rir":null,"source_organization":null,"recipient_organization":null,"inventory_effect":"Likely issued from APNIC-controlled inventory","inventory_effect_code":"ISSUED","provisional":false,"classifier_version":"1.4.0","classified_at":"2026-10-14T00:06:30+00:00","page":"https://rirtracker.com/ip/103.106.0.0-103.106.3.255/#e-b9d9a0179e4a3e41","report_page":"https://rirtracker.com/apnic/reports/2017-12-15/","evidence_url":"https://rirtracker.com/api/v1/resources/ip/103.106.0.0-103.106.3.255.json","observed":"103.106.0.0/22 available on 2017-12-15, allocated on 2017-12-16","explanation":"No transfer record matches. APNIC's statistics show it available on 2017-12-15 and allocated (dated 2017-12-15) on 2017-12-16. It moved from APNIC's unissued pool to an active registration dated around that day, so it appears to be newly issued by APNIC.","evidence":[{"type":"statistics_diff","url":"https://ftp.apnic.net/stats/apnic/2017/delegated-apnic-extended-20171216.gz","retrieved_at":"2026-10-12T22:18:16+00:00","summary":"Found by comparing APNIC's daily statistics: 103.106.0.0/22 available on 2017-12-15, allocated on 2017-12-16"},{"type":"delegated_before","url":"https://ftp.apnic.net/stats/apnic/2017/delegated-apnic-extended-20171215.gz","retrieved_at":"2026-10-12T22:18:13+00:00","summary":"APNIC delegated statistics 2017-12-15, before the change: available"},{"type":"delegated_after","url":"https://ftp.apnic.net/stats/apnic/2017/delegated-apnic-extended-20171216.gz","retrieved_at":"2026-10-12T22:18:16+00:00","summary":"APNIC delegated statistics 2017-12-16, after the change: allocated (dated 2017-12-15)"}]}],"classification_history":{"4e5808657d707db8":[{"raw_change_id":40364,"classification_code":"INTER_RIR_TRANSFER_OUT","confidence":"CONFIRMED","classifier_version":"1.3.0","classified_at":"2026-10-13T02:37:54+00:00","current":0,"public_explanation":"APNIC's transfer log records a transfer from Parvez Mahmud (APNIC) to ORG-PHS8-RIPE (RIPE NCC) on 2023-11-29 20:29 UTC: it left APNIC for the RIPE NCC. It is not a new allocation and is not offered to APNIC applicants."},{"raw_change_id":40364,"classification_code":"INTER_RIR_TRANSFER_OUT","confidence":"CONFIRMED","classifier_version":"1.3.1","classified_at":"2026-10-13T08:02:02+00:00","current":0,"public_explanation":"APNIC's transfer log records a transfer from Parvez Mahmud (APNIC) to ORG-PHS8-RIPE (RIPE NCC) on 2023-11-29 20:29 UTC: it left APNIC for the RIPE NCC. It is not a new allocation and is not offered to APNIC applicants."},{"raw_change_id":40364,"classification_code":"INTER_RIR_TRANSFER_OUT","confidence":"CONFIRMED","classifier_version":"1.3.2","classified_at":"2026-10-13T14:44:13+00:00","current":0,"public_explanation":"APNIC's transfer log records a transfer from Parvez Mahmud (APNIC) to ORG-PHS8-RIPE (RIPE NCC) on 2023-11-29 20:29 UTC: it left APNIC for the RIPE NCC. It is not a new allocation and is not offered to APNIC applicants."},{"raw_change_id":40364,"classification_code":"INTER_RIR_TRANSFER_OUT","confidence":"CONFIRMED","classifier_version":"1.4.0","classified_at":"2026-10-13T23:46:49+00:00","current":1,"public_explanation":"APNIC's transfer log records a transfer from Parvez Mahmud (APNIC) to ORG-PHS8-RIPE (RIPE NCC) on 2023-11-29 20:29 UTC: it left APNIC for the RIPE NCC. It is not a new allocation and is not offered to APNIC applicants."}],"a89a18af9be6c362":[{"raw_change_id":100697,"classification_code":"INTER_RIR_TRANSFER_IN","confidence":"CONFIRMED","classifier_version":"1.3.0","classified_at":"2026-10-13T03:02:59+00:00","current":0,"public_explanation":"The RIPE NCC's transfer log records a transfer from an unnamed organization (APNIC) to WEISS HOSTING GROUP S.R.L. (RIPE NCC) on 2023-11-29 19:00 UTC: it came to the RIPE NCC from APNIC. It was already issued by another registry, so this is not a new issuance."},{"raw_change_id":100697,"classification_code":"INTER_RIR_TRANSFER_IN","confidence":"CONFIRMED","classifier_version":"1.3.1","classified_at":"2026-10-13T08:04:28+00:00","current":0,"public_explanation":"The RIPE NCC's transfer log records a transfer from an unnamed organization (APNIC) to WEISS HOSTING GROUP S.R.L. (RIPE NCC) on 2023-11-29 19:00 UTC: it came to the RIPE NCC from APNIC. It was already issued by another registry, so this is not a new issuance."},{"raw_change_id":100697,"classification_code":"INTER_RIR_TRANSFER_IN","confidence":"CONFIRMED","classifier_version":"1.3.2","classified_at":"2026-10-13T14:46:56+00:00","current":0,"public_explanation":"The RIPE NCC's transfer log records a transfer from an unnamed organization (APNIC) to WEISS HOSTING GROUP S.R.L. (RIPE NCC) on 2023-11-29 19:00 UTC: it came to the RIPE NCC from APNIC. It was already issued by another registry, so this is not a new issuance."},{"raw_change_id":100697,"classification_code":"INTER_RIR_TRANSFER_IN","confidence":"CONFIRMED","classifier_version":"1.4.0","classified_at":"2026-10-13T23:49:46+00:00","current":1,"public_explanation":"The RIPE NCC's transfer log records a transfer from an unnamed organization (APNIC) to WEISS HOSTING GROUP S.R.L. (RIPE NCC) on 2023-11-29 19:00 UTC: it came to the RIPE NCC from APNIC. It was already issued by another registry, so this is not a new issuance."}],"97f7142bab8b6b28":[{"raw_change_id":511108,"classification_code":"RESTORED","confidence":"STRONG_INFERENCE","classifier_version":"1.3.0","classified_at":"2026-10-13T06:29:33+00:00","current":0,"public_explanation":"No transfer record matches. APNIC's statistics show it reserved on 2023-07-17 and allocated (dated 2017-12-15) on 2023-07-18. The tracker saw it removed from registration on 2023-04-17 (91 days earlier), and it is back with the same holder record it had before, so it went back to its previous holder rather than to a new one: most likely a suspension lifted, a reinstatement or a correction."},{"raw_change_id":511108,"classification_code":"RESTORED","confidence":"STRONG_INFERENCE","classifier_version":"1.3.1","classified_at":"2026-10-13T08:25:37+00:00","current":0,"public_explanation":"No transfer record matches. APNIC's statistics show it reserved on 2023-07-17 and allocated (dated 2017-12-15) on 2023-07-18. The tracker saw it removed from registration on 2023-04-17 (91 days earlier), and it is back with the same holder record it had before, so it went back to its previous holder rather than to a new one: most likely a suspension lifted, a reinstatement or a correction."},{"raw_change_id":511108,"classification_code":"RESTORED","confidence":"STRONG_INFERENCE","classifier_version":"1.3.2","classified_at":"2026-10-13T15:09:54+00:00","current":0,"public_explanation":"No transfer record matches. APNIC's statistics show it reserved on 2023-07-17 and allocated (dated 2017-12-15) on 2023-07-18. The tracker saw it removed from registration on 2023-04-17 (91 days earlier), and it is back with the same holder record it had before, so it went back to its previous holder rather than to a new one: most likely a suspension lifted, a reinstatement or a correction."},{"raw_change_id":511108,"classification_code":"RESTORED","confidence":"STRONG_INFERENCE","classifier_version":"1.4.0","classified_at":"2026-10-14T00:15:32+00:00","current":1,"public_explanation":"No transfer record matches. APNIC's statistics show it reserved on 2023-07-17 and allocated (dated 2017-12-15) on 2023-07-18. The tracker saw it removed from registration on 2023-04-17 (91 days earlier), and it is back with the same holder record it had before, so it went back to its previous holder rather than to a new one: most likely a suspension lifted, a reinstatement or a correction."}],"2accb7aecd509a8a":[{"raw_change_id":506752,"classification_code":"REMOVED_REASON_UNKNOWN","confidence":"STRONG_INFERENCE","classifier_version":"1.3.0","classified_at":"2026-10-13T06:27:53+00:00","current":0,"public_explanation":"Removed from active registration. The tracker found it by comparing APNIC's daily statistics. APNIC's statistics show it allocated (dated 2017-12-15) on 2023-04-17 and reserved on 2023-04-18. Public sources do not distinguish a voluntary return, revocation, or reclamation. APNIC publishes no fixed period for which it holds returned IPv4 space before reissuing it, so the tracker gives no estimate. This does not confirm availability."},{"raw_change_id":506752,"classification_code":"REMOVED_REASON_UNKNOWN","confidence":"STRONG_INFERENCE","classifier_version":"1.3.1","classified_at":"2026-10-13T08:25:18+00:00","current":0,"public_explanation":"Removed from active registration. The tracker found it by comparing APNIC's daily statistics. APNIC's statistics show it allocated (dated 2017-12-15) on 2023-04-17 and reserved on 2023-04-18. Public sources do not distinguish a voluntary return, revocation, or reclamation. APNIC publishes no fixed period for which it holds returned IPv4 space before reissuing it, so the tracker gives no estimate. This does not confirm availability."},{"raw_change_id":506752,"classification_code":"REMOVED_REASON_UNKNOWN","confidence":"STRONG_INFERENCE","classifier_version":"1.3.2","classified_at":"2026-10-13T15:09:34+00:00","current":0,"public_explanation":"Removed from active registration. The tracker found it by comparing APNIC's daily statistics. APNIC's statistics show it allocated (dated 2017-12-15) on 2023-04-17 and reserved on 2023-04-18. Public sources do not distinguish a voluntary return, revocation, or reclamation. APNIC publishes no fixed period for which it holds returned IPv4 space before reissuing it, so the tracker gives no estimate. This does not confirm availability."},{"raw_change_id":506752,"classification_code":"REMOVED_REASON_UNKNOWN","confidence":"STRONG_INFERENCE","classifier_version":"1.4.0","classified_at":"2026-10-14T00:15:10+00:00","current":1,"public_explanation":"Removed from active registration. The tracker found it by comparing APNIC's daily statistics. APNIC's statistics show it allocated (dated 2017-12-15) on 2023-04-17 and reserved on 2023-04-18. Public sources do not distinguish a voluntary return, revocation, or reclamation. APNIC publishes no hold period, but its statistics have released returned IPv4 space a year after the removal or later since 2014, so the tracker estimates the hold ends on 2024-04-17. That is what APNIC has done, not a rule it states. This does not confirm availability."}],"b9d9a0179e4a3e41":[{"raw_change_id":388614,"classification_code":"APPARENT_NEW_ISSUANCE","confidence":"STRONG_INFERENCE","classifier_version":"1.3.0","classified_at":"2026-10-13T05:34:29+00:00","current":0,"public_explanation":"No transfer record matches. APNIC's statistics show it available on 2017-12-15 and allocated (dated 2017-12-15) on 2017-12-16. It moved from APNIC's unissued pool to an active registration dated around that day, so it appears to be newly issued by APNIC."},{"raw_change_id":388614,"classification_code":"APPARENT_NEW_ISSUANCE","confidence":"STRONG_INFERENCE","classifier_version":"1.3.1","classified_at":"2026-10-13T08:18:17+00:00","current":0,"public_explanation":"No transfer record matches. APNIC's statistics show it available on 2017-12-15 and allocated (dated 2017-12-15) on 2017-12-16. It moved from APNIC's unissued pool to an active registration dated around that day, so it appears to be newly issued by APNIC."},{"raw_change_id":388614,"classification_code":"APPARENT_NEW_ISSUANCE","confidence":"STRONG_INFERENCE","classifier_version":"1.3.2","classified_at":"2026-10-13T15:02:01+00:00","current":0,"public_explanation":"No transfer record matches. APNIC's statistics show it available on 2017-12-15 and allocated (dated 2017-12-15) on 2017-12-16. It moved from APNIC's unissued pool to an active registration dated around that day, so it appears to be newly issued by APNIC."},{"raw_change_id":388614,"classification_code":"APPARENT_NEW_ISSUANCE","confidence":"STRONG_INFERENCE","classifier_version":"1.4.0","classified_at":"2026-10-14T00:06:30+00:00","current":1,"public_explanation":"No transfer record matches. APNIC's statistics show it available on 2017-12-15 and allocated (dated 2017-12-15) on 2017-12-16. It moved from APNIC's unissued pool to an active registration dated around that day, so it appears to be newly issued by APNIC."}]},"arin_statistics_now":{"status":"not listed"}}