{"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":"AS28851","resource_type":"asn","page":"https://rirtracker.com/asn/28851/","statistics_now":{"registry":"RIPE NCC","status":"available"},"current_holder":{"rir":"RIPE NCC","org":null,"how":"The RIPE NCC's latest statistics"},"rdap_snapshots":[],"transfers":[{"id":88802,"date":"2022-07-28T19:00:00Z","type":"MERGER_ACQUISITION","source_rir":"RIPE NCC","recipient_rir":"RIPE NCC","source_org":"Nordic Telecom s.r.o","recipient_org":"Nordic Telecom Regional s.r.o.","range":"AS28851","log":"RIPE NCC"},{"id":72271,"date":"2020-09-18T19:00:00Z","type":"RESOURCE_TRANSFER","source_rir":"RIPE NCC","recipient_rir":"RIPE NCC","source_org":"Fortech s.r.o.","recipient_org":"Nordic Telecom s.r.o","range":"AS28851","log":"RIPE NCC"}],"events":[{"event_id":"e3dbfa6110d12abb","registry":"RIPE NCC","report_date":"2025-08-10","source":"statistics","raw_action":"RELEASED","raw_line":null,"resource_type":"asn","resource":"AS28851","start":28851,"end":28851,"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:16:52+00:00","page":"https://rirtracker.com/asn/28851/#e-e3dbfa6110d12abb","report_page":"https://rirtracker.com/ripe/reports/2025-08-10/","evidence_url":"https://rirtracker.com/api/v1/resources/asn/28851.json","observed":"AS28851 reserved on 2025-08-09, available on 2025-08-10","explanation":"The RIPE NCC's statistics show it reserved on 2025-08-09 and available on 2025-08-10. The RIPE NCC moved it from its reserved (held) records to the status it calls 'available'. The tracker saw it removed from registration on 2025-02-11, 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/2025/delegated-ripencc-extended-20250810.bz2","retrieved_at":"2026-10-13T01:06:04+00:00","summary":"Found by comparing the RIPE NCC's daily statistics: AS28851 reserved on 2025-08-09, available on 2025-08-10"},{"type":"delegated_before","url":"https://ftp.ripe.net/pub/stats/ripencc/2025/delegated-ripencc-extended-20250809.bz2","retrieved_at":"2026-10-13T01:06:01+00:00","summary":"RIPE NCC delegated statistics 2025-08-09 (produced 2025-08-09T21:59:59+00:00), before the change: reserved"},{"type":"delegated_after","url":"https://ftp.ripe.net/pub/stats/ripencc/2025/delegated-ripencc-extended-20250810.bz2","retrieved_at":"2026-10-13T01:06:04+00:00","summary":"RIPE NCC delegated statistics 2025-08-10 (produced 2025-08-10T21:59:59+00:00), after the change: available"}]},{"event_id":"daa8245a0d0fce1e","registry":"RIPE NCC","report_date":"2025-02-11","source":"statistics","raw_action":"REMOVED","raw_line":null,"resource_type":"asn","resource":"AS28851","start":28851,"end":28851,"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:59+00:00","page":"https://rirtracker.com/asn/28851/#e-daa8245a0d0fce1e","report_page":"https://rirtracker.com/ripe/reports/2025-02-11/","evidence_url":"https://rirtracker.com/api/v1/resources/asn/28851.json","observed":"AS28851 allocated on 2025-02-10, reserved on 2025-02-11","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":"2025-08-10","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 2003-03-14) on 2025-02-10 and reserved on 2025-02-11. Public sources do not distinguish a voluntary return, revocation, or reclamation. The RIPE NCC holds returned, revoked and reclaimed ASNs for 180 days (six months), or longer while still routed, before reissuing them, so the estimated hold end is 2025-08-10. This does not confirm availability.","evidence":[{"type":"statistics_diff","url":"https://ftp.ripe.net/pub/stats/ripencc/2025/delegated-ripencc-extended-20250211.bz2","retrieved_at":"2026-10-13T00:52:29+00:00","summary":"Found by comparing the RIPE NCC's daily statistics: AS28851 allocated on 2025-02-10, reserved on 2025-02-11"},{"type":"delegated_before","url":"https://ftp.ripe.net/pub/stats/ripencc/2025/delegated-ripencc-extended-20250210.bz2","retrieved_at":"2026-10-13T00:52:05+00:00","summary":"RIPE NCC delegated statistics 2025-02-10 (produced 2025-02-10T22:59:59+00:00), before the change: allocated (dated 2003-03-14)"},{"type":"delegated_after","url":"https://ftp.ripe.net/pub/stats/ripencc/2025/delegated-ripencc-extended-20250211.bz2","retrieved_at":"2026-10-13T00:52:29+00:00","summary":"RIPE NCC delegated statistics 2025-02-11 (produced 2025-02-11T22:59:59+00:00), after the change: reserved"}]},{"event_id":"d737fb8c715f8b54","registry":"RIPE NCC","report_date":"2022-07-28","source":"transfers","raw_action":"TRANSFER","raw_line":null,"resource_type":"asn","resource":"AS28851","start":28851,"end":28851,"classification":"MERGER_ACQUISITION","classification_label":"Merger/acquisition or reorganization","confidence":"CONFIRMED","source_rir":"RIPE NCC","recipient_rir":"RIPE NCC","source_organization":"Nordic Telecom s.r.o","recipient_organization":"Nordic Telecom Regional s.r.o.","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:49:10+00:00","page":"https://rirtracker.com/asn/28851/#e-d737fb8c715f8b54","report_page":"https://rirtracker.com/ripe/reports/2022-07-28/","evidence_url":"https://rirtracker.com/api/v1/resources/asn/28851.json","observed":"Merger/acquisition: Nordic Telecom s.r.o (RIPE NCC) to Nordic Telecom Regional s.r.o. (RIPE NCC)","explanation":"The RIPE NCC's transfer log records a merger, acquisition or reorganization from Nordic Telecom s.r.o (RIPE NCC) to Nordic Telecom Regional s.r.o. (RIPE NCC) on 2022-07-28 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 2022-07-28 19:00 UTC, Nordic Telecom s.r.o (RIPE NCC) to Nordic Telecom Regional s.r.o. (RIPE NCC); resources moved: AS28851"},{"type":"delegated_before","url":"https://ftp.ripe.net/pub/stats/ripencc/2022/delegated-ripencc-extended-20220727.bz2","retrieved_at":"2026-10-12T23:40:29+00:00","summary":"RIPE NCC delegated statistics 2022-07-27 (produced 2022-07-27T21:59:59+00:00), before the change: allocated (dated 2003-03-14)"},{"type":"delegated_after","url":"https://ftp.ripe.net/pub/stats/ripencc/2022/delegated-ripencc-extended-20220728.bz2","retrieved_at":"2026-10-12T23:40:32+00:00","summary":"RIPE NCC delegated statistics 2022-07-28 (produced 2022-07-28T21:59:59+00:00), after the change: allocated (dated 2003-03-14)"}]},{"event_id":"38eaab402047eec7","registry":"RIPE NCC","report_date":"2020-09-18","source":"transfers","raw_action":"TRANSFER","raw_line":null,"resource_type":"asn","resource":"AS28851","start":28851,"end":28851,"classification":"INTRA_RIR_TRANSFER","classification_label":"Intra-RIPE NCC transfer","confidence":"CONFIRMED","source_rir":"RIPE NCC","recipient_rir":"RIPE NCC","source_organization":"Fortech s.r.o.","recipient_organization":"Nordic Telecom s.r.o","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:48:18+00:00","page":"https://rirtracker.com/asn/28851/#e-38eaab402047eec7","report_page":"https://rirtracker.com/ripe/reports/2020-09-18/","evidence_url":"https://rirtracker.com/api/v1/resources/asn/28851.json","observed":"Transfer: Fortech s.r.o. (RIPE NCC) to Nordic Telecom s.r.o (RIPE NCC)","explanation":"The RIPE NCC's transfer log records a transfer from Fortech s.r.o. (RIPE NCC) to Nordic Telecom s.r.o (RIPE NCC) on 2020-09-18 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 2020-09-18 19:00 UTC, Fortech s.r.o. (RIPE NCC) to Nordic Telecom s.r.o (RIPE NCC); resources moved: AS28851"},{"type":"delegated_before","url":"https://ftp.ripe.net/pub/stats/ripencc/2020/delegated-ripencc-extended-20200917.bz2","retrieved_at":"2026-10-12T22:49:44+00:00","summary":"RIPE NCC delegated statistics 2020-09-17 (produced 2020-09-17T21:59:59+00:00), before the change: allocated (dated 2003-03-14)"},{"type":"delegated_after","url":"https://ftp.ripe.net/pub/stats/ripencc/2020/delegated-ripencc-extended-20200918.bz2","retrieved_at":"2026-10-12T22:49:47+00:00","summary":"RIPE NCC delegated statistics 2020-09-18 (produced 2020-09-18T21:59:59+00:00), after the change: allocated (dated 2003-03-14)"}]}],"classification_history":{"e3dbfa6110d12abb":[{"raw_change_id":526201,"classification_code":"HOLD_RELEASED","confidence":"STRONG_INFERENCE","classifier_version":"1.3.0","classified_at":"2026-10-13T06:37:04+00:00","current":0,"public_explanation":"The RIPE NCC's statistics show it reserved on 2025-08-09 and available on 2025-08-10. The RIPE NCC moved it from its reserved (held) records to the status it calls 'available'. The tracker saw it removed from registration on 2025-02-11, 180 days earlier. That is the RIPE NCC's own label: whether and when it is reissued is not confirmed."},{"raw_change_id":526201,"classification_code":"HOLD_RELEASED","confidence":"STRONG_INFERENCE","classifier_version":"1.3.1","classified_at":"2026-10-13T08:26:39+00:00","current":0,"public_explanation":"The RIPE NCC's statistics show it reserved on 2025-08-09 and available on 2025-08-10. The RIPE NCC moved it from its reserved (held) records to the status it calls 'available'. The tracker saw it removed from registration on 2025-02-11, 180 days earlier. That is the RIPE NCC's own label: whether and when it is reissued is not confirmed."},{"raw_change_id":526201,"classification_code":"HOLD_RELEASED","confidence":"STRONG_INFERENCE","classifier_version":"1.3.2","classified_at":"2026-10-13T15:11:01+00:00","current":0,"public_explanation":"The RIPE NCC's statistics show it reserved on 2025-08-09 and available on 2025-08-10. The RIPE NCC moved it from its reserved (held) records to the status it calls 'available'. The tracker saw it removed from registration on 2025-02-11, 180 days earlier. That is the RIPE NCC's own label: whether and when it is reissued is not confirmed."},{"raw_change_id":526201,"classification_code":"HOLD_RELEASED","confidence":"STRONG_INFERENCE","classifier_version":"1.4.0","classified_at":"2026-10-14T00:16:52+00:00","current":1,"public_explanation":"The RIPE NCC's statistics show it reserved on 2025-08-09 and available on 2025-08-10. The RIPE NCC moved it from its reserved (held) records to the status it calls 'available'. The tracker saw it removed from registration on 2025-02-11, 180 days earlier. That is the RIPE NCC's own label: whether and when it is reissued is not confirmed."}],"daa8245a0d0fce1e":[{"raw_change_id":517123,"classification_code":"REMOVED_REASON_UNKNOWN","confidence":"STRONG_INFERENCE","classifier_version":"1.3.0","classified_at":"2026-10-13T06:33:10+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 2003-03-14) on 2025-02-10 and reserved on 2025-02-11. Public sources do not distinguish a voluntary return, revocation, or reclamation. The RIPE NCC holds returned, revoked and reclaimed ASNs for 180 days (six months), or longer while still routed, before reissuing them, so the earliest estimated hold expiration is 2025-08-10. This does not confirm availability."},{"raw_change_id":517123,"classification_code":"REMOVED_REASON_UNKNOWN","confidence":"STRONG_INFERENCE","classifier_version":"1.3.1","classified_at":"2026-10-13T08:25:59+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 2003-03-14) on 2025-02-10 and reserved on 2025-02-11. Public sources do not distinguish a voluntary return, revocation, or reclamation. The RIPE NCC holds returned, revoked and reclaimed ASNs for 180 days (six months), or longer while still routed, before reissuing them, so the earliest estimated hold expiration is 2025-08-10. This does not confirm availability."},{"raw_change_id":517123,"classification_code":"REMOVED_REASON_UNKNOWN","confidence":"STRONG_INFERENCE","classifier_version":"1.3.2","classified_at":"2026-10-13T15:10:18+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 2003-03-14) on 2025-02-10 and reserved on 2025-02-11. Public sources do not distinguish a voluntary return, revocation, or reclamation. The RIPE NCC holds returned, revoked and reclaimed ASNs for 180 days (six months), or longer while still routed, before reissuing them, so the earliest estimated hold expiration is 2025-08-10. This does not confirm availability."},{"raw_change_id":517123,"classification_code":"REMOVED_REASON_UNKNOWN","confidence":"STRONG_INFERENCE","classifier_version":"1.4.0","classified_at":"2026-10-14T00:15:59+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 2003-03-14) on 2025-02-10 and reserved on 2025-02-11. Public sources do not distinguish a voluntary return, revocation, or reclamation. The RIPE NCC holds returned, revoked and reclaimed ASNs for 180 days (six months), or longer while still routed, before reissuing them, so the estimated hold end is 2025-08-10. This does not confirm availability."}],"d737fb8c715f8b54":[{"raw_change_id":89093,"classification_code":"MERGER_ACQUISITION","confidence":"CONFIRMED","classifier_version":"1.3.0","classified_at":"2026-10-13T02:58:05+00:00","current":0,"public_explanation":"The RIPE NCC's transfer log records a merger, acquisition or reorganization from Nordic Telecom s.r.o (RIPE NCC) to Nordic Telecom Regional s.r.o. (RIPE NCC) on 2022-07-28 19:00 UTC. The registration changed hands; it is not a new allocation from the RIPE NCC."},{"raw_change_id":89093,"classification_code":"MERGER_ACQUISITION","confidence":"CONFIRMED","classifier_version":"1.3.1","classified_at":"2026-10-13T08:03:59+00:00","current":0,"public_explanation":"The RIPE NCC's transfer log records a merger, acquisition or reorganization from Nordic Telecom s.r.o (RIPE NCC) to Nordic Telecom Regional s.r.o. (RIPE NCC) on 2022-07-28 19:00 UTC. The registration changed hands; it is not a new allocation from the RIPE NCC."},{"raw_change_id":89093,"classification_code":"MERGER_ACQUISITION","confidence":"CONFIRMED","classifier_version":"1.3.2","classified_at":"2026-10-13T14:46:23+00:00","current":0,"public_explanation":"The RIPE NCC's transfer log records a merger, acquisition or reorganization from Nordic Telecom s.r.o (RIPE NCC) to Nordic Telecom Regional s.r.o. (RIPE NCC) on 2022-07-28 19:00 UTC. The registration changed hands; it is not a new allocation from the RIPE NCC."},{"raw_change_id":89093,"classification_code":"MERGER_ACQUISITION","confidence":"CONFIRMED","classifier_version":"1.4.0","classified_at":"2026-10-13T23:49:10+00:00","current":1,"public_explanation":"The RIPE NCC's transfer log records a merger, acquisition or reorganization from Nordic Telecom s.r.o (RIPE NCC) to Nordic Telecom Regional s.r.o. (RIPE NCC) on 2022-07-28 19:00 UTC. The registration changed hands; it is not a new allocation from the RIPE NCC."}],"38eaab402047eec7":[{"raw_change_id":72124,"classification_code":"INTRA_RIR_TRANSFER","confidence":"CONFIRMED","classifier_version":"1.3.0","classified_at":"2026-10-13T02:51:08+00:00","current":0,"public_explanation":"The RIPE NCC's transfer log records a transfer from Fortech s.r.o. (RIPE NCC) to Nordic Telecom s.r.o (RIPE NCC) on 2020-09-18 19:00 UTC. The registration changed hands; it is not a new allocation from the RIPE NCC."},{"raw_change_id":72124,"classification_code":"INTRA_RIR_TRANSFER","confidence":"CONFIRMED","classifier_version":"1.3.1","classified_at":"2026-10-13T08:03:17+00:00","current":0,"public_explanation":"The RIPE NCC's transfer log records a transfer from Fortech s.r.o. (RIPE NCC) to Nordic Telecom s.r.o (RIPE NCC) on 2020-09-18 19:00 UTC. The registration changed hands; it is not a new allocation from the RIPE NCC."},{"raw_change_id":72124,"classification_code":"INTRA_RIR_TRANSFER","confidence":"CONFIRMED","classifier_version":"1.3.2","classified_at":"2026-10-13T14:45:37+00:00","current":0,"public_explanation":"The RIPE NCC's transfer log records a transfer from Fortech s.r.o. (RIPE NCC) to Nordic Telecom s.r.o (RIPE NCC) on 2020-09-18 19:00 UTC. The registration changed hands; it is not a new allocation from the RIPE NCC."},{"raw_change_id":72124,"classification_code":"INTRA_RIR_TRANSFER","confidence":"CONFIRMED","classifier_version":"1.4.0","classified_at":"2026-10-13T23:48:18+00:00","current":1,"public_explanation":"The RIPE NCC's transfer log records a transfer from Fortech s.r.o. (RIPE NCC) to Nordic Telecom s.r.o (RIPE NCC) on 2020-09-18 19:00 UTC. The registration changed hands; it is not a new allocation from the RIPE NCC."}]},"arin_statistics_now":{"status":"not listed"}}