BTW.Media
Daily editionStrategic Internet Intelligence
Sign InRegister

RIPE NCC · RIR Watchdog

Revised IPv6 PI Assignment Policy

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
2024-01
RIR
RIPE NCC
Official status
Withdrawn
Normalized status
Withdrawn
Introduced
Aug 13, 2024
Last source update
Oct 12, 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%

Policy evolution

2.0
Aug 13, 2024
Source facts ↗

Policy text · Astra identified a substantive wording change in this retained policy section.

Source facts −
ummary of the Proposal This proposal aims to reduce operational burden operators working with PI experience, while clarifying long-standing issues in the IPv6 addressing policy.
Source facts ↗
Source facts +
ummary of the Proposal This proposal aims to reduce the operational burden that operators experience when working with PI.
Source facts ↗

Policy text · Astra identified a substantive wording change in this retained policy section.

Source facts −
ummary of the Proposal This proposal aims to reduce operational burden operators working with PI experience, while clarifying long-standing issues in the IPv6 addressing policy.
Source facts ↗
Source facts +
It also clarifies some long-standing issues in the IPv6 addressing policy.
Source facts ↗

Policy text · Astra identified a substantive wording change in this retained policy section.

Source facts −
Specifically, it makes the following changes: Separate notions of assignment requirements and End Sites for ‘PI Assignments’ and ‘Assignments from IPv6 Allocations to End Users’.
Source facts ↗
Source facts +
Specifically, it makes the following changes: Separates assignment requirements for ‘PI assignments’ from ‘assignments from IPv6 allocations to End Users’.
Source facts ↗

Policy text · Astra identified a substantive wording change in this retained policy section.

Source facts −
Clarify permitted and non-permitted use cases of PI Assignments.
Source facts ↗
Source facts +
Clarifies permitted and non-permitted use cases of PI assignments.
Source facts ↗

Policy text · Astra identified a substantive wording change in this retained policy section.

Source facts −
Clarify wording, definitions, and requirements in the text.
Source facts ↗
Source facts +
Clarifies wording, definitions, and requirements in the text.
Source facts ↗

Policy text · Astra identified a substantive wording change in this retained policy section.

Source facts −
Introduce PI Assignments at the Nibble boundary, an aggregation principle for PI, and registration in a single object for assignments.
Source facts ↗
Source facts +
Introduces PI assignments at the nibble boundary, an aggregation principle for PI, and registration in a single object for assignments.
Source facts ↗

Policy text · Astra identified a substantive wording change in this retained policy section.

Source facts −
Assignments must only be made for specific purposes documented by specific organisations, and it is not allowed to create further sub-assignments to another entity from address space partially or fully covering an assignment.
Source facts ↗
Source facts +
Assignments must only be made for specific purposes documented by specific organisations, and it is not allowed to fully or partially sub-assign them to another entity.
Source facts ↗

Policy text · Astra identified a substantive wording change in this retained policy section.

Source facts −
Providing connectivity to another entity inside the assignment holder’s network located at the same geographical End Site as the holder’s network with a prefix size of /56 or longer from the assignment is not considered a sub-assignment.
Source facts ↗
Source facts +
Providing connectivity to another entity inside the assignment holder’s network, at the same geographical End Site, with a prefix size of /56 or longer from the assignment, is not considered a sub-assignment.
Source facts ↗

Policy text · Astra identified a substantive wording change in this retained policy section.

Source facts −
This includes letting visitors connect to the assignment holder's network, providing static addresses when connecting a server or appliance to an assignment holder's network, providing a single service with multiple addresses, or using a /64 or longer when setting up point-to-point links with other ISPs for the purpose of exchanging traffic and Internet routing information.
Source facts ↗
Source facts +
This includes letting visitors connect to the assignment holder's network, providing static addresses when connecting a server or appliance to the assignment holder's network, providing a single service with multiple addresses, or using a /64 or longer when setting up point-to-point links with other ISPs for the purpose of exchanging traffic and Internet routing information.
Source facts ↗

Policy text · Astra identified a substantive wording change in this retained policy section.

Source facts −
Finally, using more specific prefixes from a less-specific assignment for different parts of the same infrastructure within one organisation does not constitute a sub-assignment, if the purpose of the assignment is the operation of that infrastructure.
Source facts ↗
Source facts +
Finally, using more specific prefixes from a less-specific assignment for different parts of the same infrastructure within one organisation does not constitute a sub-assignment, provided the purpose of the assignment is the operation of that infrastructure.
Source facts ↗

Policy text · Astra identified a substantive wording change in this retained policy section.

