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
A Locally Served DNS Root Has a Refresh Bill
Serving the root zone beside a recursive resolver removes many outward queries, but it does not remove network traffic. A new measurement highlighted by APNIC shows that the bill moves into the update loop—and that software behaviour can matter more than the name of the…
Story
A Failed RIPE Database Update Can Still Change Records
RIPE NCC's documentation describes an update message whose entities can finish differently. The useful response is therefore not just a verdict on the message: it is an account of the changes already made, those rejected and those the caller still cannot confirm.
Story
AFRINIC's IPv6 Monitor Shows What Its 54% Contains
A routing dashboard now distinguishes an advertised allocation prefix from routes to smaller pieces of it. Its South Africa data show why that distinction is useful—and why neither the combined total nor the narrower category is a service-quality score.
Story
RIPE's Flip Chart Experiment and the Work After the Introduction
A paper board helped researchers and network operators find one another. RIPE NCC's new account points to a useful next test: whether a promising introduction becomes a question both sides can afford to pursue, without silently committing either to data access or production…
Story
One Prefix, Two Countries in LACNIC’s Geofeed
A public location feed repeats 23 prefixes, four with conflicting country codes. The useful repair is narrower than deciding where the networks are: stop a loading rule from masquerading as geographic evidence.
Story
LACNIC’s Voice Primer and the Bandwidth Beyond the Codec
An 8 kbit/s voice encoder can send a 24 kbit/s stream before Ethernet, security and control traffic enter the calculation. LACNIC’s latest telephone explainer points to a distinction that matters when operators turn compression into a capacity budget.
Story
ARIN’s Reverse-DNS Controls Follow the Parent Block
A customer’s address range does not tell an operator where the reverse-DNS handoff belongs. ARIN’s direct-allocation rules put the editing boundary higher in the tree than a downstream inventory may suggest.
Story
What Comes After ARIN’s Empty Whois Replies
ARIN resolved a problem with some Whois queries in August. For anyone whose tools retained a suspect result, the next task is different: checking the local copy without turning a failed observation into a registration verdict.
Story
APNIC’s Automation Workshop Has a Second Job: Teaching Its Successors
The Mumbai course is meant to prepare engineers to teach and rebuild their own training labs. That makes it part of a practical handoff before network automation leaves APNIC’s instructor-led curriculum at the end of 2026.
Story
APNIC REx: When a Date Becomes a Matching Key
Three historical address records changed their dates without changing their ranges. The case shows why reconstructing a resource's past also requires understanding the past of the fields used to identify it.
Story
Inside AFRINIC’s June Reserve Total
AFRINIC’s June financial report puts a reserve balance and an interest estimate on the same page. Reading the distinction properly changes what its $6.6 million total can tell members about growth, cash and the year ahead.
Story
RIPEstat’s Empty IP Lookup and the Route Beside It
A user’s two differently worded requests produced different views of a route. A successful retest leaves a narrower question than an outage: what did an empty answer actually establish?
Story
The Refill Behind LACNIC’s Falling ASN Forecast
The Refill Behind LACNIC’s Falling ASN Forecast 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 intelligence…
Story
Inside AFRINIC’s Reverse-DNS Cleanup
The registry’s public data distinguish delegation records, domain entities and resource holders. They also distinguish an error inventory from removal events. Those differences explain why a falling count can reflect worthwhile maintenance without measuring the restoration of…
Story
ARIN Publishes IPv6 Requests Beside Delegations. The Cohorts Are Not Joined.
An IPv6 request can enter ARIN’s system, pass automatically or move into staff review, prompt a request for more information, receive approval, wait for fees and a signed agreement, and only then become an issuance. ARIN publishes useful numbers at the entrance and the exit of…
Story
APNIC Logged 57,088 Addresses as M&A Transfers. Its Daily File Still Shows 2007.
One APNIC file says that nine IPv4 prefixes changed hands on 1 September 2026. The next daily statistics file gives every resulting row the date 3 December 2007. This is not a contradiction or a stale update. It is what happens when an event clock and an origin clock share the…
Story
APNIC Called RPKI Mirroring Marginal. Its NNIX Pilot Tests a Different Benefit
In October 2025, APNIC assessed a repository mirror as a short-lived aid during a long outage and called the benefit very marginal. Seven months later, its agreement with NNIX proposed a Hangzhou mirror pilot around latency, validation speed and data availability. The…
Story
AFRINIC's Current RPKI CPS Says It Manages Asia-Pacific
The Certification Practice Statement linked from AFRINIC's current resource-certification page is version 3.0 from May 2020. In its CA-termination clause, the registry assigns itself the Asia-Pacific region. AFRINIC and IANA assign that region to APNIC and place AFRINIC in Africa…
Story
RIPE NCC Reports a 467-Day IPv4 Wait. The Queue Needs a Flow Ledger
RIPE NCC’s August member update says 757 LIRs were waiting for IPv4 space and the first LIR had been in line for 467 days. Its public chart records the queue’s size and its oldest wait, but those two stocks cannot show whether movement came from allocations, new requests…
Story
LACNIC Published a 98% Outreach Score. The Response Count Is Missing
LACNIC says more than 330 organizations attended its 2025 member gatherings and that 98% of the feedback it received fell in the highest satisfaction levels. Both statements may be accurate. The public post does not disclose the number of responses, so the percentage cannot be…