BTW.Media
Daily editionStrategic Internet Intelligence
Sign InRegister

RIPE NCC · RIR Watchdog

Allocations from the last /8

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
2010-02
RIR
RIPE NCC
Official status
Accepted
Normalized status
Accepted
Introduced
Unknown
Last source update
Sep 14, 2026
Coverage
Partial

Who actually shaped the debate?

3Total participants
1Discussion contributors
2Formal actors
1Discussion messages
1Effective participants
100%Top-five discussion share
1People covering 50%
1People covering 80%

Policy evolution

2.0
Accepted · Accepted
Aug 14, 2010
Source facts ↗

Summary's timing language · Version 2 removes the summary's express reference to total depletion of the IANA free pool. This is a change in the summary; the retained Version 2 proposal text does not reproduce operative clauses, so it does not establish a replacement activation rule.

Source facts −
This proposal describes how the RIPE NCC should distribute address space from its last /8 worth of IPv4 address space at the time of total depletion of the IANA free pool.
Source facts ↗
Source facts +
This proposal describes how the RIPE NCC should distribute address space from its last /8 worth of IPv4 address space.
Source facts ↗

New entrants in the rationale · Version 2 adds an explicit justification for preserving access for new entrants: they may still need a small IPv4 block before an IPv6-only Internet is practical. This develops the earlier transition rationale without demonstrating a new allocation entitlement.

Source facts −
The proposal attempts to ensure that no organisation lacks real routable IPv4 address space during the coming transition to IPv6.
Source facts ↗
Source facts +
It is very important that new entrants also have the chance to get some IPv4 space before it totally runs out because a small block of IPv4 addresses will be necessary for a while before the Internet can run on an IPv6-only platform.
Source facts ↗

Provider-independent assignments · Version 2 expressly states in its opposing-arguments section that IPv4 PI addresses will not be assigned under this proposal. The earlier opposing-arguments section instead begins with organisations whose requirements exceed the minimum sizes. This is an explicit scope statement in the later rationale, not proof of a change in an adopted policy.

Source facts −
b. Arguments Opposing the Proposal Some organisations may believe and can demonstrate that their IPv4 requirements are larger than the minimum allocation or assignment sizes in RIPE region.
Source facts ↗
Source facts +
b. Arguments Opposing the Proposal IPv4 PI addresses will not be assigned through this policy.
Source facts ↗

Limits of the retained Version 2 comparison · The retained Version 1 proposal includes allocation clauses, while the retained Version 2 proposal moves directly from its summary to the rationale. The source page's separate staff impact analysis is not operative policy text. The missing clause block cannot establish that the earlier allocation cap, IPv6 condition or reserve was abolished.

Source facts −
LIRs may only receive one allocation from this /8. The size of the allocation made under this policy will be no larger than a /22.
Source facts ↗
Source facts +
Summary of Proposal: This proposal describes how the RIPE NCC should distribute address space from its last /8 worth of IPv4 address space. Rationale:
Source facts ↗
3.0
Accepted · Accepted
Aug 14, 2010
Source facts ↗

Final IANA block and PA-only scope · Version 3 specifies the final /8 address block received from IANA and expressly limits the proposal to PA allocations, excluding other allocation and assignment types. Version 2's summary refers more generally to the last /8 worth of IPv4 space; its rationale separately excludes IPv4 PI assignments.

Source facts −
This proposal describes how the RIPE NCC should distribute address space from its last /8 worth of IPv4 address space.
Source facts ↗
Source facts +
This proposal describes how the RIPE NCC should distribute IPv4 address space from the final /8 address block it receives from the IANA. The proposal only discusses PA allocations; any other type of allocation or assignment is out of scope for this proposal.
Source facts ↗

Express trigger in Version 3 policy text · Version 3 includes an operative-text trigger: the rules take effect when the RIPE NCC must allocate from the final /8 received from IANA. Version 2's retained proposal passage contains its summary and rationale but no operative clause block, so this comparison does not establish what wording that block replaced or when the policy was implemented.

