More Editions
Vol. 1, Issue 2 | Aug. 28, 2026 Covering: Aug. 13 – Aug. 26, 2026

Operational intelligence for enterprise operators. Written for those who need to run AI inside their enterprise and want to know: What would an operator do?

AI got easier to buy and harder to verify

AI got cheaper, faster and easier to place where enterprises need it over the past two weeks. OpenAI cut the price of GPT-5.6 Sol while revealing that monitoring its own AI can consume roughly 20% as much compute as the inference being monitored. AWS expanded regional access and made in-country inference configurable for India. OpenAI committed to zero data retention for frontier models, and Anthropic began watermarking every new Claude model worldwide.

But the proof behind several of those claims is still catching up: the retention mechanism has yet to be published, the watermark detector hasn’t shipped and Claude recorded 14 incidents in 14 days. For operators, the expanding menu of AI capabilities comes with an equally important question: Can you independently verify what your provider says is happening?Jump to the stories

At a glance

  • $4 per 1M input tokens/$20 per 1M output tokens is the new promotional price for GPT-5.6 Sol, down from $5/$30. Input fell 20% and output fell 33.3%, with the promotion running at least through Nov. 21. OpenAI pricing page, observed Aug. 26
  • About 20% of monitored inference compute is consumed by the monitoring itself, according to OpenAI’s estimate for its own workloads. OpenAI, published Aug. 18
  • 25 days past the Aug. 1 deadline for a U.S. federal pre-release access framework, no framework text has been published. This remains developing because no agency has confirmed its status. AWS, published Aug. 20
  • 4.25 gigawatts of capacity are committed at an Ohio AI campus backed by NVIDIA credit support, with another 3.75 gigawatts optioned. The first phases are expected in 2028. NVIDIA and OpenAI, announced Aug. 17
  • 14 incidents were recorded by Claude across nine of the past 14 days, according to Anthropic’s status page. Its 90-day uptime ranged from 99.36% to 100%, depending on the surface. Status.claude.com, observed Aug. 26
  • 1.5 to 1.9 times more work per watt was reported for OpenAI’s inference chip versus comparison systems on a public benchmark. The results were normalized using rated power rather than the lower measured draw. OpenAI, published Aug. 25

Editor’s note

AI is getting easier to put into production. Prices are falling, regional access is expanding and providers are turning controls such as residency, retention and provenance into product features. The harder part is establishing exactly what those controls do, where they apply and how you can verify them.

That distinction shows up in several of this issue’s biggest developments. AWS expanded GPT-5.6 across more than 25 regions and introduced India-specific inference profiles that keep requests within the country. OpenAI committed to zero data retention for frontier models, while the technical paper behind its new cross-session safety system is still to come. Anthropic began watermarking every new Claude model worldwide, but the detection API has not shipped. The controls are arriving. The documentation and tooling needed to validate them are not always arriving with them.

Cost tells a similar story. OpenAI lowered the published price of GPT-5.6 Sol while disclosing that monitoring its own inference can consume roughly 20% as much compute as the inference being monitored. Memory costs are also rising, with server prices reported to be increasing on some NVIDIA-based configurations. A lower token price is good news, but it is not the same thing as a lower cost to operate AI. Monitoring, infrastructure and the controls needed to run AI responsibly belong in that calculation too.

Reliability makes the need for scrutiny even clearer. Anthropic recorded 14 incidents across nine of the past 14 days, while its published 90-day availability ranged from 99.36% to 100%, depending on the product surface. The public data does not tell us why those numbers differ, and we shouldn’t speculate. But it does tell us that an availability figure is only useful when you know exactly what it measures.

That is the operator’s job in this increasingly capable AI market: know what you are buying, understand what sits behind the claims and decide what evidence you need before you rely on them. The technology is moving quickly. Operators need to distinguish what can be independently verified today from what still needs to be tested or remains a provider claim.

The Rackspace AI Team

