FR
live

HPE closes its $14 billion Juniper acquisition after two and a half years

On August 13, 2026 a federal judge approved the settlement between HPE and the US Department of Justice, ending a two-and-a-half-year regulatory saga over Juniper Networks. For network teams, the HPE–Aruba–Juniper combination redraws the enterprise switching and Wi-Fi market against Cisco and Arista.

A wall of identical network switches in a dark rack, one port showing a single amber link LED.

August 13, 2026. Judge P. Casey Pitts, of the US District Court for the Northern District of California, approved the settlement between Hewlett Packard Enterprise and the US Department of Justice. The acquisition of Juniper Networks, announced on January 9, 2024 for $14 billion, is finally closed. A January 2024 announcement, an unconditional EU approval in August 2024, a DOJ lawsuit, a June 2025 settlement, and a thirteen-state challenge dismissed: the longest regulatory saga in enterprise networking just ended in a 41-page ruling.

For a network engineer, this is not a legal footnote. It is the starting gun for a reshuffling of the switching, enterprise Wi-Fi, and network observability markets — with your current vendor’s future sitting right in the middle.

Two and a half years of procedure, compressed

The timeline alone tells you how heavy this case was. HPE announced the deal on January 9, 2024, at $40 per share$14 billion in total. UK and EU regulators both reviewed it, and the European Commission cleared it without conditions in August 2024.

The block came from the United States. The DOJ filed a full merger challenge — the first outright one under the second Trump administration. Its core argument was about enterprise Wi-Fi competition: HPE and Juniper were the second- and third-largest enterprise WLAN vendors in the US, behind Cisco. Adding them together, the DOJ argued, would shrink a three-player market to two.

The case settled in June 2025, only for thirteen state attorneys general — led by California — to attack the settlement in March 2026, accusing HPE of improperly lobbying senior Justice Department officials. The New York Times called it the most significant courtroom vetting of an antitrust settlement between the government and a technology company in thirty years.

On August 13, 2026, Judge Pitts ruled: “the states have performed an invaluable public service in bringing to light additional details about the machinations at the DOJ,” but they “have not shown that entry of the amended proposed final judgment would not be in the public interest.” The deal is done.

One detail of the settlement is worth noting: the divestitures the DOJ imposed were so thin that Judge Pitts himself suggested in court they may have been designed to “create the appearance” of a structural fix. In other words, the merger was approved without any significant carve-out. HPE gets all of Juniper in one piece — which shapes what follows: no major divestiture will fragment the portfolio.

What HPE has already built on Juniper

The merger did not wait for the judge’s stamp to produce product. Since the June 2025 settlement, HPE has been folding Juniper’s technology into its catalog:

  • HPE Juniper Networking QFX, a switching line aimed at inference and scale-up architectures for AI clusters;
  • the integration of Juniper’s data-center switching and operations into the Mist AI engine, the observability platform Juniper acquired in 2019;
  • a unified, “AI-native” SASE platform that pulls security and networking under one console.

The common thread is Mist AI. It is the heart of Juniper’s value — a machine-learning operations layer that built the Juniper/Mist Wi-Fi reputation in large-scale deployments. HPE did not buy boxes; it bought a software layer capable of federating Aruba and Juniper under a single pane of governance.

What it changes for your estate

In practice, three questions matter for a network lead or a CISO who owns the infrastructure:

  • If you are an Aruba customer. The Aruba catalog — access points, CX switches, ClearPass for NAC — remains alive, but the roadmap converges on Mist. Expect tooling migrations rather than a sudden cut: the two brands coexist today, and HPE’s public line is convergence, not extinction.
  • If you are a Juniper customer. Your JUNOS and EX/QFX gear stay supported, but the strategic heading is now a unified HPE. Long-term support for legacy lines is the open question in any merger — document your contracts and end-of-life dates.
  • If you are running an RFP. The enterprise network market is consolidating around three poles — Cisco (which closed Splunk in 2024), HPE/Juniper, and Arista (which just posted its first $3 billion quarter on August 5, 2026, riding AI networking demand). Consolidation mechanically narrows your negotiation leverage, but it also simplifies multi-vendor architectures.

The deeper story goes beyond brand names. This is a race for AI infrastructure: data-center switches are becoming the bottleneck of compute clusters, and every vendor wants to sell the full stack — compute, storage, network — rather than a bare switch. HPE is explicit about it: the point of the deal was never to sell more Juniper, but to sell an HPE that does everything, from the server to the access point.

What to watch over the next eighteen months

The technical question that will occupy network teams is not legal: it is operating-system convergence. HPE inherits two software stacks — ArubaOS/AOS‑CX on the Aruba side, Junos OS on the Juniper side — plus the Mist orchestration layer. Every networking merger historically hits the same wall: running two operating systems side by side for years is expensive in maintenance and training.

Three signals will tell you whether the merger succeeds technically:

  • The Junos OS release cadence. If it slows in favor of a unified OS, Juniper customers will have to plan an operations migration, not just a hardware swap.
  • The fate of ClearPass. Aruba’s access-control platform anchors many estates; whether it survives — or is absorbed into the Mist stack — drives the security roadmap of thousands of deployments.
  • Mist integration into SASE. HPE announced an “AI-native” SASE platform; if it holds, it brings campus networking and cloud networking under one policy — the central sales pitch against Cisco and Fortinet.

For now HPE is talking coexistence. The history of past mergers — Extreme/Brocade, or Aruba itself absorbed by HPE in 2015 — suggests convergence will win out. The only unknown is the timeline.

Verdict

Judge Pitts’s ruling changes nothing in the short term for an estate already in production: your hardware keeps running and your contracts stay valid. It changes everything in the medium term for your architecture decisions.

If you are already committed to Aruba or Juniper, do not flee — but demand a written convergence roadmap toward Mist, with dated support milestones, before signing any multi-year renewal.

If you are running a new network RFP in 2026, price consolidation risk into your scoring: an absorbed vendor can see its legacy lines slow down. Contract for support duration and license portability, not for a product name.

If you are building an AI network, the market has already moved: inference switches and Mist observability are the axis HPE is doubling down on, and Arista is posting record quarters on the same ground. The choice is no longer “which switch” but “which network-compute stack do you standardize on.”

The lesson of this saga reaches past HPE. When a networking acquisition takes two and a half years to close, it means the enterprise network has become strategic again — strategic enough for courts to weigh in.

References

The cyber brief, every Tuesday

The flaws that matter and the patches to apply, in a ten-minute read.

No spam. One-click unsubscribe.
read next

On the same topic

CVE-2026-20349 takes Cisco firewall VPNs offline with a single unauthenticated HTTP request

In August 2026 Cisco disclosed CVE-2026-20349, an 8.6 CVSS flaw in the SSL VPN of its ASA and FTD firewalls: one unauthenticated HTTP request forces the device to reload and drops VPN access for every remote worker. With no workaround available, patching is the only fix — and the flaw is already being exploited in the wild.

← Back to the feed

Type at least two characters.

navigate open esc dismiss