BTW.Media
Daily editionStrategic Internet Intelligence
Sign InRegister

APNIC · RIR Watchdog

Modification of transfer policies

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
prop-130
RIR
APNIC
Official status
Abandoned at APNIC 51
Normalized status
Abandoned
Introduced
Mar 14, 2019
Last source update
Oct 12, 2026
Coverage
Partial

Who actually shaped the debate?

9Total participants
9Discussion contributors
1Formal actors
19Discussion messages
4.5Effective participants
78.9%Top-five discussion share
2People covering 50%
6People covering 80%

Policy evolution

v002
Unknown
Source facts ↗

IPv4 inter-RIR transfer reciprocity requirement · For IPv4 transfers, the counterpart RIR requirement changes from having a policy that allows the transfer to having a reciprocal policy or procedure that allows it.

Source facts −
nd inter-RIR. In the case of inter-RIR, the counterpart RIR need to have a policy t
Source facts ↗
Source facts +
nd inter-RIR. In the case of inter-RIR, the counterpart RIR need to have a reciprocal policy/procedure that
Source facts ↗

IPv6 inter-RIR transfer reciprocity requirement · For IPv6 transfers, the counterpart RIR requirement changes from having a policy that allows the transfer to having a reciprocal policy or procedure that allows it.

Source facts −
ences apply. In the case of inter-RIR, the counterpart RIR need to have a policy th
Source facts ↗
Source facts +
es apply. In the case of inter-RIR, the counterpart RIR need to have a reciprocal policy/procedure that all
Source facts ↗

ASN inter-RIR transfer reciprocity requirement · For ASN transfers, the counterpart RIR requirement changes from having a policy that allows the transfer to having a reciprocal policy or procedure that allows it.

Source facts −
nd inter-RIR. In the case of inter-RIR, the counterpart RIR need to have a policy t
Source facts ↗
Source facts +
er-RIR. In the case of inter-RIR, the counterpart RIR need to have a reciprocal policy/procedure that allow
Source facts ↗

Stated advantages · The stated advantage that the proposal would encourage waiting-list members to implement IPv6 is removed; only fulfillment of the indicated objectives remains.

Source facts −
------------- Advantages: Fulfilling the objectives above indicated. It will also encourage the waiting list members to i
Source facts ↗
Source facts +
---- Advantages: Fulfilling the objectives above indic
Source facts ↗

Stated disadvantages · The disadvantages assessment changes from none foreseen to a possible risk of further disaggregation, especially in IPv6, described as rare, negligible in impact, and justified by documentation provided to the secretariat.

Source facts −
plement IPv6. Disadvantages:
Source facts ↗
Source facts +
ted. Disadvantages: It could be considered that it can create further disaggregation, especially in IPv6, however, those cases are rare and only happening from time to time, so the impact is negligible, and justified by the documentation provided to the secreta
Source facts ↗
v003
Unknown
Source facts ↗

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

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

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

Source facts −
Problem statement ------------------------------------------------------- Existing transfer policies for IPv4, IPv6 and ASN resources have some differences among what is allowed and what not, if in the case of intra-RIR and inter-RIR, and it is not clear if in case of merger and acquisitions it is referring to a complete company, part of it, or even if in case of a company reorganization or relocation, the policy is supportive to that case.
Source facts ↗
Source facts +
Problem statement -------------------- Existing transfer policies for IPv4, IPv6 and ASN resources have some differences among what is allowed and what not, if in the case of intra-RIR and inter-RIR, and it is not clear if in case of merger and acquisitions it is referring to a complete company, part of it, or even if in case of a company reorganization or relocation, the policy is supportive to that case.
Source facts ↗

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

Source facts −
In the case of inter-RIR, the counterpart RIR need to have a reciprocal policy or procedure that allows it.
Source facts ↗
Source facts +
In some regions, this may not be a policy, but an administrative procedure, but this may change in the future by means of a policy proposal.
Source facts ↗

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

Source facts −
In the case of inter-RIR, the counterpart RIR need to have a reciprocal policy or procedure that allows it.
Source facts ↗
Source facts +
In the caser of inter-RIR, the counterpart RIR need to have a reciprocal policy or procedure that allows it.
Source facts ↗

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

