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.
Global National Telecom 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…
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…
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…
History
The Address You Needed DNS to Find: How Glue Broke the Delegation Loop
A DNS referral can name the server that knows the answer and still leave a resolver unable to reach it. Glue was the small, deliberately non-authoritative exception that let the resolver cross that gap without giving the parent zone control over the child's facts.
History
The Address That Asked the Wire: How ARP Made Local Reachability Revisable
Routing can choose the next IP address without knowing how to put a frame on the local cable. ARP filled that last gap with a public question, a private answer, and a memory designed to be corrected.
History
The Connection That Had to Prove It Was New: Why TCP Needed a Three-Way Handshake
A packet can arrive at the right address, carry a plausible number and still belong to a conversation that has already died. TCP's familiar opening exchange was designed around that ambiguity: before accepting a new connection, both endpoints must show that they have seen each…
Global National Telecom Trends
An IRU Buys the Strand, Not the Road Around It
A dark-fibre contract can name a strand, reserve it for twenty years and make it feel like an owned asset. The harder question begins one layer out: who controls the ducts, access, power, maintenance, relocation and remedies that keep that strand useful when the route changes or…
Asia-Pacific Cloud Services Trends
Mercury Buys Into Datagrid Before the 140MW Power Option Becomes Load
Mercury has paid NZ$53 million for a 12.7% stake and a board seat in Datagrid NZ after signing a 140MW power purchase option. The structure gives the generator an early position beside a possible anchor customer, but it does not turn consent, earthworks or an option into an…
History
The Packet That Had to Learn Its Size: How Path MTU Discovery Moved Fragmentation to the Edge
A packet may cross a path whose narrowest link is invisible to its sender. The Internet spent four decades changing who should discover that limit, who should report it and who should decide what size to send next.
History
Two Kinds of Nothing: How DNS Learned to Separate NXDOMAIN from NODATA
An empty DNS answer can conceal two opposite realities: the requested name may be absent altogether, or it may be alive and carrying every record except the one requested. The Internet had to make that difference portable, cacheable and temporary before saving queries could stop…
Africa Cloud Services Trends
Nigeria Bets Federal Cloud Buying Power Can Anchor an Open Provider Market
Nigeria’s new cloud policy puts aggregated federal demand at the centre of its market-building strategy: ministries, departments and agencies would buy through coordinated mechanisms from multiple registered providers, creating an anchor customer large enough to improve…