Source facts −
Summary of Proposal: This proposal describes how the RIPE NCC should distribute address space from its last /8 worth of IPv4 address space. Rationale:
Source facts ↗
Source facts +
The following policies come into effect as soon as RIPE NCC is required to make allocations from the final /8 it receives from the IANA.
Source facts ↗

Exactly one /22 allocation stated in the later text · Version 3's policy text states one allocation of exactly /22 per LIR, even when a larger need is justified. Version 2's retained rationale does not supply the corresponding operative clause. Its appearance here must not be described as proof that this condition was newly introduced in Version 3.

Source facts −
Some organisations may believe and can demonstrate that their IPv4 requirements are larger than the minimum allocation or assignment sizes in RIPE region. But this final /8 is not intended as a solution to the growth needs of a few organisations, but for assisting with the transition from IPv4 to IPv6.
Source facts ↗
Source facts +
LIRs may only receive one allocation from this /8. The size of the allocation made under this policy will be exactly one /22. LIRs receive only one /22, even if their needs justify a larger allocation.
Source facts ↗

Reserve provision visible in Version 3 · Version 3's operative text includes a /16 reserve for unforeseen uses and returns it to the allocation pool if still unused after the rest of the /8 is distributed. The corresponding clause block is absent from the retained Version 2 proposal passage; this is a document-coverage difference, not evidence that Version 3 newly created the reserve.

Source facts −
Summary of Proposal: This proposal describes how the RIPE NCC should distribute address space from its last /8 worth of IPv4 address space. Rationale:
Source facts ↗
Source facts +
Unforeseen circumstances A /16 will be held in reserve for some future uses, as yet unforeseen. The Internet is a disruptive technology and we cannot predict what might happen. Therefore it is prudent to keep a /16 in reserve, just in case some future requirement makes a demand of it. In the event that this /16 remains unused at the time the remaining /8 covered by this policy has been distributed, it returns to the pool to be distributed as per clause 1.
Source facts ↗

Debate timeline

  1. Official version

    1.0

    Accepted · Accepted

    Source facts ↗

  2. Official version

    2.0

    Accepted · Accepted

    Source facts ↗

  3. Official version

    3.0

    Accepted · Accepted

    Source facts ↗

  4. Official decision

    accepted

    accepted

    Source facts ↗

Entities

