Summary

  • Akamai's Form 10-Q for the quarter ended 30 September 2026 reports one operating and reportable segment. Security, Delivery and other cloud applications, and Cloud infrastructure services are revenue solution categories, not segments.
  • Cloud infrastructure services — the category the filing says includes compute and storage — produced $108.803 million of $1,121.961 million in revenue. Accrual capital spending in the same quarter was $464.146 million; cash-basis capital spending was $605.155 million.

There is a version of the Akamai story in which the company stopped being a content-delivery network and became a cloud. It is a good story, four years old, told in every investor deck. The filing tells a narrower one, and the gap between the two is entirely a matter of what the company is willing to name.

Start with the structure. The 10-Q filed on 6 November 2026 under accession 0001086222-26-000100 says Akamai operates as one operating and reportable segment. What it discloses instead are three revenue solution categories, and the difference between a segment and a solution category is not pedantry: a segment carries allocated cost, margin and capital. A revenue category carries a top line and nothing else.

Summary
Three months ended 30 September 2025 2026
Security $568.437m $621.892m
Delivery and other cloud applications $405.014m $391.266m
Cloud infrastructure services $81.179m $108.803m
Total revenue $1,054.630m $1,121.961m

The filing defines Cloud infrastructure services as including compute and storage solutions, EdgeWorkers, and compute partner solutions operating on Akamai's platform. That is the cloud business, as close as the document comes to naming it.

Now the arithmetic, which is mine and not the company's. Security was 55.4% of third-quarter revenue; Delivery and other cloud applications 34.9%; Cloud infrastructure services 9.7%. The dollar change year over year reconciles exactly: Security added $53.455 million, Cloud infrastructure services added $27.624 million, and Delivery and other cloud applications subtracted $13.748 million, for a total increase of $67.331 million. In percentage terms that is +9.4%, +34.0% and −3.4% against +6.4% for the company. Security alone supplied 79.4% of the dollar growth; the cloud category supplied 41.0%; the residual bucket was negative 20.4%.

Read that table twice, because it inverts the marketing. The fastest-growing category by rate is the smallest. The category that produced four-fifths of the new dollars is a security portfolio. And the category that shrank is the one that carries what used to be the whole company.

The revenue-recognition language explains why a cloud category can be small and still capital-hungry. Akamai says most of its solutions are stand-ready obligations satisfied over time, and that most revenue is recognised over time, generally ratably over the arrangement term, with usage above a contractual commitment recognised as the units are served. Only a smaller portion — certain professional-services, integration-services and licence contracts — is recognised at a point in time. Ratable stand-ready revenue arrives in a thin monthly line no matter how much capacity sits behind it.

Then there is the capital. Akamai's Q3 2026 supplemental financial information, published 5 November 2026 on the investor-relations quarterly archive, reports three-month capital expenditures of $464.146 million on an accrual basis, made up of $376.833 million of property and equipment purchases and $87.313 million of capitalised internal-use software, against $224.163 million a year earlier. The same release reports $605.155 million on a cash basis for the quarter, and $1,022.755 million for the nine months, of which $761.516 million was property and equipment and $261.239 million was internal-use software.

Two numbers, one quarter, both the company's. Akamai states the two bases differ for changes in accrued but unpaid property, equipment and internal-use software costs. Cash-basis spending runs heavier than the accrual measure in this quarter by $141.009 million, which means the company was writing cheques faster than it was booking the obligation. Anyone quoting one figure without the other is quoting a basis, not a total.

My ratios: accrual capital spending was 41.4% of quarterly revenue, 2.42 times the quarter's depreciation and amortisation of $191.592 million, and 4.3 times the entire quarterly revenue of Cloud infrastructure services. On the cash measure it was 5.6 times that category's revenue. Capital spending grew about 107% year over year while total revenue grew 6.4% and the cloud category grew 34.0%.

What no reviewed document answers is the question those ratios raise. Because Akamai reports one segment, there is no disclosure that assigns a dollar of that $464.146 million to compute, to storage, to edge capacity or to the security platform. The cloud category's own definition includes compute partner solutions running on Akamai's platform, and nothing read here splits partner capacity from Akamai-owned capacity. A reader can therefore measure the money going into the business and the money coming out of the smallest category, and cannot connect them.

One more check on the depreciation line. The release names non-GAAP depreciation and amortisation of $149.622 million and amortisation of acquired intangible assets of $26.331 million, against a stated total of $191.592 million. Those two named components sum to $175.953 million, leaving $15.639 million unnamed in the excerpt read. Nine-month depreciation and amortisation of $560.880 million against nine-month cash capital spending of $1,022.755 million puts capital spending at about 1.82 times the depreciation charge, which is what a company looks like when its asset base is still expanding faster than it is wearing out.

Here is where BTW stands. Akamai's category labels are accurate — Cloud infrastructure services really does contain compute and storage, and the company is not dressing a delivery product as a cloud. The problem is one level up. A single-segment structure with three revenue categories lets a company put its most capital-intensive, slowest-recognising, smallest line beside two mature ones and publish a single gross number for the whole.

That is a disclosure choice with a cost, and the cost is transferred to whoever is trying to price the cloud story: the analyst modelling a category margin that does not exist in the filing, the enterprise buyer benchmarking a compute price against a company that will not say what its compute costs, the supplier negotiating capacity against a capital plan that is not allocated.

The EDGAR filing index shows this is the current quarterly report, not an old one. Nothing here is a scandal. It is a boundary, drawn by a company that has every right to draw it — and drawn in the place that makes the most interesting question unanswerable. Akamai's cloud is real. It is also one-tenth of Akamai, and the capital buying the other nine-tenths cannot be seen from outside.

Directory entry: Akamai