/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

days · browse · Enter similar · o open

Cisco confirms it won't offer its Intercloud public cloud infrastructure beyond March 2017, shifting existing clients to other services

Jordan Novet / VentureBeat :

VentureBeat Jordan Novet

Context & Ripple Effects

Cisco is following HP's Helion shutdown out of the public cloud business, confirming Intercloud ends after March 2017 with clients moved to other services. The retreat comes despite Cisco spending the prior two years building cloud credibility: a $260M acquisition of cloud-management software maker CliQr in March and a joint platform pairing its networking gear with Azure aimed at other cloud vendors.

The significance is that two major networking-hardware incumbents have now independently concluded they cannot compete head-on with hyperscalers — and Cisco's answer, visible in what came before and after, is to sell the management and connectivity layer instead.

First-order effects

  • Intercloud clients face a forced migration to other providers before the March 2017 cutoff, while Cisco redirects the engineering and sales effort behind the service toward its software and networking portfolio.

Second-order effects

  • Hyperscalers absorb the displaced workloads, reinforcing the scale gap that killed the offering; competitors still running public clouds from a hardware base now have a second data point that the market rewards partnering over building.

Third-order effects

  • The pattern points toward hardware incumbents abandoning first-party public clouds in favor of hybrid positioning — a path Cisco itself completed when it partnered with AWS on hybrid Kubernetes rather than hosting workloads itself.

The trend: Enterprise infrastructure vendors are exiting commodity public cloud to monetize the software and connectivity layer between customers and hyperscalers instead.