Time Horizon
Near
Within the Time Horizon facet, Near 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.

Story
India Opened Lower 6 GHz. APNIC 62 Still Needed a Client Receipt
The band could be lawful, the access point could contain the right radio, and a device could still never see the network. APNIC 62 turned that gap between authorization and usable capacity into an operational record—but not yet a reproducible one.

Story
AFRINIC’s Merge Question Could Bind Two Section 3 Decisions Together
The co-chairs asked whether a meeting-calendar rule and a broad rewrite of the policy working group should become one draft. Before that happens, the community needs to know what would be combined—and what it would still be allowed to decide separately.

Story
Rapport Counts Outcomes Only After a Requested Test Path Exists
LACNIC’s revised Rapport runner can expand several category and test selectors into a matrix. Yet a requested cell with no matching directory leaves no row in the result: it returns before a test identity is printed or any outcome counter moves.

Story
APNIC’s Two-Nameserver Run Had Fewer Repeats. The Difference Still Needs a Reproduction Receipt
APNIC measured fewer authoritative DNS queries in a later run using two nameservers than in an earlier run using one. The observation is real in the published aggregates; the cause is not settled. A reproducible decision needs the two treatments to share a clock, cohort and…

Story
AFRINIC’s Holiday Notice Appeared One Day Before Closure. That Is Not a 72-Hour Verdict
AFRINIC’s public record shows a 14 September notice for a 15 September office closure. Its service commitment speaks of seventy-two hours, but on a different channel: announcement mail. The right audit separates the website, the mail record, human response time and always-on…

Story
RIPE’s RDAP Marks a Mixed AS Block Reserved at Either Boundary
RIPE’s RDAP Marks a Mixed AS Block Reserved at Either Boundary 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 follow. The…

Story
LACNIC’s Election Upload Test Reads Bytes, Not Excel or PDF
A new compatibility test in LACNIC’s open election system carries two reassuring filenames across a disk boundary. The bytes arrive intact. That is valuable evidence—but it is evidence about transport, not about whether a workbook or a result letter is a valid document, whether…

Story
LACNIC’s Hackathon Repo Sends Agents to an Unpinned Sibling Harness
A September change makes the repository’s agent rules more explicit, yet the rulebook itself still lives behind a 13-byte relative link. The useful control is not another instruction: it is a receipt identifying the external instructions that governed each mutating run.

Story
RIPEstat Explains 12859:4000 With 12859:4xxx. The Wildcard Is Evidence
RIPEstat’s Looking Glass can place a useful sentence beside an opaque BGP community. In one frozen response, however, the observed value `12859:4000` received the description “customer routes” from the broader expression `12859:4xxx`. The explanation may be right. The missing…

Story
ARIN Approved a Revised Strategic Plan. Its Public PDF Still Says December 2025.
ARIN’s draft minutes record an August 2026 vote on a “new” or “revised” strategic plan. The plan linked from ARIN’s public planning page, however, identifies itself as the version adopted in December 2025. That mismatch does not prove the strategy changed. It does show that the…

Story
AFRINIC’s Uganda Anycast Node Is Two Services, Not One
AFRINIC’s Uganda Anycast Node Is Two Services, Not One 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 follow. The Story…

Story
APNIC's RDAP Use Is 20%. That Is Not an Adoption Rate.
APNIC's new survey puts RDAP at 20% among respondents asked about core registry services. The number is useful evidence about reported use; it is not a census of deployed systems, a traffic share or a verdict on whether RDAP can replace WHOIS.

Story
Rapport’s Forbidden-AKI Test Starts at Barry, Not at the Validator
A conformance test cannot prove that a validator rejected a forbidden certificate field until it proves that the field reached the certificate. A September correction to one LACNIC Rapport fixture makes that dependency unusually visible. The change replaces a scalar value that…

Story
AFRINIC's RRDP Lists 32 Deltas. That Is Not a Recovery Window.
AFRINIC's live RPKI notification showed a neat chain of 32 incremental updates. The number is useful, but it does not tell a network operator how long a validator may be offline before recovery changes from a small replay to a full snapshot.

Story
RIPE NCC Has 110 Sanctions Investigations. Its Table Has No Clock.
RIPE NCC’s latest sanctions report makes the size of its screening work visible: the cumulative register reached 2,172 alerts, with 110 still under investigation on 2 July 2026. What the table cannot show is equally consequential. A reader can see where cases sit, but not how…

Story
APNIC Says prop-170 Reached Consensus. APNIC-127 Still Does Not Say “Nibble”
On 14 September, two official APNIC pages described prop-170 as having reached consensus at APNIC 62. A third official page still labelled it “For Discussion at APNIC 62 OPM”. The operative policy supplied a more important answer: APNIC-127 still contained the old IPv6 allocation…

Story
The RIR Draft Counts 1,000 Members, Not 1,000 Votes
The proposed compliance-review threshold uses legal entities, not voting weight. LACNIC’s own election figures show why an auditable denominator must come first.

Story
ARIN’s Jacksonville Workshop Has Two Start Times
Three days before the event, ARIN’s dated notice says 9:30 while its live outreach page says 10:00. One labelled schedule can make both times useful.

Story
RIPE WHOIS Gives Invalid API Keys an Audit Identity
A failed credential usually looks like absence: no user, no permission, no successful update. In the current RIPE WHOIS source, however, the failure path can carry one durable-looking fact into its audit representation—the API key ID supplied as the Basic-auth username—even when…

Story
TWNIC’s Table Leaves 68 Completions Beyond Its 30-Day Gate
A 328-member validation ledger closes arithmetically, but its cumulative milestones imply 68 completions after the access-restriction threshold without showing which controls were used.
