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
One Recusal and One No Would Block AFRINIC GovCom Advice
AFRINIC’s five voting members do not approve formal advice through an ordinary supermajority. If one member recuses, a 3–1 vote clears the approval floor and still fails the separate dissent test.
Story
LACNIC Budgets a $390,000 Operating Gap. Financial Results Close All but $87,000 on Paper
A budget can show a small loss while concealing three different movements: the recurring cost of running the registry, the accounting result of a portfolio and the cash that actually entered or left the institution. LACNIC’s 2025 accounts show why its 2026 plan needs those…
Story
ARIN Put Three Candidate Pools on One Slate. Only Two Go to Members
ARIN's 2026 slate is a single page with three sets of candidates and two different decision makers. General Members choose the Board and Advisory Council. Trustees choose this year's NRO Number Council representative.
Story
AFRINIC’s Draft Says Slides Must Match the Proposal. A Mismatch Creates a Version That Cannot Count
A policy meeting can be perfectly public and still leave its decisive entity obscure. AFRINIC’s proposed working-group rules require presentation slides to match the submitted proposal; if they differ, an updated version must go to the mailing list even when its changes will not…
Story
APNIC's Honeynet Logged 1.27 Million Events. That Is Not 1.27 Million Attacks
An APNIC 62 presentation turns one deliberately exposed server into a useful security instrument. Its headline, however, moves between attacks, attack events and events—three labels that cannot safely share one number.
Story
RIPE Atlas Counts Probe Farming by a BGP Prefix. The Cohort Can Move Without the Probe
A probe can stay on the same shelf, under the same account and on the same access line, yet acquire different neighbours for an admission rule. RIPE Atlas limits software probes partly by the IP prefix “as seen in BGP”. That is a defensible way to protect a shared measurement…
Story
LACNIC’s ASPA Explainer Cites a Moving Percentage Without a Snapshot
LACNIC’s ASPA Explainer Cites a Moving Percentage Without a Snapshot 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.…
Story
AFRINIC's IPv4 Summary Rose by Two. One Reserved Block Split into Three
AFRINIC's daily file gained two IPv4 records on 9 September. The tempting story is two new allocations. The rows tell a more useful one: a conserved block changed shape.
Story
ARIN’s Board Slate Has One Candidate Beyond Three Seats
Three seats. Four candidates. ARIN’s 2026 Board slate satisfies the rule that there must be more names than vacancies, but it does so at the narrowest possible margin. That fourth name is not decorative competition. It is the point at which an elected choice remains a contest and…
Story
RIPE Atlas Can Show the Edge. It Cannot Show Who Chose It
A path measurement can show where one request landed. It cannot, on its own, reveal the platform rule that sent it there, the traffic that was eligible, the share served locally or what happens when the appliance disappears.
Story
APNIC’s Electoral-Committee Recusal Safeguard Lives in a Blog Comment
APNIC has a sensible answer to an awkward governance question: Executive Council members who may seek re-election do not help choose the committee that polices the election. The trouble is not the answer. It is where the answer lives—and how little of the annual record shows the…
Story
LACNIC 46's Attendee List Has Consent. It Still Needs a Retention Clock
LACNIC tells registrants that their names will appear on the event website. That clarity settles the easy argument; the harder one is how a public list shows the scope, duration and outcome of the permission it already has.
Story
AFRINIC Calls Its NS2 Dashboard ‘Real-time.’ All Twelve Linked Measurements Are Stopped One-Offs
A page can refresh on demand without measuring the present. AFRINIC’s public NS2 dashboard illustrates the distinction: it advertises “Real-time Anycast Node Monitoring”, yet every RIPE Atlas measurement wired into the interface is a stopped one-off. The result is useful evidence…
Story
A Backup DNS Plan Is Not a Second Resolver
A 9 September APNIC Blog account turns a household outage into a precise infrastructure lesson: resilience begins only when an alternative service is running, reaches the clients that depend on it, survives a controlled failure and can be rolled back.
Story
RIPE NCC’s K-root Refresh Needs Three Acceptance Records, Not One Batch Status
Amsterdam can be refreshed while the three-site programme remains in progress. That is not a contradiction; it is a warning about the unit of evidence. RIPE NCC has named three K-root core sites whose seven-year-old routers and servers were due for replacement. The useful public…
Story
AFRINIC Says It Belongs to All of Us. Its SGMM Notice Draws a Smaller Corporate Boundary
AFRINIC’s anniversary message speaks to members, stakeholders and the wider Internet community in one generous voice. Six days later, the meeting named in that message operated through a narrower set of corporate roles. Both can be legitimate. The governance test is whether a…
Story
LACNIC’s Autonomous-Network Ladder Needs a Scenario Ledger, Not a Company Badge
Two operators can both call themselves level three while describing entirely different machines. One may automate fault diagnosis in a radio network; the other may automate service fulfilment but leave every consequential configuration change to a person. The number sounds…
Story
RIPE NCC Says Its 2027 Invoicing Changes Are Complete. The Bill Still Waits for 31 December
RIPE NCC has finished the applications work for its 2027 charging scheme before the data that will determine the first bills exists. That is sensible project management. It is also why “complete” needs a second, more operational meaning in January: can each charge be reproduced…
Story
ARIN’s RPKI Constraint Is Only as Current as the Package That Ships It
A trust boundary can be carefully designed, correctly signed and still arrive too late. ARIN’s planned RPKI constraint work makes that mundane distribution problem part of routing-security policy.
Story
ARIN’s Open 1,024-Character Ticket Is Really About a Private Routing Grammar
An open ARIN suggestion asks for more room in an IRR remarks field. Its motivating case is not really about storage. Lumen documents a parser that can turn a marked remark into the effective membership of an AS-SET, overriding the field that ordinary RPSL readers expect to carry…