The big stories

The facts, our assessment and the operator takeaway

1 OpenAI put a price on the compute required to monitor AI

Topics: AI SECURITY & COMPLIANCE

On Aug. 18, OpenAI disclosed that monitoring models during reinforcement learning training and evaluation can consume roughly 20% of the inference compute being monitored. The company also said it had paused reinforcement learning training for two weeks while it evaluated safety controls for planned frontier models.

  • Aug. 18 — OpenAI said monitoring is required for reinforcement learning training and tool-using evaluations involving models at Sol capability or above.
  • Aug. 18 — The company estimated monitoring overhead at roughly 20% of the inference compute being monitored, while noting that the cost varies across workloads.
  • Aug. 18 — OpenAI said its largest planned frontier training run remained on hold pending smaller-scale evaluations.
  • Aug. 7 — After determining that it could not rule out critical cyber capability in Astra, OpenAI extended monitoring to all Astra inference using tools. The company said the monitoring is designed to alert within 30 minutes of concerning activity.
Our read

Monitoring has usually been discussed as a security control. OpenAI has now put a measurable compute cost on running it. That changes the operating conversation: monitoring is part of the infrastructure required to run some AI workloads, not just a policy decision made around them.

The pause is significant too. OpenAI is showing that stronger safety controls can affect when and how a model is trained and released, not just what happens after deployment.

Operator takeaway: Ask providers what monitoring runs alongside your production workloads, how much compute it consumes and how that overhead is reflected in your capacity and cost planning.

Sources: ources: OpenAI, “Pacing model development in an era of cyber-critical capabilities,” published Aug. 18, 2026. OpenAI, “Responding to the next frontier of critical cyber capabilities,” published Aug. 7, 2026. Axios, Aug. 18, 2026, independently reporting the Preparedness Framework rewrite.

2 Every new Claude model now watermarks its text, and the detector is not built yet

Topics: AI GOVERNANCE & RESPONSIBLE AI

On Aug. 14, Anthropic published how its text watermark works. The watermark is live worldwide on models launched since Aug. 2, but the detection API is still to come.

  • Anthropic described its watermarking method, based on the SynthID-Text approach published by Google DeepMind in 2024. It changes the source of randomness used to select the next word.
  • The watermark applies worldwide to models launched on or after Aug. 2, 2026, rather than only in the EU.
  • Anthropic said a watermark detection API is coming, with implementation details still being worked out. Files use a C2PA content credential rather than a text watermark.
Our read

Anthropic has created a provenance signal that enterprises can receive now but cannot yet reliably check. That distinction is important. A watermark can indicate that Claude was likely involved in producing content, but it cannot establish authorship on its own, and the detection tooling needed to use the signal has not shipped.

For organizations using AI in customer-facing, regulated or records-sensitive work, the policy question comes before the technology question. What level of evidence is enough to treat content as AI-generated, and what happens when the detection result is unavailable or inconclusive?

Operator takeaway: Decide what evidence you need to identify AI-generated content, and document how you will handle output that cannot yet be independently detected.

Sources: Anthropic, “How Claude’s text watermark works,” published Aug. 14, 2026. Anthropic Help Center, “How Claude marks AI-generated content,” observed Aug. 26, 2026. Regulation (EU) 2024/1689, Article 50, applicable Aug. 2, 2026. TechCrunch and Euronews, Aug. 11, 2026, independently reporting the initial disclosure.

3 Token prices fell while hardware costs increased

Topics: AI OPERATOR

