BTW.Media
Daily editionStrategic Internet Intelligence
Sign InRegister

RIPE NCC · RIR Watchdog

Anycasting Assignments for TLDs and Tier 0/1 ENUM

Start here for the proposal-by-proposal record: what changed, why it mattered, who argued for what, how positions evolved, what was decided, and where the evidence still has gaps.

Source facts

Policy ID
2008-05
RIR
RIPE NCC
Official status
Accepted
Normalized status
Accepted
Introduced
Feb 14, 2022
Last source update
Oct 9, 2026
Coverage
Partial

Who actually shaped the debate?

16Total participants
14Discussion contributors
2Formal actors
18Discussion messages
10.1Effective participants
50%Top-five discussion share
5People covering 50%
11People covering 80%

Policy evolution

2.0
Accepted · Accepted
Apr 27, 2009
Source facts ↗

IPv4 anycast eligibility · Eligibility is changed from a test based on whether a ccTLD, gTLD or Tier 0/1 ENUM name-server set would fail the cited IANA procedure to a category-based rule covering TLD operators defined by IANA and ENUM operators defined by the ITU as critical DNS infrastructure.

Source facts −
If the name server set of a ccTLD, gTLD or a Tier 0/1 ENUM without anycasting technology applied would not pass the 'IANA Administrative Procedure for Root Zone Name Server Delegation and Glue Data' the TLD or the ENUM administrator
Source facts ↗
Source facts +
Critical DNS infrastructure is defined as infrastructure providing Authoritative TLD or ENUM Tier 0/1 DNS lookup services. The organisation(s) applicable under this policy are TLDs operators as defined by IANA and ENUM operators as defined by the ITU.
Source facts ↗

IPv4 anycast assignment limit · The proposed IPv4 entitlement increases from one dedicated /24 to up to four /24 prefixes per TLD or ENUM.

Source facts −
may receive a single dedicated /24 network prefix for the sole purpose of anycasting name servers, as described in RFC 3258.
Source facts ↗
Source facts +
The organisation may receive up to four /24 prefixes per TLD/ENUM. These prefixes must be used for the sole purpose of anycasting authoratitve DNS servers for the stated TLD/ENUM, as described in RFC 3258.
Source facts ↗

IPv4 assignment conditions · The proposed IPv4 text removes the explicit direct-assignment-through-an-existing-LIR procedure and instead makes critical-DNS assignments subject to the general Provider Independent number-resource policies and the stated contractual requirements.

Source facts −
The prefix will be assigned by the RIPE NCC directly to the TLD or ENUM operator, upon a request submitted via an existing LIR and will be registered with a status of 'ASSIGNED ANYCAST'
Source facts ↗
Source facts +
Assignments for Critical DNS infrastructure are subject to Provider Independent (PI) number resource policies as described in this document and also to the policies described in the RIPE NCC document entitled "Contractual Requirements for Provider Independent Resources Holders in the RIPE NCC Service Region".
Source facts ↗

IPv6 anycast eligibility · Eligibility is changed from a test based on whether a ccTLD, gTLD or Tier 0/1 ENUM name-server set would fail the cited IANA procedure to a category-based rule covering TLD operators defined by IANA and ENUM operators defined by the ITU as critical DNS infrastructure.

Source facts −
If the name server set of a ccTLD, gTLD or a Tier 0/1 ENUM without anycasting technology applied would not pass the 'IANA Administrative Procedure for Root Zone Name Server Delegation and Glue Data' the TLD or the ENUM administrator
Source facts ↗
Source facts +
Critical DNS infrastructure is defined as infrastructure providing Authoratitve TLD or ENUM Tier 0/1 DNS lookup services. The organisation(s) applicable under this policy are TLDs operators as defined by IANA and ENUM operators as defined by the ITU.
Source facts ↗

IPv6 anycast assignment limit · The proposed IPv6 entitlement increases from one dedicated /48 to up to four /48 prefixes per TLD or ENUM.

Source facts −
may receive a single dedicated /48 network prefix for the sole purpose of anycasting name servers, as described in RFC 3258.
Source facts ↗
Source facts +
The organisation may receive up to four /48 prefixes per TLD/ENUM. These prefixes must be used for the sole purpose of anycasting authoratitve DNS servers for the stated TLD/ENUM, as described in RFC 3258.
Source facts ↗