Source facts −
In the case of inter-RIR, the counterpart RIR need to have a reciprocal policy or procedure that allows it. 2.
Source facts ↗
Source facts +
Finally, there should not be differences from the APNIC perspective, on the considerations of an M&A for different type of resources, because there is no reason for allowing, for example, IPv4 resources to be transferred, and instead IPv6 ones not.
Source facts ↗

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

Source facts −
Objective of policy change ------------------------------------------------------- To ensure that the policy text is clarified, if those cases are supported by the community.
Source facts ↗
Source facts +
Objective of policy change ------------------------------ To ensure that the policy text is clarified, if those cases are supported by the community.
Source facts ↗

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

Source facts −
It will also facilitate companies or business units, moving or being established in other regions. 3.
Source facts ↗
Source facts +
It will minimize legal issues in case an acquisition claiming their rights over the acquired company and their existing assets (resources).
Source facts ↗

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

Source facts −
Situation in other regions ------------------------------------------------------- There is a variety of support of all those cases in different regions.
Source facts ↗
Source facts +
Situation in other regions ------------------------------ There is a variety of support of all those cases in different regions.
Source facts ↗

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

Source facts −
The one more open is RIPE, followed by ARIN.
Source facts ↗
Source facts +
The one more open is RIPE, followed by ARIN and LACNIC.
Source facts ↗

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

Source facts −
Similar policy proposals are being submitted in LACNIC and AFRINIC.
Source facts ↗
Source facts +
A similar policy proposal is being discussed in AFRINIC.
Source facts ↗

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

Source facts −
Proposed policy solution ------------------------------------------------------- Actual Text 8.4.
Source facts ↗
Source facts +
Proposed policy solution ---------------------------- Actual Text 8.4.
Source facts ↗

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

Source facts −
Mergers, acquisitions and relocations APNIC will process and record the transfer of IPv4 resources as the result of a partial or complete merger, acquisition, reorganization or relocation, in both cases, intra-RIR and inter-RIR.
Source facts ↗
Source facts +
Mergers, acquisitions and relocations APNIC will recognize the transfer of IPv4 resources resulting from a partial or complete merger, acquisition, reorganization or relocation.
Source facts ↗

Debate timeline

  1. Official version

    v001

    Source facts ↗

  2. Official version

    v002

    Source facts ↗

  3. Official version

    v003

    Source facts ↗

  4. Introduced

    Introduced

    Source facts ↗

  5. Public discussion

    Re: [sig-policy] Policy Proposal: prop-130-v001: Modification of transfer policies

    4 Discussion messages · 3 Entities

    Source facts 1 ↗Source facts 2 ↗Source facts 3 ↗Source facts 4 ↗

  6. Public discussion

    [sig-policy] prop-130-v002: Secretariat impact assessment

    3 Discussion messages · 3 Entities

    Source facts 1 ↗Source facts 2 ↗Source facts 3 ↗

  7. Public discussion

    Re: [sig-policy] prop-130-v003: Modification of transfer policies

    6 Discussion messages · 3 Entities

    Source facts 1 ↗Source facts 2 ↗Source facts 3 ↗Source facts 4 ↗Source facts 5 ↗Source facts 6 ↗

  8. Official decision

    abandoned

    abandoned

    Source facts ↗

Entities

