Summary

  • HPE defines its annualized revenue run-rate as qualifying revenue recognised in a quarter multiplied by four, over a named set of as-a-service offerings, and states in the same filing that the figure is not revenue and should not be combined with it.
  • HPE enlarged that population from the quarter ended 31 July 2025 by adding software licence support and maintenance, which it justified by reference to Juniper Networks.
  • The Networking segment printed $2,690 million for the quarter ended 30 April 2026: 148.2% growth against the as-reported $1,084 million comparator, and about 10% against HPE's own normalized comparator of $2,444 million, which is my arithmetic on two published table values.

A run-rate is a rate. It says what a quarter looked like, scaled up. It does not say what anyone has promised to buy, for how long, or at what price after the first renewal. HPE is unusually explicit about this, and the explicitness is the interesting part: the company publishes both the arithmetic and a warning against using the result the way the market prefers to use it.

The definition is a multiplication

The FY2025 annual report defines annualized revenue run-rate as annualized revenue from net HPE GreenLake cloud services, related financial services revenue, software-as-a-service, software consumption and other as-a-service offerings, "calculated by taking qualifying revenue recognized during a quarter and multiplying by four" (HPE FY2025 Form 10-K).

Four times a quarter is not a year. Nothing in that formula imports a contract term, a renewal date, a cancellation right or a committed volume. A customer who bought in February and may leave in July contributes exactly as much to the annualized figure as one who signed for five years, because the multiplication happens after the fact and asks no questions about duration. The metric measures the speed at which qualifying revenue is arriving. It is a speedometer, and speedometers do not tell you how much road is left.

HPE then says so itself, in the same disclosure: ARR "is a performance metric that should be viewed independently of net revenue and is not intended to be combined with net revenue", it "has no standardized definition" and may not be comparable with similarly titled measures, and it is not a forecast (Form 10-K). Three sentences that a reader can use as a fence, printed by the party whose number it is.

The population moved on a date HPE chose

Definitions are not geology. They move when someone moves them, and this one moved in a specific quarter.

"Beginning with the quarter ended July 31, 2025," the filing states, HPE added revenue from software licence support and maintenance to ARR "to better align the metric with Juniper Networks' business and offerings", adding that the impact was not material to the current and prior periods presented (Form 10-K).

An immaterial change to a definition is still a change to a definition. The sentence tells a reader two useful things at once: that the boundary of the number was redrawn in a quarter that happens to be the first full quarter after a $14 billion acquisition closed, and that the company judged the redrawing small enough not to disturb comparability. Both can be true. Neither removes the obligation to know where the fence now stands, because a reader comparing a fiscal 2026 run-rate to a fiscal 2024 run-rate is comparing two populations whose membership differs by a category the filer selected.

The balances HPE does print show what the combination did to the headline: ARR of $3,151 million for fiscal 2025 against $1,938 million for fiscal 2024, a 63% increase, which the filing attributes primarily to Networking growth from the Juniper merger and an expanding installed base (Form 10-K). That attribution is honest and it is also the whole point. Most of the growth in an annualized as-a-service figure came from buying a business that already had one, not from a quarter's orders multiplying themselves.

The other number in the story, and its two bases

Now put the segment revenue beside it. For the three months ended 30 April 2026, HPE reported Networking net revenue of $2,690 million — Campus & Branch $1,322 million, Data Center Networking $320 million, Security $273 million and Routing $775 million (HPE Q2 FY2026 Form 10-Q).

Against the as-reported prior-year comparator of $1,084 million, that is 148.2% growth, which the filing attributes primarily to revenue from Juniper Networks (Form 10-Q). HPE's own quarterly deck prints the same series plainly: $1,084 million in the second quarter of fiscal 2025, $1,654 million in the third, $2,722 million in the fourth, $2,706 million in the first quarter of fiscal 2026 and $2,690 million in the second (HPE Q2 FY2026 earnings presentation).

Then the same deck prints a second table, for the "newly combined Networking business", in which the prior-year comparator is $2,444 million against the same $2,690 million (earnings presentation). Divide one by the other and subtract one and you get about 10%. That division is mine, performed on two published table values; HPE prints the table values, not that percentage, and the two comparators answer different questions. One describes what HPE's networking business did before it owned Juniper. The other describes what the combined business would have done had it existed a year earlier.

The deck is careful about the second table in a way that deserves quoting rather than paraphrasing. The information was presented "solely to facilitate comparisons of the newly combined Networking business"; it combines HPE Networking information with adjusted Juniper information, reconciles different fiscal quarter ends, and is not Article 11 pro forma, not audited or reviewed, and not indicative of historical or future performance. The endnotes add that normalized fiscal 2025 growth rates include eight months of pre-acquisition Juniper Networks results, and that the underlying monthly data were internally prepared and not reviewed or audited (earnings presentation).

So the segment's growth rate is not in dispute. There are two of them, both published by the same company on adjacent pages, and the difference between them is the entire distance between a business that grew and a business that was bought.

The label moved too

One more relocation, and it is quieter. HPE now reports under the segment name Networking rather than Intelligent Edge; the realignment took effect 1 November 2025 and prior segment information was recast retrospectively. The Q2 filing also states that former Intelligent Edge and Juniper Networks were combined into a single Networking reporting unit for goodwill purposes (Form 10-Q).

Recasting prior periods is ordinary practice and it is the right thing to do. It also means the word "Networking" in a 2026 filing and the word "Intelligent Edge" in an older document are not the same perimeter, even where the numbers are laid end to end as though the label had always meant the same set of products. When a company both buys a business and reorganises the reporting around it, the continuing series has to be rebuilt before it can be read as a trend.

What the record does not print

The quarter's filing contains no dedicated ARR definition and no ARR table; the phrase appears in forward-looking risk language. Nor did I locate a fiscal 2026 quarterly ARR dollar figure in the Q2 filing or the Q2 earnings materials (Form 10-Q). That is a statement about the documents I read, not a claim that HPE discloses no such figure anywhere. Anyone quoting a quarterly run-rate for this period is quoting something outside those two documents.

Segment profit, order intake and any backlog schedule were not obtained in readable form for this reading and are not asserted here.

What to do with a number like this

For an enterprise buyer, the practical instruction is narrow: a run-rate is not a price and not a commitment, so it cannot anchor a multi-year budget on its own. What anchors a budget is the contract in front of you — term, unit price at renewal, exit terms. The metric tells you which way a supplier's as-a-service business is pointed. It does not tell you what you will pay in year three.

For a channel partner, the sharper problem is that a quota built on a rate has no expiry date. If the definition's population can be enlarged in a quarter to accommodate an acquisition, the base against which a partner is measured can move without the partner moving.

For an investor, the discipline is arithmetic hygiene. Do not divide a run-rate by anything, and do not add it to revenue. HPE has printed the fence around the number; the only party who can put the number on the wrong side of that fence is the reader.

HPE is filed in the BTW directory as HEWLETT PACKARD ENTERPRISE COMPANY.

The useful question here is not whether the number is true. It plainly is, in the sense that HPE performed the multiplication it says it performed. The question is what population the word covers, and this filing answers that twice — once in the definition, once in the warning beneath it.