IPv6 assignment procedure and contractual conditions · The request path is broadened from submission through an existing LIR to submission either directly to the RIPE NCC or through a sponsoring LIR, and the revised text adds the stated contractual requirements for critical-DNS assignments.

Source facts −
The prefix will be assigned by the RIPE NCC directly to the TLD or ENUM operator, upon a request submitted via an existing LIR and will be registered with a status of 'ASSIGNED ANYCAST'
Source facts ↗
Source facts +
The prefix will be assigned by the RIPE NCC directly to the organisation, upon a request properly submitted to the RIPE NCC, either directly or through a sponsoring LIR. Assignments for Critical DNS infrastructure are subject to the policies described in the RIPE NCC document entitled "Contractual Requirements for Provider Independent Resources Holders in the RIPE NCC Service Region".
Source facts ↗
3.0
Accepted · Accepted
Apr 27, 2009
Source facts ↗

Existing IPv4 policy baseline · The document refreshes the quoted existing IPv4 rule from RIPE-424 to ripe-449. The newer baseline replaces the explicit direct-assignment-via-existing-LIR wording with applicability of Provider Independent number-resource policies and the contractual requirements. This is a change to the comparison baseline, not the proposal's new entitlement.

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

Proposed IPv4 policy dependencies · The proposed IPv4 text drops the explicit statement that critical-DNS assignments are subject to the general Provider Independent number-resource policies, while retaining the contractual-requirements reference.

Source facts −
Assignments for Critical DNS infrastructure are subject to Provider Independent (PI) number resource policies as described in this document and also to the policies described in the RIPE NCC document entitled "Contractual Requirements for Provider Independent Resources Holders in the RIPE NCC Service Region".
Source facts ↗
Source facts +
Assignments for Critical DNS infrastructure are subject to the policies described in the RIPE document entitled "Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region".
Source facts ↗

Existing IPv6 policy baseline · The quoted existing IPv6 rule is refreshed from RIPE-421 to ripe-466: the baseline now names only the TLD administrator, allows a request either directly or through a sponsoring LIR, and adds the contractual-requirements condition. This is a baseline update rather than a new proposal entitlement.

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

Proposed IPv6 assignment procedure · The revised proposed IPv6 text removes the sentence explicitly assigning the prefix directly to the organisation and allowing requests either directly or through a sponsoring LIR; it proceeds instead from the anycast-use rule to the contractual-requirements condition.

Source facts −
The prefix will be assigned by the RIPE NCC directly to the organisation, upon a request properly submitted to the RIPE NCC, either directly or through a sponsoring LIR.
Source facts ↗
Source facts +
Assignments for Critical DNS infrastructure are subject to the policies described in the RIPE document entitled "Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region".
Source facts ↗
4.0
Accepted · Accepted
Apr 27, 2009
Source facts ↗

IPv4 eligible operator definition · The IPv4 text replaces the generic critical-DNS definition and TLD/ENUM operators defined by IANA or ITU with TLD managers recorded in IANA's Root Zone Database and ENUM administrators assigned by the ITU.

Source facts −
Critical DNS infrastructure is defined as infrastructure providing Authoritative TLD or ENUM Tier 0/1 DNS lookup services. The organisations applicable under this policy are TLD operators as defined by IANA and ENUM operators as defined by the ITU.
Source facts ↗
Source facts +
The organisations applicable under this policy are TLD managers, as recorded in the IANA's Root Zone Database and ENUM administrators, as assigned by the ITU.
Source facts ↗

IPv4 assignment-cap wording · The cap is made explicit as up to four /24 prefixes per TLD and up to four /24 prefixes per ENUM, replacing the shorter 'per TLD/ENUM' formulation.

Source facts −
The organisation may receive up to four /24 prefixes per TLD/ENUM.
Source facts ↗
Source facts +
The organisation may receive up to four /24 prefixes per TLD and four /24 prefixes per ENUM.
Source facts ↗

