Primary Domain
Internet Infrastructure
Within the Primary Domain facet, Internet Infrastructure 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.

Story
A Fresh RIPEstat Query Can Still Return Older Data
RIPE NCC’s 20 October status notice says data freshness varies by RIPEstat API endpoint. One official Looking Glass response makes the distinction tangible: a request at 18:04:43 UTC returned a latest observation stamped 12:13:37 UTC.

History
The BOOTP “Gateway” Wasn’t the Client’s Gateway: What giaddr Meant, 1985–93
A diskless computer had to ask for help before it knew its own Internet address. BOOTP let a nearby relay carry that request to a distant boot server, but its field named `giaddr` was easy to mistake for the client’s ordinary router.

History
The WELL Ran Usenet and E-Mail Before Its Internet Link, 1985–92
The WELL’s own history places Usenet and worldwide e-mail exchange in 1985, years before it dates a separate Internet connection to January 1992. The distinction shows how an online community could be networked without yet offering the Internet access later users expected.

History
ARPANET Carried Batch Jobs to an IBM 360: UCLA’s NETRJS Service, 1977
A user could send a deck of card images across the network, let UCLA’s computer center run the batch, sign off and return later for the printout. NETRJS made that round trip a service, not merely a connection.

History
Before the Profile Page, a Remote User Could Ask Where You Were: NAME/FINGER, 1977
Before a profile page could follow you across a website, a bare network query could ask whether you were logged in, where your terminal sat, and what you wanted strangers to know while you were away.

Asia-Pacific National Telecom
Eighty Hours Announced, No Restoration Time Measured: Bangladesh's SEA-ME-WE-5 Repair Window
For four days in April 2026 the operator took Bangladesh's newest submarine cable out of service, moved Singapore-bound traffic onto the older cable, and published a schedule. Its announcement carried one consequence for the people at the far end of the cable: users could expect…

History
The Clock Trial Ran Through a Working Network: NTP’s 1985 ARPANET Experiment
A clock can display a number without agreeing with another clock. In 1985, the question was whether networked machines could keep time together while their links also carried ordinary traffic—and what a leap second would reveal about the answer.

History
An Autonomous System Was a Routing Policy, Not a Pile of Routers
An AS number looks like a network’s name. The 1994 RIPE application and RFC 1930 gave it a narrower job: mark a coherent routing policy visible to other networks.

History
Ethernet Began with a Network Sketch. DIX Drew the Local Boundary
Ethernet’s 1973 proposal pictured more than a cable joining computers: it imagined “boosters” linking branched wire, telephone and radio media. Seven years later, Digital, Intel and Xerox published something deliberately narrower: a design reference for a local network’s…

History
The Route Collector Could Not See the Whole Internet: RIPE NCC’s RIS, 1999
The Route Collector Could Not See the Whole Internet: RIPE NCC’s RIS, 1999 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…

Leaders
Lee Howard's ARIN Record Puts Registry Resilience on the Board Agenda
At an August 2026 board meeting, Lee Howard moved acceptance of ARIN’s annual audit, then raised a less tidy operational issue: manual processes were still a risk in the registry’s control-plane redesign. The draft minutes connect financial oversight to the mechanics that keep a…

History
RIPE’s 1990 debate: connectivity first, costs by bilateral agreement
Before European IP networks could behave like a wider system, their operators had to answer an awkward question: who would pay when one network carried traffic for another? RIPE’s January 1990 minutes show a community trying to grow connections without a central fund or a body…

History
The Queen’s ARPANET Message Announced CORAL 66, 1976
A familiar image shows Elizabeth II at a computer in Malvern. The message she sent on 26 March 1976 was less a greeting than a service notice: it told ARPANET users that the CORAL 66 compiler on the Royal Signals and Radar Establishment’s GEC 4080 was available. For a researcher…

North America Institutional
The Capacity Sum That Closes: Seattle Internet Exchange's Published Inventory, Read Against Its Own Peak
On 19 October 2026, between 03:08:40 and 03:11:42 UTC, the Seattle Internet Exchange published five port classes, a peak figure and a capacity figure on the same page. Two of those numbers sit four words apart in one sentence. The capacity figure can be reproduced exactly from…

Europe and Middle East Cloud Services
The Number Outlives the Name: AS57063 and the Register Record That Did Not Follow
A routing identifier, a registration code and a company name are three different kinds of fact, maintained by three different processes on three different clocks. On 18 October 2026 the first two still agreed with each other. The third had already moved.

CASE FILE
Five Sites, 67 Customers, No Per-Port Load: FICIX and the Utilisation Ratio That Cannot Be Built
Between 21:38 and 21:44 UTC on 18 October 2026, three public documents bearing on Finland's largest internet exchange were retrieved and retained. They establish what FICIX says it is, what interface speeds it offers, and something less comfortable: the two number classes a…

Story
APNIC lists its Kubernetes upgrade on two different dates
The service notice and status page put a six-hour upgrade window on 21 October in Brisbane. The linked iCalendar feed starts the same event 24 hours earlier.

History
250 X.25 Access Points Were Not an Internet Backbone: Hungary, 1992
Hungary had a national packet network before it had a national IP backbone. In 1992, about 250 public X.25 access points helped smaller and medium-sized sites join wide-area networking, while international IP still depended on a 9.6 kbit/s Budapest–Linz line shared by EARN…

History
A Ping Reached a .cm Host. Nationwide Internet Access Was Another Question, 1997–98
One successful Internet probe in March 1997 made a Cameroonian host visible from London. It did not settle whether Cameroon had a finished international link, where people could buy access, or how far that access reached. The contemporary record keeps those questions apart.

Asia-Pacific National Telecom
NBN Co is closing the capacity dial its retailers spent a decade turning
For years the wholesale tariff priced two different things: a monthly charge per service and a separate charge per megabit of busy-hour capacity. The record available to this desk on 18 October 2026 says the second is being folded into the first. That is reported rather than…
