{"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.214.180.0/22","resource_type":"ipv4","page":"https://rirtracker.com/ip/103.214.180.0-103.214.183.255/","statistics_now":{"registry":"RIPE NCC","status":"allocated (dated 2016-04-13)"},"current_holder":{"rir":"RIPE NCC","org":"Stadtwerke Baden-Baden","how":"The RIPE NCC's latest statistics and the latest transfer record"},"rdap_snapshots":[],"transfers":[{"id":115015,"date":"2025-09-03T19:00:00Z","type":"RESOURCE_TRANSFER","source_rir":"RIPE NCC","recipient_rir":"RIPE NCC","source_org":"Stiegeler Gaggenau GmbH","recipient_org":"Stadtwerke Baden-Baden","range":"103.214.180.0/22","log":"RIPE NCC"},{"id":97641,"date":"2023-08-24T19:00:00Z","type":"MERGER_ACQUISITION","source_rir":"RIPE NCC","recipient_rir":"RIPE NCC","source_org":"Alexander Siebnich trading as siebnich.com - it.competence! e.K","recipient_org":"siebnich.com GmbH","range":"103.214.180.0/22","log":"RIPE NCC"},{"id":128720,"date":"2023-07-10T21:01:40Z","type":"RESOURCE_TRANSFER","source_rir":"APNIC","recipient_rir":"RIPE NCC","source_org":"BizCap Investment Funds BV","recipient_org":"ORG-AS234-RIPE","range":"103.214.180.0/22","log":"APNIC"},{"id":96891,"date":"2023-07-10T19:00:00Z","type":"RESOURCE_TRANSFER","source_rir":"APNIC","recipient_rir":"RIPE NCC","source_org":null,"recipient_org":"Alexander Siebnich trading as siebnich.com - it.competence! e.K","range":"103.214.180.0/22","log":"RIPE NCC"}],"events":[{"event_id":"ebf795cd7b6530c3","registry":"RIPE NCC","report_date":"2025-09-03","source":"transfers","raw_action":"TRANSFER","raw_line":null,"resource_type":"ipv4","resource":"103.214.180.0/22","start":"103.214.180.0","end":"103.214.183.255","classification":"INTRA_RIR_TRANSFER","classification_label":"Intra-RIPE NCC transfer","confidence":"CONFIRMED","source_rir":"RIPE NCC","recipient_rir":"RIPE NCC","source_organization":"Stiegeler Gaggenau GmbH","recipient_organization":"Stadtwerke Baden-Baden","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:33+00:00","page":"https://rirtracker.com/ip/103.214.180.0-103.214.183.255/#e-ebf795cd7b6530c3","report_page":"https://rirtracker.com/ripe/reports/2025-09-03/","evidence_url":"https://rirtracker.com/api/v1/resources/ip/103.214.180.0-103.214.183.255.json","observed":"Transfer: Stiegeler Gaggenau GmbH (RIPE NCC) to Stadtwerke Baden-Baden (RIPE NCC)","explanation":"The RIPE NCC's transfer log records a transfer from Stiegeler Gaggenau GmbH (RIPE NCC) to Stadtwerke Baden-Baden (RIPE NCC) on 2025-09-03 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-09-03 19:00 UTC, Stiegeler Gaggenau GmbH (RIPE NCC) to Stadtwerke Baden-Baden (RIPE NCC); resources moved: 103.214.180.0/22"},{"type":"delegated_before","url":"https://ftp.ripe.net/pub/stats/ripencc/2025/delegated-ripencc-extended-20250902.bz2","retrieved_at":"2026-10-13T01:08:02+00:00","summary":"RIPE NCC delegated statistics 2025-09-02 (produced 2025-09-02T21:59:59+00:00), before the change: allocated (dated 2016-04-13)"},{"type":"delegated_after","url":"https://ftp.ripe.net/pub/stats/ripencc/2025/delegated-ripencc-extended-20250903.bz2","retrieved_at":"2026-10-13T01:08:05+00:00","summary":"RIPE NCC delegated statistics 2025-09-03 (produced 2025-09-03T21:59:59+00:00), after the change: allocated (dated 2016-04-13)"}]},{"event_id":"012f6b5d6a30f380","registry":"RIPE NCC","report_date":"2023-08-24","source":"transfers","raw_action":"TRANSFER","raw_line":null,"resource_type":"ipv4","resource":"103.214.180.0/22","start":"103.214.180.0","end":"103.214.183.255","classification":"MERGER_ACQUISITION","classification_label":"Merger/acquisition or reorganization","confidence":"CONFIRMED","source_rir":"RIPE NCC","recipient_rir":"RIPE NCC","source_organization":"Alexander Siebnich trading as siebnich.com - it.competence! e.K","recipient_organization":"siebnich.com GmbH","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:38+00:00","page":"https://rirtracker.com/ip/103.214.180.0-103.214.183.255/#e-012f6b5d6a30f380","report_page":"https://rirtracker.com/ripe/reports/2023-08-24/","evidence_url":"https://rirtracker.com/api/v1/resources/ip/103.214.180.0-103.214.183.255.json","observed":"Merger/acquisition: Alexander Siebnich trading as siebnich.com - it.competence! e.K (RIPE NCC) to siebnich.com GmbH (RIPE NCC)","explanation":"The RIPE NCC's transfer log records a merger, acquisition or reorganization from Alexander Siebnich trading as siebnich.com - it.competence! e.K (RIPE NCC) to siebnich.com GmbH (RIPE NCC) on 2023-08-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: MERGER_ACQUISITION on 2023-08-24 19:00 UTC, Alexander Siebnich trading as siebnich.com - it.competence! e.K (RIPE NCC) to siebnich.com GmbH (RIPE NCC); resources moved: 103.214.180.0/22"},{"type":"delegated_before","url":"https://ftp.ripe.net/pub/stats/ripencc/2023/delegated-ripencc-extended-20230823.bz2","retrieved_at":"2026-10-13T00:10:08+00:00","summary":"RIPE NCC delegated statistics 2023-08-23 (produced 2023-08-23T21:59:59+00:00), before the change: allocated (dated 2016-04-13)"},{"type":"delegated_after","url":"https://ftp.ripe.net/pub/stats/ripencc/2023/delegated-ripencc-extended-20230824.bz2","retrieved_at":"2026-10-13T00:10:11+00:00","summary":"RIPE NCC delegated statistics 2023-08-24 (produced 2023-08-24T21:59:59+00:00), after the change: allocated (dated 2016-04-13)"}]},{"event_id":"547bb366e192f74e","registry":"APNIC","report_date":"2023-07-11","source":"transfers","raw_action":"TRANSFER","raw_line":null,"resource_type":"ipv4","resource":"103.214.180.0/22","start":"103.214.180.0","end":"103.214.183.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":"BizCap Investment Funds BV","recipient_organization":"ORG-AS234-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:48+00:00","page":"https://rirtracker.com/ip/103.214.180.0-103.214.183.255/#e-547bb366e192f74e","report_page":"https://rirtracker.com/apnic/reports/2023-07-11/","evidence_url":"https://rirtracker.com/api/v1/resources/ip/103.214.180.0-103.214.183.255.json","observed":"Transfer: BizCap Investment Funds BV (APNIC) to ORG-AS234-RIPE (RIPE NCC)","same_transfer_as":"c711c0924833641a","explanation":"APNIC's transfer log records a transfer from BizCap Investment Funds BV (APNIC) to ORG-AS234-RIPE (RIPE NCC) on 2023-07-10 21:01 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-07-10 21:01 UTC, BizCap Investment Funds BV (APNIC) to ORG-AS234-RIPE (RIPE NCC); resources moved: 103.214.180.0/22"},{"type":"delegated_before","url":"https://ftp.apnic.net/stats/apnic/2023/delegated-apnic-extended-20230711.gz","retrieved_at":"2026-10-13T00:44:16+00:00","summary":"APNIC delegated statistics 2023-07-11, before the change: allocated (dated 2016-04-13)"},{"type":"delegated_after","url":"https://ftp.apnic.net/stats/apnic/2023/delegated-apnic-extended-20230712.gz","retrieved_at":"2026-10-13T00:44:20+00:00","summary":"APNIC delegated statistics 2023-07-12, after the change: not listed"}]},{"event_id":"c711c0924833641a","registry":"RIPE NCC","report_date":"2023-07-10","source":"transfers","raw_action":"TRANSFER","raw_line":null,"resource_type":"ipv4","resource":"103.214.180.0/22","start":"103.214.180.0","end":"103.214.183.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":"Alexander Siebnich trading as siebnich.com - it.competence! e.K","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:35+00:00","page":"https://rirtracker.com/ip/103.214.180.0-103.214.183.255/#e-c711c0924833641a","report_page":"https://rirtracker.com/ripe/reports/2023-07-10/","evidence_url":"https://rirtracker.com/api/v1/resources/ip/103.214.180.0-103.214.183.255.json","observed":"Transfer: (no name) (APNIC) to Alexander Siebnich trading as siebnich.com - it.competence! e.K (RIPE NCC)","same_transfer_as":"547bb366e192f74e","explanation":"The RIPE NCC's transfer log records a transfer from an unnamed organization (APNIC) to Alexander Siebnich trading as siebnich.com - it.competence! e.K (RIPE NCC) on 2023-07-10 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-07-10 19:00 UTC, (no name) (APNIC) to Alexander Siebnich trading as siebnich.com - it.competence! e.K (RIPE NCC); resources moved: 103.214.180.0/22"},{"type":"delegated_before","url":"https://ftp.ripe.net/pub/stats/ripencc/2023/delegated-ripencc-extended-20230709.bz2","retrieved_at":"2026-10-13T00:06:45+00:00","summary":"RIPE NCC delegated statistics 2023-07-09 (produced 2023-07-09T21:59:59+00:00), before the change: not listed"},{"type":"delegated_after","url":"https://ftp.ripe.net/pub/stats/ripencc/2023/delegated-ripencc-extended-20230710.bz2","retrieved_at":"2026-10-13T00:06:48+00:00","summary":"RIPE NCC delegated statistics 2023-07-10 (produced 2023-07-10T21:59:59+00:00), after the change: allocated (dated 2016-04-13)"}]},{"event_id":"3e68d8e84a6cdc53","registry":"APNIC","report_date":"2019-10-17","source":"statistics","raw_action":"ADDED","raw_line":null,"resource_type":"ipv4","resource":"103.214.180.0/22","start":"103.214.180.0","end":"103.214.183.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:09:29+00:00","page":"https://rirtracker.com/ip/103.214.180.0-103.214.183.255/#e-3e68d8e84a6cdc53","report_page":"https://rirtracker.com/apnic/reports/2019-10-17/","evidence_url":"https://rirtracker.com/api/v1/resources/ip/103.214.180.0-103.214.183.255.json","observed":"103.214.180.0/22 reserved on 2019-10-17, allocated on 2019-10-18","explanation":"No transfer record matches. APNIC's statistics show it reserved on 2019-10-17 and allocated (dated 2016-04-13) on 2019-10-18. The tracker saw it removed from registration on 2019-10-11 (6 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/2019/delegated-apnic-extended-20191018.gz","retrieved_at":"2026-10-12T23:04:31+00:00","summary":"Found by comparing APNIC's daily statistics: 103.214.180.0/22 reserved on 2019-10-17, allocated on 2019-10-18"},{"type":"delegated_before","url":"https://ftp.apnic.net/stats/apnic/2019/delegated-apnic-extended-20191017.gz","retrieved_at":"2026-10-12T23:04:28+00:00","summary":"APNIC delegated statistics 2019-10-17, before the change: reserved"},{"type":"delegated_after","url":"https://ftp.apnic.net/stats/apnic/2019/delegated-apnic-extended-20191018.gz","retrieved_at":"2026-10-12T23:04:31+00:00","summary":"APNIC delegated statistics 2019-10-18, after the change: allocated (dated 2016-04-13)"}]},{"event_id":"fab8b53aca539017","registry":"APNIC","report_date":"2019-10-11","source":"statistics","raw_action":"REMOVED","raw_line":null,"resource_type":"ipv4","resource":"103.214.180.0/22","start":"103.214.180.0","end":"103.214.183.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:09:27+00:00","page":"https://rirtracker.com/ip/103.214.180.0-103.214.183.255/#e-fab8b53aca539017","report_page":"https://rirtracker.com/apnic/reports/2019-10-11/","evidence_url":"https://rirtracker.com/api/v1/resources/ip/103.214.180.0-103.214.183.255.json","observed":"103.214.180.0/22 allocated on 2019-10-11, reserved on 2019-10-12","hold":{"hold_rule_source_url":"https://www.apnic.net/manage-ip/manage-resources/address-status","hold_rule_months":12,"estimated_hold_end":"2020-10-11","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 2016-04-13) on 2019-10-11 and reserved on 2019-10-12. 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 2020-10-11. 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/2019/delegated-apnic-extended-20191012.gz","retrieved_at":"2026-10-12T23:04:01+00:00","summary":"Found by comparing APNIC's daily statistics: 103.214.180.0/22 allocated on 2019-10-11, reserved on 2019-10-12"},{"type":"delegated_before","url":"https://ftp.apnic.net/stats/apnic/2019/delegated-apnic-extended-20191011.gz","retrieved_at":"2026-10-12T23:03:57+00:00","summary":"APNIC delegated statistics 2019-10-11, before the change: allocated (dated 2016-04-13)"},{"type":"delegated_after","url":"https://ftp.apnic.net/stats/apnic/2019/delegated-apnic-extended-20191012.gz","retrieved_at":"2026-10-12T23:04:01+00:00","summary":"APNIC delegated statistics 2019-10-12, after the change: reserved"}]},{"event_id":"fe833a471be3b33f","registry":"APNIC","report_date":"2018-11-22","source":"statistics","raw_action":"ADDED","raw_line":null,"resource_type":"ipv4","resource":"103.214.180.0/22","start":"103.214.180.0","end":"103.214.183.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:08:06+00:00","page":"https://rirtracker.com/ip/103.214.180.0-103.214.183.255/#e-fe833a471be3b33f","report_page":"https://rirtracker.com/apnic/reports/2018-11-22/","evidence_url":"https://rirtracker.com/api/v1/resources/ip/103.214.180.0-103.214.183.255.json","observed":"103.214.180.0/22 reserved on 2018-11-22, allocated on 2018-11-23","explanation":"No transfer record matches. APNIC's statistics show it reserved on 2018-11-22 and allocated (dated 2016-04-13) on 2018-11-23. The tracker saw it removed from registration on 2018-10-08 (45 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/2018/delegated-apnic-extended-20181123.gz","retrieved_at":"2026-10-12T22:41:00+00:00","summary":"Found by comparing APNIC's daily statistics: 103.214.180.0/22 reserved on 2018-11-22, allocated on 2018-11-23"},{"type":"delegated_before","url":"https://ftp.apnic.net/stats/apnic/2018/delegated-apnic-extended-20181122.gz","retrieved_at":"2026-10-12T22:40:57+00:00","summary":"APNIC delegated statistics 2018-11-22, before the change: reserved"},{"type":"delegated_after","url":"https://ftp.apnic.net/stats/apnic/2018/delegated-apnic-extended-20181123.gz","retrieved_at":"2026-10-12T22:41:00+00:00","summary":"APNIC delegated statistics 2018-11-23, after the change: allocated (dated 2016-04-13)"}]},{"event_id":"941fd14c1134ef58","registry":"APNIC","report_date":"2018-10-08","source":"statistics","raw_action":"REMOVED","raw_line":null,"resource_type":"ipv4","resource":"103.214.180.0/22","start":"103.214.180.0","end":"103.214.183.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:07:55+00:00","page":"https://rirtracker.com/ip/103.214.180.0-103.214.183.255/#e-941fd14c1134ef58","report_page":"https://rirtracker.com/apnic/reports/2018-10-08/","evidence_url":"https://rirtracker.com/api/v1/resources/ip/103.214.180.0-103.214.183.255.json","observed":"103.214.180.0/22 allocated on 2018-10-08, reserved on 2018-10-09","hold":{"hold_rule_source_url":"https://www.apnic.net/manage-ip/manage-resources/address-status","hold_rule_months":12,"estimated_hold_end":"2019-10-08","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 2016-04-13) on 2018-10-08 and reserved on 2018-10-09. 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 2019-10-08. 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/2018/delegated-apnic-extended-20181009.gz","retrieved_at":"2026-10-12T22:38:04+00:00","summary":"Found by comparing APNIC's daily statistics: 103.214.180.0/22 allocated on 2018-10-08, reserved on 2018-10-09"},{"type":"delegated_before","url":"https://ftp.apnic.net/stats/apnic/2018/delegated-apnic-extended-20181008.gz","retrieved_at":"2026-10-12T22:38:01+00:00","summary":"APNIC delegated statistics 2018-10-08, before the change: allocated (dated 2016-04-13)"},{"type":"delegated_after","url":"https://ftp.apnic.net/stats/apnic/2018/delegated-apnic-extended-20181009.gz","retrieved_at":"2026-10-12T22:38:04+00:00","summary":"APNIC delegated statistics 2018-10-09, after the change: reserved"}]},{"event_id":"4f29231c87edcdc7","registry":"APNIC","report_date":"2016-04-13","source":"statistics","raw_action":"ADDED","raw_line":null,"resource_type":"ipv4","resource":"103.214.180.0/22","start":"103.214.180.0","end":"103.214.183.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:03:39+00:00","page":"https://rirtracker.com/ip/103.214.180.0-103.214.183.255/#e-4f29231c87edcdc7","report_page":"https://rirtracker.com/apnic/reports/2016-04-13/","evidence_url":"https://rirtracker.com/api/v1/resources/ip/103.214.180.0-103.214.183.255.json","observed":"103.214.180.0/22 available on 2016-04-13, allocated on 2016-04-14","explanation":"No transfer record matches. APNIC's statistics show it available on 2016-04-13 and allocated (dated 2016-04-13) on 2016-04-14. 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/2016/delegated-apnic-extended-20160414.gz","retrieved_at":"2026-10-12T21:37:28+00:00","summary":"Found by comparing APNIC's daily statistics: 103.214.180.0/22 available on 2016-04-13, allocated on 2016-04-14"},{"type":"delegated_before","url":"https://ftp.apnic.net/stats/apnic/2016/delegated-apnic-extended-20160413.gz","retrieved_at":"2026-10-12T21:37:24+00:00","summary":"APNIC delegated statistics 2016-04-13, before the change: available"},{"type":"delegated_after","url":"https://ftp.apnic.net/stats/apnic/2016/delegated-apnic-extended-20160414.gz","retrieved_at":"2026-10-12T21:37:28+00:00","summary":"APNIC delegated statistics 2016-04-14, after the change: allocated (dated 2016-04-13)"}]}],"classification_history":{"ebf795cd7b6530c3":[{"raw_change_id":115817,"classification_code":"INTRA_RIR_TRANSFER","confidence":"CONFIRMED","classifier_version":"1.3.0","classified_at":"2026-10-13T03:09:38+00:00","current":0,"public_explanation":"The RIPE NCC's transfer log records a transfer from Stiegeler Gaggenau GmbH (RIPE NCC) to Stadtwerke Baden-Baden (RIPE NCC) on 2025-09-03 19:00 UTC. The registration changed hands; it is not a new allocation from the RIPE NCC."},{"raw_change_id":115817,"classification_code":"INTRA_RIR_TRANSFER","confidence":"CONFIRMED","classifier_version":"1.3.1","classified_at":"2026-10-13T08:05:05+00:00","current":0,"public_explanation":"The RIPE NCC's transfer log records a transfer from Stiegeler Gaggenau GmbH (RIPE NCC) to Stadtwerke Baden-Baden (RIPE NCC) on 2025-09-03 19:00 UTC. The registration changed hands; it is not a new allocation from the RIPE NCC."},{"raw_change_id":115817,"classification_code":"INTRA_RIR_TRANSFER","confidence":"CONFIRMED","classifier_version":"1.3.2","classified_at":"2026-10-13T14:47:37+00:00","current":0,"public_explanation":"The RIPE NCC's transfer log records a transfer from Stiegeler Gaggenau GmbH (RIPE NCC) to Stadtwerke Baden-Baden (RIPE NCC) on 2025-09-03 19:00 UTC. The registration changed hands; it is not a new allocation from the RIPE NCC."},{"raw_change_id":115817,"classification_code":"INTRA_RIR_TRANSFER","confidence":"CONFIRMED","classifier_version":"1.4.0","classified_at":"2026-10-13T23:50:33+00:00","current":1,"public_explanation":"The RIPE NCC's transfer log records a transfer from Stiegeler Gaggenau GmbH (RIPE NCC) to Stadtwerke Baden-Baden (RIPE NCC) on 2025-09-03 19:00 UTC. The registration changed hands; it is not a new allocation from the RIPE NCC."}],"012f6b5d6a30f380":[{"raw_change_id":98116,"classification_code":"MERGER_ACQUISITION","confidence":"CONFIRMED","classifier_version":"1.3.0","classified_at":"2026-10-13T03:01:52+00:00","current":0,"public_explanation":"The RIPE NCC's transfer log records a merger, acquisition or reorganization from Alexander Siebnich trading as siebnich.com - it.competence! e.K (RIPE NCC) to siebnich.com GmbH (RIPE NCC) on 2023-08-24 19:00 UTC. The registration changed hands; it is not a new allocation from the RIPE NCC."},{"raw_change_id":98116,"classification_code":"MERGER_ACQUISITION","confidence":"CONFIRMED","classifier_version":"1.3.1","classified_at":"2026-10-13T08:04:22+00:00","current":0,"public_explanation":"The RIPE NCC's transfer log records a merger, acquisition or reorganization from Alexander Siebnich trading as siebnich.com - it.competence! e.K (RIPE NCC) to siebnich.com GmbH (RIPE NCC) on 2023-08-24 19:00 UTC. The registration changed hands; it is not a new allocation from the RIPE NCC."},{"raw_change_id":98116,"classification_code":"MERGER_ACQUISITION","confidence":"CONFIRMED","classifier_version":"1.3.2","classified_at":"2026-10-13T14:46:48+00:00","current":0,"public_explanation":"The RIPE NCC's transfer log records a merger, acquisition or reorganization from Alexander Siebnich trading as siebnich.com - it.competence! e.K (RIPE NCC) to siebnich.com GmbH (RIPE NCC) on 2023-08-24 19:00 UTC. The registration changed hands; it is not a new allocation from the RIPE NCC."},{"raw_change_id":98116,"classification_code":"MERGER_ACQUISITION","confidence":"CONFIRMED","classifier_version":"1.4.0","classified_at":"2026-10-13T23:49:38+00:00","current":1,"public_explanation":"The RIPE NCC's transfer log records a merger, acquisition or reorganization from Alexander Siebnich trading as siebnich.com - it.competence! e.K (RIPE NCC) to siebnich.com GmbH (RIPE NCC) on 2023-08-24 19:00 UTC. The registration changed hands; it is not a new allocation from the RIPE NCC."}],"547bb366e192f74e":[{"raw_change_id":39952,"classification_code":"INTER_RIR_TRANSFER_OUT","confidence":"CONFIRMED","classifier_version":"1.3.0","classified_at":"2026-10-13T02:37:44+00:00","current":0,"public_explanation":"APNIC's transfer log records a transfer from BizCap Investment Funds BV (APNIC) to ORG-AS234-RIPE (RIPE NCC) on 2023-07-10 21:01 UTC: it left APNIC for the RIPE NCC. It is not a new allocation and is not offered to APNIC applicants."},{"raw_change_id":39952,"classification_code":"INTER_RIR_TRANSFER_OUT","confidence":"CONFIRMED","classifier_version":"1.3.1","classified_at":"2026-10-13T08:02:01+00:00","current":0,"public_explanation":"APNIC's transfer log records a transfer from BizCap Investment Funds BV (APNIC) to ORG-AS234-RIPE (RIPE NCC) on 2023-07-10 21:01 UTC: it left APNIC for the RIPE NCC. It is not a new allocation and is not offered to APNIC applicants."},{"raw_change_id":39952,"classification_code":"INTER_RIR_TRANSFER_OUT","confidence":"CONFIRMED","classifier_version":"1.3.2","classified_at":"2026-10-13T14:44:12+00:00","current":0,"public_explanation":"APNIC's transfer log records a transfer from BizCap Investment Funds BV (APNIC) to ORG-AS234-RIPE (RIPE NCC) on 2023-07-10 21:01 UTC: it left APNIC for the RIPE NCC. It is not a new allocation and is not offered to APNIC applicants."},{"raw_change_id":39952,"classification_code":"INTER_RIR_TRANSFER_OUT","confidence":"CONFIRMED","classifier_version":"1.4.0","classified_at":"2026-10-13T23:46:48+00:00","current":1,"public_explanation":"APNIC's transfer log records a transfer from BizCap Investment Funds BV (APNIC) to ORG-AS234-RIPE (RIPE NCC) on 2023-07-10 21:01 UTC: it left APNIC for the RIPE NCC. It is not a new allocation and is not offered to APNIC applicants."}],"c711c0924833641a":[{"raw_change_id":97361,"classification_code":"INTER_RIR_TRANSFER_IN","confidence":"CONFIRMED","classifier_version":"1.3.0","classified_at":"2026-10-13T03:01:31+00:00","current":0,"public_explanation":"The RIPE NCC's transfer log records a transfer from an unnamed organization (APNIC) to Alexander Siebnich trading as siebnich.com - it.competence! e.K (RIPE NCC) on 2023-07-10 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":97361,"classification_code":"INTER_RIR_TRANSFER_IN","confidence":"CONFIRMED","classifier_version":"1.3.1","classified_at":"2026-10-13T08:04:20+00:00","current":0,"public_explanation":"The RIPE NCC's transfer log records a transfer from an unnamed organization (APNIC) to Alexander Siebnich trading as siebnich.com - it.competence! e.K (RIPE NCC) on 2023-07-10 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":97361,"classification_code":"INTER_RIR_TRANSFER_IN","confidence":"CONFIRMED","classifier_version":"1.3.2","classified_at":"2026-10-13T14:46:46+00:00","current":0,"public_explanation":"The RIPE NCC's transfer log records a transfer from an unnamed organization (APNIC) to Alexander Siebnich trading as siebnich.com - it.competence! e.K (RIPE NCC) on 2023-07-10 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":97361,"classification_code":"INTER_RIR_TRANSFER_IN","confidence":"CONFIRMED","classifier_version":"1.4.0","classified_at":"2026-10-13T23:49:35+00:00","current":1,"public_explanation":"The RIPE NCC's transfer log records a transfer from an unnamed organization (APNIC) to Alexander Siebnich trading as siebnich.com - it.competence! e.K (RIPE NCC) on 2023-07-10 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."}],"3e68d8e84a6cdc53":[{"raw_change_id":430546,"classification_code":"RESTORED","confidence":"STRONG_INFERENCE","classifier_version":"1.3.0","classified_at":"2026-10-13T05:52:26+00:00","current":0,"public_explanation":"No transfer record matches. APNIC's statistics show it reserved on 2019-10-17 and allocated (dated 2016-04-13) on 2019-10-18. The tracker saw it removed from registration on 2019-10-11 (6 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":430546,"classification_code":"RESTORED","confidence":"STRONG_INFERENCE","classifier_version":"1.3.1","classified_at":"2026-10-13T08:20:44+00:00","current":0,"public_explanation":"No transfer record matches. APNIC's statistics show it reserved on 2019-10-17 and allocated (dated 2016-04-13) on 2019-10-18. The tracker saw it removed from registration on 2019-10-11 (6 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":430546,"classification_code":"RESTORED","confidence":"STRONG_INFERENCE","classifier_version":"1.3.2","classified_at":"2026-10-13T15:04:39+00:00","current":0,"public_explanation":"No transfer record matches. APNIC's statistics show it reserved on 2019-10-17 and allocated (dated 2016-04-13) on 2019-10-18. The tracker saw it removed from registration on 2019-10-11 (6 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":430546,"classification_code":"RESTORED","confidence":"STRONG_INFERENCE","classifier_version":"1.4.0","classified_at":"2026-10-14T00:09:29+00:00","current":1,"public_explanation":"No transfer record matches. APNIC's statistics show it reserved on 2019-10-17 and allocated (dated 2016-04-13) on 2019-10-18. The tracker saw it removed from registration on 2019-10-11 (6 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."}],"fab8b53aca539017":[{"raw_change_id":430100,"classification_code":"REMOVED_REASON_UNKNOWN","confidence":"STRONG_INFERENCE","classifier_version":"1.3.0","classified_at":"2026-10-13T05:52:13+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 2016-04-13) on 2019-10-11 and reserved on 2019-10-12. 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":430100,"classification_code":"REMOVED_REASON_UNKNOWN","confidence":"STRONG_INFERENCE","classifier_version":"1.3.1","classified_at":"2026-10-13T08:20:42+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 2016-04-13) on 2019-10-11 and reserved on 2019-10-12. 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":430100,"classification_code":"REMOVED_REASON_UNKNOWN","confidence":"STRONG_INFERENCE","classifier_version":"1.3.2","classified_at":"2026-10-13T15:04:37+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 2016-04-13) on 2019-10-11 and reserved on 2019-10-12. 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":430100,"classification_code":"REMOVED_REASON_UNKNOWN","confidence":"STRONG_INFERENCE","classifier_version":"1.4.0","classified_at":"2026-10-14T00:09:27+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 2016-04-13) on 2019-10-11 and reserved on 2019-10-12. 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 2020-10-11. That is what APNIC has done, not a rule it states. This does not confirm availability."}],"fe833a471be3b33f":[{"raw_change_id":411469,"classification_code":"RESTORED","confidence":"STRONG_INFERENCE","classifier_version":"1.3.0","classified_at":"2026-10-13T05:45:04+00:00","current":0,"public_explanation":"No transfer record matches. APNIC's statistics show it reserved on 2018-11-22 and allocated (dated 2016-04-13) on 2018-11-23. The tracker saw it removed from registration on 2018-10-08 (45 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":411469,"classification_code":"RESTORED","confidence":"STRONG_INFERENCE","classifier_version":"1.3.1","classified_at":"2026-10-13T08:19:34+00:00","current":0,"public_explanation":"No transfer record matches. APNIC's statistics show it reserved on 2018-11-22 and allocated (dated 2016-04-13) on 2018-11-23. The tracker saw it removed from registration on 2018-10-08 (45 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":411469,"classification_code":"RESTORED","confidence":"STRONG_INFERENCE","classifier_version":"1.3.2","classified_at":"2026-10-13T15:03:25+00:00","current":0,"public_explanation":"No transfer record matches. APNIC's statistics show it reserved on 2018-11-22 and allocated (dated 2016-04-13) on 2018-11-23. The tracker saw it removed from registration on 2018-10-08 (45 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":411469,"classification_code":"RESTORED","confidence":"STRONG_INFERENCE","classifier_version":"1.4.0","classified_at":"2026-10-14T00:08:06+00:00","current":1,"public_explanation":"No transfer record matches. APNIC's statistics show it reserved on 2018-11-22 and allocated (dated 2016-04-13) on 2018-11-23. The tracker saw it removed from registration on 2018-10-08 (45 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."}],"941fd14c1134ef58":[{"raw_change_id":408841,"classification_code":"REMOVED_REASON_UNKNOWN","confidence":"STRONG_INFERENCE","classifier_version":"1.3.0","classified_at":"2026-10-13T05:44:00+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 2016-04-13) on 2018-10-08 and reserved on 2018-10-09. 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":408841,"classification_code":"REMOVED_REASON_UNKNOWN","confidence":"STRONG_INFERENCE","classifier_version":"1.3.1","classified_at":"2026-10-13T08:19:25+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 2016-04-13) on 2018-10-08 and reserved on 2018-10-09. 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":408841,"classification_code":"REMOVED_REASON_UNKNOWN","confidence":"STRONG_INFERENCE","classifier_version":"1.3.2","classified_at":"2026-10-13T15:03:15+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 2016-04-13) on 2018-10-08 and reserved on 2018-10-09. 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":408841,"classification_code":"REMOVED_REASON_UNKNOWN","confidence":"STRONG_INFERENCE","classifier_version":"1.4.0","classified_at":"2026-10-14T00:07:55+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 2016-04-13) on 2018-10-08 and reserved on 2018-10-09. 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 2019-10-08. That is what APNIC has done, not a rule it states. This does not confirm availability."}],"4f29231c87edcdc7":[{"raw_change_id":344025,"classification_code":"APPARENT_NEW_ISSUANCE","confidence":"STRONG_INFERENCE","classifier_version":"1.3.0","classified_at":"2026-10-13T05:16:43+00:00","current":0,"public_explanation":"No transfer record matches. APNIC's statistics show it available on 2016-04-13 and allocated (dated 2016-04-13) on 2016-04-14. 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":344025,"classification_code":"APPARENT_NEW_ISSUANCE","confidence":"STRONG_INFERENCE","classifier_version":"1.3.1","classified_at":"2026-10-13T08:15:55+00:00","current":0,"public_explanation":"No transfer record matches. APNIC's statistics show it available on 2016-04-13 and allocated (dated 2016-04-13) on 2016-04-14. 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":344025,"classification_code":"APPARENT_NEW_ISSUANCE","confidence":"STRONG_INFERENCE","classifier_version":"1.3.2","classified_at":"2026-10-13T14:59:28+00:00","current":0,"public_explanation":"No transfer record matches. APNIC's statistics show it available on 2016-04-13 and allocated (dated 2016-04-13) on 2016-04-14. 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":344025,"classification_code":"APPARENT_NEW_ISSUANCE","confidence":"STRONG_INFERENCE","classifier_version":"1.4.0","classified_at":"2026-10-14T00:03:39+00:00","current":1,"public_explanation":"No transfer record matches. APNIC's statistics show it available on 2016-04-13 and allocated (dated 2016-04-13) on 2016-04-14. 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"}}