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.
Asia-Pacific Institutional
eNIC's .cc Registry Control Surface: Delegation, DNSSEC, RDAP, and Continuity Costs
eNIC Cocos (Keeling) Islands Pty. Ltd. d/b/a Island Internet Services is the company named by IANA as the current manager of the .cc country-code top-level domain. That public role creates a compact but consequential technology control surface: root-zone delegation data…
North America National Telecom Trends
Michigan’s nine water-system reports widen the cyber incident without showing unsafe water
Michigan says nine water systems reported malicious activity consistent with a federal alert. The systems kept operating safely and local teams addressed the issues, leaving a serious operational-technology investigation but no disclosed public-health impact or named culprit.
Africa National Telecom Trends
Twilio saw recovery on a subset of SMS routes to Safaricom, but had not closed the incident
Twilio reported delays and failures from some alphanumeric sender IDs and long codes to Safaricom subscribers in Kenya. It identified an undisclosed cause, observed recovery after 94 minutes and was still monitoring stability at the fixed cutoff.
Global Cloud Services
Cloudflare's 2026 BYOIP Outage Made Prefix-State Control an Accountability Test
A control-plane change withdrew customer-owned prefixes and exposed why address authority, service bindings, route intent, deployed configuration and public reachability need separate, continuously reconciled evidence.
Global Institutional
The 2015 Root DNS Flood Made Cross-Operator Telemetry an Accountability Test
Two concentrated query floods exposed the difference between root-system continuity and localized saturation, making shared, layer-specific telemetry the basis for judging operator preparedness and response.
Asia-Pacific Regional ISP
Planet Information Technology Solution and AS136903: IPv4, IPv6, RPKI, DNS, and ISP Continuity Costs
Planet Information Technology Solution and AS136903: IPv4, IPv6, RPKI, DNS, and ISP Continuity Costs intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure…
Europe and Middle East Institutional
Spamhaus's 2013 DDoS Made Open DNS Recursion a Network Accountability Test
The March 2013 campaign showed how exposed recursive DNS, source-address spoofing and shared interconnection paths could turn individually small configuration failures into a large external cost. Accountability depends on proving which operator controlled each executable step and…
Asia-Pacific Regional ISP
Techno Asia Infotech and AS135037: Routing, RPKI, DNS, and ISP Continuity Costs
Techno Asia Infotech and AS135037: Routing, RPKI, DNS, and ISP Continuity Costs 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…
Asia-Pacific Regional ISP
AS139618 Stays in the Registry While Its Public Routing Surface Is Silent
AS139618 Stays in the Registry While Its Public Routing Surface Is Silent 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…
Global Cloud Services Trends
Zoom disclosed a 76-minute Marketplace and AI Companion degradation only after it had ended
Zoom says users experienced degraded service across Marketplace and AI Companion from 00:00 to 01:16 UTC on 2 August. The incident record appeared roughly 29 minutes later, naming two service families but no affected function, cause, scale or geography.
North America Cloud Services
Microsoft's 2001 DNS Outage Made Shared Router Failure Domains an Accountability Test
Microsoft's January 2001 outage demonstrated a basic but still consequential property of network infrastructure: correct DNS records and several authoritative server processes do not create a resilient naming service when every reachable path to those servers depends on the same…
Global Cloud Services Trends
Cloudflare’s 15-minute Istanbul network incident left a precise window but almost no diagnosis
Cloudflare says elevated latency and connection errors affected Istanbul for 15 minutes on 1 August. The unusually exact interval is the firmest part of a record that identifies no product, route, cause or scale—and whose only visible notice appeared after the reported impact had…
Global Cloud Services Trends
GitHub restored GPT-5.6 Luna after 74 minutes, but the incident exposes a model-routing dependency
GPT-5.6 Luna became degraded across GitHub Copilot products and IDE surfaces because of an unnamed upstream model provider on 1 August. GitHub offered a practical escape route—choose another model or Auto—but published no measure of how many requests failed or what functional…
Global Cloud Services Trends
Twilio’s Globe Philippines incident delayed the receipt signal, not necessarily the SMS
For 2 hours and 42 minutes on 1 August, Twilio reported delayed SMS delivery receipts from its phone numbers to Globe Telecom subscribers in the Philippines. Messages could still succeed. That distinction matters because applications often treat the receipt as a control signal…
Global Cloud Services Trends
Cloudflare’s RealtimeKit join failures lasted 65 minutes, while its incident metadata says otherwise
Cloudflare says some RealtimeKit users faced slow socket connections and failed meeting joins from 13:10 to 14:15 UTC on 1 August. Yet the incident entity records both creation and resolution at 13:10:30. The narrative is operationally useful; the metadata cannot describe the…
Global Cloud Services Trends
GitHub took 17 minutes to name Fable 5 after upstream model errors began
GitHub’s second public Copilot model-provider incident on 1 August began with generic reports of upstream errors and only later identified Fable 5. Mitigation followed 28 seconds after that model-specific disclosure. The chronology shows fast recovery once the route was named…
Asia-Pacific Institutional
IBC Digital and AS10078: Hosting, DNS, Connectivity, and Operational Continuity Costs
Public registry, routing, DNS, hosting, maintenance, and contractual records expose a real operating surface while leaving private architecture, longitudinal reliability, and customer production outcomes subject to separate evidence.
Asia-Pacific National Telecom
KT's 2021 Routing Error Made Protocol-Boundary Validation a National Network Accountability Test
KT's nationwide Internet disruption showed why a carrier cannot treat an approved maintenance plan or two layers of manual review as proof that a live routing change is safe: accountability depends on the exact commands routers execute, the protocol boundaries they preserve, the…
Global Cloud Services
GitHub's 2015 Great Cannon DDoS Made On-Path Code Injection a Network Accountability Test
The 2015 attack on GitHub showed that network accountability begins with the bytes a user actually receives, not merely the address, certificate, contract or status page associated with a service.
Europe and Middle East National Telecom
Belgacom's 2013 Intrusion Made Roaming-Router Access an Operator Accountability Test
The lasting issue in the Belgacom case is whether an international carrier could substantiate its assurances with preserved evidence about privileged access, running router state, customer-traffic effects and operational continuity.