AI costs are moving in different directions. OpenAI cut its token prices, DeepSeek changed how it prices usage and reported server costs are rising.

  • Aug. 21 — OpenAI cut GPT-5.6 Sol from $5 to $4 per 1M input tokens and from $30 to $20 per 1M output tokens. The lower rate is described as a promotion running at least through Nov. 21, 2026.
  • Aug. 13 — OpenAI opened a limited preview of Ultrafast, running GPT-5.6 Sol at up to 14 times standard throughput and serving up to 750 output tokens per second through Cerebras.
  • Aug. 13 and Aug. 16 — DeepSeek made V4-Pro generally available and revised its pricing structure, with V4 Flash priced by cache hit versus miss and peak versus off-peak usage.
  • Aug. 22 — Bloomberg reported that prices for servers carrying NVIDIA AI chips could rise more than 15% in many configurations shipping in early 2027, citing higher memory costs.
Our read

Token prices are only one part of the cost of running AI. They can fall while infrastructure costs rise, and provider pricing can vary by throughput, cache state and time of day. Operators should track model pricing, usage and infrastructure costs separately rather than rely on a single cost-per-token figure.

Operator takeaway: Reforecast high-volume workloads using each provider’s current rate, note when promotional pricing ends and model infrastructure costs separately from token costs.

Sources: OpenAI API pricing page and API changelog entry of Aug. 13, 2026, both observed Aug. 26, 2026. DeepSeek API documentation change log, V4-Pro general availability Aug. 13, 2026 and revised rates effective 16:00 UTC Aug. 16, 2026. Bloomberg, Aug. 22, 2026, on NVIDIA server pricing, with Reuters reporting it could not verify. TrendForce conventional DRAM contract pricing, cited for its own findings.

4 AWS made data residency a setting rather than a contract clause

Topics: ENTERPRISE AI CLOUD & SOVEREIGN

Between Aug. 17 and Aug. 20, AWS expanded GPT-5.6 availability to more than 25 regions and introduced geographic inference profiles, including India-specific profiles that keep inference within the country.

  • Aug. 17 — Amazon Bedrock added GPT-5.6 Sol, Terra and Luna and introduced geographic and global cross-Region inference.
  • Aug. 20 — AWS documented the models across more than 25 regions. Geographic profiles route within one geography, while global profiles can route across commercial regions where the model is deployed.
  • Aug. 17 to Aug. 24 — Global cross-Region inference is priced lower per token than in-region and geographic inference for OpenAI models. Billing, quotas and logging remain in the source region.
  • Aug. 20 — India-specific profiles for GPT-5.6 Terra and Luna route only within India, across Mumbai and Hyderabad.
Our read

Data residency is becoming a workload-level configuration decision rather than a provider-level commitment. AWS now gives customers a way to specify where inference runs, but the lower-cost global option can route requests across commercial regions. For regulated environments, the inference profile itself becomes part of the architecture and governance decision.

The practical question is whether each production workload is using the configuration that meets its residency requirement.

Operator takeaway: Document the required residency for each production workload and record the inference profile that enforces it.

Sources: AWS, “Amazon Bedrock expands API support and introduces Cross Region Inferencing for OpenAI models,” What’s New, Aug. 17, 2026. AWS Machine Learning Blog, “Introducing cross-Region inference for OpenAI GPT-5.6 models on Amazon Bedrock,” Aug. 20, 2026. AWS, “Amazon Bedrock now supports OpenAI models in India,” What’s New, August 2026. Dataconomy, Aug. 21, 2026, independently reporting the Region count.

5 Thomson Reuters built its own model while becoming part of Google’s AI platform

Topics: OPEN VS. CLOSED MODELS

On Aug. 24, Thomson Reuters, a global provider of legal, tax and news information, launched its first proprietary large language model. Built on open-source technology and trained on decades of its own content, Thomson 1.0 launched one day before Google Cloud introduced Gemini Enterprise for Legal and Financial Services with Thomson Reuters among its connectors.

  • Aug. 24 — Thomson Reuters launched Thomson 1.0, built on open-source technology and trained on decades of its own legal, tax and news content.
  • Aug. 25 — Google Cloud launched Gemini Enterprise for Legal and Financial Services in preview, with Thomson Reuters among the connected data sources.
  • Aug. 25 — Connectors give Gemini Enterprise access through the Model Context Protocol to systems including iManage, NetDocuments, Everlaw, RelativityOne, Docusign, Harvey, Legora, CourtListener and Thomson Reuters.
  • Aug. 25 — Thomson Reuters connected HighQ to Gemini Enterprise for Legal.
