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

History
The Pointer That Was Never Out of Band: How TCP Urgent Split from Its Own Stream
TCP offered applications a way to interrupt ordinary processing without creating another connection. The wire carried one ordered stream and a pointer into it; decades of software turned that boundary into a mythical side channel, then made the myth too widespread simply to…
CASE FILE
The Request That Vanished but Kept Working: What Rapid Reset Revealed About Cancellation
HTTP/2 let a client withdraw one request without closing the connection; Rapid Reset exposed the moment when that valid cancellation stopped being a courtesy and became an unlimited claim on somebody else’s queues.
CASE FILE
The Patch That Could Not Retire a Key: Debian's OpenSSL Entropy Failure and the Afterlife of Weak Credentials
The repaired library stopped minting predictable keys. It did not find the old ones, remove them from remote authorization files, revoke their certificates or persuade a single relying party to refuse them.

History
The Message the Internet Learned to Ignore: Why ICMP Source Quench Lost Its Authority
The early Internet allowed an overloaded gateway to send a separate command telling a distant source to slow down. Three decades of operational evidence reversed that bargain: congestion still required feedback, but a bare ICMP order no longer deserved the power to change a…
CASE FILE
The Signature That Demanded Every Key: What KeyTrap Revealed About the Cost of Trust
KeyTrap turned a valid-looking DNSSEC workload into a claim on somebody else’s processor, exposing the point at which faithful verification must yield to a locally governed budget.
CASE FILE
The Root That Wasn't Sold: What Symantec's Exit Revealed About Transferable Trust
Symantec could sell its certificate-authority business, but it could not sell a command to keep trusting the old roots. That decision remained inside independently operated clients.

Global Regional ISP Trends
The Five Percent That Prices the Network
A 95th-percentile bandwidth bill looks like a statistic. In practice it is a contract: a rule for deciding which traffic peaks the buyer absorbs, which the provider ignores, how much capacity remains physically available, and whether the buyer can reproduce the number on the…
CASE FILE
The Route That Borrowed a Name: What the MyEtherWallet Hijack Revealed About Layered Authority
A route accepted elsewhere let false DNS answers arrive locally, but the 2018 MyEtherWallet attack still had to cross a chain of independent technical vetoes.

ICANN
ICANN’s CIP Is Underway. Its Accountability Test Comes Later
ICANN’s first annual progress table for its Continuous Improvement Program shows six of eight community structures at work and one already implementing improvements. That is useful evidence of mobilisation. It is not yet evidence that any structure has become more effective or…
Story
The Signed Outage: What Orange España Revealed About RPKI Write Authority
Orange España showed how a hostile but valid ROA can pass through validators and local policy, turning account access into staggered route loss.

North America National Telecom Trends
Cox's 33.6m Charter Units Were Valued at $11.9bn at Signing and $5bn at Close
Charter completed its acquisition of Cox with approximately the same 33.6 million exchangeable common units promised in 2025. What changed was their implied value: Charter called them US$11.9 billion at signing and approximately US$5 billion at closing, making the seller's…

History
The Sum That Had Two Zeros: How the Internet Checksum Bounded Error, Not Trust
The Internet checksum made damaged packets easier to reject by making a deliberately small claim. Its strangest corner case—two representations of zero—shows why even cheap evidence must preserve an exact boundary.

History
The Report the Sender Could Not Trust: Why TCP SACK Remained Advice
A TCP sender may keep a byte range in memory even after the receiver has explicitly reported it. That apparent distrust is the safeguard at the centre of selective acknowledgment: a precise observation can guide recovery without becoming a final receipt or a command.

Asia-Pacific Cloud Services Trends
Singapore Has Assigned 200MW of Data-Centre Capacity, Not 200MW of Live Compute
Singapore has provisionally divided 200MW of new data-centre capacity among Digital Realty, Equinix, Keppel Data Centres and ST Telemedia Global Data Centres. The award is a valuable entry in a constrained market, but land, low-carbon energy, construction, customers and…

Global Cloud Services Trends
Cloud Portability Has a Postcode
Cloud computing was sold as locationless infrastructure, but the economics of leaving it are becoming conspicuously geographic. Within the same hyperscaler, the rights and price attached to moving data can now turn on account country, billing address, source region, network path…

History
The Acknowledgment That Learned to Point: How TCP SACK Made Loss Visible
TCP's original acknowledgment could certify an unbroken prefix of a byte stream, but it could not describe the islands waiting beyond the first gap. Selective acknowledgment added a small map of those islands while leaving the sender—not the receiver—in charge of repair.

History
The Router That Pointed Sideways: How ICMP Redirect Stayed Local
ICMP Redirect let a gateway reveal a better local next hop without becoming a routing authority. Its power ended at the host that had just used it.

History
The Number That Became Newer After Zero: How DNS Ordered Versions Without a Clock
At the edge of a 32-bit counter, DNS asks operators to accept an apparent impossibility: zero may be newer than 4,294,967,295. That rule let independent name servers agree on version order without sharing a clock, but only inside a deliberately bounded window.

History
The Zone That Knocked: How DNS NOTIFY and IXFR Cut Staleness
DNS once made every secondary wait before learning its authority was stale. In 1996, NOTIFY delivered the knock and IXFR carried only the edit.

Latin America and Caribbean National Telecom Trends
Viettel's $560m Dominican Plan Has Spectrum, Not a Network
Viettel Global has paired a US$560 million overseas-investment authorisation with 240MHz of Dominican spectrum. The two approvals make a serious market entry possible, but a 90-day legal closing, a financed build and a customer-ready operating system still stand between the award…