IPv4 anycast technical standard · The cited technical basis for use of the prefixes changes from RFC 3258 to BCP126/RFC4786.

Source facts −
These prefixes must be used for the sole purpose of anycasting authoritative DNS servers for the stated TLD/ENUM, as described in RFC 3258.
Source facts ↗
Source facts +
These prefixes must be used for the sole purpose of anycasting authoritative DNS servers for the stated TLD/ENUM, as described in BCP126/RFC4786.
Source facts ↗

IPv6 eligible operator definition · The IPv6 text replaces the generic critical-DNS definition and TLD/ENUM operators defined by IANA or ITU with TLD managers recorded in IANA's Root Zone Database and ENUM administrators assigned by the ITU.

Source facts −
Critical DNS infrastructure is defined as infrastructure providing Authoritative TLD or ENUM Tier 0/1 DNS lookup services. The organisations applicable under this policy are TLD operators as defined by IANA and ENUM operators as defined by the ITU.
Source facts ↗
Source facts +
The organisations applicable under this policy are TLD managers as, recorded in the IANA's Root Zone Database and ENUM administrators, as assigned by the ITU.
Source facts ↗

IPv6 assignment-cap wording · The cap is made explicit as up to four /48 prefixes per TLD and up to four /48 prefixes per ENUM, replacing the shorter 'per TLD/ENUM' formulation.

Source facts −
The organisation may receive up to four /48 prefixes per TLD/ENUM.
Source facts ↗
Source facts +
The organisation may receive up to four /48 prefixes per TLD and four /48 prefixes per ENUM.
Source facts ↗

IPv6 anycast technical standard · The cited technical basis for use of the prefixes changes from RFC 3258 to BCP126/RFC4786.

Source facts −
These prefixes must be used for the sole purpose of anycasting authoritative DNS servers for the stated TLD/ENUM, as described in RFC 3258.
Source facts ↗
Source facts +
These prefixes must be used for the sole purpose of anycasting authoritative DNS servers for the stated TLD/ENUM, as described in BCP126/RFC4786
Source facts ↗

Debate timeline

  1. Public discussion

    [address-policy-wg] 2008-05 New Policy Proposal (Anycasting Tier 0/1 ENUM)

    2 Discussion messages · 2 Entities

    Source facts ↗

  2. Public discussion

    [address-policy-wg] DRAFT agenda for RIPE address policy WG in Dubai

    2 Discussion messages · 2 Entities

    Source facts ↗

  3. Public discussion

    Re: [address-policy-wg] Re: Assignments for Critical Infrastruction

    3 Discussion messages · 3 Entities

    Source facts ↗

  4. Public discussion

    Re: [address-policy-wg] IPv6 assignment for the RIPE meeting network

    3 Discussion messages · 3 Entities

    Source facts ↗

  5. Official version

    1.0

    Accepted · Accepted

    Source facts ↗

  6. Official version

    2.0

    Accepted · Accepted

    Source facts ↗

  7. Official version

    3.0

    Accepted · Accepted

    Source facts ↗

  8. Official version

    4.0

    Accepted · Accepted

    Source facts ↗

  9. Official decision

    accepted

    accepted

    Source facts ↗

  10. Introduced

    Introduced

    Source facts ↗

Entities