Our read

Thomson Reuters is showing how proprietary domain content can become part of a broader enterprise AI platform. It built Thomson 1.0 on an open-source base using decades of its own legal, tax and news content, then connected that content to Gemini Enterprise. For regulated buyers, model selection is only part of the decision. The source and governance of the content, the permissions that carry into the AI environment and accountability for incorrect output all become part of evaluating the service.

Operator takeaway: Ask domain AI vendors which model they use, what content it was trained or grounded on, whether existing permissions carry into the AI environment and who is accountable for incorrect output.

Sources: Google Cloud, “Google Cloud Launches Gemini Enterprise for Legal,” press release of Aug. 25, 2026, and “Introducing Gemini Enterprise for Legal,” Google Cloud blog, Aug. 25, 2026. Thomson Reuters Institute, “Thomson Reuters and Google Cloud: Bringing Trusted Matter Context to Gemini Enterprise for Legal,” Aug. 25, 2026. Reuters, Aug. 25, 2026, independently reporting the Thomson 1.0 launch.

Other developments

1 OpenAI leased 8 gigawatts of Ohio capacity that NVIDIA is underwriting

Topics: ENTERPRISE AI CLOUD & SOVEREIGN

On Aug. 17, OpenAI agreed to secure approximately 8 gigawatts of capacity at the PORTS-Pike Technology Campus in Ohio under a 20-year lease. SB Energy will build, own and operate the site. NVIDIA is providing credit support for an initial 4.25 gigawatts, with the remaining 3.75 gigawatts optioned, and will invest $1.5 billion in SB Energy.

Our read

NVIDIA is helping finance the land, power and buildings needed to support its own demand. That is a different relationship from simply selling accelerators.

Operator takeaway: Do not model 2027 capacity on projects announced in 2026. Ask any provider quoting future capacity which phase is funded, which is optioned and what the first in-service date is.

Sources: NVIDIA newsroom release, Aug. 17, 2026. OpenAI, “OpenAI joins PORTS-Pike project,” published Aug. 17, 2026. SB Energy campus release, Aug. 17, 2026.

2 OpenAI said zero data retention survives the next model generation

Topics: AI SECURITY & COMPLIANCE

On Aug. 19, OpenAI said eligible API customers using zero data retention have prompts and responses discarded after processing, with customer content excluded from training unless the customer opts in. OpenAI also previewed Private Safety Processing, which evaluates misuse across related interactions and can use customer content wherever it is held.

Our read

OpenAI has put the zero-retention commitment in writing, but the mechanism behind the new safety processing capability is not yet fully documented.

Operator takeaway: Review the September technical paper against your data-processing requirements before relying on the combination in production.

Sources: OpenAI, “Offering Zero Data Retention for frontier models,” published Aug. 19, 2026. OpenAI API platform documentation, observed Aug. 26, 2026. The Next Web, Aug. 20, 2026, independently reporting the commitment.

3 Anthropic logged 14 incidents in 14 days, including an outage of its status page

Topics: AI OPERATOR

Anthropic’s status page recorded 14 incidents across nine of the past 14 days. A disruption on Aug. 16 affected claude.ai, platform.claude.com, the API, Claude Code and Cowork. On Aug. 14, the status page itself was unreachable for nearly three hours because of an invalid certificate.

Our read

A single platform-wide availability number would not describe these surfaces accurately.

Operator takeaway: Add an independent signal to your incident runbook and ask any provider quoting an availability number which service surface it covers.

Sources: Anthropic, status.claude.com incident history and ninety-day uptime panel, observed Aug. 26, 2026, with a retained export of the same date. BleepingComputer, Aug. 16, 2026, independently reporting the multi-surface disruption.

