RIPE NCC · RIR Watchdog
PI Assignment Size
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
- 2006-05
- RIR
- RIPE NCC
- Official status
- Accepted
- Normalized status
- Accepted
- Introduced
- Unknown
- Last source update
- Oct 12, 2026
- Coverage
- Partial
Who actually shaped the debate?
11Total participants
9Discussion contributors
2Formal actors
13Discussion messages
7.3Effective participants
69.2%Top-five discussion share
3People covering 50%
7People covering 80%
Policy evolution
Debate timeline
Public discussion
RE: [address-policy-wg] PA Assignment questions
2 Discussion messages · 2 Entities
Source facts ↗Public discussion
Re: [address-policy-wg] Reopening discussion on RIPE Policy Proposal 2006-05
8 Discussion messages · 6 Entities
Source facts ↗
Entities
Freshness: Stale
- Discussion messages3First activityApr 22, 2009Last activityNov 15, 2010First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyInsufficient evidence to assess consistencyOther policies15Freshness: Stale
Last research attempt: Oct 6, 2026
Identity verified: Sep 25, 2026
SpaceNet AG · Historical Gert Doering [SpaceNet AG]
ripe.netRIPE Address Policy Working Group · Historical Gert Doering from SpaceNet AG was reconfirmed for another term as Co-chair.
ripe74.ripe.netRIPE NCC · Historical Gert Doering - 24-11-2021 17:57:02 we can move the charging scheme to APWG, would simplify Erik's and my life :-)
www.ripe.netVerified public profiles
- Discussion messages
- 3
- First activity
- Apr 22, 2009
- Last activity
- Nov 15, 2010
- First explicit stance
- Unknown
- Latest explicit stance
- Unknown
- Stance changes
- 0
- Viewpoint consistency
- Insufficient evidence to assess consistency
- Other policies
- 15
First explicit stance: Unknown → Latest explicit stance: Unknown · Stance changes: 0
Viewpoint consistency: Insufficient evidence to assess consistency
The supplied record contains one meeting agenda and one later explanation of final-/8 policy scope. Chairing discussion, listing proposals and explaining a rule do not establish a sequence of personal votes. The two messages show no demonstrated contradiction, but do not justify a general claim that the author consistently supported or opposed these policies.
Temporary Internet Number Assignment Policies
Assessment: Insufficient evidence to assess consistency · The agenda schedules Nick Hilliard to discuss temporary assignments and marks the proposal ongoing. Scheduling the item and moving its time slot establish procedural participation, not the chair's endorsement or opposition.
2010-01 Temporary Internet Number Assignment Policies
Assessment: Insufficient evidence to assess consistency · The PI assignment-size proposal is listed as ongoing or revived under another presenter. This single agenda entry contains no personal position or subsequent change to compare.
2006-05 PI Assignment Size
Registration Requirements for IPv6 End User Assignments
Assessment: Insufficient evidence to assess consistency · The proposal appears only in a brief overview of new proposals. Nearby discussion of IPv6 utilisation thresholds and end-site definitions cannot be treated as a substantive stance on the registration-requirements proposal merely because it shares the agenda.
brief overview over new proposals (2010-05, 2010-06, 2010-07)
Assessment: Insufficient evidence to assess consistency · The agenda schedules the combined last-/8 proposal for discussion without a vote. The later message explains the purpose of the existing last-/8 rule while discussing a separate clarification; it does not retrospectively turn this agenda into support for all terms of the earlier proposal.
2010-02 Allocations from the last /8
Ambiguity cleanup on IPv6 Address Space Policy for IXP
Assessment: Insufficient evidence to assess consistency · The chair frames a wider discussion of what the IPv6 IXP policy should achieve before settling wording. That is a substantive agenda choice, but it selects no final eligibility rule and provides no sequence of positions from which to infer consistency or reversal.
Conditions: A listed presentation by the author does not make every proposed rule his own position.
initiated by 2010-07, but widening the scope from "wording change" to "figure out what the policy should be, *then* talk about specific wording"
Initial Certification Policy in the RIPE NCC Service Region
Assessment: Insufficient evidence to assess consistency · The certification item names Nigel Titley and a version-two update. The agenda shows that discussion was scheduled; it supplies no personal assessment of certification benefits, political risks or safeguards by the chair.
2008-08 Initial Certification Policy for PA Space Holders
Global Policy for IPv4 Allocation by the IANA Post Exhaustion
Assessment: Insufficient evidence to assess consistency · The global post-exhaustion allocation proposal is scheduled for presentation and discussion. The provocative description of a possible argument signals expected disagreement, not an attributable policy vote or evidence of what participants eventually decided.
2010-05 Global Policy for IPv4 Allocation by the IANA
Post-depletion IPv4 address recycling
Assessment: Insufficient evidence to assess consistency · The later reply explains that the proposed clarification would keep final-/8 rules in effect even after returned space lifted the pool above a /8. It distinguishes this from revisiting the opportunity for future entrants to obtain transition addresses. One explanation of scope is insufficient to establish a stable personal voting position.
Conditions: The author explicitly acknowledges that IPv4 still runs out. · An explanation of intended effect is not a consensus declaration, adoption decision or endorsement of every draft provision.
this is to clarify that the "last /8" policy will *stay* in effect after it became active, even if some address space is returned and the NCC ends up having again more than a /8 available.
Allocations from the last /8 · Post-depletion IPv4 address recycling
Assessment: Insufficient evidence to assess consistency · Listing the original final-/8 proposal in 2010 and explaining a narrower continuation rule in 2011 are compatible procedural acts. They do not demonstrate a reversal, but neither act establishes two substantive personal positions sufficient for a strong cross-policy consistency claim.
Conditions: The 2011 reply discusses the clarification rather than reopening the original allocation design.
2010-02 Allocations from the last /8
and this part is not being discussed at all by the policy proposal here
- Apr 22, 2009 · Unknown
[address-policy-wg] (Draft) Agenda for RIPE 58
Validated evidence is unavailable.
Source facts ↗ - Sep 20, 2009 · Unknown
[address-policy-wg] agenda for upcoming APWG meeting
Validated evidence is unavailable.
Source facts ↗ - Nov 15, 2010 · Procedural or neutral
[address-policy-wg] Agenda (second draft) for RIPE 61 in Rome
H. Discussion of open policy proposals, "PI related" … 2006-05 PI Assignment Size [15 min] … [ONGOING] … [ONGOING]
Source facts ↗
Per-policy stance timelines:2005-09 · Unknown · No explicit position stated2005-11 · Unknown · No explicit position stated2006-05 · Unknown · Insufficient evidence to assess consistency2007-08 · Unknown · No explicit position stated2008-05 · Unknown · No explicit position stated2008-08 · Unknown · Insufficient evidence to assess consistency2009-03 · Unknown · No explicit position stated2009-04 · Unknown · No explicit position stated2009-05 · Unknown · No explicit position stated2009-06 · Unknown · No explicit position stated2010-01 · Unknown · Insufficient evidence to assess consistency2010-02 · Unknown · Insufficient evidence to assess consistency2010-05 · Unknown · Insufficient evidence to assess consistency2010-06 · Unknown · Insufficient evidence to assess consistency2010-07 · Unknown · Insufficient evidence to assess consistency2011-03 · Unknown · Insufficient evidence to assess consistencyTotal policy messages: 41
- Leo Vegoda · Identity unresolvedDiscussion messages2First activityJul 27, 2009Last activityJul 27, 2009First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies1
- Per Heldal · Identity unresolvedDiscussion messages2First activityJul 28, 2009Last activityJul 28, 2009First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies1
- Wilfried Woeber, UniVie/ACOnet · Identity unresolvedDiscussion messages1First activityAug 20, 2009Last activityAug 20, 2009First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies2
- Nolan, Keith · Identity unresolvedDiscussion messages1First activityJul 16, 2009Last activityJul 16, 2009First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies0
- Sascha Lenz · Identity unresolvedDiscussion messages1First activityJul 16, 2009Last activityJul 16, 2009First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies1
- David Freedman · Identity unresolvedDiscussion messages1First activityJul 28, 2009Last activityJul 28, 2009First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies0
- Stream Service || Mark Scholten · Identity unresolvedDiscussion messages1First activityJul 27, 2009Last activityJul 27, 2009First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies2
- Jeroen Massar · Identity unresolvedDiscussion messages1First activityJul 28, 2009Last activityJul 28, 2009First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies1
- Discussion messages0First activityUnknownLast activityUnknownFirst explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies2
- 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 12, 2026
- Last refresh
- Aug 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 20,625
- Known gaps
- 69
- www.ripe.net
- ripencc-accountability-tf-ripe.net
- Earliest captured
- Nov 24, 2016
- Latest captured
- May 9, 2019
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 4,288
- Known gaps
- 0
- ripencc-agm-nominations-ripe.net
- Earliest captured
- Mar 26, 2008
- Latest captured
- Apr 28, 2026
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 4,039
- Known gaps
- 0
- ripencc-all-anchors-ripe.net
- Earliest captured
- Oct 31, 2014
- Latest captured
- Oct 31, 2014
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 543
- Known gaps
- 0
- ripencc-anti-abuse-wg-ripe.net
- Earliest captured
- Sep 16, 2008
- Latest captured
- Nov 4, 2025
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,989
- Known gaps
- 0
- ripencc-atlas-sponsors-ripe.net
- Earliest captured
- Dec 7, 2012
- Latest captured
- Mar 31, 2014
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 1,767
- Known gaps
- 0
- ripencc-atlas-sw-probes-ripe.net
- Earliest captured
- Oct 21, 2019
- Latest captured
- Jul 24, 2024
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,665
- Known gaps
- 0
- ripencc-bcop-ripe.net
- Earliest captured
- Jun 16, 2013
- Latest captured
- Oct 29, 2024
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 5,008
- Known gaps
- 0
- ripencc-coc-tf-ripe.net
- Earliest captured
- Sep 18, 2020
- Latest captured
- Apr 20, 2023
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,943
- Known gaps
- 0
- ripencc-connect-bof-ripe.net
- Earliest captured
- Oct 18, 2013
- Latest captured
- Jul 14, 2014
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,913
- Known gaps
- 1
- ripencc-connect-wg-ripe.net
- Earliest captured
- Oct 20, 2014
- Latest captured
- Sep 28, 2026
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 4,972
- Known gaps
- 0
- ripencc-cooperation-wg-ripe.net
- Earliest captured
- Aug 26, 2008
- Latest captured
- Oct 6, 2026
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 4,940
- Known gaps
- 0
- ripencc-db-help-ripe.net
- Earliest captured
- Aug 20, 2003
- Latest captured
- Jan 13, 2016
- Last refresh
- Oct 12, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 4,775
- Known gaps
- 1
- ripencc-db-wg-ripe.net
- Earliest captured
- Oct 21, 1992
- Latest captured
- Oct 12, 2026
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,679
- Known gaps
- 0
- ripencc-diversity-ripe.net
- Earliest captured
- May 18, 2017
- Latest captured
- Feb 9, 2026
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 4,332
- Known gaps
- 0
- ripencc-dns-resolver-tf-ripe.net
- Earliest captured
- Jan 23, 2023
- Latest captured
- Feb 16, 2025
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,194
- Known gaps
- 0
- ripencc-dns-wg-ripe.net
- Earliest captured
- Jun 30, 1992
- Latest captured
- Oct 9, 2026
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,511
- 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
- 3,079
- 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,285
- Known gaps
- 68
- ripencc-eix-wg-ripe.net
- Earliest captured
- Jan 1, 1999
- Latest captured
- Oct 21, 2013
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 4,316
- Known gaps
- 0
- ripencc-election-cc-team-ripe.net
- Earliest captured
- Aug 18, 2026
- Latest captured
- Aug 18, 2026
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 481
- Known gaps
- 1
- ripencc-enum-announce-ripe.net
- Earliest captured
- Aug 15, 2003
- Latest captured
- Sep 15, 2026
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,724
- Known gaps
- 0
- ripencc-enum-wg-ripe.net
- Earliest captured
- Jun 16, 2004
- Latest captured
- Nov 20, 2013
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,992
- Known gaps
- 0
- ripencc-green-tech-hackathon-orga-ripe.net
- Earliest captured
- Unknown
- Latest captured
- Unknown
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 25
- Known gaps
- 0
- ripencc-hackathon-list-ripe.net
- Earliest captured
- Feb 26, 2015
- Latest captured
- Jan 9, 2025
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,423
- Known gaps
- 0
- ripencc-icann-plan-ripe.net
- Earliest captured
- Dec 8, 2004
- Latest captured
- Jan 31, 2005
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 852
- Known gaps
- 0
- ripencc-iot-wg-ripe.net
- Earliest captured
- Nov 3, 2016
- Latest captured
- Aug 19, 2026
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,647
- Known gaps
- 0
- ripencc-ipmap-ripe.net
- Earliest captured
- Nov 25, 2021
- Latest captured
- May 17, 2022
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 649
- Known gaps
- 0
- ripencc-ipmt-dev-ripe.net
- Earliest captured
- May 3, 2001
- Latest captured
- Jul 2, 2003
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,006
- Known gaps
- 0
- ripencc-ipv6-wg-ripe.net
- Earliest captured
- Mar 31, 1995
- Latest captured
- Oct 12, 2026
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,583
- Known gaps
- 0
- ripencc-irrtoolset-ripe.net
- Earliest captured
- Aug 12, 2003
- Latest captured
- Dec 15, 2004
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,807
- Known gaps
- 0
- ripencc-lir-wg-ripe.net
- Earliest captured
- Oct 8, 1992
- Latest captured
- Jun 30, 2003
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,436
- Known gaps
- 0
- ripencc-mat-wg-ripe.net
- Earliest captured
- May 18, 2010
- Latest captured
- Sep 23, 2026
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,098
- Known gaps
- 0
- ripencc-measure-voip-ripe.net
- Earliest captured
- May 25, 2004
- Latest captured
- Jul 9, 2004
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 1,176
- Known gaps
- 0
- ripencc-members-discuss-unmoderated-ripe.net
- Earliest captured
- Jun 1, 2026
- Latest captured
- Oct 12, 2026
- Last refresh
- Oct 9, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 7,813
- Known gaps
- 14
- ripencc-members-discuss-ripe.net
- Earliest captured
- Mar 8, 2007
- Latest captured
- Oct 6, 2026
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,725
- Known gaps
- 0
- ripencc-myasntesting-ripe.net
- Earliest captured
- Aug 14, 2003
- Latest captured
- Jun 29, 2009
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,885
- Known gaps
- 0
- ripencc-ncc-announce-ripe.net
- Earliest captured
- Jun 27, 2006
- Latest captured
- Oct 6, 2026
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,342
- Known gaps
- 0
- ripencc-ncc-services-wg-ripe.net
- Earliest captured
- Aug 6, 2003
- Latest captured
- Oct 2, 2026
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,696
- Known gaps
- 0
- ripencc-nccdays-pc-ripe.net
- Earliest captured
- Unknown
- Latest captured
- Unknown
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 26
- Known gaps
- 0
- ripencc-opensource-wg-ripe.net
- Earliest captured
- Mar 14, 2013
- Latest captured
- Oct 2, 2026
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 4,166
- Known gaps
- 1
- ripencc-persian-lir-ripe.net
- Earliest captured
- Jul 9, 2015
- Latest captured
- Jul 8, 2023
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 6,014
- Known gaps
- 0
- ripencc-policy-announce-ripe.net
- Earliest captured
- Aug 30, 2005
- Latest captured
- Oct 12, 2026
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 4,176
- Known gaps
- 1
- ripencc-raci-list-ripe.net
- Earliest captured
- Jul 24, 2014
- Latest captured
- Sep 22, 2026
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,608
- Known gaps
- 0
- ripencc-regional-russia-ripe.net
- Earliest captured
- Sep 27, 2005
- Latest captured
- Jul 4, 2011
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 5,193
- 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
- 2,002
- Known gaps
- 1
- ripencc-ripe-atlas-ambassadors-ripe.net
- Earliest captured
- Dec 20, 2013
- Latest captured
- Sep 23, 2026
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 5,520
- Known gaps
- 0
- ripencc-ripe-atlas-tools-maintainers-ripe.net
- Earliest captured
- Jan 12, 2016
- Latest captured
- Mar 25, 2016
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 1,580
- 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,583
- Known gaps
- 1
- ripencc-ripe-chair-discuss-ripe.net
- Earliest captured
- Oct 7, 2016
- Latest captured
- Oct 17, 2022
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,833
- Known gaps
- 0
- ripencc-ripe-db-requirements-tf-ripe.net
- Earliest captured
- Oct 15, 2019
- Latest captured
- Nov 16, 2021
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 4,772
- Known gaps
- 0
- ripencc-ripe-forum-test-ripe.net
- Earliest captured
- Apr 11, 2016
- Latest captured
- Jun 20, 2019
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,598
- Known gaps
- 0
- ripencc-ripe-list-unmoderated-ripe.net
- Earliest captured
- Jun 1, 2026
- Latest captured
- Oct 12, 2026
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 7,507
- Known gaps
- 0
- ripencc-ripe-list-ripe.net
- Earliest captured
- Jul 2, 1992
- Latest captured
- Oct 5, 2026
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 4,008
- Known gaps
- 0
- ripencc-ripe-parents-ripe.net
- Earliest captured
- Oct 19, 2011
- Latest captured
- May 5, 2016
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,054
- Known gaps
- 0
- ripencc-ripecast-ripe.net
- Earliest captured
- Aug 29, 2003
- Latest captured
- Sep 28, 2009
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 4,698
- Known gaps
- 0
- ripencc-rirs-lea-ripe.net
- Earliest captured
- Jul 2, 2016
- Latest captured
- Apr 9, 2019
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,293
- Known gaps
- 1
- ripencc-ris-int-ripe.net
- Earliest captured
- Dec 31, 1997
- Latest captured
- Nov 26, 2016
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 4,657
- Known gaps
- 0
- ripencc-ris-users-ripe.net
- Earliest captured
- Aug 8, 2003
- Latest captured
- Aug 24, 2026
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 4,224
- 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,671
- Known gaps
- 1
- ripencc-rpslng-ripe.net
- Earliest captured
- Aug 26, 2003
- Latest captured
- Nov 8, 2007
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,616
- Known gaps
- 0
- ripencc-security-wg-ripe.net
- Earliest captured
- Nov 18, 2024
- Latest captured
- Oct 5, 2026
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 14,222
- Known gaps
- 1
- ripencc-see-regional-ripe.net
- Earliest captured
- Aug 24, 2011
- Latest captured
- Sep 28, 2026
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,995
- Known gaps
- 0
- ripencc-techsec-wg-ripe.net
- Earliest captured
- May 15, 2001
- Latest captured
- Feb 29, 2016
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 4,239
- Known gaps
- 1
- ripencc-tld-wg-ripe.net
- Earliest captured
- Jul 9, 1997
- Latest captured
- Apr 22, 2015
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 4,871
- Known gaps
- 0
- ripencc-tt-tf-ripe.net
- Earliest captured
- May 30, 2006
- Latest captured
- Dec 7, 2007
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,315
- Known gaps
- 0
Coverage
Partial
Earliest captured: Jun 30, 1992
Latest captured: Oct 13, 2026
Freshness
Freshness: Stale · Last refresh:
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.