Freshness: Stale · Last refresh: · The latest refresh failed. The last successful result is shown.
  1. Jordi Palet Martinez
    Discussion messages8
    First activitySep 9, 2019
    Last activityMar 3, 2021
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyInsufficient evidence to assess consistency
    Other policies18
    Freshness: Stale · Last refresh: · The latest refresh failed. The last successful result is shown.

    Identity verified: Oct 11, 2026

    The IPv6 Company · Historical
    Name: Jordi Palet Martínez Email: [email protected] Organization: The IPv6 Company
    politicas.lacnic.net
    Discussion messages
    8
    First activity
    Sep 9, 2019
    Last activity
    Mar 3, 2021
    First explicit stance
    Unknown
    Latest explicit stance
    Unknown
    Stance changes
    0
    Viewpoint consistency
    Insufficient evidence to assess consistency
    Other policies
    18

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

    Viewpoint consistency: Insufficient evidence to assess consistency

    Jordi Palet's two January 2022 interventions seek a sound basis for decisions: a broader Policy SIG discussion where views remain divided, and Secretariat input on unresolved questions about historical resources. These are compatible procedural positions. One intervention per proposal does not establish a history of substantive support, opposition or reversal.

    Experimental Allocations – no reservation for IPv4

    Assessment: Insufficient evidence to assess consistency · Palet calls for the disputed experimental-allocation issue to reach the broader Policy SIG. He does not claim that consensus already exists or state a final vote on the allocation rule. This single procedural intervention cannot establish a change of position.

    Conditions: The call to determine consensus is distinct from evidence that consensus was achieved.

    it is neccesary to have the discussion in a broader community, the Policy SIG.

    Recovery of unused historical resources

    Assessment: Insufficient evidence to assess consistency · On recovery of historical resources, Palet requests Secretariat input, particularly on legal questions. Asking for that information leaves the substantive recovery decision open; it is not an endorsement of a particular legal interpretation.

    Conditions: No later answer or explicit final policy preference is supplied.

    especially the legal aspects. May be in this case, is not just the chairs but the secretariat who should provide some inputs.

    Experimental Allocations – no reservation for IPv4 · Recovery of unused historical resources

    Assessment: Consistent · Seeking wider community deliberation on one proposal and specialist Secretariat input on another are compatible ways to resolve different decision gaps. Neither message assigns the Secretariat authority to replace community consensus. The comparison supports procedural compatibility, not a shared substantive vote on the two policies.

    Conditions: The proposals raise different questions and each is represented by one message.

    It is the only way to determine consensus in a PDP valid way.

    the secretariat who should provide some inputs.

    1. Sep 9, 2019 · Unknown

      Re: [sig-policy] Policy Proposal: prop-130-v001: Modification of transfer policies

      Validated evidence is unavailable.

      Source facts ↗
    2. Sep 9, 2019 · Unknown

      Re: [sig-policy] Policy Proposal: prop-130-v001: Modification of transfer policies

      Validated evidence is unavailable.

      Source facts ↗
    3. Feb 16, 2020 · Unknown

      Re: [sig-policy] prop-130-v002: Secretariat impact assessment

      Validated evidence is unavailable.

      Source facts ↗
    4. Feb 18, 2020 · Unknown

      Re: [sig-policy] prop-130-v002: Secretariat impact assessment

      Validated evidence is unavailable.

      Source facts ↗
    5. Feb 17, 2021 · Unknown

      Re: [sig-policy] prop-130-v003: Modification of transfer policies

      Validated evidence is unavailable.

      Source facts ↗
    6. Mar 1, 2021 · Unknown

      Re: [sig-policy] prop-130-v003: Modification of transfer policies

      Validated evidence is unavailable.

      Source facts ↗
    7. Mar 2, 2021 · Unknown

      Re: [sig-policy] Policy Discussion in bdNOG for APNIC51

      Validated evidence is unavailable.

      Source facts ↗
    8. Mar 3, 2021 · Unknown

      Re: [sig-policy] prop-130-v003: Modification of transfer policies

      Validated evidence is unavailable.

      Source facts ↗
    Per-policy stance timelines:prop-121 · Unknown · No explicit position statedprop-122 · Unknown · No explicit position statedprop-124 · Unknown · No explicit position statedprop-125 · Unknown · No explicit position statedprop-126 · Unknown · No explicit position statedprop-128 · Unknown · No explicit position statedprop-130 · Unknown · No explicit position statedprop-131 · Unknown · No explicit position statedprop-133 · Unknown · No explicit position statedprop-134 · Unknown · No explicit position statedprop-135 · Unknown · No explicit position statedprop-139 · Unknown · No explicit position statedprop-140 · Unknown · No explicit position statedprop-143 · Unknown · No explicit position statedprop-148 · Unknown · No explicit position statedprop-154 · Unknown · No explicit position statedprop-157 · Unknown · No explicit position statedExperimental Allocations – no reservation for IPv4 · Unknown · Insufficient evidence to assess consistencyRecovery of unused historical resources · Unknown · Insufficient evidence to assess consistency

    Total policy messages: 141

  2. Srinivas Chendi · Identity unresolved
    Discussion messages2
    First activityFeb 14, 2020
    Last activityFeb 17, 2021
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies23
  3. chku · Identity unresolved
    Discussion messages2
    First activityAug 10, 2020
    Last activityFeb 2, 2021
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies4
  4. Unknown · Identity unresolved
    Discussion messages2
    First activityMar 1, 2021
    Last activityMar 2, 2021
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies3
  5. Bertrand Cherrier · Identity unresolved
    Discussion messages1
    First activityFeb 24, 2020
    Last activityFeb 24, 2020
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies18
  6. Tsurumaki, Satoru · Identity unresolved
    Discussion messages1
    First activityFeb 17, 2020
    Last activityFeb 17, 2020
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies4
  7. Satoru Tsurumaki · Identity unresolved
    Discussion messages1
    First activitySep 2, 2019
    Last activitySep 2, 2019
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies14
  8. Hiroki Kawabata · Identity unresolved
    Discussion messages1
    First activitySep 6, 2019
    Last activitySep 6, 2019
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies8
  9. bdNOG Secretariat · Identity unresolved
    Discussion messages1
    First activityMar 2, 2021
    Last activityMar 2, 2021
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies2

