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.
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.
Asia-Pacific Regional ISP
AS148972 Keeps Zero Cirrus in the Registry After Its Visible Route Goes Quiet
AS148972 Keeps Zero Cirrus in the Registry After Its Visible Route Goes Quiet 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…
Europe and Middle East Institutional
dot Webcam Limited and the .webcam Control Plane: Delegation, RDAP, DNSSEC, and Registry Continuity Costs
dot Webcam Limited is the accountable registry operator for .webcam, while the namespace visible to users depends on delegation records, DNS and DNSSEC, WHOIS and RDAP, registrar interfaces, escrow, reporting, provider boundaries, and recoverable operating responsibility…
Global National Telecom
Raptor Train Made Edge-Router Lifecycle Evidence an Operator Accountability Test
Raptor Train showed how a rapidly rotating population of compromised edge devices can remain operationally persistent even when individual malware instances are short-lived, making support state, network evidence, remediation authority and proof against reinfection an…
Asia-Pacific Institutional
Function4 and AS153748: Connectivity, RPKI Gaps, and Business Continuity Costs
Function4 and AS153748: Connectivity, RPKI Gaps, and Business 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
AS136922 Keeps Anttel Wholesale in the Registry While Its Public Routing Surface Is Silent
AS136922 Keeps Anttel Wholesale 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…
Global National Telecom
The 2023 Pumpkin Eclipse Made CPE Recovery Evidence an ISP Accountability Test
The October 2023 destruction of hundreds of thousands of home and small-office routers turned firmware authority, fleet inventory, hardware replacement and proof of restored connectivity into one operator-accountability test.
Asia-Pacific Regional ISP
Chittagong Multi Channel Limited and AS137029: IPv4 Routing, RPKI, and ISP Continuity Costs
Chittagong Multi Channel Limited offers a compact view of how an access provider's public company identity, Internet-number records, route announcements, security metadata, customer-facing promises, and day-to-day operating duties have to remain aligned.
Asia-Pacific Regional ISP
AS142282 Leaves Wuhan LSHIY in the Registry After Its Last Visible Route Was Seen in 2024
AS142282 Leaves Wuhan LSHIY in the Registry After Its Last Visible Route Was Seen in 2024 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 National Telecom
LINX's 2023 LON2 Incidents Made Lab-to-Production Network State an Accountability Test
When a router moves from a laboratory into a live Internet exchange, a clean configuration file is not enough. LINX's public account of its 2023 LON2 incidents shows why operators must verify the identity and forwarding state that the device is actually running, especially when a…
Global Cloud Services
Akamai's 2004 Network Attack Made Distributed Edge Failover an Accountability Test
Akamai's bounded account of a 2004 denial-of-service incident shows why a distributed edge network must prove customer impact, destination capacity and failover behavior from the running network rather than architecture claims alone.