Source facts −
Any other use of a prefix from an assignment up to prefixes of /128 bit to connect a separate End Site of another entity to the Internet always constitutes a prohibited sub-assignment.
Source facts ↗
Source facts +
Any other use of a prefix from an assignment (up to prefixes of /128) to connect the separate End Site of another entity to the Internet constitutes a prohibited sub-assignment.
Source facts ↗

Policy text · Astra identified a substantive wording change in this retained policy section.

Source facts −
2.6 Purpose and Considerations 2.6 Purpose: Clarify that even assignment holders may, for example, host a customer’s server or VM in their network, providing more than a single IPv6 address as common for IPv6 (at least /64).
Source facts ↗
Source facts +
Any other use of a prefix from an assignment (up to prefixes of /128) to connect the separate End Site of another entity to the Internet constitutes a prohibited sub-assignment. 5.4 Current policy text 5.4 Assignment 5.4.2.
Source facts ↗
3.0
Aug 13, 2024
Source facts ↗

Policy text · Astra identified a substantive wording change in this retained policy section.

Source facts −
This includes letting visitors connect to the assignment holder's network, providing static addresses when connecting a server or appliance to the assignment holder's network, providing a single service with multiple addresses, or using a /64 or longer when setting up point-to-point links with other ISPs for the purpose of exchanging traffic and Internet routing information.
Source facts ↗
Source facts +
This includes letting visitors connect to the assignment holder's network, providing persistent addresses when connecting a server or appliance to the assignment holder's network, providing a single service with multiple addresses, or using a /64 or longer when setting up point-to-point links with other ISPs for the purpose of exchanging traffic and Internet routing information.
Source facts ↗

Policy text · Astra identified a substantive wording change in this retained policy section.

Source facts −
Any other use of a prefix from an assignment (up to prefixes of /128) to connect the separate End Site of another entity to the Internet constitutes a prohibited sub-assignment.
Source facts ↗
Source facts +
Any other use of a prefix from an assignment (up to prefixes of /128) to connect the separate End Site of another entity to the Internet without the exchange of Internet routing information constitutes a prohibited sub-assignment.
Source facts ↗

Policy text · Astra identified a substantive wording change in this retained policy section.

Source facts −
Purposes Clarifying PI assignment scope Assignment holders may assign more than a single IPv6 address (/64) for custom servers/VMs within their End Site, static prefixes and routable prefixes.
Source facts ↗
Source facts +
Purposes Clarifying PI assignment scope Assignment holders may assign more than a single IPv6 address (/64) for custom servers/VMs within their End Site, persistent prefixes and routable prefixes.
Source facts ↗

Debate timeline

  1. Introduced

    Introduced

    Source facts ↗

  2. Official version

    1.0

    Source facts ↗

  3. Official version

    2.0

    Source facts ↗

  4. Official version

    3.0

    Source facts ↗

  5. Official decision

    withdrawn

    withdrawn

    Source facts ↗

Entities

Freshness: Stale
  1. Clara Wade
    Discussion messages0
    First activityUnknown
    Last activityUnknown
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies0
  2. Tobias Fiebig · Identity unresolved
    Discussion messages0
    First activityUnknown
    Last activityUnknown
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies0

Sources and coverage

Official policy sources

