. We need to write naturally. Let's draft: Lead: Cisco raised its fiscal 2026 hyperscaler AI orders forecast to $9 billion from $5 billion, and boosted its AI revenue outlook to $4 billion from $3 billion, after reporting $5.3 billion in AI infrastructure orders from hyperscalers so far this year. The company also posted record quarterly revenue of $15.8 billion in its fiscal third quarter, with non-GAAP earnings per share of $1.06 and a record non-GAAP operating margin of 34.2%. Then we need to elaborate. We can have an H2 like "AI orders build through the year" and then talk about the quarterly breakdown: Q1 $1.3B, Q2 $2.1B, Q3 $1.9B. That sums to $5.3B. We can say that the company's hyperscaler customers are driving the growth. Another H2 "Margins squeezed by memory costs" and talk about gross margin decline from 68.6% to 66.0% non-GAAP total, and product gross margin from 67.6% to 64.3%. Cisco attributed the pressure to product mix and higher memory costs. Another H2 "Splunk transition drags on revenue" and mention that the shift to cloud subscriptions is creating a near-term drag on revenue growth. Maybe also "Shareholder returns" but we have $2.9B returned to shareholders. Could include in a paragraph. End with a concrete next step: "The raised targets will be put to the test as Cisco works to convert its $5.3 billion in year-to-date AI orders into revenue. The company has said it expects hyperscaler AI orders to reach $9 billion by the end of fiscal 2026." That's a forward-looking statement. But we need to avoid "will be put to the test" maybe too dramatic. Let's say: "Cisco now expects $9 billion in hyperscaler AI orders for the full year, up from $5 billion. That target leaves it needing another $3.7 billion in orders over the final two quarters." That's a concrete next thing. But we don't know fiscal quarters? We know year-to-date as of May 13, 2026. Q3 ends? We have Q3 FY26 reported. So they have Q4 remaining. So we can say "The company needs to book another $3.7 billion in hyperscaler AI orders in the fourth quarter to hit the new target." That's a concrete next thing. But we don't know the exact target for Q4? We have year-to-date $5.3B and full-year target $9B, so difference $3.7B. That's factual arithmetic. We can say "That leaves $3.7 billion in orders needed in the final quarter to reach the $9 billion mark." That's a good ending. Let's write the article. We need to ensure no invented quotes. We can paraphrase: "Cisco said the margin decline was due to product mix and higher memory costs." That's fine. Also mention Splunk: "The transition of Splunk to a cloud subscription model is creating a near-term drag on revenue growth, the company said." We don't have a quote but we can state as fact. We need to keep the word count around 650. Let's write. First paragraph: As above. Then H2: "AI orders climb as hyperscalers spend" - but we need to avoid clichés. Maybe "Hyperscaler AI orders keep piling up" or "A $5.3 billion year for AI orders" but that's not specific. Let's use "AI orders from hyperscalers top $5 billion" as subhead. Then paragraphs: detail the quarterly numbers, the raised guidance. Then H2: "Margins slip on memory costs" - then paragraphs. Then H2: "Splunk transition drags" - then paragraph. Then final paragraph: "Cisco needs to book another $3.7 billion in hyperscaler AI orders in the fiscal fourth quarter to hit its new $9 billion target." That's a good ending. We can also mention shareholder returns in a sentence. Let's write the content. We need to make it sound human. Avoid AI tells. Use contractions like "it's", "they're", "we're". Vary sentence length. Let's craft. I'll write the JSON. Word count: I'll count later. Let's produce. Note: We must not copy phrasing from sources. So we need to rephrase. The facts are given in bullet points. We need to write in our own words. Let's write. Article:
Cisco raised its fiscal 2026 hyperscaler AI orders target to $9 billion from $5 billion, and lifted its AI revenue forecast to $4 billion from $3 billion, after reporting $5.3 billion in AI infrastructure orders from hyperscalers year-to-date as of May 13. The company also posted record quarterly revenue of $15.8 billion in its fiscal third quarter, with non-GAAP EPS of $1.06 and a record non-GAAP operating margin of 34.2%.
AI orders from hyperscalers top $5 billion
The $5.3 billion in year-to-date AI orders came in three chunks: $1.3 billion in the first quarter, $2.1 billion in the second, and $1.9 billion in the third. That pace convinced Cisco to nearly double its full-year order expectation.
Management now expects $9 billion in hyperscaler AI orders for fiscal 2026, up from the prior $5 billion forecast. The AI revenue outlook also jumped to $4 billion from $3 billion.
Margins slip on memory costs
Revenue growth didn't come without a cost. Cisco's non-GAAP gross margin fell to 66.0% in Q3 from 68.6% a year earlier. Product gross margin dropped to 64.3% from 67.6%.
The company attributed the squeeze to product mix and higher memory prices. Those pressures are likely to linger, though Cisco didn't provide specific guidance on margins for the rest of the year.
Splunk transition drags on growth
The Splunk acquisition continues to weigh on the top line. Cisco said the shift of Splunk to a cloud subscription model is creating a near-term drag on revenue growth. That transition is a deliberate move, but it's not helping current quarter numbers.
Even with that drag, Cisco managed record revenue and a record operating margin. The company also returned $2.9 billion to shareholders during the quarter.
Cisco needs to book another $3.7 billion in hyperscaler AI orders in the fiscal fourth quarter to reach the new $9 billion target. That's a steep ask, but the company's order flow so far suggests it's not out of reach.
We have about 300 words? Let's count. Actually that's around 300. We need 500-800. So we need to expand. We can add more details about the order breakdown, maybe mention that the orders are from hyperscaler customers, and that the company's guidance is for the full fiscal year. Also we can discuss the margin decline in more context. We can also mention that the record revenue was driven by AI infrastructure. But we don't have that specifically. We have facts: record revenue, etc. We can say "The record revenue came even as product margins contracted." We can also mention that the company's non-GAAP operating margin hit a record, which indicates cost control. We need to ensure we don't invent. We can paraphrase the facts. Let me expand. We have the facts: Cisco raised guidance, reported Q3 results. We can write a lead that includes the date? We don't have a date. We can say "In its fiscal third quarter" but no date. The facts mention "as of May 13, 2026" so we know it's about that time. But we don't have the exact earnings date. We'll just say "on Wednesday" or something? But we don't know the day. So we should avoid that. We can say "Cisco reported its fiscal third quarter results..." That's fine. We can add a paragraph about the significance of the $5.3B orders: "The year-to-date total represents orders from hyperscaler customers, the largest cloud providers. These are the companies building out massive AI data centers." But that's interpretation. We can say "Hyperscalers are the big cloud providers that are investing heavily in AI infrastructure." But that's common knowledge, but we shouldn't invent specific names. We can describe them as "hyperscaler customers" as in facts. We can also mention that the Q3 order of $1.9 billion was slightly below the Q2's $2.1 billion, but still strong. We can say "The third-quarter orders of $1.9 billion were down from the $2.1 billion in the prior quarter, but still ahead of the $1.3 billion in Q1." That's factual. We can also discuss the margin pressure: "The decline in gross margin was driven by a higher mix of lower-margin products and rising memory costs, which have been a challenge across the industry." But we don't have industry context. We'll stick to what's given. We can also add a note about shareholder returns: "Cisco returned $2.9 billion to shareholders through buybacks and dividends." But we don't know the split. We'll say "returned $2.9 billion to shareholders" as given. We need to ensure we don't add "experts say" etc. Let me write a fuller version. I'll structure with three H2s as above. Now, let's write the final content. We need to output JSON. Also meta description. Let's compute word count. I'll write the article in the content field. Let me draft a longer version:Cisco raised its fiscal 2026 hyperscaler AI orders target to $9 billion from $5 billion and lifted its AI revenue forecast to $4 billion from $3 billion, after reporting $5.3 billion in AI infrastructure orders from hyperscaler customers year-to-date as of May 13. The company also posted record quarterly revenue of $15.8 billion in its fiscal third quarter, with non-GAAP earnings per share of $1.06 and a record non-GAAP operating margin of 34.2%.
The year-to-date order total breaks down to $1.3 billion in Q1, $2.1 billion in Q2, and $1.9 billion in Q3. That trajectory — consistent quarterly orders above $1.3 billion — gave management confidence to nearly double the full-year order outlook.
AI orders from hyperscalers top $5 billion
Hyperscaler customers are the biggest cloud providers building out AI data centers. Their orders for Cisco's AI infrastructure have become a key growth driver. The $5.3 billion booked so far this year is more than double the $2.5 billion Cisco had previously guided for the full year? Wait, we don't have that. Actually the prior guidance was $5 billion, so year-to-date $5.3 billion already exceeds that. So the company raised the target to $9 billion. We can say "The $5.3 billion already exceeds the previous full-year target of $5 billion, prompting the raise." That's a good point. So we can write: "The $5.3 billion already exceeds the $5 billion full-year target Cisco had set earlier, which is why the company lifted the bar to $9 billion." But careful: The prior target was $5 billion, and year-to-date is $5.3 billion, so yes. So we can add: "With three quarters in the books, Cisco has already surpassed its prior full-year target of $5 billion, leading to the new $9 billion expectation." That's a strong statement. Let me incorporate that. Now, margin pressure: "Cisco's non-GAAP gross margin slipped to 66.0% in Q3 from 68.6% a year earlier. Product gross margin fell to 64.3% from 67.6%. The company blamed product mix and higher memory costs." That's fine. We can add: "The margin decline comes even as Cisco posted a record non-GAAP operating margin of 34.2%, suggesting the company is controlling operating expenses even as product profitability shrinks." That's an inference, but it's based on facts: record operating margin, lower gross margin. We can say "The record operating margin came despite the gross margin pressure, indicating tight cost control." That's a reasonable observation, not an invention. Splunk: "The Splunk acquisition, closed last year, is still in transition. Cisco said the move to cloud subscriptions for Splunk is creating a near-term drag on revenue growth. That means customers are shifting from upfront license fees to recurring payments, which spreads revenue over time." That's an explanation, but we don't have that detail. We can say "The shift to cloud subscriptions spreads revenue recognition over a longer period, which can depress current growth." But that's not in facts. We should stick to the fact: "The transition to cloud subscriptions is creating a near-term drag on
