BTW.Media
Daily editionStrategic Internet Intelligence
Sign InRegister

RIPE NCC · RIR Watchdog

SLURM file for Unallocated and Unassigned RIPE NCC Address Space

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
2019-08
RIR
RIPE NCC
Official status
Withdrawn
Normalized status
Withdrawn
Introduced
Oct 31, 2019
Last source update
Oct 11, 2026
Coverage
Partial

Who actually shaped the debate?

5Total participants
UnknownDiscussion contributors
5Formal actors
UnknownDiscussion messages
UnknownEffective participants
UnknownTop-five discussion share
UnknownPeople covering 50%
UnknownPeople covering 80%

BTW Analysis

BTW Analysis

What changed

No policy change can be identified because the supplied verified policy chronology is empty and no proposal versions, change log, or implementation record are provided.

What the debate was really about

No substantive debate theme can be established. The verified dataset contains zero messages, zero discussion participants, zero formal actors, no stance timelines, and no recorded arguments.

Decision vs debate

Neither a formal decision nor an observed discussion is documented. The supplied facts do not establish whether the proposal was accepted, rejected, withdrawn, appealed, implemented, or otherwise resolved; zero participation metrics cannot determine its procedural or substantive disposition.

Participation concentration

The top-one, top-five, and top-ten message shares, HHI, effective participant count, and core-group counts are all zero because the observed dataset contains zero messages and zero participants. These values do not demonstrate broad or evenly distributed participation, nor do they demonstrate concentration; there is no nonempty participation distribution to assess.

Chokepoint analysis

No participant, coalition, formal actor, or institutional stage can be identified as a policy-process chokepoint from the supplied facts. The immediate analytical chokepoint is the absence of chronology, messages, stance records, formal milestones, and final-disposition evidence, which prevents reconstruction of agenda control, deliberation, consensus formation, or decision authority.

Uncertainties

  • It is uncertain whether the zero activity metrics reflect an actual absence of public debate, an empty source collection, or relevant material outside the measured source revision.
  • The zero concentration measures have limited substantive meaning because the denominator population contains no messages or participants.
  • No verified fact identifies the proposal's final procedural or substantive disposition, decision date, decision-maker, rationale, or implementation status.
  • The supplied Doctrine package has partial status for this subject and does not establish a complete official position or supply missing facts about this policy process.

Policy evolution

2.0
Withdrawn · Withdrawn
Apr 24, 2020
Source facts ↗

Separate trust anchor for registry-created AS0 ROAs · Version 2 adds a dedicated trust anchor and TAL file for RIPE NCC's AS0 ROAs, so tools and researchers can distinguish registry-created records for unallocated or unassigned space from operational ROAs created by resource holders. Version 1 stated the registry's authority to create these ROAs but did not specify this separate distribution arrangement.

Source facts −
Only the RIPE NCC has the authority to create RPKI ROAs for address space not yet allocated or assigned to its members.
Source facts ↗
Source facts +
RIPE NCC creates all its AS0 ROAs under a specific Trust Anchor, and provides a specific Trust Anchor Locator (TAL) file. This way, tools and researchers could benefit from a distinction between operational ROAs created by holders of the address space, and ROAs created by RIPE NCC for unallocated/unassigned address space.
Source facts ↗

Revocation wording before an allocation · Version 1 explicitly allowed allocation only after the AS0 ROAs had been fully removed and were no longer visible in repositories. Version 2 retains the requirement to revoke the relevant AS0 ROAs when allocating space, but omits that explicit repository-visibility condition and the word 'beforehand'. Its opposing-arguments section still discusses a delay of at least 24 hours; this comparison does not turn that discussion into an adopted timing rule.

Source facts −
If the RIPE NCC wants to allocate address space to one of its members, the RPKI ROA or ROAs with origin AS0 will have to be revoked beforehand. Address space can only be allocated once the ROA or ROAs with origin AS0 have been fully removed and are not visible in the repositories.
Source facts ↗
Source facts +
If the RIPE NCC wants to allocate address space to one of its members, the RPKI ROA or ROAs with origin AS0 will have to be revoked.
Source facts ↗

