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.
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.
North America Institutional
Granite Networks After Acquisition: Data-Centre Identity, IPv4 Continuity, and Operational Handover Costs
Granite Networks is a bounded test of whether legal succession, hosting assets, IPv4 records, and operational responsibility can remain coherent after an acquisition without turning public routing evidence into unsupported reliability or customer-outcome claims.
Asia-Pacific Regional ISP
AS142199 Keeps XEONFIBER in the Registry After Its Visible Route Goes Quiet
AS142199 Keeps XEONFIBER 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…
Global Cloud Services Trends
Cloudflare’s IAD 5XX episode lasted 256 minutes but was disclosed in one retrospective update
Cloudflare says an increased level of HTTP 5XX errors affected Ashburn, US (IAD), from 18:45 to 23:01 UTC on 31 July. Yet the public incident contains only one visible update, timestamped more than two hours after that interval ended. The fault is closed; the operational…
Global Cloud Services Trends
Twilio’s Claro Colombia short-code delay was still under investigation at the 20-minute cutoff
Twilio opened a minor incident at 02:57:20.918 UTC on 1 August for SMS delivery delays from a subset of its short codes to Claro subscribers in Colombia. At the fixed 03:17:59 cutoff, 20 minutes and 38.082 seconds had elapsed. There was no identified cause, recovery signal or…
North America Institutional
F6 Networks After Acquisition: AS3367, Fibre Continuity, and the Cost of Operational Handover
F6 Networks is a useful test of whether a network identity, its public routing records, and operational responsibility can remain coherent after an acquisition without turning dated capability claims into unsupported reliability or customer-outcome claims.
Global Cloud Services Trends
Anthropic closed a 47-minute Claude Sonnet 5 degradation with the service boundary still undisclosed
Anthropic marked a minor Claude Sonnet 5 performance incident resolved at 07:04:49.691 UTC on 31 July, 46 minutes and 41.623 seconds after it opened. That short chronology establishes a start and an end, but almost nothing about the customer experience between them: no symptom…
Global Cloud Services Trends
Cloudflare’s us-east-1-aws path returned intermittent 5xx errors for 138 minutes
Cloudflare resolved a minor incident involving intermittent HTTP 5xx responses for customers using the label us-east-1-aws at 04:19:32.991 UTC on 31 July. A fix had entered monitoring 10 minutes and 51.068 seconds earlier. The operator disclosed the request outcome and…
Global Cloud Services Trends
Twilio’s El Salvador incident delayed proof of SMS delivery, not necessarily the message
For 9 hours, 41 minutes and 49.987 seconds on 31 July, Twilio tracked delayed SMS delivery receipts for messages sent toward Telefónica subscribers in El Salvador. Its most important qualification was present from the first notice: message delivery might succeed while the receipt…
Global Cloud Services Trends
A subset of Twilio numbers failed to deliver SMS to C+W LIME for more than 12 hours
Twilio closed a minor SMS incident affecting a subset of its phone numbers on the route to C+W LIME subscribers in the Cayman Islands at 06:18:08.210 UTC on 31 July. The case had opened the previous day and lasted 12 hours, 27 minutes and 40.379 seconds. The narrow route and…
Global Cloud Services Trends
Twilio’s Celcom Malaysia SMS delay recovered without an identified public cause
Twilio resolved a 3-hour, 21-minute and 39.361-second incident affecting SMS delivery toward Celcom subscribers in Malaysia at 02:12:32.051 UTC on 31 July. The case moved from investigation to observed recovery and then resolution; it never displayed an identified state. No delay…
Global Cloud Services Trends
Twilio’s Claro Colombia voice incident changed its scope wording without measuring an expansion
Twilio resolved a minor voice-call incident affecting a subset of origin numbers toward Claro subscribers in Colombia at 02:09:34.991 UTC on 31 July. During the 5-hour, 41-minute and 10.935-second case, “Mobile Numbers” became “Phone Numbers” and one update omitted Claro. The…
Global Cloud Services Trends
Twilio was still monitoring Africell Angola SMS recovery after 25 hours at the cutoff
Twilio had observed recovery in SMS delivery toward Africell subscribers in Angola four times by the fixed 00:13:55 UTC cutoff on 1 August. It had not declared the minor incident resolved. The public case had been open for 25 hours, 42 minutes and 51.122 seconds, while cause…
Global National Telecom Trends
Fénix promises a 14 Tbps Venezuela–Curaçao ring, but the cable is still an announced project
Liberty Networks and CANTV announced Fénix on 31 July as a 378-kilometre submarine cable system between Camuri in Venezuela and Willemstad in Curaçao, with a stated minimum ring capacity of 14 Tbps. The design would connect Venezuela to a broader Caribbean hub. The release is…
Africa Regional ISP
AS37286 makes Nigeria ICT Forum resource visibility public without proving the network behind it
AS37286 makes Nigeria ICT Forum resource visibility public without proving the network behind it intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure…
Global Cloud Services
OVH's 2016 Mirai Attack Made DDoS Scrubbing Capacity an Accountability Test
OVHcloud's report of traffic above one terabit per second during the first Mirai wave turned a spectacular attack number into a practical network question: could a hosting operator measure the flood, activate mitigation, preserve clean traffic and show customers that the service…
Europe and Middle East Institutional
Philips' Dual Brand-TLD Control Surface: DNS Delegation, Connected-Care Security, and Continuity Costs
**By Theo March, Technology and AI Correspondent**
Global Cloud Services
GitHub's 2018 Memcached Attack Made Anti-Spoofing and Mitigation Handoff an Accountability Test
GitHub's response to a 1.35-terabit-per-second attack showed that DDoS resilience depends on more than buying bandwidth: operators must detect abnormal traffic, move routing authority safely, preserve clean delivery and reduce the spoofing conditions that make reflection…
Global Cloud Services Trends
Twilio’s Brazil voice incident reached monitoring after 18 hours without a public cause
Twilio said voice calls from its phone numbers to subscribers on multiple networks in Brazil were recovering on 31 July, but the incident was not resolved at the 20:19:07 UTC reporting cutoff. The first monitoring update came more than 18 hours after the case opened. Across that…