Time Horizon
Immediate 0 30d
Within the Time Horizon facet, Immediate 0 30d time-horizon intelligence organises articles by the period over which a signal is expected to matter. The page helps readers distinguish immediate operational changes from longer-cycle governance, investment, standards, and infrastructure shifts that may unfold across quarters or years. It connects timing assumptions with public evidence, related actors, market context, customer exposure, policy pressure, and infrastructure planning so readers can judge whether a development is urgent, strategic, or still waiting on confirming evidence. The page also explains how time horizon changes the meaning of a signal, which organisations may be exposed, and which infrastructure decisions require short-term action or long-cycle monitoring.
CASE FILE
The Route Was Accepted So Packets Would Die: BGP BLACKHOLE and the Authority to Destroy Reachability
A blackhole announcement is a rare routing message whose success is measured by non-delivery. That inversion can save a network during a DDoS attack, but only if the right to sacrifice one destination is narrower, more observable and more reversible than the emergency that…
Story
LACNIC's ASO AC Result Became Official Without a Closure Receipt
At 18:00 UTC on 20 August, one public election table crossed a consequential boundary. The names and 144 votes did not change. The page's status did: the provisional result became the official result after two audit windows. What did not appear beside that new status was the…
Story
ARIN's New “Sole Use” Definition Has No Observation Window
Imagine one address prefix serving three anycast sites: one inside ARIN's service region and two outside it. The inside site is withdrawn for maintenance, then restored an hour later. The holder, service design and prefix have not changed. Under the wording of a new ARIN…
Story
APNIC's SIG Review Lists Twelve Changes Before It Has Decision Text
Twelve headings can make a governance review look nearly finished. They can also hide the one thing a consensus call must actually decide: the precise rules that will replace the current ones. APNIC's July SIG Guidelines draft has diagnosed a connected set of problems; its next…
Story
AFRINIC's Survey Can Count Replies. It Cannot Count Representation Yet
A response box can fill quickly and still leave the room outside it invisible. AFRINIC's new member and stakeholder survey may produce useful service evidence, but its eventual weight will depend on a record the launch has not yet supplied: who could answer, who was reached, what…
Latin America and Caribbean Cloud Services Trends
F5 leaves Mexico edge unconfirmed after scheduled go-live
More than 25 hours after F5's stated activation time for its `qro1-mx` Distributed Cloud Regional Edge, the public notice still says `Monitoring` and offers no completion update. The same change also depends on customers allowing a new `159.60.179.0/24` source range into their…
Story
RIPE's IPv6 PI Draft Has a Trigger but No Transition Receipt
Nine `/48` assignments can remain a valid deployed state while nothing changes. The next request for address space is different: it can activate a next-nibble decision, a contiguity test, a new prefix and a six-month return clock. Proposal 2024-01 names that trigger but does not…
Story
LACNIC's Anti-Fake-IXP Log Has No Event Column
LACNIC has made a scarce IPv4 reserve unusually visible. Its public file can show who holds an issued interval and how much of the pool remains reserved. What it cannot say in one row is what happened. A log commissioned to cover assignments, recoveries and returns still…
Story
ARIN's ISP/LIR Claim Needs a Predicate Ledger
One card asks what a company sells. Another asks whether it receives and redistributes Internet number resources. Draft Policy ARIN-2025-1 wants every holder of the first card to fit inside the second. Its proposed definitions do not yet make that containment rule true.
Story
APNIC Would Remove `/23`; Three Prefix Sizes Still Need Names
One bit separates a `/23` from a `/24`. It also separates 512 IPv4 addresses from 256. APNIC's current initial-LIR test can ask for immediate need for the smaller block and a one-year plan for the larger one. Prop-169 would repair that mismatch. Its replacement noun now needs an…
Story
AFRINIC Draft 2 Can Waive 90%; “Sufficiently Documented” Has No Fields
AFRINIC recorded the second-data-centre trap in 2018. An End User wanted another `/24` for redundancy, had used less than 90% of its existing space and was therefore ineligible. Draft 2 finally names that class of problem, then leaves the proof inside two words: sufficiently…
Story
RIPE's First-ASN Proposal Removes One Test but Leaves Three Records Open
RIPE's First-ASN Proposal Removes One Test but Leaves Three Records Open intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that may…
Story
Three National Registers Expose the Gap Behind LACNIC's No-Consensus Result
Brazil calls an individual entrepreneur a natural person doing business in their own name. Argentina opens its simplified tax register to `personas humanas`. Uruguay describes a one-person monotributo business as a natural person registering before economic activity begins.…
IETF
Bruno Decraene and the Discipline of Draining Before Shutdown
A planned BGP maintenance window is not a surprise failure. Yet an operator who closes the session first can make it behave like one: the old routes vanish, the network begins searching, and packets arrive while the replacement path is still becoming usable. The more disciplined…
Story
ARIN's IPv6 Waiver Expiry Notice Leaves the Transition Count Unstated
At midnight on 1 January, a `/36` will not gain a single address. Its holder may nevertheless cross a billing boundary. ARIN has announced the end of a five-year IPv6 incentive and promised direct contact; the missing public number is how many organisations must make that…
Story
APNIC's Impact Assessments Leave the Both-Pass Outcome Undefined
The word `nibble` will appear twice on APNIC 62's policy agenda. One proposal would move the minimum IPv6 allocation from `/32` to `/40`. The other would leave `/32` untouched and align a larger, already-validated request. A shared hexadecimal convenience hides two different…
Story
AFRINIC's First Article 24 Text Now Needs Its Own Review
The deadline passed at 23:59 UTC. In the 53-page constitutional draft still linked the next day, Article 24 had a heading, a number and a promise to add the law and dispute route later—but no clause for entities to review.
ICANN
ICANN’s Alternative-Name Test Stops at Technical Feasibility
ICANN has opened public comment on a model for linking a gTLD to the same string in alternative naming systems. The initial report says the arrangement can be technically safe if one controller and one coherent source of truth govern every copy of the name. That is a demanding…
Story
One Document Store Put Five RIPE NCC Workflows on Hold
A resource transfer can wait because a policy question is unresolved, because evidence is incomplete, or because the filing cabinet is being upgraded. On 22 August, RIPE NCC members encountered the third case. The distinction matters: a planned administrative pause is not a…
Story
LACNIC's Legacy Deadline Is Running Ahead of Its Policy
Prior BTW reporting describes legacy IPv4 holders answering an administrative request while the community rule that would govern the same evidence is still being debated. That sequence does not make the outreach illegitimate. It makes the label on every decision unusually…