BTW.Media
Daily editionStrategic Internet Intelligence
Sign InRegister

RIPE NCC · RIR Watchdog

Personal Data in the RIPE Database

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
2022-01
RIR
RIPE NCC
Official status
Withdrawn
Normalized status
Withdrawn
Introduced
May 10, 2022
Last source update
Oct 10, 2026
Coverage
Partial

Who actually shaped the debate?

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

Policy evolution

2.0
Withdrawn · Withdrawn
Oct 6, 2022
Source facts ↗

Purposes justifying personal-data use · The proposal expands the acknowledged purposes that may justify personal data from two to three by adding disclosure of registrant and maintainer information to legally authorised parties investigating suspected unlawful activity.

Source facts −
The two most significant purposes that could be considered as requiring personal data are: Ensuring the uniqueness of Internet number resource usage through registration of information related to the resources and Registrants. Facilitating coordination between network operators (network problem resolution, outage notification etc.).
Source facts ↗
Source facts +Validated evidence is unavailable.

Natural-person identification and address publication · The organisation rules are rewritten from allowing a natural person's name while restricting non-public personal addresses to a consent-based rule covering the name and address of a natural person who holds or uses resources, while expressly barring address detail more specific than country and region from object attributes.

Source facts −Validated evidence is unavailable.
Source facts +Validated evidence is unavailable.

Contact reachability · The proposal adds an explicit requirement that contacts be contactable and that every role contain at least one verified contact method.

Source facts −
Contacts must only be entered into the database if they can fulfil a role for one of the acknowledged types of contacts according to the purposes of the RIPE Database.
Source facts ↗
Source facts +
Contacts must only be entered into the database if they can fulfil a role for one of the acknowledged types of contacts according to the purposes of the RIPE Database. Contacts must be contactable. There must be at least one verified method of contact included for each role.
Source facts ↗

Implementation scope · The revised rationale explicitly limits the proposal to principles for processing personal data and leaves implementation objectives, migration planning and detailed technical changes to follow-up work if the proposal is approved.

Source facts −
When you also factor in that publishing personal data in a PUBLIC database is an irreversible step, maintainers of this data should seriously avoid entering it unless it is necessary. a. Arguments Supporting the Proposal
Source facts ↗
Source facts +Validated evidence is unavailable.
3.0
Withdrawn · Withdrawn
Oct 6, 2022
Source facts ↗

Organisation contact-detail verification · Verification changes from confirming that email and phone details are held by the referencing organisation to requiring the holder of each contact email address or phone number to know of its publication and verify that they hold it.

Source facts −
Any email and phone details entered into the database must be verified as held by the referencing organisation.
Source facts ↗
Source facts +
The holder of any contact email address and phone number must be aware of the registration and publication of these contact details in the RIPE Database and will be required to verify that they are the holder of these contact details.
Source facts ↗

Fax-number verification · Fax numbers are removed from the mandatory verification requirement and are expressly stated not to be verified; email addresses and phone numbers remain subject to verification.

Source facts −
Email addresses added as contact details and all phone and fax numbers entered into the RIPE Database must be verified. Updates to database objects will fail if the verification fails.
Source facts ↗
Source facts +
Email addresses added as contact details and all phone numbers entered into the RIPE Database must be verified. Updates to database objects will fail if the verification fails. If existing contact emails and phone numbers fail to be verified, the RIPE NCC will follow up in compliance with relevant RIPE Policies and RIPE NCC procedures. No one should be able to enter the email address or phone number of another organisation without its permission. Fax numbers will not be verified.
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. Denis Walker
    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,305
    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,787
    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,527
    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,459
    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,570
    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,223
    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,294
    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,458
    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,603
    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,419
    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,575
    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,244
    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,415
    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,842
    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,875
    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,215
    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,765
    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,161
    Known gaps
    56
  • 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,757
    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
    468
    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,228
    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,522
    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
    25
    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,007
    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
    802
    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,113
    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
    599
    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,690
    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,206
    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,354
    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,021
    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,670
    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,072
    Known gaps
    0
  • ripencc-members-discuss-unmoderated-ripe.net
    Earliest captured
    Jun 1, 2026
    Latest captured
    Oct 10, 2026
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    7,094
    Known gaps
    9
  • 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,429
    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,472
    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,053
    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,363
    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
    24
    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,689
    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,342
    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,771
    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,110
    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,655
    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,866
    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,872
    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,440
    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,219
    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,477
    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,214
    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,324
    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
    6,937
    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,648
    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,849
    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,224
    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,909
    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,184
    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,787
    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,370
    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,270
    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,873
    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,517
    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,812
    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,381
    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,067
    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.