Primary Domain
Infrastructure
Within the Primary Domain facet, 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.
CASE FILE
The Card Was Removed. Its Configuration Stayed: RFC 10016 and the Authority of System State
RFC 10016 gives device-supplied configuration a standard place to be seen. It also exposes a harder operational truth: the device can withdraw a system node while client intent remains, and a client can withdraw an override only to uncover the system value beneath it. The four…
MENOG
MENOG’s Local Host Can Sign Contracts, but the Secretariat Holds Approval
MENOG gives a local host substantial work and visible benefits. Its host requirements also draw a precise line: the host may sign service contracts on the Secretariat’s behalf, but only subject to the Secretariat’s approval.
CASE FILE
The Tree Was Active. One Leaf Still Had No Packet: RFC 10018 and the P2MP Closeout Boundary
The Tree Was Active. One Leaf Still Had No Packet: RFC 10018 and the P2MP Closeout Boundary intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure…
CASE FILE
The Endpoint Still Spoke TLS 1.2. Its Old Handshake Had to Go: RFC 10015 and the Retirement Boundary
RFC 10015 does not switch TLS 1.2 off. It makes a more exacting intervention: keep the protocol version where it is still needed, but remove the finite-field Diffie-Hellman and RSA key-exchange paths whose risk can no longer be justified. The hard part begins after that sentence…
Europe and Middle East Regional ISP Trends
SeaExpress’s AS31444 makes route visibility easier than route-authorisation accountability
SeaExpress’s AS31444 makes route visibility easier than route-authorisation accountability intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure…
Story
Four Counterparty Pairs Made 89% of RIPE NCC's July IPv4 Transfer Total
RIPE NCC's August member update says 5,935,616 IPv4 addresses were transferred in July, 4,159,744 more than in June. The public transfer tables reproduce both numbers exactly. They also change the meaning of the headline: four repeated from-to pairs account for 5,299,712…
Europe and Middle East Regional ISP Trends
SC TECHNOLOGICAL's low-price fibre tiers make recovery economics the real product
Technological advertises fibre from €2.90 a month, no annual commitment and a portfolio that extends into voice and television. The compelling question is not whether those prices look attractive. It is what must keep working—and who must pay for recovery—after a customer…
CASE FILE
The Name Matched. The Key Had No Right to Revoke: RFC 10007 and the Missing `cRLSign` Proof
One certification authority gave the same named subject two different keys. Only one was meant to sign revocation lists. For years, the validation text could let the other key cross that boundary precisely because its certificate said nothing about permitted use.
CASE FILE
The JSON Was Valid. The Trunk Still Needed an Owner: RFC 10006 and the Apply Boundary
A service provider can now describe a SIP trunk in a form an enterprise edge can discover, authenticate for and parse. The consequential question begins one step later: who is entitled to turn that description into running configuration?
Story
LACNIC’s TAL Page Shows Two URLs and Links to Two Others
LACNIC’s trust-anchor page presents two addresses as TAL downloads. A reader who clicks them reaches distinct, valid TAL files through legacy Innovaportal targets. A reader or script that copies the addresses printed on the page instead receives the same HTML application shell…
CASE FILE
The Route Advertised 70. The Local Link Could Carry 50: RFC 10005 and Bandwidth Authority
One upstream says it has 70 units of capacity. The receiving router can reach that upstream only across a 50-unit local link, yet policy assigns it 70% of the traffic. The BGP UPDATE is valid, every session remains established, and congestion is still the expected result. RFC…
Europe and Middle East Regional ISP Trends
A tenant's fibre request is not an operator's right to enter the building
The installer has an order number, a coil of fibre and a resident waiting upstairs. The riser door is locked. The work pack says the customer has requested service, but it contains no signed access agreement, no completed notice chain and no court order. A simple phrase begins to…
Story
ARIN’s 29 August Stats Pair Split Across Two 2023 Filenames
ARIN’s public statistics directory contained a small but unusually legible publishing error on 29 August. The current data and checksum were available under their correct 2026 names, yet current-period artifacts also appeared through two extra paths dated 2023—and those two paths…
Story
AFRINIC Is Shrinking Its Data-Centre Footprint. Recovery Now Crosses a Cloud Boundary
AFRINIC's 2025 infrastructure report describes a sensible modernisation: retire obsolete equipment, use a smaller physical estate, place backups off site and test restoration every quarter. The harder question begins after the backup succeeds. Can the registry show that an…
CASE FILE
The DNS Said the Domain Was for Sale. It Did Not Have Authority to Close the Deal
RFC 10023 makes a registered domain’s availability visible in DNS. Its compact signal can open a negotiation while the domain remains in use; it cannot identify the rightful seller, bind a price or complete the transfer.
Story
APNIC's Firewall Reboot Put Registry Writes and Repository Reads Under One Clock
APNIC says a network firewall detected a hardware fault and rebooted on 28 August, interrupting six named service surfaces for an incident window of eight minutes. The short duration is reassuring. The single clock is not a complete recovery statement, because the list stretches…
CASE FILE
The Zone Was Online. One Address Family Could Not Reach Its Authority: RFC 10001 and DNS Partition
The dashboard stayed green because its resolver quietly used IPv4. An IPv6-only resolver followed the same published delegation, reached a missing dependency and stopped. The name had not disappeared; its authority existed on one transport path and not the other. RFC 10001 turns…
CASE FILE
The Route Tree Remembered Every Target It Saw. It Did Not Authorize the Detour
SIP History-Info can show how a request moved from one target to another. That makes it valuable evidence. It does not make the resulting route complete, truthful, permitted or successful.
CASE FILE
The Packet Came Back Complete. The Evidence Set Didn't: RFC 10029 and Authority Across DNS Types
A resolver asks once for an address, an IPv6 address and an HTTPS service binding. One successful packet returns. That packet can still leave one of the three questions unfinished. RFC 10029 makes the missing distinction operational: a shared envelope can reduce transactions, but…
Europe and Middle East Regional ISP Trends
Trifle's pioneer story needs a current operator-control map
Trifle's pioneer story needs a current operator-control map 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. The Europe…