ARIN closes directory-services consultation: what BYOIP teams should check

ARIN announced on 15 September that its consultation on the future of its directory services had closed. This page is that consultation milestone. ARIN published its decision on 21 October; see our roadmap follow-up for the conditions it set. The closure announcement itself did not establish a retirement schedule.

What changed

The consultation ran from 14 August to 14 September. ARIN said it would communicate next steps at ARIN 58 and through its website. At the close of the feedback period, implementation decisions were still to follow. The 21 October decision is covered in the update above.

The August proposal outlined consolidation around the Registration Data Access Protocol, or RDAP. Its proposed earliest retirement dates were:

Service	Proposed timing in the consultation
Whois-RWS	On or after 1 July 2027
RWhois	No sooner than 1 January 2028, dependent on migration-tool availability
Whois on port 43	On or after 1 January 2029

These remain proposal dates in the sources reviewed. They should not be entered into migration plans as confirmed shutdown deadlines.

Update - 6 October 2026

The ARIN 58 agenda now provides a specific checkpoint: an ARIN Directory Services Roadmap session is scheduled for Friday, 23 October, at 10:05 a.m. as listed on the meeting agenda. Check the agenda for any subsequent scheduling changes.

The session followed ARIN's commitment to report next steps after the consultation. ARIN published the decision on 21 October. The dates in the table above are the dates proposed during the consultation. They are historical context, not confirmed shutdown deadlines.

Why it matters for BYOIP

Registry information is part of the operational context for bringing address space to a provider. For example, Azure's BYOIP documentation describes validation of the address range's ownership and its association with the customer's subscription. Teams maintaining their own onboarding checks should understand which registry interfaces those checks use.

ARIN documents RDAP as a way to retrieve registration data in structured JSON over HTTP/HTTPS. Moving a script that parses Whois text to RDAP therefore calls for a review of its data handling, rather than simply replacing an endpoint.

For operators, the practical implication is a dependency audit. A registry-service transition could affect internal verification tools even when the cloud deployment itself requires no immediate change. The notice alone is not a reason to alter a live route announcement or an existing cloud configuration.

What to check now

• Inventory scripts, IPAM integrations and supplier workflows that query ARIN. Identify the specific protocol each uses.
• Test RDAP against the address records your workflow actually needs. Compare required fields, referrals, missing-data handling and failure behavior before changing production automation.
• Ask maintainers of third-party integrations about their RDAP support and migration plans.
• Keep the proposed dates labeled as historical. Use the 21 October decision, covered in the roadmap follow-up, before setting an internal retirement date.
• Review the roadmap session and any accompanying written announcement before converting the proposed retirement dates into migration deadlines.

For decision makers, this is a sensible maintenance item to assign to the owner of registry integrations. The evidence supports preparation; it does not establish an emergency migration or a new BYOIP eligibility requirement.

Further reading

See our guide to registered holders, address rights and BYOIP and the Azure BYOIP profile for related context. The linked primary documentation should guide implementation-specific checks.