Freshness: Stale
  1. Gert Doering
    Discussion messages4
    First activitySep 4, 2008
    Last activitySep 20, 2009
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies15
  2. Filiz Yilmaz · Identity unresolved
    Discussion messages2
    First activitySep 4, 2008
    Last activityOct 15, 2008
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies2
  3. Krzysztof Olesik · Identity unresolved
    Discussion messages1
    First activityNov 4, 2008
    Last activityNov 4, 2008
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies0
  4. Ondřej Surý · Identity unresolved
    Discussion messages1
    First activityNov 20, 2008
    Last activityNov 20, 2008
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies1
  5. Niall O'Reilly · Public sources found; identity verification pending
    Discussion messages1
    First activityOct 22, 2008
    Last activityOct 22, 2008
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies1
  6. Scott Donald · Identity unresolved
    Discussion messages1
    First activityJul 16, 2009
    Last activityJul 16, 2009
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies8
  7. Greg L. · Identity unresolved
    Discussion messages1
    First activityAug 8, 2007
    Last activityAug 8, 2007
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies0
  8. Elmar K. Bins · Identity unresolved
    Discussion messages1
    First activityOct 29, 2008
    Last activityOct 29, 2008
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies0
  9. Jim Reid · Identity unresolved
    Discussion messages1
    First activitySep 4, 2008
    Last activitySep 4, 2008
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies2
  10. Tomas Hlavacek · Identity unresolved
    Discussion messages1
    First activityDec 3, 2008
    Last activityDec 3, 2008
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies0
  11. B C · Identity unresolved
    Discussion messages1
    First activityNov 17, 2008
    Last activityNov 17, 2008
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies0
  12. Florian Weimer · Identity unresolved
    Discussion messages1
    First activityOct 30, 2008
    Last activityOct 30, 2008
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies1
  13. Nick Hilliard · Identity unresolved
    Discussion messages1
    First activityNov 20, 2008
    Last activityNov 20, 2008
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies1
  14. Andreas Bäß/Denic · Identity unresolved
    Discussion messages1
    First activityAug 23, 2006
    Last activityAug 23, 2006
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies0
  15. Ondřej Surý
    Discussion messages0
    First activityUnknown
    Last activityUnknown
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies0
  16. Brett Carr
    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,200
    Known gaps
    83
  • www.ripe.net
  • ripencc-accountability-tf-ripe.net
    Earliest captured
    Nov 24, 2016
    Latest captured
    May 9, 2019
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,706
    Known gaps
    0
  • ripencc-agm-nominations-ripe.net
    Earliest captured
    Mar 26, 2008
    Latest captured
    Apr 28, 2026
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,408
    Known gaps
    0
  • ripencc-all-anchors-ripe.net
    Earliest captured
    Oct 31, 2014
    Latest captured
    Oct 31, 2014
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    502
    Known gaps
    0
  • ripencc-anti-abuse-wg-ripe.net
    Earliest captured
    Sep 16, 2008
    Latest captured
    Nov 4, 2025
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,350
    Known gaps
    0
  • ripencc-atlas-sponsors-ripe.net
    Earliest captured
    Dec 7, 2012
    Latest captured
    Mar 31, 2014
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    1,507
    Known gaps
    0
  • ripencc-atlas-sw-probes-ripe.net
    Earliest captured
    Oct 21, 2019
    Latest captured
    Jul 24, 2024
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,102
    Known gaps
    0
  • ripencc-bcop-ripe.net
    Earliest captured
    Jun 16, 2013
    Latest captured
    Oct 29, 2024
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    4,150
    Known gaps
    0
  • ripencc-coc-tf-ripe.net
    Earliest captured
    Sep 18, 2020
    Latest captured
    Apr 20, 2023
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,339
    Known gaps
    0
  • ripencc-connect-bof-ripe.net
    Earliest captured
    Oct 18, 2013
    Latest captured
    Jul 14, 2014
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    2,500
    Known gaps
    1
  • ripencc-connect-wg-ripe.net
    Earliest captured
    Oct 20, 2014
    Latest captured
    Sep 28, 2026
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    4,320
    Known gaps
    0
  • ripencc-cooperation-wg-ripe.net
    Earliest captured
    Aug 26, 2008
    Latest captured
    Oct 6, 2026
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    4,469
    Known gaps
    0
  • ripencc-db-help-ripe.net
    Earliest captured
    Aug 20, 2003
    Latest captured
    Jan 13, 2016
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    4,153
    Known gaps
    0
  • ripencc-db-wg-ripe.net
    Earliest captured
    Oct 21, 1992
    Latest captured
    Oct 6, 2026
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,311
    Known gaps
    0
  • ripencc-diversity-ripe.net
    Earliest captured
    May 18, 2017
    Latest captured
    Feb 9, 2026
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,751
    Known gaps
    0
  • ripencc-dns-resolver-tf-ripe.net
    Earliest captured
    Jan 23, 2023
    Latest captured
    Feb 16, 2025
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    2,797
    Known gaps
    0
  • ripencc-dns-wg-ripe.net
    Earliest captured
    Jun 30, 1992
    Latest captured
    Oct 9, 2026
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,114
    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,687
    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,133
    Known gaps
    52
  • ripencc-eix-wg-ripe.net
    Earliest captured
    Jan 1, 1999
    Latest captured
    Oct 21, 2013
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,669
    Known gaps
    0
  • ripencc-election-cc-team-ripe.net
    Earliest captured
    Aug 18, 2026
    Latest captured
    Aug 18, 2026
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    452
    Known gaps
    0
  • ripencc-enum-announce-ripe.net
    Earliest captured
    Aug 15, 2003
    Latest captured
    Sep 15, 2026
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,145
    Known gaps
    0
  • ripencc-enum-wg-ripe.net
    Earliest captured
    Jun 16, 2004
    Latest captured
    Nov 20, 2013
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,434
    Known gaps
    0
  • ripencc-green-tech-hackathon-orga-ripe.net
    Earliest captured
    Unknown
    Latest captured
    Unknown
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    21
    Known gaps
    0
  • ripencc-hackathon-list-ripe.net
    Earliest captured
    Feb 26, 2015
    Latest captured
    Jan 9, 2025
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    2,921
    Known gaps
    0
  • ripencc-icann-plan-ripe.net
    Earliest captured
    Dec 8, 2004
    Latest captured
    Jan 31, 2005
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    782
    Known gaps
    0
  • ripencc-iot-wg-ripe.net
    Earliest captured
    Nov 3, 2016
    Latest captured
    Aug 19, 2026
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,022
    Known gaps
    0
  • ripencc-ipmap-ripe.net
    Earliest captured
    Nov 25, 2021
    Latest captured
    May 17, 2022
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    579
    Known gaps
    0
  • ripencc-ipmt-dev-ripe.net
    Earliest captured
    May 3, 2001
    Latest captured
    Jul 2, 2003
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    2,612
    Known gaps
    0
  • ripencc-ipv6-wg-ripe.net
    Earliest captured
    Mar 31, 1995
    Latest captured
    Oct 5, 2026
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,110
    Known gaps
    0
  • ripencc-irrtoolset-ripe.net
    Earliest captured
    Aug 12, 2003
    Latest captured
    Dec 15, 2004
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,264
    Known gaps
    0
  • ripencc-lir-wg-ripe.net
    Earliest captured
    Oct 8, 1992
    Latest captured
    Jun 30, 2003
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    2,943
    Known gaps
    0
  • ripencc-mat-wg-ripe.net
    Earliest captured
    May 18, 2010
    Latest captured
    Sep 23, 2026
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    2,578
    Known gaps
    0
  • ripencc-measure-voip-ripe.net
    Earliest captured
    May 25, 2004
    Latest captured
    Jul 9, 2004
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    1,053
    Known gaps
    0
  • ripencc-members-discuss-unmoderated-ripe.net
    Earliest captured
    Jun 1, 2026
    Latest captured
    Oct 9, 2026
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    6,870
    Known gaps
    5
  • ripencc-members-discuss-ripe.net
    Earliest captured
    Mar 8, 2007
    Latest captured
    Oct 6, 2026
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,339
    Known gaps
    0
  • ripencc-myasntesting-ripe.net
    Earliest captured
    Aug 14, 2003
    Latest captured
    Jun 29, 2009
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,381
    Known gaps
    0
  • ripencc-ncc-announce-ripe.net
    Earliest captured
    Jun 27, 2006
    Latest captured
    Oct 6, 2026
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    2,949
    Known gaps
    0
  • ripencc-ncc-services-wg-ripe.net
    Earliest captured
    Aug 6, 2003
    Latest captured
    Oct 2, 2026
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,263
    Known gaps
    0
  • ripencc-nccdays-pc-ripe.net
    Earliest captured
    Unknown
    Latest captured
    Unknown
    Last refresh
    Oct 9, 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 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,590
    Known gaps
    0
  • ripencc-persian-lir-ripe.net
    Earliest captured
    Jul 9, 2015
    Latest captured
    Jul 8, 2023
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    5,215
    Known gaps
    0
  • ripencc-policy-announce-ripe.net
    Earliest captured
    Aug 30, 2005
    Latest captured
    Sep 28, 2026
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,678
    Known gaps
    0
  • ripencc-raci-list-ripe.net
    Earliest captured
    Jul 24, 2014
    Latest captured
    Sep 22, 2026
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,021
    Known gaps
    0
  • ripencc-regional-russia-ripe.net
    Earliest captured
    Sep 27, 2005
    Latest captured
    Jul 4, 2011
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    4,545
    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,831
    Known gaps
    1
  • ripencc-ripe-atlas-ambassadors-ripe.net
    Earliest captured
    Dec 20, 2013
    Latest captured
    Sep 23, 2026
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    4,772
    Known gaps
    0
  • ripencc-ripe-atlas-tools-maintainers-ripe.net
    Earliest captured
    Jan 12, 2016
    Latest captured
    Mar 25, 2016
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    1,405
    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,088
    Known gaps
    1
  • ripencc-ripe-chair-discuss-ripe.net
    Earliest captured
    Oct 7, 2016
    Latest captured
    Oct 17, 2022
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,382
    Known gaps
    0
  • ripencc-ripe-db-requirements-tf-ripe.net
    Earliest captured
    Oct 15, 2019
    Latest captured
    Nov 16, 2021
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    4,087
    Known gaps
    0
  • ripencc-ripe-forum-test-ripe.net
    Earliest captured
    Apr 11, 2016
    Latest captured
    Jun 20, 2019
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    2,243
    Known gaps
    0
  • ripencc-ripe-list-unmoderated-ripe.net
    Earliest captured
    Jun 1, 2026
    Latest captured
    Oct 9, 2026
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    6,724
    Known gaps
    0
  • ripencc-ripe-list-ripe.net
    Earliest captured
    Jul 2, 1992
    Latest captured
    Oct 5, 2026
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,521
    Known gaps
    0
  • ripencc-ripe-parents-ripe.net
    Earliest captured
    Oct 19, 2011
    Latest captured
    May 5, 2016
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    1,793
    Known gaps
    0
  • ripencc-ripecast-ripe.net
    Earliest captured
    Aug 29, 2003
    Latest captured
    Sep 28, 2009
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    4,100
    Known gaps
    0
  • ripencc-rirs-lea-ripe.net
    Earliest captured
    Jul 2, 2016
    Latest captured
    Apr 9, 2019
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    2,808
    Known gaps
    1
  • ripencc-ris-int-ripe.net
    Earliest captured
    Dec 31, 1997
    Latest captured
    Nov 26, 2016
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    4,061
    Known gaps
    0
  • ripencc-ris-users-ripe.net
    Earliest captured
    Aug 8, 2003
    Latest captured
    Aug 24, 2026
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,664
    Known gaps
    0
  • ripencc-routing-wg-ripe.net
    Earliest captured
    Nov 29, 1993
    Latest captured
    Oct 2, 2026
    Last refresh
    Oct 8, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    4,252
    Known gaps
    1
  • ripencc-rpslng-ripe.net
    Earliest captured
    Aug 26, 2003
    Latest captured
    Nov 8, 2007
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,175
    Known gaps
    0
  • ripencc-security-wg-ripe.net
    Earliest captured
    Nov 18, 2024
    Latest captured
    Oct 5, 2026
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    13,784
    Known gaps
    1
  • ripencc-see-regional-ripe.net
    Earliest captured
    Aug 24, 2011
    Latest captured
    Sep 28, 2026
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,421
    Known gaps
    0
  • ripencc-techsec-wg-ripe.net
    Earliest captured
    May 15, 2001
    Latest captured
    Feb 29, 2016
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,710
    Known gaps
    0
  • ripencc-tld-wg-ripe.net
    Earliest captured
    Jul 9, 1997
    Latest captured
    Apr 22, 2015
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    4,261
    Known gaps
    0
  • ripencc-tt-tf-ripe.net
    Earliest captured
    May 30, 2006
    Latest captured
    Dec 7, 2007
    Last refresh
    Oct 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    1,990
    Known gaps
    0

Coverage

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