BTW.Media
Daily editionStrategic Internet Intelligence
Sign InRegister

RIPE NCC · RIR Watchdog

Openness about Policy Violations

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
2013-01
RIR
RIPE NCC
Official status
Withdrawn
Normalized status
Withdrawn
Introduced
Feb 1, 2013
Last source update
Oct 13, 2026
Coverage
Partial

Who actually shaped the debate?

2Total participants
UnknownDiscussion contributors
2Formal 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 chronology contains no stages, revisions, rationales, milestones, implementation events, or final disposition.

What the debate was really about

The subject of the debate cannot be determined from the supplied record. There are no discussion messages, substantive summaries, participant stance timelines, or unresolved or minority arguments from which to identify the underlying policy disagreement.

Decision vs debate

No relationship between discussion and decision can be established. The verified record contains neither observable discussion activity nor a formal assessment, consensus determination, final decision, decision rationale, withdrawal, rejection, adoption, or implementation event.

Participation concentration

The participation snapshot is empty: zero messages, zero discussion participants, zero formal actors, zero total participants, zero active days, zero stance participants, and zero stance transitions. Accordingly, the zero message shares, zero HHI, zero effective-participant count, and zero core-contributor counts are degenerate values; they do not demonstrate broad, equal, or concentrated participation among actual contributors.

Chokepoint analysis

The decisive chokepoint is evidentiary absence rather than an identified procedural or institutional actor: without a dated chronology, discussion records, stance timelines, formal-authority records, and a documented disposition, the policy's evolution, influence structure, and outcome cannot be reconstructed. The supplied facts also do not identify who held authority or whether the empty extract is complete.

Uncertainties

  • It is uncertain whether no debate occurred, whether relevant activity fell outside the measured corpus, or whether extraction produced no qualifying records.
  • The source revision and computation timestamp identify the measured snapshot but do not establish substantive completeness.
  • The Doctrine package's official position is partial and does not supply a policy outcome or fill the missing factual record.
  • No conclusion can be drawn about support, opposition, consensus, minority positions, adoption, rejection, withdrawal, or implementation.

Policy evolution

2.0
Withdrawn · Withdrawn
May 23, 2013
Source facts ↗

Public complaint transparency · Version 2.0 replaces the public list of individual reports with aggregate statistics: running totals for new and under-investigation reports and counts of closed reports by outcome. The earlier list would have exposed submission dates, resources and current state, plus content and reporter identity if the reporter consented. The revised section does not carry forward the individual website/FTP report-list requirement.

Source facts −
The existence of all such reports shall be made public. The submitter of the report will choose whether or not the contents of the report and the submitter's own identity is to bemade public. The published list of reports shall at least include: Date submitted; The resources the report is about; A reference to the report content, if the submitter indicated that it can be made public; The identity of the submitter, if the submitter indicated that it can be made public; The current state.
Source facts ↗
Source facts +
The RIPE NCC will handle all such reports and publish statistics about such reports publicly. The RIPE NCC will publish regularly statistics of the reports that have been received but not yet closed. These statistics will show the number of reports in each of the following categories: 'new': Submitted but not being investigated yet 'under-investigation': The RIPE NCC is investigating the report
Source facts ↗

Private investigation progress · A new section gives both the reporter and the organisations mentioned in a report a way to follow the investigation, explicitly keeping this information non-public. This accompanies removal of the earlier public per-report state list.

Source facts −
The published list of reports shall at least include: Date submitted; The resources the report is about; A reference to the report content, if the submitter indicated that it can be made public; The identity of the submitter, if the submitter indicated that it can be made public; The current state.
Source facts ↗
Source facts +
2. Progress The RIPE NCC will provide a way to follow the progress of the investigation for both the person submitting a report and the organization(s) mentioned in the report. This information will not be published publicly.
Source facts ↗

Historical reports · Version 1.0 expressly excluded reports made before policy adoption from publication. The aggregate-statistics replacement omits that sentence. The revised text does not itself establish a historical reporting start date or expressly require retrospective publication, so neither is inferred from the omission.

Source facts −
Reports made prior to the adoption of this policy are not to be published.
Source facts ↗
Source facts +
The RIPE NCC will publish regularly statistics of the reports that have been received but not yet closed. These statistics will show the number of reports in each of the following categories: 'new': Submitted but not being investigated yet 'under-investigation': The RIPE NCC is investigating the report
Source facts ↗

Stated tradeoff and attribution · The opposing rationale changes from the risk of false complaints damaging organisations' reputations to the concern that the proposal imposes procedures better decided by the RIPE NCC. The revised document also adds an attribution section naming Sander Steffann and Shane Kerr as active contributors. The returned-resource ledger remains in the proposal.

Source facts −
It is possible that someone maysubmit false complaints in order to damage the good name of other organisations. The proposers think that providing transparency will make such abuse of the reporting system less likely and if it should occur easier to identify.
Source facts ↗
Source facts +
b. Arguments opposing the proposal Such a policy as this forces a procedure on the RIPE NCC which is better left decided by the RIPE NCC. The proposers have tried to keep the policy as flexible as possible, while still providing transparency.
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 decision

    withdrawn

    withdrawn

    Source facts ↗

Entities

Freshness: Stale
  1. Shane Kerr · Identity unresolved
    Discussion messages0
    First activityUnknown
    Last activityUnknown
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies0
  2. Sander Steffann · 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,672
    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,799
    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,714
    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,069
    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,979
    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,956
    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,007
    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,976
    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,814
    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,723
    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,381
    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,236
    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,542
    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,121
    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,300
    Known gaps
    70
  • 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,364
    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
    494
    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,771
    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,041
    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
    29
    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,460
    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
    865
    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,695
    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
    661
    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,038
    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,628
    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,843
    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,479
    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,144
    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,186
    Known gaps
    0
  • ripencc-members-discuss-unmoderated-ripe.net
    Earliest captured
    Jun 1, 2026
    Latest captured
    Oct 14, 2026
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    7,905
    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,756
    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,393
    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,735
    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
    26
    Known gaps
    0
  • ripencc-opensource-wg-ripe.net
    Earliest captured
    Mar 14, 2013
    Latest captured
    Oct 2, 2026
    Last refresh
    Oct 13, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    4,207
    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,214
    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,638
    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,228
    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,017
    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,559
    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,598
    Known gaps
    0
  • ripencc-ripe-atlas-ripe.net
    Earliest captured
    Oct 14, 2010
    Latest captured
    Oct 14, 2026
    Last refresh
    Oct 8, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    4,640
    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,858
    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,824
    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,626
    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,602
    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,052
    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,075
    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,753
    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,340
    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,687
    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,267
    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,711
    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,651
    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,256
    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,028
    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,277
    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,914
    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,343
    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.