Primary Domain
Technology
Within the Primary Domain facet, Technology intelligence groups reporting by primary domain so readers can follow a focused area of internet infrastructure, governance, connectivity markets, or digital capital. The page brings together related articles, public evidence, institutions, companies, people, regional exposure, operating dependencies, and market context that may otherwise sit across separate category pages. It explains the domain, the likely actor class, the market or governance context, and the source material readers should use when comparing signals. Operators, analysts, and governance readers can see how the same domain appears across events, profiles, market shifts, public-source evidence, regional dependencies, and longer-cycle infrastructure decisions over time.

Global Cloud Services Trends
Gartner's AI Forecast Has Rewritten Its Own Rules Twice This Year: A Dissection of What the $2.67 Trillion Actually Counts
Gartner's worldwide AI spending forecast is the number the technology industry quotes most readily: $2.7 trillion for 2026, a 49.5% increase year over year. Less quoted is the fact that within twelve months the firm redefined what that number counts — twice. The January 2026…

History
Jitendra Padhye and the Throughput Equation That Was Never Capacity
A number expressed in packets per second is easily mistaken for a ceiling built into a network path. Jitendra Padhye and three collaborators derived something more precise and more conditional: a prediction of the long-run sending throughput of a saturated TCP Reno flow, given…

History
David Culler and the Command That Was Never Completion
On a TinyOS mote, the most honest thing a command could do was return before the work was finished. The radio might still be transmitting, the sensor might still be converting and the relevant hardware interrupt might not yet exist. David Culler and his collaborators built that…

History
Sylvia Ratnasamy and the Map That Was Never Geography
CAN drew a map in order to avoid keeping one central index. Its coordinates did not mark countries, cables or even nearby machines. They marked a temporary division of work: hash a key to a point, then ask whichever node currently holds the enclosing zone. Sylvia Ratnasamy and…

History
Larry Peterson and the Global Slice That Never Owned a Node
PlanetLab gave a research service one name across machines it did not own. That was the power of the slice and also its limit. Larry Peterson and his collaborators made a distributed set of virtual machines behave like one experimental place, while the universities and…

History
Jon Crowcroft and the Internet That Became One Context Among Many
The cleanest network diagram has one middle and many edges. Plutarch drew a more difficult picture. In the 2003 architecture proposed by Jon Crowcroft, Steven Hand, Richard Mortier, Timothy Roscoe and Andrew Warfield, the globally routed Internet remained useful but ceased to be…

History
Frank Kelly and the Fairness That No Single Flow Could Prove
One connection can report its rate, delay and losses. It cannot, from those observations alone, certify that a shared network is fair. Frank Kelly's work on proportional fairness made the missing evidence precise: the claim belongs to a complete feasible allocation, not to the…

Asia-Pacific Datacenter Trends
Gartner's Trillion-Dollar AI Forecast Restates the Same Year Twice: What the Numbers Count, and What They Cannot
Gartner has revised its worldwide AI spending picture three times in twelve months — $1.4786 trillion for 2025 in September 2025, restated to $1.765 trillion in May 2026, then $1.7867 trillion in September 2026 — while the taxonomy underneath changed twice and the 2026 forecast…

Europe and Middle East Cloud Services
AlmazCloud's Commercial Story Meets the Routing Record: What AS210328 Can Actually Sell
AlmazCloud's Commercial Story Meets the Routing Record: What AS210328 Can Actually Sell intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences…

North America Datacenter
Vertiv: AI racks are priced on power and thermal, and the record says performance — not demand backlog — is quantified
In a liquid-cooled AI rack, the silicon is no longer the first failure mode. Power conversion, coolant distribution and heat rejection set the deployment ceiling — and Vertiv's own disclosures let readers test whether the supplier layer is shipping at that pace, not merely…

Europe and Middle East Datacenter Trends
Mistral Compute: four megawatt figures, one signed loan
Public statements about [Mistral Compute](https://btw.media/en/directory/mistral-compute) mix a 1,400 MW design ceiling at Fouju, 700 MW pre-reserved with transmission operator RTE, connection tranches of 240 MW and 700 MW, and 44 MW at Eclairion's Bruyères-le-Châtel site. Those…

History
David Tennenhouse and the Packet That Asked the Router to Run Code
In the passive Internet, a packet could ask to be forwarded. David Tennenhouse and David Wetherall proposed a more demanding message: a capsule that arrived carrying, or naming, the computation it wanted the next node to perform. That change made service innovation faster in…

History
Craig Partridge and the Gigabit That Did Not Need a New Internet
In 1989, one gigabit per second sounded large enough to indict an architecture. Craig Partridge answered by refusing to let the unit make the decision. He converted the rate into packets, instructions, memory touches, buffers and round trips, then asked which component actually…

History
Srinivasan Keshav and the Two Packets That Made a Hidden Queue Observable
The queue was inside a router, beyond the sender's sight. Srinivasan Keshav's answer was not to ask the router for a declaration, but to create a tiny event whose deformation could travel back as evidence: send two packets together and examine the distance between their…

History
Jeffrey C. Mogul and the Busy Receiver That Delivered No Packets
The processor was not idle. It was obeying every new arrival with such urgency that the work already admitted could not finish. Jeffrey C. Mogul and K. K. Ramakrishnan called the failure receive livelock: a receiver visibly running at full speed while useful delivery falls to…

History
Hari Balakrishnan and the Detour That Could Only Promise What It Measured
The direct path is dropping packets, yet the routing system still considers it alive. A second machine can reach both ends, but only an application that measures those two legs knows the detour exists. Hari Balakrishnan and his coauthors made that gap operational in RON: not a…

History
Christian Huitema and the DHCP Client That Had to Forget More Than Its Address
A laptop leaves one network, changes its wireless address and arrives at another. The visible label is new, yet its DHCP request repeats an old client identifier, asks for options in the same peculiar order and offers the address it used before. Christian Huitema and his…

History
Eddie Kohler and the Router Arrow That Did Not Say Who Called First
A packet-processing diagram contains an arrow from one component to the next. It looks like an instruction: the left side acts, the right side receives. In Eddie Kohler's Click modular router, that inference is unsafe. The packet still travels along the arrow, but control may…

History
Robert Metcalfe and the Collision That Gave Nobody the Next Turn
Two stations listen to the same cable, hear nothing and begin speaking. The contradiction is only apparent: a signal needs time to travel, so each station can be locally correct and globally in conflict. Early Ethernet made that conflict observable as a collision. It did not…

IETF
Nick Hilliard and the IPv6 Prefix That Works Only When It Goes Nowhere
`100::/64` is globally unique, forwardable inside a network and deliberately not globally reachable. That apparent contradiction is the point. The prefix gives IPv6 remote-triggered blackholing a clean internal next hop, but its success cannot be read from an IANA row or a green…