Sources and coverage

Official policy sources

Public discussion archives

  • apnic-sig-policy
    Earliest captured
    Jun 1, 2001
    Latest captured
    Sep 21, 2026
    Last refresh
    Aug 13, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    405
    Known gaps
    36
  • apnic-sig-policy
    Earliest captured
    Jun 1, 2001
    Latest captured
    Sep 21, 2026
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,528
    Known gaps
    0
  • www.apnic.net
  • conference.apnic.net
  • apnic-academy-talk-apnic.net
    Earliest captured
    Jan 12, 2023
    Latest captured
    Jan 19, 2026
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    2,056
    Known gaps
    0
  • apnic-afg-community-apnic.foundation
    Earliest captured
    Sep 27, 2023
    Latest captured
    Jun 24, 2026
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    2,010
    Known gaps
    0
  • apnic-apac-ict-women-apnic.net
    Earliest captured
    Oct 22, 2024
    Latest captured
    Aug 11, 2026
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    2,496
    Known gaps
    0
  • apnic-apix-chair-apnic.net
    Earliest captured
    Unknown
    Latest captured
    Unknown
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    0
    Known gaps
    0
  • apnic-apix-secretary-apnic.net
    Earliest captured
    Unknown
    Latest captured
    Unknown
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    0
    Known gaps
    0
  • apnic-apix-treasurer-apnic.net
    Earliest captured
    Unknown
    Latest captured
    Unknown
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    0
    Known gaps
    0
  • apnic-apnic-alumni-apnic.net
    Earliest captured
    Feb 14, 2024
    Latest captured
    Jul 14, 2026
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    2,491
    Known gaps
    0
  • apnic-apnic-announce-apnic.net
    Earliest captured
    Jun 11, 2025
    Latest captured
    Sep 3, 2026
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    2,844
    Known gaps
    0
  • apnic-apnic-foundation-discuss-apnic.foundation
    Earliest captured
    Sep 12, 2022
    Latest captured
    Mar 11, 2026
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    2,138
    Known gaps
    0
  • apnic-apnic-services-apnic.net
    Earliest captured
    Aug 31, 2020
    Latest captured
    Aug 4, 2026
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    2,569
    Known gaps
    0
  • apnic-apnic-talk-lists.apnic.net
    Earliest captured
    Apr 15, 2004
    Latest captured
    Sep 8, 2026
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    2,683
    Known gaps
    0
  • apnic-apnic-transfers-apnic.net
    Earliest captured
    Sep 21, 2012
    Latest captured
    Feb 22, 2025
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    2,537
    Known gaps
    0
  • apnic-bgp-stats-lists.apnic.net
    Earliest captured
    Aug 30, 2026
    Latest captured
    Sep 15, 2026
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,685
    Known gaps
    0
  • apnic-community-elections-apnic.net
    Earliest captured
    Nov 12, 2021
    Latest captured
    Nov 22, 2021
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    4
    Known gaps
    0
  • apnic-community-events-apnic.net
    Earliest captured
    May 9, 2025
    Latest captured
    Aug 19, 2025
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    2,696
    Known gaps
    0
  • apnic-diversity-in-leadership-apnic.net
    Earliest captured
    Jun 9, 2026
    Latest captured
    Jul 8, 2026
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    123
    Known gaps
    0
  • apnic-ianaxfer-apnic.net
    Earliest captured
    Mar 27, 2014
    Latest captured
    Jul 11, 2019
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    2,563
    Known gaps
    0
  • apnic-icp-2review-apnic.net
    Earliest captured
    Apr 24, 2025
    Latest captured
    Sep 1, 2026
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    2,019
    Known gaps
    0
  • apnic-measurement-apnic.net
    Earliest captured
    May 31, 2023
    Latest captured
    Mar 8, 2026
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    2,554
    Known gaps
    0
  • apnic-mvnog-apnic.net
    Earliest captured
    Feb 5, 2026
    Latest captured
    Sep 28, 2026
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    138
    Known gaps
    0
  • apnic-orbit-discuss-apnic.net
    Earliest captured
    Sep 13, 2022
    Latest captured
    Nov 13, 2022
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    649
    Known gaps
    0
  • apnic-pngnog-apnic.net
    Earliest captured
    Dec 26, 2019
    Latest captured
    Oct 28, 2024
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    2,372
    Known gaps
    0
  • apnic-security-discuss-apnic.net
    Earliest captured
    Mar 27, 2024
    Latest captured
    Aug 16, 2024
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    2,373
    Known gaps
    0
  • apnic-sig-cooperation-apnic.net
    Earliest captured
    Jan 15, 2015
    Latest captured
    Aug 25, 2026
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    2,572
    Known gaps
    0
  • apnic-sig-guidelines-review-apnic.net
    Earliest captured
    Jun 3, 2026
    Latest captured
    Sep 2, 2026
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    1,323
    Known gaps
    0
  • apnic-sig-nir-lists.apnic.net
    Earliest captured
    May 13, 2004
    Latest captured
    Sep 4, 2026
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    2,672
    Known gaps
    0
  • apnic-sig-routingsecurity-apnic.net
    Earliest captured
    Apr 3, 2020
    Latest captured
    Aug 25, 2026
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    2,429
    Known gaps
    0
  • apnic-user-feedback-group-apnic.net
    Earliest captured
    Sep 12, 2022
    Latest captured
    Jul 14, 2026
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    2,138
    Known gaps
    0
  • apnic-wg-pdr-apnic.net
    Earliest captured
    Mar 29, 2021
    Latest captured
    Sep 21, 2022
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    2,128
    Known gaps
    0
  • apnic-youth4ig-lists.apnic.net
    Earliest captured
    Feb 19, 2020
    Latest captured
    Jul 28, 2023
    Last refresh
    Oct 12, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    2,475
    Known gaps
    0

