{"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":"91.207.79.0/24","resource_type":"ipv4","page":"https://rirtracker.com/ip/91.207.79.0-91.207.79.255/","statistics_now":{"registry":"RIPE NCC","status":"allocated (dated 2023-10-02)"},"current_holder":{"rir":"RIPE NCC","org":"Clausal Computing Oy","how":"The RIPE NCC's latest statistics and the latest transfer record"},"rdap_snapshots":[],"transfers":[{"id":108984,"date":"2024-11-06T19:00:00Z","type":"MERGER_ACQUISITION","source_rir":"RIPE NCC","recipient_rir":"RIPE NCC","source_org":"Bitfoam Oy","recipient_org":"Clausal Computing Oy","range":"91.207.79.0/24","log":"RIPE NCC"},{"id":50961,"date":"2016-06-24T19:00:00Z","type":"RESOURCE_TRANSFER","source_rir":"RIPE NCC","recipient_rir":"RIPE NCC","source_org":"Joint Stock Company \"New-Tech\"","recipient_org":"Federal state budgetary institution Center expertizy y koordinacii","range":"91.207.79.0/24","log":"RIPE NCC"}],"events":[{"event_id":"178d1d2b651f4a34","registry":"RIPE NCC","report_date":"2024-11-06","source":"transfers","raw_action":"TRANSFER","raw_line":null,"resource_type":"ipv4","resource":"91.207.79.0/24","start":"91.207.79.0","end":"91.207.79.255","classification":"MERGER_ACQUISITION","classification_label":"Merger/acquisition or reorganization","confidence":"CONFIRMED","source_rir":"RIPE NCC","recipient_rir":"RIPE NCC","source_organization":"Bitfoam Oy","recipient_organization":"Clausal Computing Oy","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:14+00:00","page":"https://rirtracker.com/ip/91.207.79.0-91.207.79.255/#e-178d1d2b651f4a34","report_page":"https://rirtracker.com/ripe/reports/2024-11-06/","evidence_url":"https://rirtracker.com/api/v1/resources/ip/91.207.79.0-91.207.79.255.json","observed":"Merger/acquisition: Bitfoam Oy (RIPE NCC) to Clausal Computing Oy (RIPE NCC)","explanation":"The RIPE NCC's transfer log records a merger, acquisition or reorganization from Bitfoam Oy (RIPE NCC) to Clausal Computing Oy (RIPE NCC) on 2024-11-06 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: MERGER_ACQUISITION on 2024-11-06 19:00 UTC, Bitfoam Oy (RIPE NCC) to Clausal Computing Oy (RIPE NCC); resources moved: 91.207.79.0/24"},{"type":"delegated_before","url":"https://ftp.ripe.net/pub/stats/ripencc/2024/delegated-ripencc-extended-20241105.bz2","retrieved_at":"2026-10-13T00:44:33+00:00","summary":"RIPE NCC delegated statistics 2024-11-05 (produced 2024-11-05T22:59:59+00:00), before the change: allocated (dated 2023-10-02)"},{"type":"delegated_after","url":"https://ftp.ripe.net/pub/stats/ripencc/2024/delegated-ripencc-extended-20241106.bz2","retrieved_at":"2026-10-13T00:44:36+00:00","summary":"RIPE NCC delegated statistics 2024-11-06 (produced 2024-11-06T22:59:59+00:00), after the change: allocated (dated 2023-10-02)"}]},{"event_id":"d692a0183e537eb7","registry":"RIPE NCC","report_date":"2023-10-02","source":"statistics","raw_action":"ADDED","raw_line":null,"resource_type":"ipv4","resource":"91.207.79.0/24","start":"91.207.79.0","end":"91.207.79.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:13:59+00:00","page":"https://rirtracker.com/ip/91.207.79.0-91.207.79.255/#e-d692a0183e537eb7","report_page":"https://rirtracker.com/ripe/reports/2023-10-02/","evidence_url":"https://rirtracker.com/api/v1/resources/ip/91.207.79.0-91.207.79.255.json","observed":"91.207.79.0/24 available on 2023-10-01, allocated on 2023-10-02","explanation":"No transfer record matches. The RIPE NCC's statistics show it available on 2023-10-01 and allocated (dated 2023-10-02) on 2023-10-02. The tracker saw this range released from hold on 2023-09-30 (91.207.79.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/2023/delegated-ripencc-extended-20231002.bz2","retrieved_at":"2026-10-13T00:13:15+00:00","summary":"Found by comparing the RIPE NCC's daily statistics: 91.207.79.0/24 available on 2023-10-01, allocated on 2023-10-02"},{"type":"delegated_before","url":"https://ftp.ripe.net/pub/stats/ripencc/2023/delegated-ripencc-extended-20231001.bz2","retrieved_at":"2026-10-13T00:13:12+00:00","summary":"RIPE NCC delegated statistics 2023-10-01 (produced 2023-10-01T21:59:59+00:00), before the change: available"},{"type":"delegated_after","url":"https://ftp.ripe.net/pub/stats/ripencc/2023/delegated-ripencc-extended-20231002.bz2","retrieved_at":"2026-10-13T00:13:15+00:00","summary":"RIPE NCC delegated statistics 2023-10-02 (produced 2023-10-02T21:59:59+00:00), after the change: allocated (dated 2023-10-02)"}]},{"event_id":"fdeef2ce9fc43d7b","registry":"RIPE NCC","report_date":"2023-09-30","source":"statistics","raw_action":"RELEASED","raw_line":null,"resource_type":"ipv4","resource":"91.207.79.0/24","start":"91.207.79.0","end":"91.207.79.255","classification":"HOLD_RELEASED","classification_label":"Released from hold (the RIPE NCC lists it as 'available')","confidence":"STRONG_INFERENCE","source_rir":null,"recipient_rir":null,"source_organization":null,"recipient_organization":null,"inventory_effect":"The RIPE NCC's statistics now list it as 'available'; reissue not confirmed","inventory_effect_code":"RELEASED","provisional":false,"classifier_version":"1.4.0","classified_at":"2026-10-14T00:13:59+00:00","page":"https://rirtracker.com/ip/91.207.79.0-91.207.79.255/#e-fdeef2ce9fc43d7b","report_page":"https://rirtracker.com/ripe/reports/2023-09-30/","evidence_url":"https://rirtracker.com/api/v1/resources/ip/91.207.79.0-91.207.79.255.json","observed":"91.207.79.0/24 reserved on 2023-09-29, available on 2023-09-30","explanation":"The RIPE NCC's statistics show it reserved on 2023-09-29 and available on 2023-09-30. The RIPE NCC moved it from its reserved (held) records to the status it calls 'available'. The tracker saw it removed from registration on 2023-04-03, 180 days earlier. That is the RIPE NCC's own label: whether and when it is reissued is not confirmed.","evidence":[{"type":"statistics_diff","url":"https://ftp.ripe.net/pub/stats/ripencc/2023/delegated-ripencc-extended-20230930.bz2","retrieved_at":"2026-10-13T00:13:09+00:00","summary":"Found by comparing the RIPE NCC's daily statistics: 91.207.79.0/24 reserved on 2023-09-29, available on 2023-09-30"},{"type":"delegated_before","url":"https://ftp.ripe.net/pub/stats/ripencc/2023/delegated-ripencc-extended-20230929.bz2","retrieved_at":"2026-10-13T00:13:06+00:00","summary":"RIPE NCC delegated statistics 2023-09-29 (produced 2023-09-29T21:59:59+00:00), before the change: reserved"},{"type":"delegated_after","url":"https://ftp.ripe.net/pub/stats/ripencc/2023/delegated-ripencc-extended-20230930.bz2","retrieved_at":"2026-10-13T00:13:09+00:00","summary":"RIPE NCC delegated statistics 2023-09-30 (produced 2023-09-30T21:59:59+00:00), after the change: available"}]},{"event_id":"0bca7ac7a49b1ad6","registry":"RIPE NCC","report_date":"2023-04-03","source":"statistics","raw_action":"REMOVED","raw_line":null,"resource_type":"ipv4","resource":"91.207.79.0/24","start":"91.207.79.0","end":"91.207.79.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:13:15+00:00","page":"https://rirtracker.com/ip/91.207.79.0-91.207.79.255/#e-0bca7ac7a49b1ad6","report_page":"https://rirtracker.com/ripe/reports/2023-04-03/","evidence_url":"https://rirtracker.com/api/v1/resources/ip/91.207.79.0-91.207.79.255.json","observed":"91.207.79.0/24 assigned on 2023-04-02, reserved on 2023-04-03","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":"2023-09-30","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 2008-10-01) on 2023-04-02 and reserved on 2023-04-03. 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 2023-09-30. This does not confirm availability.","evidence":[{"type":"statistics_diff","url":"https://ftp.ripe.net/pub/stats/ripencc/2023/delegated-ripencc-extended-20230403.bz2","retrieved_at":"2026-10-12T23:59:25+00:00","summary":"Found by comparing the RIPE NCC's daily statistics: 91.207.79.0/24 assigned on 2023-04-02, reserved on 2023-04-03"},{"type":"delegated_before","url":"https://ftp.ripe.net/pub/stats/ripencc/2023/delegated-ripencc-extended-20230402.bz2","retrieved_at":"2026-10-12T23:59:22+00:00","summary":"RIPE NCC delegated statistics 2023-04-02 (produced 2023-04-02T21:59:59+00:00), before the change: assigned (dated 2008-10-01)"},{"type":"delegated_after","url":"https://ftp.ripe.net/pub/stats/ripencc/2023/delegated-ripencc-extended-20230403.bz2","retrieved_at":"2026-10-12T23:59:25+00:00","summary":"RIPE NCC delegated statistics 2023-04-03 (produced 2023-04-03T21:59:59+00:00), after the change: reserved"}]},{"event_id":"b6c0bb4a75f2d434","registry":"RIPE NCC","report_date":"2016-06-24","source":"transfers","raw_action":"TRANSFER","raw_line":null,"resource_type":"ipv4","resource":"91.207.79.0/24","start":"91.207.79.0","end":"91.207.79.255","classification":"INTRA_RIR_TRANSFER","classification_label":"Intra-RIPE NCC transfer","confidence":"CONFIRMED","source_rir":"RIPE NCC","recipient_rir":"RIPE NCC","source_organization":"Joint Stock Company \"New-Tech\"","recipient_organization":"Federal state budgetary institution Center expertizy y koordinacii","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:11+00:00","page":"https://rirtracker.com/ip/91.207.79.0-91.207.79.255/#e-b6c0bb4a75f2d434","report_page":"https://rirtracker.com/ripe/reports/2016-06-24/","evidence_url":"https://rirtracker.com/api/v1/resources/ip/91.207.79.0-91.207.79.255.json","observed":"Transfer: Joint Stock Company \"New-Tech\" (RIPE NCC) to Federal state budgetary institution Center expertizy y koordinacii (RIPE NCC)","explanation":"The RIPE NCC's transfer log records a transfer from Joint Stock Company \"New-Tech\" (RIPE NCC) to Federal state budgetary institution Center expertizy y koordinacii (RIPE NCC) on 2016-06-24 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 2016-06-24 19:00 UTC, Joint Stock Company \"New-Tech\" (RIPE NCC) to Federal state budgetary institution Center expertizy y koordinacii (RIPE NCC); resources moved: 91.207.79.0/24"},{"type":"delegated_before","url":"https://ftp.ripe.net/pub/stats/ripencc/2016/delegated-ripencc-extended-20160623.bz2","retrieved_at":"2026-10-12T20:58:25+00:00","summary":"RIPE NCC delegated statistics 2016-06-23 (produced 2016-06-23T21:59:59+00:00), before the change: assigned (dated 2008-10-01)"},{"type":"delegated_after","url":"https://ftp.ripe.net/pub/stats/ripencc/2016/delegated-ripencc-extended-20160624.bz2","retrieved_at":"2026-10-12T20:58:28+00:00","summary":"RIPE NCC delegated statistics 2016-06-24 (produced 2016-06-24T21:59:59+00:00), after the change: assigned (dated 2008-10-01)"}]}],"classification_history":{"178d1d2b651f4a34":[{"raw_change_id":109619,"classification_code":"MERGER_ACQUISITION","confidence":"CONFIRMED","classifier_version":"1.3.0","classified_at":"2026-10-13T03:06:53+00:00","current":0,"public_explanation":"The RIPE NCC's transfer log records a merger, acquisition or reorganization from Bitfoam Oy (RIPE NCC) to Clausal Computing Oy (RIPE NCC) on 2024-11-06 19:00 UTC. The registration changed hands; it is not a new allocation from the RIPE NCC."},{"raw_change_id":109619,"classification_code":"MERGER_ACQUISITION","confidence":"CONFIRMED","classifier_version":"1.3.1","classified_at":"2026-10-13T08:04:49+00:00","current":0,"public_explanation":"The RIPE NCC's transfer log records a merger, acquisition or reorganization from Bitfoam Oy (RIPE NCC) to Clausal Computing Oy (RIPE NCC) on 2024-11-06 19:00 UTC. The registration changed hands; it is not a new allocation from the RIPE NCC."},{"raw_change_id":109619,"classification_code":"MERGER_ACQUISITION","confidence":"CONFIRMED","classifier_version":"1.3.2","classified_at":"2026-10-13T14:47:19+00:00","current":0,"public_explanation":"The RIPE NCC's transfer log records a merger, acquisition or reorganization from Bitfoam Oy (RIPE NCC) to Clausal Computing Oy (RIPE NCC) on 2024-11-06 19:00 UTC. The registration changed hands; it is not a new allocation from the RIPE NCC."},{"raw_change_id":109619,"classification_code":"MERGER_ACQUISITION","confidence":"CONFIRMED","classifier_version":"1.4.0","classified_at":"2026-10-13T23:50:14+00:00","current":1,"public_explanation":"The RIPE NCC's transfer log records a merger, acquisition or reorganization from Bitfoam Oy (RIPE NCC) to Clausal Computing Oy (RIPE NCC) on 2024-11-06 19:00 UTC. The registration changed hands; it is not a new allocation from the RIPE NCC."}],"d692a0183e537eb7":[{"raw_change_id":490592,"classification_code":"APPARENT_REISSUANCE","confidence":"STRONG_INFERENCE","classifier_version":"1.3.0","classified_at":"2026-10-13T06:20:29+00:00","current":0,"public_explanation":"No transfer record matches. The RIPE NCC's statistics show it available on 2023-10-01 and allocated (dated 2023-10-02) on 2023-10-02. The tracker saw this range released from hold on 2023-09-30 (91.207.79.0/24), so it appears to have been issued again from the RIPE NCC's pool."},{"raw_change_id":490592,"classification_code":"APPARENT_REISSUANCE","confidence":"STRONG_INFERENCE","classifier_version":"1.3.1","classified_at":"2026-10-13T08:24:18+00:00","current":0,"public_explanation":"No transfer record matches. The RIPE NCC's statistics show it available on 2023-10-01 and allocated (dated 2023-10-02) on 2023-10-02. The tracker saw this range released from hold on 2023-09-30 (91.207.79.0/24), so it appears to have been issued again from the RIPE NCC's pool."},{"raw_change_id":490592,"classification_code":"APPARENT_REISSUANCE","confidence":"STRONG_INFERENCE","classifier_version":"1.3.2","classified_at":"2026-10-13T15:08:29+00:00","current":0,"public_explanation":"No transfer record matches. The RIPE NCC's statistics show it available on 2023-10-01 and allocated (dated 2023-10-02) on 2023-10-02. The tracker saw this range released from hold on 2023-09-30 (91.207.79.0/24), so it appears to have been issued again from the RIPE NCC's pool."},{"raw_change_id":490592,"classification_code":"APPARENT_REISSUANCE","confidence":"STRONG_INFERENCE","classifier_version":"1.4.0","classified_at":"2026-10-14T00:13:59+00:00","current":1,"public_explanation":"No transfer record matches. The RIPE NCC's statistics show it available on 2023-10-01 and allocated (dated 2023-10-02) on 2023-10-02. The tracker saw this range released from hold on 2023-09-30 (91.207.79.0/24), so it appears to have been issued again from the RIPE NCC's pool."}],"fdeef2ce9fc43d7b":[{"raw_change_id":490561,"classification_code":"HOLD_RELEASED","confidence":"STRONG_INFERENCE","classifier_version":"1.3.0","classified_at":"2026-10-13T06:20:28+00:00","current":0,"public_explanation":"The RIPE NCC's statistics show it reserved on 2023-09-29 and available on 2023-09-30. The RIPE NCC moved it from its reserved (held) records to the status it calls 'available'. The tracker saw it removed from registration on 2023-04-03, 180 days earlier. That is the RIPE NCC's own label: whether and when it is reissued is not confirmed."},{"raw_change_id":490561,"classification_code":"HOLD_RELEASED","confidence":"STRONG_INFERENCE","classifier_version":"1.3.1","classified_at":"2026-10-13T08:24:18+00:00","current":0,"public_explanation":"The RIPE NCC's statistics show it reserved on 2023-09-29 and available on 2023-09-30. The RIPE NCC moved it from its reserved (held) records to the status it calls 'available'. The tracker saw it removed from registration on 2023-04-03, 180 days earlier. That is the RIPE NCC's own label: whether and when it is reissued is not confirmed."},{"raw_change_id":490561,"classification_code":"HOLD_RELEASED","confidence":"STRONG_INFERENCE","classifier_version":"1.3.2","classified_at":"2026-10-13T15:08:29+00:00","current":0,"public_explanation":"The RIPE NCC's statistics show it reserved on 2023-09-29 and available on 2023-09-30. The RIPE NCC moved it from its reserved (held) records to the status it calls 'available'. The tracker saw it removed from registration on 2023-04-03, 180 days earlier. That is the RIPE NCC's own label: whether and when it is reissued is not confirmed."},{"raw_change_id":490561,"classification_code":"HOLD_RELEASED","confidence":"STRONG_INFERENCE","classifier_version":"1.4.0","classified_at":"2026-10-14T00:13:59+00:00","current":1,"public_explanation":"The RIPE NCC's statistics show it reserved on 2023-09-29 and available on 2023-09-30. The RIPE NCC moved it from its reserved (held) records to the status it calls 'available'. The tracker saw it removed from registration on 2023-04-03, 180 days earlier. That is the RIPE NCC's own label: whether and when it is reissued is not confirmed."}],"0bca7ac7a49b1ad6":[{"raw_change_id":480220,"classification_code":"REMOVED_REASON_UNKNOWN","confidence":"STRONG_INFERENCE","classifier_version":"1.3.0","classified_at":"2026-10-13T06:14:38+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 2008-10-01) on 2023-04-02 and reserved on 2023-04-03. 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 2023-09-30. This does not confirm availability."},{"raw_change_id":480220,"classification_code":"REMOVED_REASON_UNKNOWN","confidence":"STRONG_INFERENCE","classifier_version":"1.3.1","classified_at":"2026-10-13T08:23:43+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 2008-10-01) on 2023-04-02 and reserved on 2023-04-03. 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 2023-09-30. This does not confirm availability."},{"raw_change_id":480220,"classification_code":"REMOVED_REASON_UNKNOWN","confidence":"STRONG_INFERENCE","classifier_version":"1.3.2","classified_at":"2026-10-13T15:07:52+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 2008-10-01) on 2023-04-02 and reserved on 2023-04-03. 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 2023-09-30. This does not confirm availability."},{"raw_change_id":480220,"classification_code":"REMOVED_REASON_UNKNOWN","confidence":"STRONG_INFERENCE","classifier_version":"1.4.0","classified_at":"2026-10-14T00:13:15+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 2008-10-01) on 2023-04-02 and reserved on 2023-04-03. 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 2023-09-30. This does not confirm availability."}],"b6c0bb4a75f2d434":[{"raw_change_id":50025,"classification_code":"INTRA_RIR_TRANSFER","confidence":"CONFIRMED","classifier_version":"1.3.0","classified_at":"2026-10-13T02:41:43+00:00","current":0,"public_explanation":"The RIPE NCC's transfer log records a transfer from Joint Stock Company \"New-Tech\" (RIPE NCC) to Federal state budgetary institution Center expertizy y koordinacii (RIPE NCC) on 2016-06-24 19:00 UTC. The registration changed hands; it is not a new allocation from the RIPE NCC."},{"raw_change_id":50025,"classification_code":"INTRA_RIR_TRANSFER","confidence":"CONFIRMED","classifier_version":"1.3.1","classified_at":"2026-10-13T08:02:20+00:00","current":0,"public_explanation":"The RIPE NCC's transfer log records a transfer from Joint Stock Company \"New-Tech\" (RIPE NCC) to Federal state budgetary institution Center expertizy y koordinacii (RIPE NCC) on 2016-06-24 19:00 UTC. The registration changed hands; it is not a new allocation from the RIPE NCC."},{"raw_change_id":50025,"classification_code":"INTRA_RIR_TRANSFER","confidence":"CONFIRMED","classifier_version":"1.3.2","classified_at":"2026-10-13T14:44:34+00:00","current":0,"public_explanation":"The RIPE NCC's transfer log records a transfer from Joint Stock Company \"New-Tech\" (RIPE NCC) to Federal state budgetary institution Center expertizy y koordinacii (RIPE NCC) on 2016-06-24 19:00 UTC. The registration changed hands; it is not a new allocation from the RIPE NCC."},{"raw_change_id":50025,"classification_code":"INTRA_RIR_TRANSFER","confidence":"CONFIRMED","classifier_version":"1.4.0","classified_at":"2026-10-13T23:47:11+00:00","current":1,"public_explanation":"The RIPE NCC's transfer log records a transfer from Joint Stock Company \"New-Tech\" (RIPE NCC) to Federal state budgetary institution Center expertizy y koordinacii (RIPE NCC) on 2016-06-24 19:00 UTC. The registration changed hands; it is not a new allocation from the RIPE NCC."}]},"arin_statistics_now":{"status":"not listed"}}