Summary

  • HPE's US$382 million of third-quarter Data Center Networking revenue compares with US$180 million as reported a year earlier, but US$408 million on the company's normalized historical base. The latter comparison is down about 6%, not up 112.2%.
  • That normalized series is management-prepared combined information, not audited organic growth or Regulation S-X pro forma results. The current quarter also improved about 19% from the preceding quarter.
  • Strong orders are relevant but use different product boundaries. Neither the combined switching-and-routing order statement nor the wider Networking segment's 22% margin establishes this product category's revenue conversion or profit.

The number that changes is last year's

No revenue has to disappear for HPE's data-centre networking growth to change sign. The numerator stays at US$382 million. Change the historical denominator from US$180 million to US$408 million and an apparent doubling becomes a modest contraction.

Both denominators appear in the documents released with HPE's 2 September results for the quarter ended 31 July 2026. The earnings release reports Data Center Networking growth of 112.2%. Page 18 of the presentation supplies the US$180 million prior-year figure behind it. Two pages later, a normalized table puts the corresponding historical business at US$408 million and displays a 6% decline.

Calculated from those rounded dollar amounts, the decline is US$26 million, or 6.37%. The normalized historical base is US$228 million larger than the reported one. That US$228 million is a comparison-base difference, not a new current-quarter revenue adjustment and not a separately audited line of acquired revenue.

The distinction matters because acquisition growth and operating growth answer different questions. The reported series describes the business within HPE's reporting perimeter at each date. The normalized series attempts to compare a fuller combined historical footprint. An investor who uses the first series to infer the second has silently changed the question.

The acquisition boundary is real; the reconstruction has limits

HPE completed the Juniper Networks acquisition on 2 July 2025. Its prior-year July quarter therefore straddled the transaction, whereas the current quarter included the acquired business throughout. A large reported increase can result even when the reconstructed combined base is not expanding.

HPE provides the normalization needed to inspect that possibility. It also provides substantial warnings about the exercise. Its combined information adds standalone HPE segment results to adjusted historical Juniper information. It was not prepared under Article 11 of Regulation S-X and does not contain every adjustment required for formal pro forma information. It does not show what the combined company would actually have earned had the transaction occurred earlier.

There is a further calendar problem. Juniper's fiscal year ended in December; HPE's ends in October. HPE aligned them using internally prepared monthly information that was not reviewed or audited by Juniper, Juniper's independent auditor or HPE's independent auditor. The normalized figures differ from historical filings and are not a prediction of future performance.

These qualifications do not make the comparison useless. They make its proper label important. “Down about 6% on HPE's normalized base” is supportable. “Audited organic revenue fell 6%” is not. Nor does the existence of a normalized table make the reported 112.2% false. The two measurements describe different perimeters with different evidentiary status.

The rest of Networking did the growing

The product bridge sharpens the finding. On HPE's normalized figures, total Networking revenue increased from US$2.638 billion to US$2.893 billion, a US$255 million gain, or roughly 10%.

Campus & Branch supplied US$103 million of that increase. Security contributed US$30 million. Routing added US$148 million. Data Center Networking subtracted US$26 million. The four movements reconcile exactly to the disclosed US$255 million total change at the table's rounding precision.

That is a more useful description than treating every part of the larger Networking business as an equally strong beneficiary of AI infrastructure spending. Routing is a separate revenue category. Its growth cannot be assigned to Data Center Networking merely because both carry traffic or appear together in an order statement.

There is also an important counterweight. Data Center Networking revenue was US$320 million in the preceding quarter. The current US$382 million represents a sequential recovery of US$62 million, or about 19.4%. This is not evidence of uninterrupted deterioration. It is a business that improved quarter to quarter while remaining below the normalized year-earlier level.

Those two time comparisons can coexist. The disclosed figures do not say whether the annual shortfall reflects product mix, shipment timing, customer acceptance, pricing, cancellations or some combination. Assigning a cause without the missing bridge would simply replace one attractive narrative with another.

Orders are a lead, not a revenue reconciliation

HPE's demand disclosures give reasons to watch for further improvement. Total Networking orders grew 36% year on year on a normalized basis. Orders for Data Center Switching & Routing grew by a high-double-digit percentage on that basis. The company also reported US$0.7 billion of new Networks for AI orders, taking cumulative orders to US$2.2 billion, with a fiscal-year outlook of US$2.5 billion to US$3 billion cumulatively.

None of these figures reconciles directly to the US$382 million revenue line. The switching-and-routing order grouping includes routing; the revenue row under examination does not. Networks for AI is a demand classification, not a disclosed identity for the entire Data Center Networking revenue category. The company has not supplied a product-by-product bridge that permits the reader to equate them.

The AI disclosures contain another boundary. AI Systems orders and backlog include products and services. Networks for AI orders and backlog exclude services. HPE began tracking the latter backlog in the first quarter of fiscal 2026, while its cumulative network-AI order series includes eight months of pre-acquisition Juniper information. That is an annual historical adjustment, not eight months squeezed into the July quarter.

Orders and backlog are quarter-end observations and remain subject to rebookings, cancellations and fulfillment issues. A cumulative order target is not annual revenue guidance. Subtracting rounded AI totals to manufacture an exact network backlog, then dividing it by one quarter's product revenue, would combine incompatible boundaries and create a spurious conversion rate.

The demand story may prove strong. It has to prove itself through delivery and recognition on a consistent perimeter, not through the proximity of attractive numbers on a slide.

A 22% margin belongs to the segment

HPE reported US$637 million of Networking operating profit and a 22% segment margin. That segment contains Campus & Branch, Data Center Networking, Security and Routing. Its margin does not identify the profitability of any one product row.

Multiplying US$382 million by 22% would produce a number, but not an observed Data Center Networking profit. Product mix, support costs, software content and shared expenditure may differ across the portfolio. The disclosed segment metric also excludes certain corporate and other adjustments; it is not interchangeable with consolidated GAAP operating margin.

This leaves a narrower but firmer conclusion. HPE's reported expansion includes a major historical-perimeter effect. The normalized data-centre networking category contracted year on year while recovering sequentially. Orders point toward opportunity, but the disclosed order groupings and segment earnings do not yet establish the category's revenue conversion or profit. There is no need to turn that finding into a verdict on the whole acquisition.

Sources