Discussion of less-specific announcements · Version 2 adds an explicit limitation: a less-specific covering announcement can circumvent the AS0 ROA protection. The authors argue that a covering route spanning allocated resources would attract monitoring alerts. This is a qualified threat assessment added to the rationale, not a guarantee that monitoring prevents such announcements.

Source facts −
Given the state of today's RPKI infrastructure, there should be a period of at least 24 hours between the revocation of the ROA or ROAs and the notification to the LIR that a given prefix has been allocated to them. This might delay allocations considerably, unless a different procedure can be created.
Source facts ↗
Source facts +
The authors note that it is possible to circumvent the protection of the AS0 ROA through the announcement of a less specific covering prefix. However, it is thought that hijackers of unallocated resources are likely to try staying under the radar and by announcing a supernet which by definition also spans an allocated resource, will trigger alarms through the various DFZ monitoring services available (for example as available in the RIPE RPKI Dashboard)
Source facts ↗

Registry and validator processing costs · Version 2 adds the possible registry cost and validator processing burden of a large AS0 ROA set. It distinguishes the limited IPv4 pools described in the proposal from the potentially much larger IPv6 set associated with sparse allocation. These are the draft's operational concerns, not measured costs or a forecast that every validator will be overloaded.

Source facts −
This might delay allocations considerably, unless a different procedure can be created.
Source facts ↗
Source facts +Validated evidence is unavailable.
3.0
Withdrawn · Withdrawn
Apr 24, 2020
Source facts ↗

Distribution through SLURM assertions · Version 3 replaces the proposed registry-created AS0 ROAs with a downloadable SLURM file containing AS0 assertions for unallocated and unassigned IPv4 and IPv6 space under RIPE NCC administration. It specifies a well-known URL and automated use by relying parties under RFC 8416. Version 2 instead separated the registry's ROAs under a dedicated trust anchor and TAL. This is a proposed distribution change, not evidence that either design was deployed.

Source facts −
RIPE NCC creates all its AS0 ROAs under a specific Trust Anchor, and provides a specific Trust Anchor Locator (TAL) file. This way, tools and researchers could benefit from a distinction between operational ROAs created by holders of the address space, and ROAs created by RIPE NCC for unallocated/unassigned address space.
Source facts ↗
Source facts +
The RIPE NCC will create a SLURM file containing assertions with origin AS0 for all the unallocated and unassigned address space (IPv4 and IPv6) for which it is the current administrator. The file will be available for download from a well-known URL published by the RIPE NCC, so that Relying Parties (the so-called Validators) will be able to, in an automated way, fetch them and make use of them as described in RFC 8416.
Source facts ↗

Relying-party choice and configuration · Version 3 explicitly makes use of the file a relying-party choice: a configuration directive can enable or disable processing, and users can incorporate the assertions or leave them out. The rationale also suggests CDN distribution and frequent updates. Version 2 described a separate TAL for distinguishing registry ROAs; it did not include this SLURM-specific configuration and distribution explanation. The proposal's claim of equivalent information does not mean all networks would choose identical validation policy.

Source facts −
This way, tools and researchers could benefit from a distinction between operational ROAs created by holders of the address space, and ROAs created by RIPE NCC for unallocated/unassigned address space.
Source facts ↗
Source facts +
Creating and publishing a SLURM file gives users the chance to decide if they want to use the information or not for their networks. Relying Parties can decide to incorporate all the assertions from this file, or they can be left out. The SLURM file could be distributed using a CDN, and it should be frequently updated to reflect the status of the unallocated and unassigned address space held by RIPE NCC.
Source facts ↗

Updating protection when resources are allocated · Version 3 requires the relevant AS0 entry in the SLURM file to be updated at the time space is allocated to a member. This replaces Version 2's requirement to revoke the relevant AS0 ROAs. The earlier opposing-arguments discussion of waiting at least 24 hours between revocation and notification is absent from Version 3; the new text does not establish how quickly every relying party will retrieve an update.

Source facts −
If the RIPE NCC wants to allocate address space to one of its members, the RPKI ROA or ROAs with origin AS0 will have to be revoked.
Source facts ↗
Source facts +
The RIPE NCC will update the relevant entry in the SLURM file with origin AS0 at the time of allocating address space to one of its members.
Source facts ↗

