{"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":"185.172.176.0/22","resource_type":"ipv4","page":"https://rirtracker.com/ip/185.172.176.0-185.172.179.255/","statistics_now":{"registry":"LACNIC","status":"allocated (dated 2025-03-25)"},"current_holder":{"rir":"LACNIC","org":null,"how":"LACNIC's latest statistics and the latest transfer record"},"rdap_snapshots":[],"transfers":[{"id":112062,"date":"2025-03-25T19:00:00Z","type":"RESOURCE_TRANSFER","source_rir":"RIPE NCC","recipient_rir":"LACNIC","source_org":"DIGAMAX GESTION DE TELECOMUNICACIONES SL","recipient_org":null,"range":"185.172.176.0/22","log":"RIPE NCC"},{"id":133204,"date":"2025-03-25T11:00:00Z","type":"RESOURCE_TRANSFER","source_rir":"RIPE NCC","recipient_rir":"LACNIC","source_org":"DIGAMAX GESTION DE TELECOMUNICACIONES SL","recipient_org":"BRITEL S.A.","range":"185.172.176.0/22","log":"LACNIC"}],"events":[{"event_id":"961dfa016301e762","registry":"RIPE NCC","report_date":"2025-03-25","source":"transfers","raw_action":"TRANSFER","raw_line":null,"resource_type":"ipv4","resource":"185.172.176.0/22","start":"185.172.176.0","end":"185.172.179.255","classification":"INTER_RIR_TRANSFER_OUT","classification_label":"Inter-RIR transfer out of the RIPE NCC","confidence":"CONFIRMED","source_rir":"RIPE NCC","recipient_rir":"LACNIC","source_organization":"DIGAMAX GESTION DE TELECOMUNICACIONES SL","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:50:24+00:00","page":"https://rirtracker.com/ip/185.172.176.0-185.172.179.255/#e-961dfa016301e762","report_page":"https://rirtracker.com/ripe/reports/2025-03-25/","evidence_url":"https://rirtracker.com/api/v1/resources/ip/185.172.176.0-185.172.179.255.json","observed":"Transfer: DIGAMAX GESTION DE TELECOMUNICACIONES SL (RIPE NCC) to (no name) (LACNIC)","same_transfer_as":"cef2a82f3631fd20","explanation":"The RIPE NCC's transfer log records a transfer from DIGAMAX GESTION DE TELECOMUNICACIONES SL (RIPE NCC) to an unnamed organization (LACNIC) on 2025-03-25 19:00 UTC: it left the RIPE NCC for LACNIC. 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 2025-03-25 19:00 UTC, DIGAMAX GESTION DE TELECOMUNICACIONES SL (RIPE NCC) to (no name) (LACNIC); resources moved: 185.172.176.0/22"},{"type":"delegated_before","url":"https://ftp.ripe.net/pub/stats/ripencc/2025/delegated-ripencc-extended-20250324.bz2","retrieved_at":"2026-10-13T00:55:19+00:00","summary":"RIPE NCC delegated statistics 2025-03-24 (produced 2025-03-24T22:59:59+00:00), before the change: allocated (dated 2016-10-12)"},{"type":"delegated_after","url":"https://ftp.ripe.net/pub/stats/ripencc/2025/delegated-ripencc-extended-20250325.bz2","retrieved_at":"2026-10-13T00:55:45+00:00","summary":"RIPE NCC delegated statistics 2025-03-25 (produced 2025-03-25T22:59:59+00:00), after the change: not listed"}]},{"event_id":"cef2a82f3631fd20","registry":"LACNIC","report_date":"2025-03-25","source":"transfers","raw_action":"TRANSFER","raw_line":null,"resource_type":"ipv4","resource":"185.172.176.0/22","start":"185.172.176.0","end":"185.172.179.255","classification":"INTER_RIR_TRANSFER_IN","classification_label":"Inter-RIR transfer into LACNIC","confidence":"CONFIRMED","source_rir":"RIPE NCC","recipient_rir":"LACNIC","source_organization":"DIGAMAX GESTION DE TELECOMUNICACIONES SL","recipient_organization":"BRITEL S.A.","inventory_effect":"Transferred into LACNIC administration; not a new issuance","inventory_effect_code":"TRANSFER_IN","provisional":false,"classifier_version":"1.4.0","classified_at":"2026-10-13T23:46:28+00:00","page":"https://rirtracker.com/ip/185.172.176.0-185.172.179.255/#e-cef2a82f3631fd20","report_page":"https://rirtracker.com/lacnic/reports/2025-03-25/","evidence_url":"https://rirtracker.com/api/v1/resources/ip/185.172.176.0-185.172.179.255.json","observed":"Transfer: DIGAMAX GESTION DE TELECOMUNICACIONES SL (RIPE NCC) to BRITEL S.A. (LACNIC)","same_transfer_as":"961dfa016301e762","explanation":"LACNIC's transfer log records a transfer from DIGAMAX GESTION DE TELECOMUNICACIONES SL (RIPE NCC) to BRITEL S.A. (LACNIC) on 2025-03-25 11:00 UTC: it came to LACNIC from the RIPE NCC. It was already issued by another registry, so this is not a new issuance.","evidence":[{"type":"transfer","url":"https://ftp.lacnic.net/pub/stats/lacnic/transfers/transfers_latest.json","retrieved_at":"2026-10-13T13:57:38+00:00","summary":"Transfer log: RESOURCE_TRANSFER on 2025-03-25 11:00 UTC, DIGAMAX GESTION DE TELECOMUNICACIONES SL (RIPE NCC) to BRITEL S.A. (LACNIC); resources moved: 185.172.176.0/22"},{"type":"delegated_before","url":"https://ftp.lacnic.net/pub/stats/lacnic/archive/2025/delegated-lacnic-extended-20250324","retrieved_at":"2026-10-13T02:04:41+00:00","summary":"LACNIC delegated statistics 2025-03-24, before the change: not listed"},{"type":"delegated_after","url":"https://ftp.lacnic.net/pub/stats/lacnic/archive/2025/delegated-lacnic-extended-20250325","retrieved_at":"2026-10-13T02:04:54+00:00","summary":"LACNIC delegated statistics 2025-03-25, after the change: allocated (dated 2025-03-25)"}]},{"event_id":"5b9df241a4af4235","registry":"RIPE NCC","report_date":"2016-10-12","source":"statistics","raw_action":"ADDED","raw_line":null,"resource_type":"ipv4","resource":"185.172.176.0/22","start":"185.172.176.0","end":"185.172.179.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 RIPE NCC-controlled inventory","inventory_effect_code":"ISSUED","provisional":false,"classifier_version":"1.4.0","classified_at":"2026-10-14T00:01:42+00:00","page":"https://rirtracker.com/ip/185.172.176.0-185.172.179.255/#e-5b9df241a4af4235","report_page":"https://rirtracker.com/ripe/reports/2016-10-12/","evidence_url":"https://rirtracker.com/api/v1/resources/ip/185.172.176.0-185.172.179.255.json","observed":"185.172.176.0/22 available on 2016-10-11, allocated on 2016-10-12","explanation":"No transfer record matches. The RIPE NCC's statistics show it available on 2016-10-11 and allocated (dated 2016-10-12) on 2016-10-12. It moved from the RIPE NCC's unissued pool to an active registration dated around that day, so it appears to be newly issued by the RIPE NCC.","evidence":[{"type":"statistics_diff","url":"https://ftp.ripe.net/pub/stats/ripencc/2016/delegated-ripencc-extended-20161012.bz2","retrieved_at":"2026-10-12T21:05:46+00:00","summary":"Found by comparing the RIPE NCC's daily statistics: 185.172.176.0/22 available on 2016-10-11, allocated on 2016-10-12"},{"type":"delegated_before","url":"https://ftp.ripe.net/pub/stats/ripencc/2016/delegated-ripencc-extended-20161011.bz2","retrieved_at":"2026-10-12T21:05:43+00:00","summary":"RIPE NCC delegated statistics 2016-10-11 (produced 2016-10-11T21:59:59+00:00), before the change: available"},{"type":"delegated_after","url":"https://ftp.ripe.net/pub/stats/ripencc/2016/delegated-ripencc-extended-20161012.bz2","retrieved_at":"2026-10-12T21:05:46+00:00","summary":"RIPE NCC delegated statistics 2016-10-12 (produced 2016-10-12T21:59:59+00:00), after the change: allocated (dated 2016-10-12)"}]}],"classification_history":{"961dfa016301e762":[{"raw_change_id":112827,"classification_code":"INTER_RIR_TRANSFER_OUT","confidence":"CONFIRMED","classifier_version":"1.3.0","classified_at":"2026-10-13T03:08:19+00:00","current":0,"public_explanation":"The RIPE NCC's transfer log records a transfer from DIGAMAX GESTION DE TELECOMUNICACIONES SL (RIPE NCC) to an unnamed organization (LACNIC) on 2025-03-25 19:00 UTC: it left the RIPE NCC for LACNIC. It is not a new allocation and is not offered to RIPE NCC applicants."},{"raw_change_id":112827,"classification_code":"INTER_RIR_TRANSFER_OUT","confidence":"CONFIRMED","classifier_version":"1.3.1","classified_at":"2026-10-13T08:04:57+00:00","current":0,"public_explanation":"The RIPE NCC's transfer log records a transfer from DIGAMAX GESTION DE TELECOMUNICACIONES SL (RIPE NCC) to an unnamed organization (LACNIC) on 2025-03-25 19:00 UTC: it left the RIPE NCC for LACNIC. It is not a new allocation and is not offered to RIPE NCC applicants."},{"raw_change_id":112827,"classification_code":"INTER_RIR_TRANSFER_OUT","confidence":"CONFIRMED","classifier_version":"1.3.2","classified_at":"2026-10-13T14:47:28+00:00","current":0,"public_explanation":"The RIPE NCC's transfer log records a transfer from DIGAMAX GESTION DE TELECOMUNICACIONES SL (RIPE NCC) to an unnamed organization (LACNIC) on 2025-03-25 19:00 UTC: it left the RIPE NCC for LACNIC. It is not a new allocation and is not offered to RIPE NCC applicants."},{"raw_change_id":112827,"classification_code":"INTER_RIR_TRANSFER_OUT","confidence":"CONFIRMED","classifier_version":"1.4.0","classified_at":"2026-10-13T23:50:24+00:00","current":1,"public_explanation":"The RIPE NCC's transfer log records a transfer from DIGAMAX GESTION DE TELECOMUNICACIONES SL (RIPE NCC) to an unnamed organization (LACNIC) on 2025-03-25 19:00 UTC: it left the RIPE NCC for LACNIC. It is not a new allocation and is not offered to RIPE NCC applicants."}],"cef2a82f3631fd20":[{"raw_change_id":31634,"classification_code":"INTER_RIR_TRANSFER_IN","confidence":"CONFIRMED","classifier_version":"1.3.0","classified_at":"2026-10-13T02:34:04+00:00","current":0,"public_explanation":"LACNIC's transfer log records a transfer from DIGAMAX GESTION DE TELECOMUNICACIONES SL (RIPE NCC) to BRITEL S.A. (LACNIC) on 2025-03-25 11:00 UTC: it came to LACNIC from the RIPE NCC. It was already issued by another registry, so this is not a new issuance."},{"raw_change_id":31634,"classification_code":"INTER_RIR_TRANSFER_IN","confidence":"CONFIRMED","classifier_version":"1.3.1","classified_at":"2026-10-13T08:01:45+00:00","current":0,"public_explanation":"LACNIC's transfer log records a transfer from DIGAMAX GESTION DE TELECOMUNICACIONES SL (RIPE NCC) to BRITEL S.A. (LACNIC) on 2025-03-25 11:00 UTC: it came to LACNIC from the RIPE NCC. It was already issued by another registry, so this is not a new issuance."},{"raw_change_id":31634,"classification_code":"INTER_RIR_TRANSFER_IN","confidence":"CONFIRMED","classifier_version":"1.3.2","classified_at":"2026-10-13T14:43:54+00:00","current":0,"public_explanation":"LACNIC's transfer log records a transfer from DIGAMAX GESTION DE TELECOMUNICACIONES SL (RIPE NCC) to BRITEL S.A. (LACNIC) on 2025-03-25 11:00 UTC: it came to LACNIC from the RIPE NCC. It was already issued by another registry, so this is not a new issuance."},{"raw_change_id":31634,"classification_code":"INTER_RIR_TRANSFER_IN","confidence":"CONFIRMED","classifier_version":"1.4.0","classified_at":"2026-10-13T23:46:28+00:00","current":1,"public_explanation":"LACNIC's transfer log records a transfer from DIGAMAX GESTION DE TELECOMUNICACIONES SL (RIPE NCC) to BRITEL S.A. (LACNIC) on 2025-03-25 11:00 UTC: it came to LACNIC from the RIPE NCC. It was already issued by another registry, so this is not a new issuance."}],"5b9df241a4af4235":[{"raw_change_id":313745,"classification_code":"APPARENT_NEW_ISSUANCE","confidence":"STRONG_INFERENCE","classifier_version":"1.3.0","classified_at":"2026-10-13T05:02:02+00:00","current":0,"public_explanation":"No transfer record matches. The RIPE NCC's statistics show it available on 2016-10-11 and allocated (dated 2016-10-12) on 2016-10-12. It moved from the RIPE NCC's unissued pool to an active registration dated around that day, so it appears to be newly issued by the RIPE NCC."},{"raw_change_id":313745,"classification_code":"APPARENT_NEW_ISSUANCE","confidence":"STRONG_INFERENCE","classifier_version":"1.3.1","classified_at":"2026-10-13T08:14:16+00:00","current":0,"public_explanation":"No transfer record matches. The RIPE NCC's statistics show it available on 2016-10-11 and allocated (dated 2016-10-12) on 2016-10-12. It moved from the RIPE NCC's unissued pool to an active registration dated around that day, so it appears to be newly issued by the RIPE NCC."},{"raw_change_id":313745,"classification_code":"APPARENT_NEW_ISSUANCE","confidence":"STRONG_INFERENCE","classifier_version":"1.3.2","classified_at":"2026-10-13T14:57:42+00:00","current":0,"public_explanation":"No transfer record matches. The RIPE NCC's statistics show it available on 2016-10-11 and allocated (dated 2016-10-12) on 2016-10-12. It moved from the RIPE NCC's unissued pool to an active registration dated around that day, so it appears to be newly issued by the RIPE NCC."},{"raw_change_id":313745,"classification_code":"APPARENT_NEW_ISSUANCE","confidence":"STRONG_INFERENCE","classifier_version":"1.4.0","classified_at":"2026-10-14T00:01:42+00:00","current":1,"public_explanation":"No transfer record matches. The RIPE NCC's statistics show it available on 2016-10-11 and allocated (dated 2016-10-12) on 2016-10-12. It moved from the RIPE NCC's unissued pool to an active registration dated around that day, so it appears to be newly issued by the RIPE NCC."}]},"arin_statistics_now":{"status":"not listed"}}