Cisco books $4.48 billion in AI orders as 800 Gb/sec optical transceiver shipments ramp
Networking and optics now take a growing share of AI cluster budgets, and the basics of the fabric are learnable at your desk.
Cisco booked $4.48 billion in AI-related orders in its fiscal fourth quarter ended in June, a fourfold increase year over year, according to an analysis of the company's results published by The Next Platform on August 17. Of that total, $4 billion came from hyperscalers and cloud providers and $475 million from neoclouds and sovereign wealth funds.
Within the AI orders, roughly $2.96 billion was for AI system components, up 5.4 times, and more than $1 billion was for optical transceivers, up four times, The Next Platform reported. The company has shipped a cumulative 850,000 transceivers at 400 Gb/sec and 75,000 at 800 Gb/sec, with 100,000 and 35,000 respectively shipped in the quarter. The publication's estimates put cumulative revenue from those products at about $6 billion for 400 Gb/sec parts and $915 million for 800 Gb/sec.
For the quarter overall, Cisco reported revenue of $17.25 billion, up 17.6 percent, and net income of $3.86 billion, up 36.7 percent, with a backlog of $46.7 billion. Full-year sales were $63.33 billion, and AI revenue from hyperscalers reached $4 billion for the year. Guidance for fiscal 2027 is $72.2 billion to $73.4 billion in sales, or about 15 percent growth at the midpoint.
The Next Platform estimated Cisco's combined data centre systems business (switching, routing and servers) at $8.81 billion in the quarter, up 28.3 percent, with about $2.16 billion in operating income. The piece noted that margins are thinner when Cisco resells Nvidia components than when it sells its own Silicon One chips, systems and software, and it traced the company's server line back to the UCS platform launched in fiscal 2009.
Why it matters
AI clusters are only as fast as the network that connects their accelerators, and Cisco's order book shows spending has spread from GPUs into switches and optics. Growth in 800 Gb/sec transceivers signals that bandwidth per port is doubling on a short cycle. Buyers beyond the big clouds, including sovereign funds and neoclouds, are now a measurable share of demand.
AI clusters are only as fast as the network that connects their accelerators, and Cisco's order book shows spending has spread from GPUs into switches and optics.
- Hyperscalers and cloud providers$4.0bn
- AI system components$2.96bn
- Optical transceivers>$1bn
- Neoclouds and sovereign funds$475m
Figures: The Next Platform, reporting Cisco's fiscal Q4 2026 results
What you can learn from this
Accelerators need a fabric. Training a large model spreads work across thousands of GPUs that must exchange gradients many times per second. The switches and cables between them, called the fabric, determine how much time is spent waiting rather than computing. That is why a share of every AI cluster's budget goes to networking, and why networking orders grow alongside GPU orders rather than lagging behind them. Inference clusters need less inter-GPU traffic than training, which is one reason the two are often built differently.
Optical transceivers convert electrons to light. Inside a rack, short copper links suffice, but between racks and rows the signal must travel further, so it is turned into light and sent down fibre. A transceiver is the small pluggable module that does this at each end of a link. Speed grades such as 400 and 800 Gb/sec describe the bandwidth of one port, and each doubling requires new modules across the cluster, which is why transceiver volumes track each generation of cluster build. Higher speed grades also run hotter and cost more per port, so operators upgrade in stages.
Merchant silicon versus in-house silicon changes margins. A vendor that designs its own switch chips keeps more of each dollar than one that assembles other companies' parts. Cisco's Silicon One is an example of in-house silicon; reselling Nvidia designs is the other model. Understanding which path a product takes explains why the same revenue can produce very different profits, and why vendors talk about their own chips even when the headline is a partnership. It is the same logic that drives cloud providers to design their own chips.
Orders, revenue and backlog are different clocks. An order is a commitment, revenue is recognised on delivery, and backlog is what has been ordered but not yet delivered. A large backlog can mean strong demand or constrained supply, or both at once. Reading all three together gives a clearer picture than any one number on its own, and it helps you tell whether growth is arriving now or promised for later. Backlog also matters for suppliers further down the chain, who plan production against it.
Customer mix shows who is building. Hyperscalers are the largest buyers, but neoclouds (specialist GPU rental providers) and sovereign funds are now significant. Each group has different priorities: scale and price for hyperscalers, speed of deployment for neoclouds, and local control for sovereign buyers, which shapes what products vendors bring to market and how they package them for each segment. The mix can shift quickly when one group pauses spending.
We teach this
How to use this in practice
Draw a two-tier cluster network. Sketch eight servers with several GPUs each, connect them to leaf switches, and connect the leaves to spine switches. Label each link with a speed and mark which links are copper and which are optical, then count how many transceivers the diagram needs. Done looks like a diagram where you can trace the path a packet takes from one GPU to another in a different rack and say how many hops it makes. Then double the number of servers and note which links become the bottleneck. Keep the drawing for the glossary exercise below.
Measure your own link speeds. On a Linux machine run
ethtool <interface>(orGet-NetAdapterin PowerShell on Windows) to read the negotiated speed of your network port, then runiperf3between two machines to see achieved throughput. Done looks like a note comparing the advertised speed with what you measured and a guess at why they differ, such as cabling, CPU limits or the other machine's port. If you only have one machine, runiperf3in loopback to see the ceiling imposed by the software stack alone.Build a one-page glossary of interconnect terms. Define fabric, leaf, spine, transceiver, oversubscription and RDMA in your own words with one sentence each, and add one sentence on why each matters for AI training. Done looks like a page you could use to explain a cluster diagram to a colleague without looking anything up. Draw one tiny sketch next to each term to test whether you actually understand it.
Estimate bandwidth per GPU for a small cluster. Pick a hypothetical 64-GPU system, assume one 400 Gb/sec port per GPU and calculate total fabric bandwidth and how much leaf-to-spine capacity is needed to avoid oversubscription. Done looks like a short worked calculation you can redo for 800 Gb/sec ports and compare side by side. Then work out how many 800 Gb/sec spine ports you would need and what fraction of the cluster's cost that might represent using any public list price you can find.
Sources
- Cisco Can Finally Sell Lots Of Supercomputers And Their Networks — The Next Platform
Our reporting is an original summary; full coverage is at the links above.
Don't just read about it — build it.
Square 1 teaches the skills behind the headlines, with every line of your work graded by AI. Find your starting point in 3 minutes.
Get your free skill report