Cost concern shifts to relying-party memory · Version 2 discusses RIPE NCC's operational cost and validator processing time for many ROAs. Version 3 reframes this concern around relying-party software needing more memory to process many assertions. The IPv4-versus-IPv6 distinction remains: the draft expects a relatively limited IPv4 set and a considerable IPv6 set because of sparse allocation. Neither version supplies a measured capacity benchmark.

Source facts −
The addition of potentially a large number of ROAs covering all the unassigned and unallocated space might increase the operational costs for the RIPE NCC. It might also have an impact on the time needed by validators to process the data.
Source facts ↗
Source facts +
The addition of potentially a large number of assertions covering all the unassigned and unallocated space might increase the operational costs for the Relying Party software by requiring them to run using more memory needed to process all the data.
Source facts ↗

Debate timeline

  1. Introduced

    Introduced

    Source facts ↗

  2. Official version

    1.0

    Withdrawn · Withdrawn

    Source facts ↗

  3. Official version

    2.0

    Withdrawn · Withdrawn

    Source facts ↗

  4. Official version

    3.0

    Withdrawn · Withdrawn

    Source facts ↗

  5. Official decision

    withdrawn

    withdrawn

    Source facts ↗

Entities

Freshness: Stale
  1. Martijn Schmidt [i3D.net · Identity unresolved
    Discussion messages0
    First activityUnknown
    Last activityUnknown
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies0
  2. Martijn Schmidt · Identity unresolved
    Discussion messages0
    First activityUnknown
    Last activityUnknown
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies0
  3. Melchior Aelmans · Identity unresolved
    Discussion messages0
    First activityUnknown
    Last activityUnknown
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies0
  4. a Ubisoft company · Identity unresolved
    Discussion messages0
    First activityUnknown
    Last activityUnknown
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies0
  5. Massimiliano Stucchi · 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 6, 2026
    Last refresh
    Aug 13, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    20,345
    Known gaps
    83
  • www.ripe.net
  • ripencc-accountability-tf-ripe.net
    Earliest captured
    Nov 24, 2016
    Latest captured
    May 9, 2019
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,878
    Known gaps
    0
  • ripencc-agm-nominations-ripe.net
    Earliest captured
    Mar 26, 2008
    Latest captured
    Apr 28, 2026
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,642
    Known gaps
    0
  • ripencc-all-anchors-ripe.net
    Earliest captured
    Oct 31, 2014
    Latest captured
    Oct 31, 2014
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    525
    Known gaps
    0
  • ripencc-anti-abuse-wg-ripe.net
    Earliest captured
    Sep 16, 2008
    Latest captured
    Nov 4, 2025
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,571
    Known gaps
    0
  • ripencc-atlas-sponsors-ripe.net
    Earliest captured
    Dec 7, 2012
    Latest captured
    Mar 31, 2014
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    1,604
    Known gaps
    0
  • ripencc-atlas-sw-probes-ripe.net
    Earliest captured
    Oct 21, 2019
    Latest captured
    Jul 24, 2024
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,317
    Known gaps
    0
  • ripencc-bcop-ripe.net
    Earliest captured
    Jun 16, 2013
    Latest captured
    Oct 29, 2024
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    4,423
    Known gaps
    0
  • ripencc-coc-tf-ripe.net
    Earliest captured
    Sep 18, 2020
    Latest captured
    Apr 20, 2023
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,563
    Known gaps
    0
  • ripencc-connect-bof-ripe.net
    Earliest captured
    Oct 18, 2013
    Latest captured
    Jul 14, 2014
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    2,663
    Known gaps
    1
  • ripencc-connect-wg-ripe.net
    Earliest captured
    Oct 20, 2014
    Latest captured
    Sep 28, 2026
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    4,543
    Known gaps
    0
  • ripencc-cooperation-wg-ripe.net
    Earliest captured
    Aug 26, 2008
    Latest captured
    Oct 6, 2026
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    4,622
    Known gaps
    0
  • ripencc-db-help-ripe.net
    Earliest captured
    Aug 20, 2003
    Latest captured
    Jan 13, 2016
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    4,341
    Known gaps
    0
  • ripencc-db-wg-ripe.net
    Earliest captured
    Oct 21, 1992
    Latest captured
    Oct 9, 2026
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,457
    Known gaps
    0
  • ripencc-diversity-ripe.net
    Earliest captured
    May 18, 2017
    Latest captured
    Feb 9, 2026
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,944
    Known gaps
    0
  • ripencc-dns-resolver-tf-ripe.net
    Earliest captured
    Jan 23, 2023
    Latest captured
    Feb 16, 2025
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    2,933
    Known gaps
    0
  • ripencc-dns-wg-ripe.net
    Earliest captured
    Jun 30, 1992
    Latest captured
    Oct 9, 2026
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,262
    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,822
    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,179
    Known gaps
    58
  • ripencc-eix-wg-ripe.net
    Earliest captured
    Jan 1, 1999
    Latest captured
    Oct 21, 2013
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,851
    Known gaps
    0
  • ripencc-election-cc-team-ripe.net
    Earliest captured
    Aug 18, 2026
    Latest captured
    Aug 18, 2026
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    469
    Known gaps
    0
  • ripencc-enum-announce-ripe.net
    Earliest captured
    Aug 15, 2003
    Latest captured
    Sep 15, 2026
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,304
    Known gaps
    0
  • ripencc-enum-wg-ripe.net
    Earliest captured
    Jun 16, 2004
    Latest captured
    Nov 20, 2013
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,595
    Known gaps
    0
  • ripencc-green-tech-hackathon-orga-ripe.net
    Earliest captured
    Unknown
    Latest captured
    Unknown
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    21
    Known gaps
    0
  • ripencc-hackathon-list-ripe.net
    Earliest captured
    Feb 26, 2015
    Latest captured
    Jan 9, 2025
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,081
    Known gaps
    0
  • ripencc-icann-plan-ripe.net
    Earliest captured
    Dec 8, 2004
    Latest captured
    Jan 31, 2005
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    807
    Known gaps
    0
  • ripencc-iot-wg-ripe.net
    Earliest captured
    Nov 3, 2016
    Latest captured
    Aug 19, 2026
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,200
    Known gaps
    0
  • ripencc-ipmap-ripe.net
    Earliest captured
    Nov 25, 2021
    Latest captured
    May 17, 2022
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    604
    Known gaps
    0
  • ripencc-ipmt-dev-ripe.net
    Earliest captured
    May 3, 2001
    Latest captured
    Jul 2, 2003
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    2,745
    Known gaps
    0
  • ripencc-ipv6-wg-ripe.net
    Earliest captured
    Mar 31, 1995
    Latest captured
    Oct 5, 2026
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,270
    Known gaps
    0
  • ripencc-irrtoolset-ripe.net
    Earliest captured
    Aug 12, 2003
    Latest captured
    Dec 15, 2004
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,434
    Known gaps
    0
  • ripencc-lir-wg-ripe.net
    Earliest captured
    Oct 8, 1992
    Latest captured
    Jun 30, 2003
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,086
    Known gaps
    0
  • ripencc-mat-wg-ripe.net
    Earliest captured
    May 18, 2010
    Latest captured
    Sep 23, 2026
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    2,732
    Known gaps
    0
  • ripencc-measure-voip-ripe.net
    Earliest captured
    May 25, 2004
    Latest captured
    Jul 9, 2004
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    1,088
    Known gaps
    0
  • ripencc-members-discuss-unmoderated-ripe.net
    Earliest captured
    Jun 1, 2026
    Latest captured
    Oct 11, 2026
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    7,220
    Known gaps
    11
  • ripencc-members-discuss-ripe.net
    Earliest captured
    Mar 8, 2007
    Latest captured
    Oct 6, 2026
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,478
    Known gaps
    0
  • ripencc-myasntesting-ripe.net
    Earliest captured
    Aug 14, 2003
    Latest captured
    Jun 29, 2009
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,566
    Known gaps
    0
  • ripencc-ncc-announce-ripe.net
    Earliest captured
    Jun 27, 2006
    Latest captured
    Oct 6, 2026
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,103
    Known gaps
    0
  • ripencc-ncc-services-wg-ripe.net
    Earliest captured
    Aug 6, 2003
    Latest captured
    Oct 2, 2026
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,414
    Known gaps
    0
  • ripencc-nccdays-pc-ripe.net
    Earliest captured
    Unknown
    Latest captured
    Unknown
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    20
    Known gaps
    0
  • ripencc-opensource-wg-ripe.net
    Earliest captured
    Mar 14, 2013
    Latest captured
    Oct 2, 2026
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,765
    Known gaps
    0
  • ripencc-persian-lir-ripe.net
    Earliest captured
    Jul 9, 2015
    Latest captured
    Jul 8, 2023
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    5,455
    Known gaps
    0
  • ripencc-policy-announce-ripe.net
    Earliest captured
    Aug 30, 2005
    Latest captured
    Sep 28, 2026
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,840
    Known gaps
    0
  • ripencc-raci-list-ripe.net
    Earliest captured
    Jul 24, 2014
    Latest captured
    Sep 22, 2026
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,199
    Known gaps
    0
  • ripencc-regional-russia-ripe.net
    Earliest captured
    Sep 27, 2005
    Latest captured
    Jul 4, 2011
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    4,785
    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,888
    Known gaps
    1
  • ripencc-ripe-atlas-ambassadors-ripe.net
    Earliest captured
    Dec 20, 2013
    Latest captured
    Sep 23, 2026
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    4,980
    Known gaps
    0
  • ripencc-ripe-atlas-tools-maintainers-ripe.net
    Earliest captured
    Jan 12, 2016
    Latest captured
    Mar 25, 2016
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    1,463
    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,291
    Known gaps
    1
  • ripencc-ripe-chair-discuss-ripe.net
    Earliest captured
    Oct 7, 2016
    Latest captured
    Oct 17, 2022
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,556
    Known gaps
    0
  • ripencc-ripe-db-requirements-tf-ripe.net
    Earliest captured
    Oct 15, 2019
    Latest captured
    Nov 16, 2021
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    4,339
    Known gaps
    0
  • ripencc-ripe-forum-test-ripe.net
    Earliest captured
    Apr 11, 2016
    Latest captured
    Jun 20, 2019
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    2,380
    Known gaps
    0
  • ripencc-ripe-list-unmoderated-ripe.net
    Earliest captured
    Jun 1, 2026
    Latest captured
    Oct 9, 2026
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    7,049
    Known gaps
    0
  • ripencc-ripe-list-ripe.net
    Earliest captured
    Jul 2, 1992
    Latest captured
    Oct 5, 2026
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,721
    Known gaps
    0
  • ripencc-ripe-parents-ripe.net
    Earliest captured
    Oct 19, 2011
    Latest captured
    May 5, 2016
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    1,893
    Known gaps
    0
  • ripencc-ripecast-ripe.net
    Earliest captured
    Aug 29, 2003
    Latest captured
    Sep 28, 2009
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    4,340
    Known gaps
    0
  • ripencc-rirs-lea-ripe.net
    Earliest captured
    Jul 2, 2016
    Latest captured
    Apr 9, 2019
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    2,995
    Known gaps
    1
  • ripencc-ris-int-ripe.net
    Earliest captured
    Dec 31, 1997
    Latest captured
    Nov 26, 2016
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    4,306
    Known gaps
    0
  • ripencc-ris-users-ripe.net
    Earliest captured
    Aug 8, 2003
    Latest captured
    Aug 24, 2026
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,901
    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,420
    Known gaps
    1
  • ripencc-rpslng-ripe.net
    Earliest captured
    Aug 26, 2003
    Latest captured
    Nov 8, 2007
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,349
    Known gaps
    0
  • ripencc-security-wg-ripe.net
    Earliest captured
    Nov 18, 2024
    Latest captured
    Oct 5, 2026
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    13,930
    Known gaps
    1
  • ripencc-see-regional-ripe.net
    Earliest captured
    Aug 24, 2011
    Latest captured
    Sep 28, 2026
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,621
    Known gaps
    0
  • ripencc-techsec-wg-ripe.net
    Earliest captured
    May 15, 2001
    Latest captured
    Feb 29, 2016
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,912
    Known gaps
    0
  • ripencc-tld-wg-ripe.net
    Earliest captured
    Jul 9, 1997
    Latest captured
    Apr 22, 2015
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    4,512
    Known gaps
    0
  • ripencc-tt-tf-ripe.net
    Earliest captured
    May 30, 2006
    Latest captured
    Dec 7, 2007
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    2,112
    Known gaps
    0

Coverage

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