RIPE NCC · RIR Watchdog
Minimum Size for IPv4 Temporary Assignments
Start here for the proposal-by-proposal record: what changed, why it mattered, who argued for what, how positions evolved, what was decided, and where the evidence still has gaps.
Source facts
- Policy ID
- 2023-02
- RIR
- RIPE NCC
- Official status
- Accepted
- Normalized status
- Accepted
- Introduced
- Feb 9, 2023
- Last source update
- Oct 10, 2026
- Coverage
- Partial
Who actually shaped the debate?
Policy evolution
Policy text · Astra identified a substantive wording change in this retained policy section.
Source facts −
This policy proposal also allows routing requirements to justify the request for more than a /24 for research purposes. Policy text: a) Current policy text (if modification): 3.3 IPv4 Address Utilisation Rates The utilisation rate of an assignment must be such that at least 50% of the total space applied for at the time of the assignment will be concurrently used at peak periods during the assignment.Source facts ↗
Source facts +
Based on feedback on the first version, the proposed new policy text has been simplified, as well as paragraph 3.1 for consistency.Source facts ↗
Policy text · Astra identified a substantive wording change in this retained policy section.
Source facts −
Policy text: a) Current policy text (if modification): 3.3 IPv4 Address Utilisation Rates The utilisation rate of an assignment must be such that at least 50% of the total space applied for at the time of the assignment will be concurrently used at peak periods during the assignment.Source facts ↗
Policy text · Astra identified a substantive wording change in this retained policy section.
Source facts −
Policy text: a) Current policy text (if modification): 3.3 IPv4 Address Utilisation Rates The utilisation rate of an assignment must be such that at least 50% of the total space applied for at the time of the assignment will be concurrently used at peak periods during the assignment.Source facts ↗
Source facts +
Current policy text (if modification): 3.1 Assignment Time Limits [...] In the case where an End User requires number resources for research purposes, and where the research project details are made public upon registration of the number resources by the RIPE NCC, and where the End User commits to making public the results of their research project free of charge and free from disclosure constraints, then the requested number resources may be issued for a period of up to one calendar year.Source facts ↗
Policy text · Astra identified a substantive wording change in this retained policy section.
Source facts −
Policy text: a) Current policy text (if modification): 3.3 IPv4 Address Utilisation Rates The utilisation rate of an assignment must be such that at least 50% of the total space applied for at the time of the assignment will be concurrently used at peak periods during the assignment. b) New policy text: 3.3 IPv4 Address Utilisation Rates The default assignment size is a /24.Source facts ↗
Policy text · Astra identified a substantive wording change in this retained policy section.
Source facts −
b) New policy text: 3.3 IPv4 Address Utilisation Rates The default assignment size is a /24.Source facts ↗
Policy text · Astra identified a substantive wording change in this retained policy section.
Source facts −
b) New policy text: 3.3 IPv4 Address Utilisation Rates The default assignment size is a /24.Source facts ↗
Source facts +
New policy text: 3.1 Assignment Time Limits [...] Number resources requested for research purposes may be issued for a period of up to one calendar year when both the following conditions are met: the research project details are made public upon registration of the number resources by the RIPE NCC.Source facts ↗
Policy text · Astra identified a substantive wording change in this retained policy section.
Source facts −
In the case where an End User requires number resources for research purposes, and where the research project details are made public upon registration of the number resources by the RIPE NCC, and where the End User commits to making public the results of their research project free of charge and free from disclosure constraints, then the need for more than a /24 may be justified by routing requirements.Source facts ↗
Source facts +
A request for more than a /24 for research purposes may be justified by routing requirements when both the following conditions are met: the research project details are made public upon registration of the number resources by the RIPE NCC.Source facts ↗
Policy text · Astra identified a substantive wording change in this retained policy section.
Source facts −
In the case where an End User requires number resources for research purposes, and where the research project details are made public upon registration of the number resources by the RIPE NCC, and where the End User commits to making public the results of their research project free of charge and free from disclosure constraints, then the need for more than a /24 may be justified by routing requirements.Source facts ↗
Source facts +
the End User commits to making public the results of their research project free of charge and free from disclosure constraints.Source facts ↗
Policy text · Astra identified a substantive wording change in this retained policy section.
Source facts −
In the case where an End User requires number resources for research purposes, and where the research project details are made public upon registration of the number resources by the RIPE NCC, and where the End User commits to making public the results of their research project free of charge and free from disclosure constraints, then the need for more than a /24 may be justified by routing requirements.Source facts ↗
Debate timeline
Entities
- Dewole Ajao · Identity unresolvedDiscussion messages1First activityDec 8, 2016Last activityDec 8, 2016First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies0
- Discussion messages0First activityUnknownLast activityUnknownFirst explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies1
- Discussion messages0First activityUnknownLast activityUnknownFirst explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies0
Sources and coverage
Official policy sources
Public discussion archives
- ripencc-address-policy-wg
- Earliest captured
- Aug 7, 2003
- Latest captured
- Oct 6, 2026
- Last refresh
- Aug 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 20,236
- Known gaps
- 83
- www.ripe.net
- ripencc-accountability-tf-ripe.net
- Earliest captured
- Nov 24, 2016
- Latest captured
- May 9, 2019
- Last refresh
- Oct 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,723
- Known gaps
- 0
- ripencc-agm-nominations-ripe.net
- Earliest captured
- Mar 26, 2008
- Latest captured
- Apr 28, 2026
- Last refresh
- Oct 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,452
- Known gaps
- 0
- ripencc-all-anchors-ripe.net
- Earliest captured
- Oct 31, 2014
- Latest captured
- Oct 31, 2014
- Last refresh
- Oct 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 511
- Known gaps
- 0
- ripencc-anti-abuse-wg-ripe.net
- Earliest captured
- Sep 16, 2008
- Latest captured
- Nov 4, 2025
- Last refresh
- Oct 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,389
- Known gaps
- 0
- ripencc-atlas-sponsors-ripe.net
- Earliest captured
- Dec 7, 2012
- Latest captured
- Mar 31, 2014
- Last refresh
- Oct 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 1,529
- Known gaps
- 0
- ripencc-atlas-sw-probes-ripe.net
- Earliest captured
- Oct 21, 2019
- Latest captured
- Jul 24, 2024
- Last refresh
- Oct 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,148
- Known gaps
- 0
- ripencc-bcop-ripe.net
- Earliest captured
- Jun 16, 2013
- Latest captured
- Oct 29, 2024
- Last refresh
- Oct 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 4,206
- Known gaps
- 0
- ripencc-coc-tf-ripe.net
- Earliest captured
- Sep 18, 2020
- Latest captured
- Apr 20, 2023
- Last refresh
- Oct 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,383
- Known gaps
- 0
- ripencc-connect-bof-ripe.net
- Earliest captured
- Oct 18, 2013
- Latest captured
- Jul 14, 2014
- Last refresh
- Oct 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,538
- Known gaps
- 1
- ripencc-connect-wg-ripe.net
- Earliest captured
- Oct 20, 2014
- Latest captured
- Sep 28, 2026
- Last refresh
- Oct 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 4,354
- Known gaps
- 0
- ripencc-cooperation-wg-ripe.net
- Earliest captured
- Aug 26, 2008
- Latest captured
- Oct 6, 2026
- Last refresh
- Oct 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 4,504
- Known gaps
- 0
- ripencc-db-help-ripe.net
- Earliest captured
- Aug 20, 2003
- Latest captured
- Jan 13, 2016
- Last refresh
- Oct 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 4,183
- Known gaps
- 0
- ripencc-db-wg-ripe.net
- Earliest captured
- Oct 21, 1992
- Latest captured
- Oct 9, 2026
- Last refresh
- Oct 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,345
- Known gaps
- 0
- ripencc-diversity-ripe.net
- Earliest captured
- May 18, 2017
- Latest captured
- Feb 9, 2026
- Last refresh
- Oct 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,781
- Known gaps
- 0
- ripencc-dns-resolver-tf-ripe.net
- Earliest captured
- Jan 23, 2023
- Latest captured
- Feb 16, 2025
- Last refresh
- Oct 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,823
- Known gaps
- 0
- ripencc-dns-wg-ripe.net
- Earliest captured
- Jun 30, 1992
- Latest captured
- Oct 9, 2026
- Last refresh
- Oct 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,149
- Known gaps
- 0
- ripencc-dp-tf-ripe.net
- Earliest captured
- Mar 5, 2007
- Latest captured
- Oct 15, 2009
- Last refresh
- Sep 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,713
- Known gaps
- 1
- ripencc-eb-candidates-ripe.net
- Earliest captured
- May 11, 2023
- Latest captured
- May 22, 2024
- Last refresh
- Sep 9, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 1,145
- Known gaps
- 53
- ripencc-eix-wg-ripe.net
- Earliest captured
- Jan 1, 1999
- Latest captured
- Oct 21, 2013
- Last refresh
- Oct 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,711
- Known gaps
- 0
- ripencc-election-cc-team-ripe.net
- Earliest captured
- Aug 18, 2026
- Latest captured
- Aug 18, 2026
- Last refresh
- Oct 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 461
- Known gaps
- 0
- ripencc-enum-announce-ripe.net
- Earliest captured
- Aug 15, 2003
- Latest captured
- Sep 15, 2026
- Last refresh
- Oct 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,181
- Known gaps
- 0
- ripencc-enum-wg-ripe.net
- Earliest captured
- Jun 16, 2004
- Latest captured
- Nov 20, 2013
- Last refresh
- Oct 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,476
- Known gaps
- 0
- ripencc-green-tech-hackathon-orga-ripe.net
- Earliest captured
- Unknown
- Latest captured
- Unknown
- Last refresh
- Oct 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 22
- Known gaps
- 0
- ripencc-hackathon-list-ripe.net
- Earliest captured
- Feb 26, 2015
- Latest captured
- Jan 9, 2025
- Last refresh
- Oct 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,961
- Known gaps
- 0
- ripencc-icann-plan-ripe.net
- Earliest captured
- Dec 8, 2004
- Latest captured
- Jan 31, 2005
- Last refresh
- Oct 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 792
- Known gaps
- 0
- ripencc-iot-wg-ripe.net
- Earliest captured
- Nov 3, 2016
- Latest captured
- Aug 19, 2026
- Last refresh
- Oct 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,067
- Known gaps
- 0
- ripencc-ipmap-ripe.net
- Earliest captured
- Nov 25, 2021
- Latest captured
- May 17, 2022
- Last refresh
- Oct 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 589
- Known gaps
- 0
- ripencc-ipmt-dev-ripe.net
- Earliest captured
- May 3, 2001
- Latest captured
- Jul 2, 2003
- Last refresh
- Oct 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,650
- Known gaps
- 0
- ripencc-ipv6-wg-ripe.net
- Earliest captured
- Mar 31, 1995
- Latest captured
- Oct 5, 2026
- Last refresh
- Oct 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,149
- Known gaps
- 0
- ripencc-irrtoolset-ripe.net
- Earliest captured
- Aug 12, 2003
- Latest captured
- Dec 15, 2004
- Last refresh
- Oct 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,308
- Known gaps
- 0
- ripencc-lir-wg-ripe.net
- Earliest captured
- Oct 8, 1992
- Latest captured
- Jun 30, 2003
- Last refresh
- Oct 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,974
- Known gaps
- 0
- ripencc-mat-wg-ripe.net
- Earliest captured
- May 18, 2010
- Latest captured
- Sep 23, 2026
- Last refresh
- Oct 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,612
- Known gaps
- 0
- ripencc-measure-voip-ripe.net
- Earliest captured
- May 25, 2004
- Latest captured
- Jul 9, 2004
- Last refresh
- Oct 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 1,061
- Known gaps
- 0
- ripencc-members-discuss-unmoderated-ripe.net
- Earliest captured
- Jun 1, 2026
- Latest captured
- Oct 9, 2026
- Last refresh
- Oct 9, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 6,941
- Known gaps
- 7
- ripencc-members-discuss-ripe.net
- Earliest captured
- Mar 8, 2007
- Latest captured
- Oct 6, 2026
- Last refresh
- Oct 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,373
- Known gaps
- 0
- ripencc-myasntesting-ripe.net
- Earliest captured
- Aug 14, 2003
- Latest captured
- Jun 29, 2009
- Last refresh
- Oct 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,411
- Known gaps
- 0
- ripencc-ncc-announce-ripe.net
- Earliest captured
- Jun 27, 2006
- Latest captured
- Oct 6, 2026
- Last refresh
- Oct 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,984
- Known gaps
- 0
- ripencc-ncc-services-wg-ripe.net
- Earliest captured
- Aug 6, 2003
- Latest captured
- Oct 2, 2026
- Last refresh
- Oct 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,302
- Known gaps
- 0
- ripencc-nccdays-pc-ripe.net
- Earliest captured
- Unknown
- Latest captured
- Unknown
- Last refresh
- Oct 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 19
- Known gaps
- 0
- ripencc-opensource-wg-ripe.net
- Earliest captured
- Mar 14, 2013
- Latest captured
- Oct 2, 2026
- Last refresh
- Oct 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,624
- Known gaps
- 0
- ripencc-persian-lir-ripe.net
- Earliest captured
- Jul 9, 2015
- Latest captured
- Jul 8, 2023
- Last refresh
- Oct 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 5,253
- Known gaps
- 0
- ripencc-policy-announce-ripe.net
- Earliest captured
- Aug 30, 2005
- Latest captured
- Sep 28, 2026
- Last refresh
- Oct 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,705
- Known gaps
- 0
- ripencc-raci-list-ripe.net
- Earliest captured
- Jul 24, 2014
- Latest captured
- Sep 22, 2026
- Last refresh
- Oct 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,049
- Known gaps
- 0
- ripencc-regional-russia-ripe.net
- Earliest captured
- Sep 27, 2005
- Latest captured
- Jul 4, 2011
- Last refresh
- Oct 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 4,569
- Known gaps
- 0
- ripencc-regional-ukraine-ripe.net
- Earliest captured
- Mar 23, 2007
- Latest captured
- Jul 12, 2007
- Last refresh
- Oct 9, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 1,837
- Known gaps
- 1
- ripencc-ripe-atlas-ambassadors-ripe.net
- Earliest captured
- Dec 20, 2013
- Latest captured
- Sep 23, 2026
- Last refresh
- Oct 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 4,800
- Known gaps
- 0
- ripencc-ripe-atlas-tools-maintainers-ripe.net
- Earliest captured
- Jan 12, 2016
- Latest captured
- Mar 25, 2016
- Last refresh
- Oct 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 1,411
- Known gaps
- 0
- ripencc-ripe-atlas-ripe.net
- Earliest captured
- Oct 14, 2010
- Latest captured
- Oct 9, 2026
- Last refresh
- Oct 8, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 4,134
- Known gaps
- 1
- ripencc-ripe-chair-discuss-ripe.net
- Earliest captured
- Oct 7, 2016
- Latest captured
- Oct 17, 2022
- Last refresh
- Oct 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,420
- Known gaps
- 0
- ripencc-ripe-db-requirements-tf-ripe.net
- Earliest captured
- Oct 15, 2019
- Latest captured
- Nov 16, 2021
- Last refresh
- Oct 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 4,134
- Known gaps
- 0
- ripencc-ripe-forum-test-ripe.net
- Earliest captured
- Apr 11, 2016
- Latest captured
- Jun 20, 2019
- Last refresh
- Oct 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,274
- Known gaps
- 0
- ripencc-ripe-list-unmoderated-ripe.net
- Earliest captured
- Jun 1, 2026
- Latest captured
- Oct 9, 2026
- Last refresh
- Oct 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 6,804
- Known gaps
- 0
- ripencc-ripe-list-ripe.net
- Earliest captured
- Jul 2, 1992
- Latest captured
- Oct 5, 2026
- Last refresh
- Oct 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,569
- Known gaps
- 0
- ripencc-ripe-parents-ripe.net
- Earliest captured
- Oct 19, 2011
- Latest captured
- May 5, 2016
- Last refresh
- Oct 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 1,810
- Known gaps
- 0
- ripencc-ripecast-ripe.net
- Earliest captured
- Aug 29, 2003
- Latest captured
- Sep 28, 2009
- Last refresh
- Oct 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 4,146
- Known gaps
- 0
- ripencc-rirs-lea-ripe.net
- Earliest captured
- Jul 2, 2016
- Latest captured
- Apr 9, 2019
- Last refresh
- Oct 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,845
- Known gaps
- 1
- ripencc-ris-int-ripe.net
- Earliest captured
- Dec 31, 1997
- Latest captured
- Nov 26, 2016
- Last refresh
- Oct 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 4,107
- Known gaps
- 0
- ripencc-ris-users-ripe.net
- Earliest captured
- Aug 8, 2003
- Latest captured
- Aug 24, 2026
- Last refresh
- Oct 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,710
- Known gaps
- 0
- ripencc-routing-wg-ripe.net
- Earliest captured
- Nov 29, 1993
- Latest captured
- Oct 9, 2026
- Last refresh
- Oct 8, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 4,303
- Known gaps
- 1
- ripencc-rpslng-ripe.net
- Earliest captured
- Aug 26, 2003
- Latest captured
- Nov 8, 2007
- Last refresh
- Oct 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,212
- Known gaps
- 0
- ripencc-security-wg-ripe.net
- Earliest captured
- Nov 18, 2024
- Latest captured
- Oct 5, 2026
- Last refresh
- Oct 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 13,818
- Known gaps
- 1
- ripencc-see-regional-ripe.net
- Earliest captured
- Aug 24, 2011
- Latest captured
- Sep 28, 2026
- Last refresh
- Oct 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,460
- Known gaps
- 0
- ripencc-techsec-wg-ripe.net
- Earliest captured
- May 15, 2001
- Latest captured
- Feb 29, 2016
- Last refresh
- Oct 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,736
- Known gaps
- 0
- ripencc-tld-wg-ripe.net
- Earliest captured
- Jul 9, 1997
- Latest captured
- Apr 22, 2015
- Last refresh
- Oct 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 4,313
- Known gaps
- 0
- ripencc-tt-tf-ripe.net
- Earliest captured
- May 30, 2006
- Latest captured
- Dec 7, 2007
- Last refresh
- Oct 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,023
- Known gaps
- 0
Coverage
Partial
Earliest captured: Jun 30, 1992
Latest captured: Oct 10, 2026
Freshness
Known gaps
- www.ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-address-policy-wg: Source coverage is incomplete. · The source boundary has not yet been reached.
- www.ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-accountability-tf-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-agm-nominations-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-all-anchors-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-anti-abuse-wg-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-atlas-sponsors-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-atlas-sw-probes-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-bcop-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-coc-tf-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-connect-bof-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-connect-wg-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-cooperation-wg-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-db-help-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-db-wg-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-diversity-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-dns-resolver-tf-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-dns-wg-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-dp-tf-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-eb-candidates-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-eix-wg-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-election-cc-team-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-enum-announce-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-enum-wg-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-green-tech-hackathon-orga-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-hackathon-list-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-icann-plan-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-iot-wg-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-ipmap-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-ipmt-dev-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-ipv6-wg-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-irrtoolset-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-lir-wg-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-mat-wg-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-measure-voip-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-members-discuss-unmoderated-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-members-discuss-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-myasntesting-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-ncc-announce-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-ncc-services-wg-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-nccdays-pc-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-opensource-wg-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-persian-lir-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-policy-announce-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-raci-list-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-regional-russia-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-regional-ukraine-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-ripe-atlas-ambassadors-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-ripe-atlas-tools-maintainers-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-ripe-atlas-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-ripe-chair-discuss-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-ripe-db-requirements-tf-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-ripe-forum-test-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-ripe-list-unmoderated-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-ripe-list-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-ripe-parents-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-ripecast-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-rirs-lea-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-ris-int-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-ris-users-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-routing-wg-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-rpslng-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-security-wg-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-see-regional-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-techsec-wg-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-tld-wg-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- ripencc-tt-tf-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.