Public discussion archives

  • ripencc-address-policy-wg
    Earliest captured
    Aug 7, 2003
    Latest captured
    Oct 6, 2026
    Last refresh
    Aug 13, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    20,481
    Known gaps
    69
  • www.ripe.net
  • ripencc-accountability-tf-ripe.net
    Earliest captured
    Nov 24, 2016
    Latest captured
    May 9, 2019
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    4,047
    Known gaps
    0
  • ripencc-agm-nominations-ripe.net
    Earliest captured
    Mar 26, 2008
    Latest captured
    Apr 28, 2026
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,822
    Known gaps
    0
  • ripencc-all-anchors-ripe.net
    Earliest captured
    Oct 31, 2014
    Latest captured
    Oct 31, 2014
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    528
    Known gaps
    0
  • ripencc-anti-abuse-wg-ripe.net
    Earliest captured
    Sep 16, 2008
    Latest captured
    Nov 4, 2025
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,746
    Known gaps
    0
  • ripencc-atlas-sponsors-ripe.net
    Earliest captured
    Dec 7, 2012
    Latest captured
    Mar 31, 2014
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    1,670
    Known gaps
    0
  • ripencc-atlas-sw-probes-ripe.net
    Earliest captured
    Oct 21, 2019
    Latest captured
    Jul 24, 2024
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,453
    Known gaps
    0
  • ripencc-bcop-ripe.net
    Earliest captured
    Jun 16, 2013
    Latest captured
    Oct 29, 2024
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    4,684
    Known gaps
    0
  • ripencc-coc-tf-ripe.net
    Earliest captured
    Sep 18, 2020
    Latest captured
    Apr 20, 2023
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,716
    Known gaps
    0
  • ripencc-connect-bof-ripe.net
    Earliest captured
    Oct 18, 2013
    Latest captured
    Jul 14, 2014
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    2,760
    Known gaps
    1
  • ripencc-connect-wg-ripe.net
    Earliest captured
    Oct 20, 2014
    Latest captured
    Sep 28, 2026
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    4,721
    Known gaps
    0
  • ripencc-cooperation-wg-ripe.net
    Earliest captured
    Aug 26, 2008
    Latest captured
    Oct 6, 2026
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    4,762
    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,521
    Known gaps
    0
  • ripencc-db-wg-ripe.net
    Earliest captured
    Oct 21, 1992
    Latest captured
    Oct 9, 2026
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,536
    Known gaps
    0
  • ripencc-diversity-ripe.net
    Earliest captured
    May 18, 2017
    Latest captured
    Feb 9, 2026
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    4,111
    Known gaps
    0
  • ripencc-dns-resolver-tf-ripe.net
    Earliest captured
    Jan 23, 2023
    Latest captured
    Feb 16, 2025
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,058
    Known gaps
    0
  • ripencc-dns-wg-ripe.net
    Earliest captured
    Jun 30, 1992
    Latest captured
    Oct 9, 2026
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,356
    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,935
    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,220
    Known gaps
    63
  • ripencc-eix-wg-ripe.net
    Earliest captured
    Jan 1, 1999
    Latest captured
    Oct 21, 2013
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    4,060
    Known gaps
    0
  • ripencc-election-cc-team-ripe.net
    Earliest captured
    Aug 18, 2026
    Latest captured
    Aug 18, 2026
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    473
    Known gaps
    0
  • ripencc-enum-announce-ripe.net
    Earliest captured
    Aug 15, 2003
    Latest captured
    Sep 15, 2026
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,504
    Known gaps
    0
  • ripencc-enum-wg-ripe.net
    Earliest captured
    Jun 16, 2004
    Latest captured
    Nov 20, 2013
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,762
    Known gaps
    0
  • ripencc-green-tech-hackathon-orga-ripe.net
    Earliest captured
    Unknown
    Latest captured
    Unknown
    Last refresh
    Oct 12, 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 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,244
    Known gaps
    0
  • ripencc-icann-plan-ripe.net
    Earliest captured
    Dec 8, 2004
    Latest captured
    Jan 31, 2005
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    823
    Known gaps
    0
  • ripencc-iot-wg-ripe.net
    Earliest captured
    Nov 3, 2016
    Latest captured
    Aug 19, 2026
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,411
    Known gaps
    0
  • ripencc-ipmap-ripe.net
    Earliest captured
    Nov 25, 2021
    Latest captured
    May 17, 2022
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    620
    Known gaps
    0
  • ripencc-ipmt-dev-ripe.net
    Earliest captured
    May 3, 2001
    Latest captured
    Jul 2, 2003
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    2,852
    Known gaps
    0
  • ripencc-ipv6-wg-ripe.net
    Earliest captured
    Mar 31, 1995
    Latest captured
    Oct 5, 2026
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,437
    Known gaps
    0
  • ripencc-irrtoolset-ripe.net
    Earliest captured
    Aug 12, 2003
    Latest captured
    Dec 15, 2004
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,596
    Known gaps
    0
  • ripencc-lir-wg-ripe.net
    Earliest captured
    Oct 8, 1992
    Latest captured
    Jun 30, 2003
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,254
    Known gaps
    0
  • ripencc-mat-wg-ripe.net
    Earliest captured
    May 18, 2010
    Latest captured
    Sep 23, 2026
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    2,915
    Known gaps
    0
  • ripencc-measure-voip-ripe.net
    Earliest captured
    May 25, 2004
    Latest captured
    Jul 9, 2004
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    1,121
    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,452
    Known gaps
    13
  • ripencc-members-discuss-ripe.net
    Earliest captured
    Mar 8, 2007
    Latest captured
    Oct 6, 2026
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,587
    Known gaps
    0
  • ripencc-myasntesting-ripe.net
    Earliest captured
    Aug 14, 2003
    Latest captured
    Jun 29, 2009
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,697
    Known gaps
    0
  • ripencc-ncc-announce-ripe.net
    Earliest captured
    Jun 27, 2006
    Latest captured
    Oct 6, 2026
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,195
    Known gaps
    0
  • ripencc-ncc-services-wg-ripe.net
    Earliest captured
    Aug 6, 2003
    Latest captured
    Oct 2, 2026
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,541
    Known gaps
    0
  • ripencc-nccdays-pc-ripe.net
    Earliest captured
    Unknown
    Latest captured
    Unknown
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    21
    Known gaps
    0
  • ripencc-opensource-wg-ripe.net
    Earliest captured
    Mar 14, 2013
    Latest captured
    Oct 2, 2026
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,937
    Known gaps
    0
  • ripencc-persian-lir-ripe.net
    Earliest captured
    Jul 9, 2015
    Latest captured
    Jul 8, 2023
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    5,679
    Known gaps
    0
  • ripencc-policy-announce-ripe.net
    Earliest captured
    Aug 30, 2005
    Latest captured
    Sep 28, 2026
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,971
    Known gaps
    0
  • ripencc-raci-list-ripe.net
    Earliest captured
    Jul 24, 2014
    Latest captured
    Sep 22, 2026
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,374
    Known gaps
    0
  • ripencc-regional-russia-ripe.net
    Earliest captured
    Sep 27, 2005
    Latest captured
    Jul 4, 2011
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    4,951
    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,930
    Known gaps
    1
  • ripencc-ripe-atlas-ambassadors-ripe.net
    Earliest captured
    Dec 20, 2013
    Latest captured
    Sep 23, 2026
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    5,206
    Known gaps
    0
  • ripencc-ripe-atlas-tools-maintainers-ripe.net
    Earliest captured
    Jan 12, 2016
    Latest captured
    Mar 25, 2016
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    1,507
    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,404
    Known gaps
    1
  • ripencc-ripe-chair-discuss-ripe.net
    Earliest captured
    Oct 7, 2016
    Latest captured
    Oct 17, 2022
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,657
    Known gaps
    0
  • ripencc-ripe-db-requirements-tf-ripe.net
    Earliest captured
    Oct 15, 2019
    Latest captured
    Nov 16, 2021
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    4,524
    Known gaps
    0
  • ripencc-ripe-forum-test-ripe.net
    Earliest captured
    Apr 11, 2016
    Latest captured
    Jun 20, 2019
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    2,464
    Known gaps
    0
  • ripencc-ripe-list-unmoderated-ripe.net
    Earliest captured
    Jun 1, 2026
    Latest captured
    Oct 9, 2026
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    7,211
    Known gaps
    0
  • ripencc-ripe-list-ripe.net
    Earliest captured
    Jul 2, 1992
    Latest captured
    Oct 5, 2026
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,822
    Known gaps
    0
  • ripencc-ripe-parents-ripe.net
    Earliest captured
    Oct 19, 2011
    Latest captured
    May 5, 2016
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    1,963
    Known gaps
    0
  • ripencc-ripecast-ripe.net
    Earliest captured
    Aug 29, 2003
    Latest captured
    Sep 28, 2009
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    4,502
    Known gaps
    0
  • ripencc-rirs-lea-ripe.net
    Earliest captured
    Jul 2, 2016
    Latest captured
    Apr 9, 2019
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,128
    Known gaps
    1
  • ripencc-ris-int-ripe.net
    Earliest captured
    Dec 31, 1997
    Latest captured
    Nov 26, 2016
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    4,474
    Known gaps
    0
  • ripencc-ris-users-ripe.net
    Earliest captured
    Aug 8, 2003
    Latest captured
    Aug 24, 2026
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    4,061
    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,518
    Known gaps
    1
  • ripencc-rpslng-ripe.net
    Earliest captured
    Aug 26, 2003
    Latest captured
    Nov 8, 2007
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,470
    Known gaps
    0
  • ripencc-security-wg-ripe.net
    Earliest captured
    Nov 18, 2024
    Latest captured
    Oct 5, 2026
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    14,062
    Known gaps
    1
  • ripencc-see-regional-ripe.net
    Earliest captured
    Aug 24, 2011
    Latest captured
    Sep 28, 2026
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,799
    Known gaps
    0
  • ripencc-techsec-wg-ripe.net
    Earliest captured
    May 15, 2001
    Latest captured
    Feb 29, 2016
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    4,052
    Known gaps
    0
  • ripencc-tld-wg-ripe.net
    Earliest captured
    Jul 9, 1997
    Latest captured
    Apr 22, 2015
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    4,678
    Known gaps
    0
  • ripencc-tt-tf-ripe.net
    Earliest captured
    May 30, 2006
    Latest captured
    Dec 7, 2007
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    2,196
    Known gaps
    0

Coverage

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