4 OpenAI published results for its own inference chip, normalized on rated power

Topics: AI OPERATOR

On Aug. 25, OpenAI reported that Jalapeño delivered 1.5 to 1.9 times more AI work per watt and 1.7 to 3.6 times lower end-to-end latency than the comparison systems in its testing. The results were normalized using each accelerator's published power rating.

Our read

The way a vendor measures power can change a per-watt comparison. In this case, the published ratios use rated power rather than measured sustained draw.

Operator takeaway: When a vendor quotes performance per watt, ask which power figure was used and how closely the test reflects your workload.

Sources: OpenAI, “Jalapeño’s first results show industry-leading speed and efficiency in AI inference,” published Aug. 25, 2026, presented at Hot Chips.

5 Alibaba confirmed an open checkpoint narrower than the model it serves

Topics: OPEN VS. CLOSED MODELS

On Aug. 20, Alibaba said it had launched Qwen3.8-Max and opened its model weights at 2.4 trillion parameters. The checkpoint itself became available Aug. 12. Alibaba also said Zhenwu M890 processors were already in commercial use through Alibaba Cloud, with more than 650 external customers across more than 20.

Our read

The open artifact and the served artifact may not be the same thing. That distinction is important when evaluating a model for self-hosting.

Operator takeaway: Before committing to an open-weight model, review the model card and the usage terms for the exact checkpoint you plan to deploy.

Sources: Alibaba Group Holding Limited, Form 6-K, Exhibit 99.1, filed Aug. 20, 2026, via SEC EDGAR. Hugging Face repository listing for the Aug. 12 checkpoint availability date.

Things to think about

For the leaders

Questions to consider.

  • Do we know how much monitoring adds to our inference costs? OpenAI estimates monitoring can consume roughly 20% as much compute as the inference being monitored. That overhead needs to be visible in capacity and cost planning.
  • Are any of our AI forecasts based on promotional pricing? GPT-5.6 Sol is currently priced at $4 per 1M input tokens and $20 per 1M output tokens through at least Nov. 21. If a production forecast uses a promotional rate, it should also account for what happens when that rate ends.
  • Does our availability requirement match what our provider actually measures? Anthropic’s published 90-day availability ranged from 99.36% to 100% across product surfaces. The availability figure in a contract should correspond to the service your workloads actually use.

For the builders

Items to act on.

  • Reforecast high-volume workloads using post-promotion rates: Record the rate and expiration date used in each forecast so temporary pricing does not become a long-term cost assumption.
  • Add an independent signal to your incident runbook: Anthropic’s status page was itself unavailable for nearly three hours on Aug. 14, highlighting the limits of relying on a provider’s status page as your only source for outage detection.
  • Check the license and usage policy for every open-weight model in production: A permissive software license does not necessarily describe every restriction attached to model use. Review both before treating a model as approved for production
  • Verify zero-data-retention settings in your own logs: OpenAI says the store parameter is forced to false for eligible zero-data-retention customers. Confirm that behavior in your environment rather than relying only on the provider commitment.

What comes next

Key dates and developments we’re watching.

  • Anthropic Sonnet 5 price increase: The introductory rate ends Aug. 31 and the standard rate applies. The change will show whether recent movement in published model prices extends beyond a single provider.
  • OpenAI Private Safety Processing white paper: OpenAI has targeted a broader rollout and technical paper for September. The capability is currently in testing with early customers. The paper should clarify whether cross-session misuse detection under zero data retention can be independently evaluated as a control.
  • EU AI Act requirements: On Dec. 2, machine-readable marking requirements apply to systems already on the market before Aug. 2, along with the new prohibitions described in the current draft. For organizations with existing AI deployments, that deadline will clarify what needs to be addressed.

Trends we’re monitoring

ENTERPRISE AI CLOUD & SOVEREIGN
Residency and isolation are becoming configurable controls

