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 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…
CASE FILE
The Dialog Was Found. The Transfer Was Not Yet Earned: SIP Replaces and the Authority to Move a Conversation
A help-desk console can show “transfer accepted” while the target has refused the new call and the original caller is still hearing hold music. The messages may all be correct. The failure lies in treating a reference, a dialog match and a completed handoff as one event.
CASE FILE
The Call Refreshed. The Conversation Might Not Have: SIP Session Timers and the Authority to Declare a Session Alive
A voice platform can receive a perfect 200 response to a session refresh while the caller hears silence, the media path has failed and the billing clock keeps running. The signaling record is real. The mistake begins when that one reality is allowed to speak for all the others.
CASE FILE
The Registry Redrew the Range. The Old Allocator Kept Issuing IDs: RFC 10028 and Authority over IPv6 Multicast Coexistence
RFC 10028 gives dynamic IPv6 multicast allocation methods separate numeric territory. That is necessary coordination, but it does not reach into an old appliance, rewrite its pool or show that the intended stream reached a listener. The operational question begins where the new…
Story
AFRINIC's New ASN and /24 Share a Holder ID, Not a Transaction ID
AFRINIC's New ASN and /24 Share a Holder ID, Not a Transaction ID 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…
Story
RIPEstat Wants Better AS Names—and a Map of Which ASNs Are One Entity
RIPEstat Wants Better AS Names—and a Map of Which ASNs Are One Entity 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.…
CASE FILE
The Session Grouped Four Streams. It Did Not Reconstruct the Scene: RFC 10034 and Authority over a V3C Representation
Volumetric video does not travel as one self-sufficient picture. It can arrive as an atlas plus occupancy, geometry and attribute streams, each with its own packets and failure state. RFC 10034 gives those parts a shared transport grammar. It does not appoint any one green…
CASE FILE
The Header Asked for a Stream. The Proxy Still Owned the Flush: RFC 10036 and the Authority to Release an HTTP Message
A sender can place `Incremental: ?1` at the front of an HTTP message and begin producing useful content immediately. That does not make the path a pipe. Every intermediary still controls a parser, a security decision, a capacity limit and a buffer. RFC 10036 turns the sender's…
Story
LACNIC's Delegation File Declares 49,894 Records. It Contains 48,214
A daily file built for machines fails the counting rule printed in its own specification, while its automatic alias and its dated signature offer two different paths to trust. The discrepancy is not evidence of missing Internet resources. It is a test of whether a registry…
CASE FILE
The Server Issued a Locator. The Network Had Not Yet Accepted the Route: RFC 10038 and the Authority to Allocate SRv6 Reachability
A DHCPv6 Reply can make an SRv6 locator administratively real in a few fields: who received it, how it is divided and when it expires. The packet path is harder. A route still has to be installed, advertised, selected, programmed, filtered and joined to a local SID behavior. RFC…
CASE FILE
The Token Matched. Permission Still Had to Be Checked: WebDAV Lock Tokens and Write Authority
A WebDAV client can present the exact token for a live lock and still be correctly refused. That is not a contradiction in the protocol. It is the point at which a coordination marker stops and authority begins.