{"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":"193.105.83.0/24","resource_type":"ipv4","page":"https://rirtracker.com/ip/193.105.83.0-193.105.83.255/","statistics_now":{"registry":"RIPE NCC","status":"allocated (dated 2022-01-25)"},"current_holder":{"rir":"RIPE NCC","org":"Multinet24 Sp.zoo","how":"The RIPE NCC's latest statistics and the latest transfer record"},"rdap_snapshots":[],"transfers":[{"id":117841,"date":"2025-12-29T19:00:00Z","type":"RESOURCE_TRANSFER","source_rir":"RIPE NCC","recipient_rir":"RIPE NCC","source_org":"NGNA Sp. z o.o.","recipient_org":"Multinet24 Sp.zoo","range":"193.105.83.0/24","log":"RIPE NCC"}],"events":[{"event_id":"398bfffd9053c32f","registry":"RIPE NCC","report_date":"2025-12-29","source":"transfers","raw_action":"TRANSFER","raw_line":null,"resource_type":"ipv4","resource":"193.105.83.0/24","start":"193.105.83.0","end":"193.105.83.255","classification":"INTRA_RIR_TRANSFER","classification_label":"Intra-RIPE NCC transfer","confidence":"CONFIRMED","source_rir":"RIPE NCC","recipient_rir":"RIPE NCC","source_organization":"NGNA Sp. z o.o.","recipient_organization":"Multinet24 Sp.zoo","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:50:43+00:00","page":"https://rirtracker.com/ip/193.105.83.0-193.105.83.255/#e-398bfffd9053c32f","report_page":"https://rirtracker.com/ripe/reports/2025-12-29/","evidence_url":"https://rirtracker.com/api/v1/resources/ip/193.105.83.0-193.105.83.255.json","observed":"Transfer: NGNA Sp. z o.o. (RIPE NCC) to Multinet24 Sp.zoo (RIPE NCC)","explanation":"The RIPE NCC's transfer log records a transfer from NGNA Sp. z o.o. (RIPE NCC) to Multinet24 Sp.zoo (RIPE NCC) on 2025-12-29 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 2025-12-29 19:00 UTC, NGNA Sp. z o.o. (RIPE NCC) to Multinet24 Sp.zoo (RIPE NCC); resources moved: 193.105.83.0/24"},{"type":"delegated_before","url":"https://ftp.ripe.net/pub/stats/ripencc/2025/delegated-ripencc-extended-20251228.bz2","retrieved_at":"2026-10-13T01:16:58+00:00","summary":"RIPE NCC delegated statistics 2025-12-28 (produced 2025-12-28T22:59:59+00:00), before the change: allocated (dated 2022-01-25)"},{"type":"delegated_after","url":"https://ftp.ripe.net/pub/stats/ripencc/2025/delegated-ripencc-extended-20251229.bz2","retrieved_at":"2026-10-13T01:17:01+00:00","summary":"RIPE NCC delegated statistics 2025-12-29 (produced 2025-12-29T22:59:59+00:00), after the change: allocated (dated 2022-01-25)"}]},{"event_id":"d8947de4f1c3fd42","registry":"RIPE NCC","report_date":"2022-01-25","source":"statistics","raw_action":"ADDED","raw_line":null,"resource_type":"ipv4","resource":"193.105.83.0/24","start":"193.105.83.0","end":"193.105.83.255","classification":"APPARENT_REISSUANCE","classification_label":"Apparent reissuance of previously removed resource","confidence":"OBSERVED_ONLY","source_rir":null,"recipient_rir":null,"source_organization":null,"recipient_organization":null,"inventory_effect":"Likely issued from RIPE NCC-controlled inventory","inventory_effect_code":"ISSUED","provisional":false,"classifier_version":"1.4.0","classified_at":"2026-10-14T00:11:05+00:00","page":"https://rirtracker.com/ip/193.105.83.0-193.105.83.255/#e-d8947de4f1c3fd42","report_page":"https://rirtracker.com/ripe/reports/2022-01-25/","evidence_url":"https://rirtracker.com/api/v1/resources/ip/193.105.83.0-193.105.83.255.json","observed":"193.105.83.0/24 available on 2022-01-24, allocated on 2022-01-25","explanation":"No transfer record matches. The RIPE NCC's statistics show it available on 2022-01-24 and allocated (dated 2022-01-25) on 2022-01-25. The tracker saw this range released from hold on 2022-01-24 (193.105.83.0 - 193.105.84.255), so it appears to have been issued again from the RIPE NCC's pool. Another change to this range was reported the day before or after (2022-01-24: Released 193.105.83.0 - 193.105.84.255), so the before-and-after statistics may include it.","evidence":[{"type":"statistics_diff","url":"https://ftp.ripe.net/pub/stats/ripencc/2022/delegated-ripencc-extended-20220125.bz2","retrieved_at":"2026-10-12T23:26:48+00:00","summary":"Found by comparing the RIPE NCC's daily statistics: 193.105.83.0/24 available on 2022-01-24, allocated on 2022-01-25"},{"type":"delegated_before","url":"https://ftp.ripe.net/pub/stats/ripencc/2022/delegated-ripencc-extended-20220124.bz2","retrieved_at":"2026-10-12T23:26:45+00:00","summary":"RIPE NCC delegated statistics 2022-01-24 (produced 2022-01-24T22:59:00+00:00), before the change: available"},{"type":"delegated_after","url":"https://ftp.ripe.net/pub/stats/ripencc/2022/delegated-ripencc-extended-20220125.bz2","retrieved_at":"2026-10-12T23:26:48+00:00","summary":"RIPE NCC delegated statistics 2022-01-25 (produced 2022-01-25T22:59:00+00:00), after the change: allocated (dated 2022-01-25)"}]},{"event_id":"aabe1a81c4c35ac7","registry":"RIPE NCC","report_date":"2021-07-28","source":"statistics","raw_action":"REMOVED","raw_line":null,"resource_type":"ipv4","resource":"193.105.83.0/24","start":"193.105.83.0","end":"193.105.83.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:10:05+00:00","page":"https://rirtracker.com/ip/193.105.83.0-193.105.83.255/#e-aabe1a81c4c35ac7","report_page":"https://rirtracker.com/ripe/reports/2021-07-28/","evidence_url":"https://rirtracker.com/api/v1/resources/ip/193.105.83.0-193.105.83.255.json","observed":"193.105.83.0/24 allocated on 2021-07-27, reserved on 2021-07-28","hold":{"hold_rule_source_url":"https://www.ripe.net/manage-ips-and-asns/resource-management/quarantine-for-returned-internet-number-resources","hold_rule_days":180,"estimated_hold_end":"2022-01-24","availability_statement":"Possible reissue candidate after this date; not confirmed available"},"explanation":"Removed from active registration. The tracker found it by comparing the RIPE NCC's daily statistics. The RIPE NCC's statistics show it allocated (dated 2019-11-15) on 2021-07-27 and reserved on 2021-07-28. Public sources do not distinguish a voluntary return, revocation, or reclamation. The RIPE NCC holds returned, revoked and reclaimed IPv4 space for 180 days (six months), or longer while still routed, before reissuing it, so the estimated hold end is 2022-01-24. This does not confirm availability.","evidence":[{"type":"statistics_diff","url":"https://ftp.ripe.net/pub/stats/ripencc/2021/delegated-ripencc-extended-20210728.bz2","retrieved_at":"2026-10-12T23:13:08+00:00","summary":"Found by comparing the RIPE NCC's daily statistics: 193.105.83.0/24 allocated on 2021-07-27, reserved on 2021-07-28"},{"type":"delegated_before","url":"https://ftp.ripe.net/pub/stats/ripencc/2021/delegated-ripencc-extended-20210727.bz2","retrieved_at":"2026-10-12T23:13:05+00:00","summary":"RIPE NCC delegated statistics 2021-07-27 (produced 2021-07-27T21:59:00+00:00), before the change: allocated (dated 2019-11-15)"},{"type":"delegated_after","url":"https://ftp.ripe.net/pub/stats/ripencc/2021/delegated-ripencc-extended-20210728.bz2","retrieved_at":"2026-10-12T23:13:08+00:00","summary":"RIPE NCC delegated statistics 2021-07-28 (produced 2021-07-28T21:59:00+00:00), after the change: reserved"}]},{"event_id":"6d83bdbd1f748f3d","registry":"RIPE NCC","report_date":"2019-11-15","source":"statistics","raw_action":"ADDED","raw_line":null,"resource_type":"ipv4","resource":"193.105.83.0/24","start":"193.105.83.0","end":"193.105.83.255","classification":"APPARENT_REISSUANCE","classification_label":"Apparent reissuance of previously removed resource","confidence":"STRONG_INFERENCE","source_rir":null,"recipient_rir":null,"source_organization":null,"recipient_organization":null,"inventory_effect":"Likely issued from RIPE NCC-controlled inventory","inventory_effect_code":"ISSUED","provisional":false,"classifier_version":"1.4.0","classified_at":"2026-10-14T00:07:01+00:00","page":"https://rirtracker.com/ip/193.105.83.0-193.105.83.255/#e-6d83bdbd1f748f3d","report_page":"https://rirtracker.com/ripe/reports/2019-11-15/","evidence_url":"https://rirtracker.com/api/v1/resources/ip/193.105.83.0-193.105.83.255.json","observed":"193.105.83.0/24 available on 2019-11-14, allocated on 2019-11-15","explanation":"No transfer record matches. The RIPE NCC's statistics show it available on 2019-11-14 and allocated (dated 2019-11-15) on 2019-11-15. The tracker saw this range removed from registration on 2016-05-10 (193.105.83.0/24), so it appears to have been issued again from the RIPE NCC's pool.","evidence":[{"type":"statistics_diff","url":"https://ftp.ripe.net/pub/stats/ripencc/2019/delegated-ripencc-extended-20191115.bz2","retrieved_at":"2026-10-12T22:24:01+00:00","summary":"Found by comparing the RIPE NCC's daily statistics: 193.105.83.0/24 available on 2019-11-14, allocated on 2019-11-15"},{"type":"delegated_before","url":"https://ftp.ripe.net/pub/stats/ripencc/2019/delegated-ripencc-extended-20191114.bz2","retrieved_at":"2026-10-12T22:23:58+00:00","summary":"RIPE NCC delegated statistics 2019-11-14 (produced 2019-11-14T22:59:59+00:00), before the change: available"},{"type":"delegated_after","url":"https://ftp.ripe.net/pub/stats/ripencc/2019/delegated-ripencc-extended-20191115.bz2","retrieved_at":"2026-10-12T22:24:01+00:00","summary":"RIPE NCC delegated statistics 2019-11-15 (produced 2019-11-15T22:59:59+00:00), after the change: allocated (dated 2019-11-15)"}]},{"event_id":"93128996e78d36ac","registry":"RIPE NCC","report_date":"2016-05-10","source":"statistics","raw_action":"REMOVED","raw_line":null,"resource_type":"ipv4","resource":"193.105.83.0/24","start":"193.105.83.0","end":"193.105.83.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:01:08+00:00","page":"https://rirtracker.com/ip/193.105.83.0-193.105.83.255/#e-93128996e78d36ac","report_page":"https://rirtracker.com/ripe/reports/2016-05-10/","evidence_url":"https://rirtracker.com/api/v1/resources/ip/193.105.83.0-193.105.83.255.json","observed":"193.105.83.0/24 assigned on 2016-05-09, reserved on 2016-05-10","hold":{"hold_rule_source_url":"https://www.ripe.net/manage-ips-and-asns/resource-management/quarantine-for-returned-internet-number-resources","hold_rule_days":180,"estimated_hold_end":"2016-11-06","availability_statement":"Possible reissue candidate after this date; not confirmed available"},"explanation":"Removed from active registration. The tracker found it by comparing the RIPE NCC's daily statistics. The RIPE NCC's statistics show it assigned (dated 2010-01-29) on 2016-05-09 and reserved on 2016-05-10. Public sources do not distinguish a voluntary return, revocation, or reclamation. The RIPE NCC holds returned, revoked and reclaimed IPv4 space for 180 days (six months), or longer while still routed, before reissuing it, so the estimated hold end is 2016-11-06. This does not confirm availability.","evidence":[{"type":"statistics_diff","url":"https://ftp.ripe.net/pub/stats/ripencc/2016/delegated-ripencc-extended-20160510.bz2","retrieved_at":"2026-10-12T20:55:35+00:00","summary":"Found by comparing the RIPE NCC's daily statistics: 193.105.83.0/24 assigned on 2016-05-09, reserved on 2016-05-10"},{"type":"delegated_before","url":"https://ftp.ripe.net/pub/stats/ripencc/2016/delegated-ripencc-extended-20160509.bz2","retrieved_at":"2026-10-12T20:55:32+00:00","summary":"RIPE NCC delegated statistics 2016-05-09 (produced 2016-05-09T21:59:59+00:00), before the change: assigned (dated 2010-01-29)"},{"type":"delegated_after","url":"https://ftp.ripe.net/pub/stats/ripencc/2016/delegated-ripencc-extended-20160510.bz2","retrieved_at":"2026-10-12T20:55:35+00:00","summary":"RIPE NCC delegated statistics 2016-05-10 (produced 2016-05-10T21:59:59+00:00), after the change: reserved"}]}],"classification_history":{"398bfffd9053c32f":[{"raw_change_id":118688,"classification_code":"INTRA_RIR_TRANSFER","confidence":"CONFIRMED","classifier_version":"1.3.0","classified_at":"2026-10-13T03:10:54+00:00","current":0,"public_explanation":"The RIPE NCC's transfer log records a transfer from NGNA Sp. z o.o. (RIPE NCC) to Multinet24 Sp.zoo (RIPE NCC) on 2025-12-29 19:00 UTC. The registration changed hands; it is not a new allocation from the RIPE NCC."},{"raw_change_id":118688,"classification_code":"INTRA_RIR_TRANSFER","confidence":"CONFIRMED","classifier_version":"1.3.1","classified_at":"2026-10-13T08:05:12+00:00","current":0,"public_explanation":"The RIPE NCC's transfer log records a transfer from NGNA Sp. z o.o. (RIPE NCC) to Multinet24 Sp.zoo (RIPE NCC) on 2025-12-29 19:00 UTC. The registration changed hands; it is not a new allocation from the RIPE NCC."},{"raw_change_id":118688,"classification_code":"INTRA_RIR_TRANSFER","confidence":"CONFIRMED","classifier_version":"1.3.2","classified_at":"2026-10-13T14:47:45+00:00","current":0,"public_explanation":"The RIPE NCC's transfer log records a transfer from NGNA Sp. z o.o. (RIPE NCC) to Multinet24 Sp.zoo (RIPE NCC) on 2025-12-29 19:00 UTC. The registration changed hands; it is not a new allocation from the RIPE NCC."},{"raw_change_id":118688,"classification_code":"INTRA_RIR_TRANSFER","confidence":"CONFIRMED","classifier_version":"1.4.0","classified_at":"2026-10-13T23:50:43+00:00","current":1,"public_explanation":"The RIPE NCC's transfer log records a transfer from NGNA Sp. z o.o. (RIPE NCC) to Multinet24 Sp.zoo (RIPE NCC) on 2025-12-29 19:00 UTC. The registration changed hands; it is not a new allocation from the RIPE NCC."}],"d8947de4f1c3fd42":[{"raw_change_id":454070,"classification_code":"APPARENT_REISSUANCE","confidence":"OBSERVED_ONLY","classifier_version":"1.3.0","classified_at":"2026-10-13T06:03:01+00:00","current":0,"public_explanation":"No transfer record matches. The RIPE NCC's statistics show it available on 2022-01-24 and allocated (dated 2022-01-25) on 2022-01-25. The tracker saw this range released from hold on 2022-01-24 (193.105.83.0 - 193.105.84.255), so it appears to have been issued again from the RIPE NCC's pool. Another change to this range was reported the day before or after (2022-01-24: Released 193.105.83.0 - 193.105.84.255), so the before-and-after statistics may include it."},{"raw_change_id":454070,"classification_code":"APPARENT_REISSUANCE","confidence":"OBSERVED_ONLY","classifier_version":"1.3.1","classified_at":"2026-10-13T08:22:03+00:00","current":0,"public_explanation":"No transfer record matches. The RIPE NCC's statistics show it available on 2022-01-24 and allocated (dated 2022-01-25) on 2022-01-25. The tracker saw this range released from hold on 2022-01-24 (193.105.83.0 - 193.105.84.255), so it appears to have been issued again from the RIPE NCC's pool. Another change to this range was reported the day before or after (2022-01-24: Released 193.105.83.0 - 193.105.84.255), so the before-and-after statistics may include it."},{"raw_change_id":454070,"classification_code":"APPARENT_REISSUANCE","confidence":"OBSERVED_ONLY","classifier_version":"1.3.2","classified_at":"2026-10-13T15:06:04+00:00","current":0,"public_explanation":"No transfer record matches. The RIPE NCC's statistics show it available on 2022-01-24 and allocated (dated 2022-01-25) on 2022-01-25. The tracker saw this range released from hold on 2022-01-24 (193.105.83.0 - 193.105.84.255), so it appears to have been issued again from the RIPE NCC's pool. Another change to this range was reported the day before or after (2022-01-24: Released 193.105.83.0 - 193.105.84.255), so the before-and-after statistics may include it."},{"raw_change_id":454070,"classification_code":"APPARENT_REISSUANCE","confidence":"OBSERVED_ONLY","classifier_version":"1.4.0","classified_at":"2026-10-14T00:11:05+00:00","current":1,"public_explanation":"No transfer record matches. The RIPE NCC's statistics show it available on 2022-01-24 and allocated (dated 2022-01-25) on 2022-01-25. The tracker saw this range released from hold on 2022-01-24 (193.105.83.0 - 193.105.84.255), so it appears to have been issued again from the RIPE NCC's pool. Another change to this range was reported the day before or after (2022-01-24: Released 193.105.83.0 - 193.105.84.255), so the before-and-after statistics may include it."}],"aabe1a81c4c35ac7":[{"raw_change_id":438684,"classification_code":"REMOVED_REASON_UNKNOWN","confidence":"STRONG_INFERENCE","classifier_version":"1.3.0","classified_at":"2026-10-13T05:55:46+00:00","current":0,"public_explanation":"Removed from active registration. The tracker found it by comparing the RIPE NCC's daily statistics. The RIPE NCC's statistics show it allocated (dated 2019-11-15) on 2021-07-27 and reserved on 2021-07-28. Public sources do not distinguish a voluntary return, revocation, or reclamation. The RIPE NCC holds returned, revoked and reclaimed IPv4 space for 180 days (six months), or longer while still routed, before reissuing it, so the earliest estimated hold expiration is 2022-01-24. This does not confirm availability."},{"raw_change_id":438684,"classification_code":"REMOVED_REASON_UNKNOWN","confidence":"STRONG_INFERENCE","classifier_version":"1.3.1","classified_at":"2026-10-13T08:21:14+00:00","current":0,"public_explanation":"Removed from active registration. The tracker found it by comparing the RIPE NCC's daily statistics. The RIPE NCC's statistics show it allocated (dated 2019-11-15) on 2021-07-27 and reserved on 2021-07-28. Public sources do not distinguish a voluntary return, revocation, or reclamation. The RIPE NCC holds returned, revoked and reclaimed IPv4 space for 180 days (six months), or longer while still routed, before reissuing it, so the earliest estimated hold expiration is 2022-01-24. This does not confirm availability."},{"raw_change_id":438684,"classification_code":"REMOVED_REASON_UNKNOWN","confidence":"STRONG_INFERENCE","classifier_version":"1.3.2","classified_at":"2026-10-13T15:05:12+00:00","current":0,"public_explanation":"Removed from active registration. The tracker found it by comparing the RIPE NCC's daily statistics. The RIPE NCC's statistics show it allocated (dated 2019-11-15) on 2021-07-27 and reserved on 2021-07-28. Public sources do not distinguish a voluntary return, revocation, or reclamation. The RIPE NCC holds returned, revoked and reclaimed IPv4 space for 180 days (six months), or longer while still routed, before reissuing it, so the earliest estimated hold expiration is 2022-01-24. This does not confirm availability."},{"raw_change_id":438684,"classification_code":"REMOVED_REASON_UNKNOWN","confidence":"STRONG_INFERENCE","classifier_version":"1.4.0","classified_at":"2026-10-14T00:10:05+00:00","current":1,"public_explanation":"Removed from active registration. The tracker found it by comparing the RIPE NCC's daily statistics. The RIPE NCC's statistics show it allocated (dated 2019-11-15) on 2021-07-27 and reserved on 2021-07-28. Public sources do not distinguish a voluntary return, revocation, or reclamation. The RIPE NCC holds returned, revoked and reclaimed IPv4 space for 180 days (six months), or longer while still routed, before reissuing it, so the estimated hold end is 2022-01-24. This does not confirm availability."}],"6d83bdbd1f748f3d":[{"raw_change_id":396294,"classification_code":"APPARENT_REISSUANCE","confidence":"STRONG_INFERENCE","classifier_version":"1.3.0","classified_at":"2026-10-13T05:38:09+00:00","current":0,"public_explanation":"No transfer record matches. The RIPE NCC's statistics show it available on 2019-11-14 and allocated (dated 2019-11-15) on 2019-11-15. The tracker saw this range removed from registration on 2016-05-10 (193.105.83.0/24), so it appears to have been issued again from the RIPE NCC's pool."},{"raw_change_id":396294,"classification_code":"APPARENT_REISSUANCE","confidence":"STRONG_INFERENCE","classifier_version":"1.3.1","classified_at":"2026-10-13T08:18:41+00:00","current":0,"public_explanation":"No transfer record matches. The RIPE NCC's statistics show it available on 2019-11-14 and allocated (dated 2019-11-15) on 2019-11-15. The tracker saw this range removed from registration on 2016-05-10 (193.105.83.0/24), so it appears to have been issued again from the RIPE NCC's pool."},{"raw_change_id":396294,"classification_code":"APPARENT_REISSUANCE","confidence":"STRONG_INFERENCE","classifier_version":"1.3.2","classified_at":"2026-10-13T15:02:28+00:00","current":0,"public_explanation":"No transfer record matches. The RIPE NCC's statistics show it available on 2019-11-14 and allocated (dated 2019-11-15) on 2019-11-15. The tracker saw this range removed from registration on 2016-05-10 (193.105.83.0/24), so it appears to have been issued again from the RIPE NCC's pool."},{"raw_change_id":396294,"classification_code":"APPARENT_REISSUANCE","confidence":"STRONG_INFERENCE","classifier_version":"1.4.0","classified_at":"2026-10-14T00:07:01+00:00","current":1,"public_explanation":"No transfer record matches. The RIPE NCC's statistics show it available on 2019-11-14 and allocated (dated 2019-11-15) on 2019-11-15. The tracker saw this range removed from registration on 2016-05-10 (193.105.83.0/24), so it appears to have been issued again from the RIPE NCC's pool."}],"93128996e78d36ac":[{"raw_change_id":304301,"classification_code":"REMOVED_REASON_UNKNOWN","confidence":"STRONG_INFERENCE","classifier_version":"1.3.0","classified_at":"2026-10-13T04:57:48+00:00","current":0,"public_explanation":"Removed from active registration. The tracker found it by comparing the RIPE NCC's daily statistics. The RIPE NCC's statistics show it assigned (dated 2010-01-29) on 2016-05-09 and reserved on 2016-05-10. Public sources do not distinguish a voluntary return, revocation, or reclamation. The RIPE NCC holds returned, revoked and reclaimed IPv4 space for 180 days (six months), or longer while still routed, before reissuing it, so the earliest estimated hold expiration is 2016-11-06. This does not confirm availability."},{"raw_change_id":304301,"classification_code":"REMOVED_REASON_UNKNOWN","confidence":"STRONG_INFERENCE","classifier_version":"1.3.1","classified_at":"2026-10-13T08:13:46+00:00","current":0,"public_explanation":"Removed from active registration. The tracker found it by comparing the RIPE NCC's daily statistics. The RIPE NCC's statistics show it assigned (dated 2010-01-29) on 2016-05-09 and reserved on 2016-05-10. Public sources do not distinguish a voluntary return, revocation, or reclamation. The RIPE NCC holds returned, revoked and reclaimed IPv4 space for 180 days (six months), or longer while still routed, before reissuing it, so the earliest estimated hold expiration is 2016-11-06. This does not confirm availability."},{"raw_change_id":304301,"classification_code":"REMOVED_REASON_UNKNOWN","confidence":"STRONG_INFERENCE","classifier_version":"1.3.2","classified_at":"2026-10-13T14:57:11+00:00","current":0,"public_explanation":"Removed from active registration. The tracker found it by comparing the RIPE NCC's daily statistics. The RIPE NCC's statistics show it assigned (dated 2010-01-29) on 2016-05-09 and reserved on 2016-05-10. Public sources do not distinguish a voluntary return, revocation, or reclamation. The RIPE NCC holds returned, revoked and reclaimed IPv4 space for 180 days (six months), or longer while still routed, before reissuing it, so the earliest estimated hold expiration is 2016-11-06. This does not confirm availability."},{"raw_change_id":304301,"classification_code":"REMOVED_REASON_UNKNOWN","confidence":"STRONG_INFERENCE","classifier_version":"1.4.0","classified_at":"2026-10-14T00:01:08+00:00","current":1,"public_explanation":"Removed from active registration. The tracker found it by comparing the RIPE NCC's daily statistics. The RIPE NCC's statistics show it assigned (dated 2010-01-29) on 2016-05-09 and reserved on 2016-05-10. Public sources do not distinguish a voluntary return, revocation, or reclamation. The RIPE NCC holds returned, revoked and reclaimed IPv4 space for 180 days (six months), or longer while still routed, before reissuing it, so the estimated hold end is 2016-11-06. This does not confirm availability."}]},"arin_statistics_now":{"status":"not listed"}}