On Fri, 12 Dec 2025, John Curran via NANOG wrote:
Short version – ARIN failed here (as you noted in your post). We’ve
published a public incident report that lays out what happened, the
impact, and what we’re changing:
https://www.arin.net/announcements/20251212/
This is a pretty epic failure considering ARIN's purpose is the assignment
of unique Internet numbers (and the necessary record keeping to facilitate
that function).
I assume 23.128.0.0/10 records are maintained partially in the "off line
Excel file" because your primary system lacks necessary features to
differentiate free space / sparse allocations in 23.128.0.0/10 from
"regular" free space? I assume the sparse allocation strategy here is to
allow a member to come back for more 4.10 space and ideally just extend an
original /24 to a /23, perhaps getting the next /24 eventually, and
finally swap the adjacent /23 and /24 for the covering /22?
Things I'm curious about that are not mentioned in the incident report:
1) When the analyst looked in the e-black-book and selected 23.150.164.0
(23.150.164.0/22, I presume) to be used to satisfy the request they
were working on, did they fail to see that this /22 was already in use
for a sparse assignment and 23.150.164.0/24 was already assigned, or
when 23.150.164.0/24 was originally assigned to AS397031, was the
e-black-book not properly updated to reflect the sparse assignment of
23.150.164.0/22?
2) When assigning IP space, is it customary for the analyst to check
current/recent snapshots of the global BGP tables to see if the space
selected for assignment is currently or has recently been advertised?
It's not guaranteed that assigned space will be in the DFZ, but if it
is, that's a pretty good indicator that something is going wrong with
the current assignment of the space.
3) Did the block split automatically delete any/all child subnets of
23.150.164.0/22, or did the analyst manually delete 23.150.164.0/24
from whois (and that automatically deleted the ROA and rDNS
delegation)?
----------------------------------------------------------------------
Jon Lewis, MCP :) | I route
Blue Stream Fiber, Sr. Neteng | therefore you are
_________ http://www.lewis.org/~jlewis/pgp for PGP public key_________
_______________________________________________
NANOG mailing list
https://lists.nanog.org/archives/list/[email protected]/message/X3WPNTJZUNDJMAOOJ5F3JKI4UAT65C3L/
