BTW.Media
Daily editionStrategic Internet Intelligence
Sign InRegister

RIPE NCC · RIR Watchdog

Initial Certification Policy in the RIPE NCC Service Region

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

Who actually shaped the debate?

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

Policy evolution

2.0
Withdrawn · Withdrawn
Unknown
Source facts ↗

Certificate maintenance and revocation basis · Version 2.0 ties certificates to the resource's registration status and says removing the holding record from the RIPE Database automatically revokes the certificate. It removes version 1.0's explicit maintenance/renewal conditions based on membership or another contract, its express non-payment/contract-closure revocation wording, and its notification and grace-period provision. The revised text does not itself define the separate process for deregistering a holding.

Source facts −
Maintenance and renewal of certificates will be tied to contractual relationship status of the LIR with the RIPE NCC. In cases of continuing non-payment, cessation of contract and/or closing of the LIR, existing certificates may be revoked by the RIPE NCC. Notification and a grace period will be provided before the RIPE NCC revokes or ceases renewal of any certificates.
Source facts ↗
Source facts +
Certificates will at all times reflect the registration status of the resource in the Registry, as also reflected in the RIPE database. In practice this means a certificate may be issued to the registered holder of the PA resource at any time that a record of that holding exists in the RIPE database. Withdrawal of the record of that holding from the RIPE database will automatically result in the certificate being revoked.
Source facts ↗

Issuance and holder verification · Version 2.0 expressly limits issuance to RIPE NCC supplied PA space and its registered LIR holder. It omits the separate statement allowing additional details to verify legitimacy and the example of delivery through the members' LIR Portal, while retaining a secure delivery channel and a maximum 18-month validity. Omission of that verification detail is not evidence that identity checks are prohibited.

Source facts −
The RIPE NCC issues certificates upon request for Provider Aggregatable (PA) address space allocations. The requester must be a RIPE NCC member LIR holding Provider Aggregatable (PA) address space allocations. When the RIPE NCC receives a certification request, they may ask for further details to ensure that the requester is the legitimate holder of the resource.
Source facts ↗
Source facts +
The RIPE NCC will issue certificates upon request for RIPE NCC supplied Provider Aggregatable (PA) address space allocations to the LIR that is the registered holder of that space. The certificate will be issued via a secure channel. Certificates will be issued with a validity period of up to 18 months.
Source facts ↗
3.0
Withdrawn · Withdrawn
Unknown
Source facts ↗

Membership and registration conditions · Version 3.0 expressly restricts the guidelines to RIPE NCC members in good standing. It retains the rule that certificates reflect resource registration status, but drops version 2.0's equation of that status with the existence of a RIPE Database holding record and its explicit automatic-revocation-on-record-removal statement. The rationale instead points to draft closure and deregistration procedures.

Source facts −
Certificates will at all times reflect the registration status of the resource in the Registry, as also reflected in the RIPE database. In practice this means a certificate may be issued to the registered holder of the PA resource at any time that a record of that holding exists in the RIPE database. Withdrawal of the record of that holding from the RIPE database will automatically result in the certificate being revoked.
Source facts ↗
Source facts +
Following guidelines are to apply only for certification of Provider Aggregatable (PA) address space allocations that are held by the RIPE NCC members in good standing.
Source facts ↗

Certificate validity · Version 3.0 qualifies the previous maximum validity of 18 months by allowing another period stated in the RIPE NCC Certificate Practice Statement. The rule that a replacement following a security-related revocation carries the revoked certificate's remaining validity is retained.

Source facts −
Certificates will be issued with a validity period of up to 18 months.
Source facts ↗
Source facts +
Certificates will be issued with a validity period of up to 18 months or as otherwise stated in the RIPE NCC Certificate Practice Statement.
Source facts ↗
4.0
Withdrawn · Withdrawn
Mar 21, 2011
Source facts ↗

Initial resource scope · Version 4.0 replaces the PA-only framing with Internet number resources and explicitly lists the initial eligible RIPE NCC distributed resources: IPv4 ALLOCATED PA and ALLOCATED UNSPECIFIED, and IPv6 ALLOCATED-BY-RIR. It keeps the member-in-good-standing and registered-holder conditions. The wider terminology does not make every resource eligible; the initial status list and the rationale's later treatment of more complicated cases still constrain scope.

Source facts −
Following guidelines are to apply only for certification of Provider Aggregatable (PA) address space allocations that are held by the RIPE NCC members in good standing. The RIPE NCC will issue certificates upon request for RIPE NCC supplied Provider Aggregatable (PA) address space allocations to the LIR that is the registered holder of that space.
Source facts ↗
Source facts +
Initially, the following Internet number resources distributed by the RIPE NCC will be eligible for certification: IPv4 resources with the status "ALLOCATED PA" and "ALLOCATED UNSPECIFIED" IPv6 resources with the status "ALLOCATED-BY-RIR"
Source facts ↗

Deregistration reference · Version 4.0 updates the rationale's closure and deregistration reference from a draft document to RIPE-517. The rationale still ties certificate validity to the resource's registration status; the reference update does not itself add a new revocation condition to the policy text.