AWS expanded GPT-5.6 to more than 25 regions and added India-specific inference profiles that keep requests within the country. An isolated government deployment also reported 100% 90-day uptime while commercial surfaces ranged from 99.36% to 99.47%.

Operational implication: For architecture owners, residency is becoming a workload-level configuration decision. Record the inference profile each production workload uses so its geography is visible in the configuration.

Government and sovereign buyers should also confirm which product surface an availability figure covers and whether isolated deployments are measured separately from commercial services.

OPEN VS. CLOSED MODELS
Open models still require scrutiny beyond the license

Alibaba confirmed a 2.4 trillion-parameter checkpoint, while reports that the open artifact is narrower than the served model remain unconfirmed. Meta’s Muse Glimmer release also includes a separate usage policy alongside its Apache 2.0 license.

Operational implication: For teams evaluating self-hosted or open-weight models, the model artifact, license and usage policy all belong in the architecture decision. Verify that the checkpoint you can run is the same one you evaluated and that its terms support the intended use.

AI GOVERNANCE & RESPONSIBLE AI
EU requirements are enforceable while the U.S. framework remains unresolved

Article 50 transparency requirements under the EU AI Act have applied since Aug. 2. In the U.S., the Aug. 1 deadline for the framework described in Executive Order 14409 passed without published framework text as of Aug. 26.

Operational implication: For governance and compliance teams operating across regions, build requirements around the rules that are actually in force. EU transparency obligations can be incorporated into current controls; the unresolved U.S. framework should remain a dated open item rather than an assumption in the compliance plan.

AI SECURITY & COMPLIANCE
AI monitoring is becoming part of the operating cost

OpenAI paused reinforcement learning training, disclosed monitoring overhead of roughly 20% of the compute being monitored and committed to zero data retention for frontier models. It also previewed a cross-session safety system that is still in testing.

Operational implication: For security teams, monitoring is now part of capacity and cost planning as well as the risk model. Ask what monitoring runs alongside your workloads, how much compute it consumes and how that overhead is accounted for.

For those responsible for data protection, OpenAI’s cross-session safety processing raises a separate question: how does a system evaluate activity across sessions while maintaining zero data retention? The September technical paper should provide more detail before enterprises rely on that combination.

AI OPERATOR
AI costs are diverging across the stack

Token prices are falling while infrastructure costs are rising, and provider pricing is becoming more variable. OpenAI cut GPT-5.6 Sol to $4 per 1M input tokens and $20 per 1M output tokens, DeepSeek now prices V4 Flash by cache state and time of day, and reported server costs for NVIDIA-based systems are rising. Anthropic also recorded 14 incidents across nine of the past 14 days.

Operational implication: For platform and reliability owners, track model pricing, usage, monitoring overhead and infrastructure costs separately. For on-call teams, use independent monitoring rather than relying on a provider’s summary availability figure alone.

WORKFORCE SHIFT & OPEN LANE
Amazon is closing Mechanical Turk

Amazon announced that AWS Mechanical Turk will close Sept. 30, 2026, ending a 21-year run. The marketplace supported annotation and other human-review work used in AI development, and Amazon says it served more than 500,000 workers at its peak.

Operational implication: For organizations that use Mechanical Turk for annotation or human review, identify affected workflows before the shutdown, select a replacement and account for the resulting change in unit cost.

Sources: Alibaba Group, Form 6-K Ex. 99.1, filed Aug. 20, 2026, for the checkpoint confirmation. OpenAI publications of Aug. 18, Aug. 19 and Aug. 25, 2026. OpenAI API pricing page and DeepSeek API change log, observed Aug. 26, 2026. AWS What’s New of Aug. 17 and AWS Machine Learning Blog of Aug. 20, 2026. Anthropic, “How Claude’s text watermark works,” Aug. 14, 2026, and status.claude.com, observed Aug. 26, 2026. Amazon Web Services closure notice for Mechanical Turk, Aug. 25, 2026. meta-models/Muse-Glimmer-30B LICENSE and USAGE_POLICY.md on Hugging Face, observed Aug. 26, 2026. Regulation (EU) 2024/1689, Article 50, applicable Aug. 2, 2026. Executive Order 14409 at 91 FR 34565, Section 3.