Coverage

Partial
Earliest captured: Jun 1, 2001
Latest captured: Oct 12, 2026

Freshness

Freshness: Stale · Last refresh: · The latest refresh failed. The last successful result is shown.

Known gaps

  • www.apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
  • apnic-sig-policy: Source coverage is incomplete. · The source boundary has not yet been reached.
  • apnic-sig-policy: Source coverage is incomplete. · The source boundary has not yet been reached.
  • www.apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
  • conference.apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
  • apnic-academy-talk-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
  • apnic-afg-community-apnic.foundation: Source coverage is incomplete. · The source boundary has not yet been reached.
  • apnic-apac-ict-women-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
  • apnic-apix-chair-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
  • apnic-apix-secretary-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
  • apnic-apix-treasurer-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
  • apnic-apnic-alumni-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
  • apnic-apnic-announce-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
  • apnic-apnic-foundation-discuss-apnic.foundation: Source coverage is incomplete. · The source boundary has not yet been reached.
  • apnic-apnic-services-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
  • apnic-apnic-talk-lists.apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
  • apnic-apnic-transfers-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
  • apnic-bgp-stats-lists.apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
  • apnic-community-elections-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
  • apnic-community-events-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
  • apnic-diversity-in-leadership-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
  • apnic-ianaxfer-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
  • apnic-icp-2review-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
  • apnic-measurement-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
  • apnic-mvnog-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
  • apnic-orbit-discuss-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
  • apnic-pngnog-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
  • apnic-security-discuss-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
  • apnic-sig-cooperation-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
  • apnic-sig-guidelines-review-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
  • apnic-sig-nir-lists.apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
  • apnic-sig-routingsecurity-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
  • apnic-user-feedback-group-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
  • apnic-wg-pdr-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
  • apnic-youth4ig-lists.apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.