Source facts −
It is proposed that the validity of certificates is tied to the registration status of the resource. Rules and processes for deregistration of resources by the RIPE NCC are being clarified by a new draft document from RIPE NCC “Draft: Closure of LIR and Deregistration of Internet number resource” presented at RIPE 61 Services WG: http://www.ripe.net/lir-services/ncc/legal/ClosureofLIRandderegistrationofINRs_finaldraft.pdf
Source facts ↗
Source facts +
It is proposed that the validity of certificates is tied to the registration status of the resource. Rules and processes for deregistration of resources by the RIPE NCC are being clarified by a new document from RIPE NCC “Closure of LIR and Deregistration of Internet number resource” presented at RIPE 61 Services WG: https://www.ripe.net/ripe/docs/ripe-517
Source facts ↗

Debate timeline

  1. Official version

    1.0

    Withdrawn · Withdrawn

    Source facts ↗

  2. Official version

    2.0

    Withdrawn · Withdrawn

    Source facts ↗

  3. Official version

    3.0

    Withdrawn · Withdrawn

    Source facts ↗

  4. Official version

    4.0

    Withdrawn · Withdrawn

    Source facts ↗

  5. Official decision

    withdrawn

    withdrawn

    Source facts ↗

Entities

Freshness: Stale
  1. Malcolm Hutty
    Discussion messages2
    First activityMay 31, 2011
    Last activityMay 31, 2011
    First explicit stanceOppose
    Latest explicit stanceOppose
    Stance changes0
    Viewpoint consistencyConsistent
    Other policies0
    Freshness: Stale

    Last research attempt: Oct 7, 2026

    Identity verified: Oct 7, 2026

    London Internet Exchange · Historical
    LINX Public Affairs Update, ‘Online Harms Bill’ – Malcolm Hutty, Head of Public Affairs
    www.linx.net
    RIPE Accountability Task Force · Historical
    Task Force Members Corinne Cath Hans Petter Holen Malcolm Hutty
    www.ripe.net

    Verified public profiles

    Discussion messages
    2
    First activity
    May 31, 2011
    Last activity
    May 31, 2011
    First explicit stance
    Oppose
    Latest explicit stance
    Oppose
    Stance changes
    0
    Viewpoint consistency
    Consistent
    Other policies
    0

    First explicit stance: Oppose → Latest explicit stance: Oppose · Stance changes: 0

    Viewpoint consistency: Consistent

    The two messages on 31 May 2011 express a consistent objection to the political use of the certification mechanisms proposed in 2008-08. The first warns that governments could use the tools once built; the second rejects the suggestion that the critics are trying to solve political problems through RIPE policy. This is a comparison of those two statements, not a conclusion about every message or the person's views across years and policies.

    Initial Certification Policy in the RIPE NCC Service Region

    Assessment: Consistent · The warning that political leaders could use the proposed certification tools and the subsequent defense of the critics make compatible claims: the author is challenging the consequences of creating the mechanism, rather than proposing that RIPE fix politics. The second message does not withdraw the first objection or introduce a contrary position.

    Conditions: The political consequences are the author's warning, not evidence that the policy was adopted or used in that way. · Randy Bush's and Gert Doering's quoted messages are context, not statements attributed to Malcolm Hutty. · Only these two same-day messages establish this comparison; other identified mail, long-term consistency, and other policies remain outside its evidence.

    2008-08 provides (some of) the tools to carry it out.

    If you build the tools, political leaders like Sarkozy will ensure they get used.

    If after all this discussion you still think those criticising 2008-08 are the ones trying to "fix broken political approaches" through RIPE policy I don't see how we're ever going to agree.

    1. May 31, 2011 · Oppose

      Re: [address-policy-wg] Legal counsel on 2008-08 (Initial Certification Policy in the RIPE NCC Service Region)

      Sarkozy has clearly described the political imperative. 2008-08 provides (some of) the tools to carry it out. … If you build the tools, political leaders like Sarkozy will ensure they get used. … Do you really think you can hold off this outcome by calling politicians rude names?

      Source facts ↗
    2. May 31, 2011 · Oppose

      Re: [address-policy-wg] Legal counsel on 2008-08 (Initial Certification Policy in the RIPE NCC Service Region)

      If after all this discussion you still think those criticising 2008-08 are the ones trying to "fix broken political approaches" through RIPE policy I don't see how we're ever going to agree.

      Source facts ↗
    Per-policy stance timelines:2008-08 · Oppose · Consistent

    Total policy messages: 2

  2. 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
  3. Nigel Titley · 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,638
    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,300
    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,057
    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
    547
    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,006
    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,778
    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,682
    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,029
    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,960
    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,928
    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
    4,975
    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,944
    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,792
    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,696
    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,349
    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,208
    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,514
    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,093
    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,291
    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,332
    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
    488
    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,739
    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,008
    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
    27
    Known gaps
    0
  • 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,439
    Known gaps
    0
  • 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
    856
    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,663
    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
    653
    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,010
    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,596
    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,823
    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,452
    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,111
    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,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,825
    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,730
    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,888
    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,353
    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,708
    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
    23
    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,168
    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,012
    Known gaps
    0
  • ripencc-policy-announce-ripe.net
    Earliest captured
    Aug 30, 2005
    Latest captured
    Oct 12, 2026
    Last refresh
    Oct 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    4,177
    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,616
    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,197
    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,006
    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,525
    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,584
    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,604
    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,837
    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,791
    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,602
    Known gaps
    0
  • ripencc-ripe-list-unmoderated-ripe.net
    Earliest captured
    Jun 1, 2026
    Latest captured
    Oct 12, 2026
    Last refresh
    Oct 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    7,545
    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,018
    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,065
    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,715
    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,308
    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,674
    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,241
    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,677
    Known gaps
    1
  • 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,630
    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,226
    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,009
    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,255
    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,881
    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,322
    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.