Freshness: Stale
  1. Gert Doering
    Discussion messages1
    First activityNov 15, 2010
    Last activityNov 15, 2010
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyInsufficient evidence to assess consistency
    Other policies15
    Freshness: Stale

    Last research attempt: Oct 6, 2026

    Identity verified: Sep 25, 2026

    SpaceNet AG · Historical
    Gert Doering [SpaceNet AG]
    ripe.net
    RIPE Address Policy Working Group · Historical
    Gert Doering from SpaceNet AG was reconfirmed for another term as Co-chair.
    ripe74.ripe.net
    RIPE 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.net
    Discussion messages
    1
    First activity
    Nov 15, 2010
    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

    PI Assignment Size

    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)

    Allocations from the last /8

    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

    1. Nov 15, 2010 · Procedural or neutral

      [address-policy-wg] Agenda (second draft) for RIPE 61 in Rome

      [ONGOING] … 2010-02 Allocations from the last /8 [15 min] … (new combined proposal from Philip Smith and Alain Bidron) … [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 consistency

    Total policy messages: 41

  2. Alain Bidron · Identity unresolved
    Discussion messages0
    First activityUnknown
    Last activityUnknown
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies0
  3. Philip Smith · Identity unresolved
    Discussion messages0
    First activityUnknown
    Last activityUnknown
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other 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,670
    Known gaps
    70
  • www.ripe.net
  • ripencc-accountability-tf-ripe.net
    Earliest captured
    Nov 24, 2016
    Latest captured
    May 9, 2019
    Last refresh
    Oct 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    4,325
    Known gaps
    0
  • ripencc-agm-nominations-ripe.net
    Earliest captured
    Mar 26, 2008
    Latest captured
    Apr 28, 2026
    Last refresh
    Oct 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    4,077
    Known gaps
    0
  • ripencc-all-anchors-ripe.net
    Earliest captured
    Oct 31, 2014
    Latest captured
    Oct 31, 2014
    Last refresh
    Oct 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    553
    Known gaps
    0
  • ripencc-anti-abuse-wg-ripe.net
    Earliest captured
    Sep 16, 2008
    Latest captured
    Nov 4, 2025
    Last refresh
    Oct 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    4,038
    Known gaps
    0
  • ripencc-atlas-sponsors-ripe.net
    Earliest captured
    Dec 7, 2012
    Latest captured
    Mar 31, 2014
    Last refresh
    Oct 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    1,794
    Known gaps
    0
  • ripencc-atlas-sw-probes-ripe.net
    Earliest captured
    Oct 21, 2019
    Latest captured
    Jul 24, 2024
    Last refresh
    Oct 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,709
    Known gaps
    0
  • ripencc-bcop-ripe.net
    Earliest captured
    Jun 16, 2013
    Latest captured
    Oct 29, 2024
    Last refresh
    Oct 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    5,064
    Known gaps
    0
  • ripencc-coc-tf-ripe.net
    Earliest captured
    Sep 18, 2020
    Latest captured
    Apr 20, 2023
    Last refresh
    Oct 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,974
    Known gaps
    0
  • ripencc-connect-bof-ripe.net
    Earliest captured
    Oct 18, 2013
    Latest captured
    Jul 14, 2014
    Last refresh
    Oct 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    2,951
    Known gaps
    1
  • ripencc-connect-wg-ripe.net
    Earliest captured
    Oct 20, 2014
    Latest captured
    Sep 28, 2026
    Last refresh
    Oct 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    5,002
    Known gaps
    0
  • ripencc-cooperation-wg-ripe.net
    Earliest captured
    Aug 26, 2008
    Latest captured
    Oct 6, 2026
    Last refresh
    Oct 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    4,970
    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,809
    Known gaps
    1
  • ripencc-db-wg-ripe.net
    Earliest captured
    Oct 21, 1992
    Latest captured
    Oct 12, 2026
    Last refresh
    Oct 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,714
    Known gaps
    0
  • ripencc-diversity-ripe.net
    Earliest captured
    May 18, 2017
    Latest captured
    Feb 9, 2026
    Last refresh
    Oct 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    4,376
    Known gaps
    0
  • ripencc-dns-resolver-tf-ripe.net
    Earliest captured
    Jan 23, 2023
    Latest captured
    Feb 16, 2025
    Last refresh
    Oct 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,220
    Known gaps
    0
  • ripencc-dns-wg-ripe.net
    Earliest captured
    Jun 30, 1992
    Latest captured
    Oct 9, 2026
    Last refresh
    Oct 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,536
    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,105
    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,296
    Known gaps
    69
  • ripencc-eix-wg-ripe.net
    Earliest captured
    Jan 1, 1999
    Latest captured
    Oct 21, 2013
    Last refresh
    Oct 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    4,346
    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
    489
    Known gaps
    1
  • ripencc-enum-announce-ripe.net
    Earliest captured
    Aug 15, 2003
    Latest captured
    Sep 15, 2026
    Last refresh
    Oct 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,754
    Known gaps
    0
  • ripencc-enum-wg-ripe.net
    Earliest captured
    Jun 16, 2004
    Latest captured
    Nov 20, 2013
    Last refresh
    Oct 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    4,023
    Known gaps
    0
  • ripencc-green-tech-hackathon-orga-ripe.net
    Earliest captured
    Unknown
    Latest captured
    Unknown
    Last refresh
    Oct 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    25
    Known gaps
    1
  • ripencc-hackathon-list-ripe.net
    Earliest captured
    Feb 26, 2015
    Latest captured
    Jan 9, 2025
    Last refresh
    Oct 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,454
    Known gaps
    1
  • ripencc-icann-plan-ripe.net
    Earliest captured
    Dec 8, 2004
    Latest captured
    Jan 31, 2005
    Last refresh
    Oct 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    859
    Known gaps
    0
  • ripencc-iot-wg-ripe.net
    Earliest captured
    Nov 3, 2016
    Latest captured
    Aug 19, 2026
    Last refresh
    Oct 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,677
    Known gaps
    0
  • ripencc-ipmap-ripe.net
    Earliest captured
    Nov 25, 2021
    Latest captured
    May 17, 2022
    Last refresh
    Oct 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    655
    Known gaps
    0
  • ripencc-ipmt-dev-ripe.net
    Earliest captured
    May 3, 2001
    Latest captured
    Jul 2, 2003
    Last refresh
    Oct 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,022
    Known gaps
    0
  • ripencc-ipv6-wg-ripe.net
    Earliest captured
    Mar 31, 1995
    Latest captured
    Oct 12, 2026
    Last refresh
    Oct 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,614
    Known gaps
    0
  • ripencc-irrtoolset-ripe.net
    Earliest captured
    Aug 12, 2003
    Latest captured
    Dec 15, 2004
    Last refresh
    Oct 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,839
    Known gaps
    0
  • ripencc-lir-wg-ripe.net
    Earliest captured
    Oct 8, 1992
    Latest captured
    Jun 30, 2003
    Last refresh
    Oct 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,466
    Known gaps
    0
  • ripencc-mat-wg-ripe.net
    Earliest captured
    May 18, 2010
    Latest captured
    Sep 23, 2026
    Last refresh
    Oct 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,129
    Known gaps
    0
  • ripencc-measure-voip-ripe.net
    Earliest captured
    May 25, 2004
    Latest captured
    Jul 9, 2004
    Last refresh
    Oct 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    1,185
    Known gaps
    0
  • ripencc-members-discuss-unmoderated-ripe.net
    Earliest captured
    Jun 1, 2026
    Latest captured
    Oct 13, 2026
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    7,900
    Known gaps
    14
  • ripencc-members-discuss-ripe.net
    Earliest captured
    Mar 8, 2007
    Latest captured
    Oct 6, 2026
    Last refresh
    Oct 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,751
    Known gaps
    0
  • ripencc-myasntesting-ripe.net
    Earliest captured
    Aug 14, 2003
    Latest captured
    Jun 29, 2009
    Last refresh
    Oct 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,921
    Known gaps
    0
  • ripencc-ncc-announce-ripe.net
    Earliest captured
    Jun 27, 2006
    Latest captured
    Oct 6, 2026
    Last refresh
    Oct 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,385
    Known gaps
    0
  • ripencc-ncc-services-wg-ripe.net
    Earliest captured
    Aug 6, 2003
    Latest captured
    Oct 2, 2026
    Last refresh
    Oct 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,727
    Known gaps
    0
  • ripencc-nccdays-pc-ripe.net
    Earliest captured
    Unknown
    Latest captured
    Unknown
    Last refresh
    Oct 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    27
    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,203
    Known gaps
    1
  • ripencc-persian-lir-ripe.net
    Earliest captured
    Jul 9, 2015
    Latest captured
    Jul 8, 2023
    Last refresh
    Oct 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    6,048
    Known gaps
    0
  • ripencc-policy-announce-ripe.net
    Earliest captured
    Aug 30, 2005
    Latest captured
    Oct 13, 2026
    Last refresh
    Oct 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    4,211
    Known gaps
    1
  • ripencc-raci-list-ripe.net
    Earliest captured
    Jul 24, 2014
    Latest captured
    Sep 22, 2026
    Last refresh
    Oct 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,635
    Known gaps
    0
  • ripencc-regional-russia-ripe.net
    Earliest captured
    Sep 27, 2005
    Latest captured
    Jul 4, 2011
    Last refresh
    Oct 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    5,223
    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,012
    Known gaps
    1
  • ripencc-ripe-atlas-ambassadors-ripe.net
    Earliest captured
    Dec 20, 2013
    Latest captured
    Sep 23, 2026
    Last refresh
    Oct 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    5,554
    Known gaps
    0
  • ripencc-ripe-atlas-tools-maintainers-ripe.net
    Earliest captured
    Jan 12, 2016
    Latest captured
    Mar 25, 2016
    Last refresh
    Oct 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    1,593
    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,628
    Known gaps
    1
  • ripencc-ripe-chair-discuss-ripe.net
    Earliest captured
    Oct 7, 2016
    Latest captured
    Oct 17, 2022
    Last refresh
    Oct 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,848
    Known gaps
    0
  • ripencc-ripe-db-requirements-tf-ripe.net
    Earliest captured
    Oct 15, 2019
    Latest captured
    Nov 16, 2021
    Last refresh
    Oct 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    4,805
    Known gaps
    0
  • ripencc-ripe-forum-test-ripe.net
    Earliest captured
    Apr 11, 2016
    Latest captured
    Jun 20, 2019
    Last refresh
    Oct 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    2,622
    Known gaps
    0
  • ripencc-ripe-list-unmoderated-ripe.net
    Earliest captured
    Jun 1, 2026
    Latest captured
    Oct 13, 2026
    Last refresh
    Oct 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    7,589
    Known gaps
    0
  • ripencc-ripe-list-ripe.net
    Earliest captured
    Jul 2, 1992
    Latest captured
    Oct 5, 2026
    Last refresh
    Oct 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    4,048
    Known gaps
    0
  • ripencc-ripe-parents-ripe.net
    Earliest captured
    Oct 19, 2011
    Latest captured
    May 5, 2016
    Last refresh
    Oct 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    2,077
    Known gaps
    0
  • ripencc-ripecast-ripe.net
    Earliest captured
    Aug 29, 2003
    Latest captured
    Sep 28, 2009
    Last refresh
    Oct 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    4,741
    Known gaps
    0
  • ripencc-rirs-lea-ripe.net
    Earliest captured
    Jul 2, 2016
    Latest captured
    Apr 9, 2019
    Last refresh
    Oct 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,330
    Known gaps
    1
  • ripencc-ris-int-ripe.net
    Earliest captured
    Dec 31, 1997
    Latest captured
    Nov 26, 2016
    Last refresh
    Oct 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    4,688
    Known gaps
    0
  • ripencc-ris-users-ripe.net
    Earliest captured
    Aug 8, 2003
    Latest captured
    Aug 24, 2026
    Last refresh
    Oct 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    4,255
    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,709
    Known gaps
    3
  • ripencc-rpslng-ripe.net
    Earliest captured
    Aug 26, 2003
    Latest captured
    Nov 8, 2007
    Last refresh
    Oct 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,653
    Known gaps
    0
  • ripencc-security-wg-ripe.net
    Earliest captured
    Nov 18, 2024
    Latest captured
    Oct 13, 2026
    Last refresh
    Oct 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    14,257
    Known gaps
    1
  • ripencc-see-regional-ripe.net
    Earliest captured
    Aug 24, 2011
    Latest captured
    Sep 28, 2026
    Last refresh
    Oct 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    4,030
    Known gaps
    0
  • ripencc-techsec-wg-ripe.net
    Earliest captured
    May 15, 2001
    Latest captured
    Feb 29, 2016
    Last refresh
    Oct 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    4,279
    Known gaps
    1
  • ripencc-tld-wg-ripe.net
    Earliest captured
    Jul 9, 1997
    Latest captured
    Apr 22, 2015
    Last refresh
    Oct 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    4,915
    Known gaps
    0
  • ripencc-tt-tf-ripe.net
    Earliest captured
    May 30, 2006
    Latest captured
    Dec 7, 2007
    Last refresh
    Oct 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    2,344
    Known gaps
    0

Coverage

Partial
Earliest captured: Jun 30, 1992
Latest captured: Oct 14, 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.