Sources

Primary and official: OpenAI (“Pacing model development in an era of cyber-critical capabilities,” Aug. 18, 2026; “Offering Zero Data Retention for frontier models,” Aug. 19, 2026; “Jalapeño’s first results show industry-leading speed and efficiency in AI inference,” Aug. 25, 2026; “Responding to the next frontier of critical cyber capabilities,” Aug. 7, 2026; API pricing page and API changelog, observed Aug. 26, 2026). Anthropic (status.claude.com incident history and ninety-day uptime panel, observed Aug. 26, 2026). Alibaba Group Holding Limited (Form 6-K, Exhibit 99.1, filed Aug. 20, 2026). Amazon Web Services (Mechanical Turk closure notice, Aug. 25, 2026). Meta (meta-models/Muse-Glimmer-30B LICENSE and USAGE_POLICY.md on Hugging Face, observed Aug. 26, 2026). NVIDIA (PORTS-Pike newsroom release, Aug. 17, 2026). DeepSeek (API documentation change log, rates effective Aug. 14, 2026). Google (Vertex AI release notes and partner model deprecations, observed Aug. 26, 2026). EUR-Lex and the European Commission (Regulation (EU) 2024/1689, Article 50; Regulation (EU) 2026/1744). Federal Register (Executive Order 14409 at 91 FR 34565, Section 3, checked Aug. 26, 2026). Congressional Research Service (In Focus IF13268, July 9, 2026). SemiAnalysis (InferenceX benchmark). Bloomberg (NVIDIA server pricing, Aug. 22, 2026, with Reuters reporting it could not verify). Axios (OpenAI Preparedness Framework rewrite, Aug. 18, 2026). CNBC (Mechanical Turk closure and Amazon statement, Aug. 25, 2026). TrendForce (memory contract pricing, cited for its own findings).

Subscribe

Like this type of content?

Subscribe to The Rackspace AI Runbook to stay up to date with the latest operational intelligence.

© 2026 Rackspace Technology
AI Disclosure

The Rackspace AI Runbook is AI-assisted and reviewed by Rackspace Technology editorial and technical staff before publication.

Legal and Forward Looking Statements

The Rackspace AI Runbook is provided for general informational purposes only and reflects the opinions and analysis by Rackspace Technology as of the date of publication. It is not, and should not be relied upon as, professional, legal, financial, investment, tax, or technical advice, and is not a recommendation to take or refrain from any action. Third-party information is drawn from sources believed to be reliable, but has not been independently verified by Rackspace Technology. Readers should conduct their own diligence before acting. Rackspace Technology undertakes no obligation to update any information after publication.

Forward Looking Statements

This briefing contains forward-looking statements within the meaning of the safe harbor provisions of the Private Securities Litigation Reform Act of 1995, including but not limited to statements regarding Rackspace’s anticipated GPU deployment timelines, capital expenditures, utilization rates, industry trends and market outlook. These statements are based on current expectations and assumptions and are subject to risks and uncertainties that could cause actual results to differ materially, including those described in Rackspace’s filings with the SEC, including its most recent Annual Report on Form 10-K and Quarterly Reports on Form 10-Q. Rackspace undertakes no obligation to update these statements except as required by law.

Third-party data, analyst estimates, and commentary referenced herein (including regarding other companies’ earnings, capital expenditures, regulatory or other matters) have not been independently verified by Rackspace and are provided for informational purposes only. This briefing does not constitute investment advice, legal advice, or an offer to sell or a solicitation of an offer to buy any security.