• Electricity demand is now growing faster than energy suppliers can keep up with
• Volatile AI workloads cause unpredictable peaks and troughs in demand
• AI could actually help predict, despite also being the cause

With three in four (77%) electricity execs now believing that data center energy demand will grow faster than utilities can keep up with, two-thirds (68%) expect electricity shortages to become more commonplace as demand for AI soars.

New data from a Capgemini report reveals just how unpredictable AI energy demands can be, with 77% admitting they struggle to accurately forecast demand amid volatile AI workloads.

During this year’s World Cup, one scene repeats itself game after game: Several players take the field with holes in the calves of their socks. Social media is rife with theories about the supposed competitive advantage this might give them. But the practice isn’t new. It has been seen at the European Championships, the Olympic Games, and other international competitions over the past decade. Still, science has yet to find evidence that it improves performance.

Professional soccer socks are, by design, form-fitting. In addition to holding shin guards in place, they provide support to the ankle, the arch of the foot, and the calf; they help manage moisture and reduce foot movement inside the cleat to improve stability. This design principle has been used in professional soccer for decades. Although materials have evolved to become lighter and more durable, they are still primarily based on synthetic fibers such as polyester, nylon, and spandex.

But quite a few players have complained that the socks are too tight and cause a tingling and numb sensation in the calf area. The discomfort is so great that, halfway through a game, they cut several holes in the calf area to “release tension” and run better.

There is a biomechanical component to this sensation. During a sprint or a change of direction, the largest muscle in the calf contracts and increases in thickness to generate the force that propels the athlete forward. This change in shape occurs thousands of times during a game. For some, the repeated expansion of the muscle is enough to create a sensation of pressure when the sock exerts constant compression on the calf.

Over time, the practice of cutting holes in socks has taken on an almost intuitive explanation among the players themselves: splitting open the fabric allows the muscle to “breathe,” relieving pressure and reducing the likelihood of pain or cramps. However, specialists in sports medicine and recovery point out that there are no studies demonstrating that cutting holes in socks provides any benefit. In fact, much of the research on compression garments concludes that, when properly designed and fitted, they can help limit muscle inflammation after intense exertion.

Despite the lack of evidence regarding physiological benefits, the practice continues to spread among professional soccer players. Today, it is considered primarily an anecdotal phenomenon, based on each player’s personal experience rather than scientific evidence. Furthermore, the rules of the game do not prohibit modifying socks, as long as the equipment remains safe and the shin guards remain properly covered. (A soccer player, however, cannot play with a torn jersey.)

Given the lack of scientific evidence, several specialists believe that part of the phenomenon could be explained by the player’s own perception of comfort. In high-performance sports, the feeling of comfort can influence the confidence with which an athlete competes. If a soccer player believes a piece of clothing is restrictive, eliminating that perceived discomfort can make them feel freer to run, accelerate, or change direction—even if their performance remains objectively unchanged.

Though there is no evidence that cutting the socks provides a competitive advantage or reduces the risk of injury, that does not mean the sensation of discomfort is imaginary. The perception of pressure, restriction, or comfort depends on multiple factors, ranging from anatomy and individual sensitivity to the athlete’s past experiences. In other words, two players may react differently while wearing exactly the same equipment.

For now, it seems the cutting of socks will continue. The available evidence points to a mechanism similar to that of other sports rituals: Its effect is primarily psychological, not necessarily physiological.

There’s an important distinction between AI that just works today, and AI that lasts at scale. Many companies optimize hard for the first one without ever asking whether they’re building the second.

Velocity without discipline and strategic direction is a liability, not an asset. The hardest part of building AI at scale isn’t getting a model to work once. It’s building systems that continue to work, scale beyond individual teams and use cases, and improve consistently over time.

Today’s AI systems do more than just predict and optimize. They converse, reason, and increasingly take action. An autonomous system making decisions on a traveler’s behalf creates a very different set of expectations around reliability, governance, and accountability. As AI takes on more of those roles, the principles behind how these systems operate matter more than ever.

We have spent years applying AI and machine learning (ML) across the traveler journey — from personalization, ranking, and recommendations, to fraud prevention, customer support, and, more recently, generative and agentic AI experiences. That depth of experience is what led us to develop a set of ML and AI principles to guide how we build, deploy, and evolve AI systems across our company.

The goal is simple: Make sure the systems we build create real business value, scale, and operate safely. These principles define how we measure, design, govern, and operate our systems.

From principles to practice

Publishing principles is the easy part. The harder and more important work is turning them into operating mechanisms: Recommendations, requirements, tooling, and release processes that teams actually use.

We have begun using ‘Agentic Release’ tollgates: A set of recommended and, in some cases, required checks before launching agentic AI features. These tollgates translate principles like clear ownership, risk-based governance, evaluation, safe rollout, and monitoring into concrete expectations for teams.

Some of these recommendations and requirements are already being automated and integrated into the software development lifecycle (SDLC). Over time, the goal is for these expectations to become embedded in how we design, evaluate, approve, launch, and monitor AI systems from the start.

Outcomes: Measuring what actually matters

The first test for any model is whether it improves a business outcome and, ultimately, the traveler experience — not whether it just improves a technical metric.

1. Align models to metrics with business impact: Every ML effort must tie directly to a key business outcome or traveler experience metric. Technical optimizations are useful midpoints, not end goals.

2. Optimize for return on cost: The value a model creates has to justify what it costs to develop, train, and monitor, plus the operational complexity it adds. Favor solutions that deliver lasting impact relative to what they cost to run.

3. Justify complexity against strong baselines: Complexity should be earned, not assumed. Start with a strong baseline: An existing general model, a simple heuristic, an off-the-shelf solution. Reach for specialized models or more complex architectures only when simpler options genuinely can’t meet the bar.

4. Require both offline and online evaluation: No model goes to broad deployment on offline validation alone or jumps straight to A/B testing. Every model must perform in both offline and online evaluations. Over time, our offline evaluations should reliably predict what we see online.

Design: building systems that scale beyond the teams that build them

Getting a model to work is one challenge. Making its value extend beyond a single team or use case is the harder one.

1. Build on shared foundations; specialize only when justified: Favor shared, platform-wide foundations for core capabilities, data representations, and model building blocks. Specialization should build on those foundations, not spin up isolated stacks, so when the foundation improves, the gains flow across the organization.

2. Treat data as a first-class product: A model’s quality is bounded by the quality of its data. We need to maintain robust pipelines, clear lineage, reproducibility, and reusable features built with documented ownership, clear schemas, and SLAs that other teams can rely on.

3. Prioritize generality over local optimization: When two approaches perform similarly, favor the one whose learnings, assets, and operating patterns can be reused across teams, brands, and use cases. We should optimize not just for local performance, but for how quickly improvements can diffuse across the company and compound over time. 

4. Minimize and sunset manual business rules: Manual rules are sometimes necessary for policy, safety, or compliance, but they should be explicit and reviewed regularly, never silent patches for weak models or a source of permanent maintenance debt.

5. Reproducibility and traceability by default: Training data, features, configurations, evaluation results, deployment versions, and key decisions should all be documented and recoverable. That’s what lets you debug a production issue months later and hand off ownership without losing institutional knowledge.

Trust: ownership, governance, and operating responsibly at scale

The bar for deploying AI isn’t just “does it work?” It’s “can we stand behind it?” Trust isn’t something you add at the end; it’s earned over time and maintained across the full lifecycle of every model we ship.

1. Assign clear ownership and accountability: Every model needs defined ownership across its lifecycle — a business owner, a product owner, an AI owner, and an operational owner. These don’t need to be four people, but the responsibilities must be explicit. Who’s accountable for outcomes? Who responds if the model drifts? Who answers the incident at 2 a.m.? Without this in place, models become orphaned and problems surface with no one to own them.

2. Adhere to standards and governance: AI and ML models must use approved platforms and comply with established company standards, release gates, and governance processes. Operating outside these guardrails requires a clear, defined path to remediation or deprecation, rather than an open-ended exception. 

3. Govern proportionally to risk: The level of review, evaluation rigor, and human oversight should scale with a model’s impact. A customer-facing model that affects pricing or availability for millions of travelers demands a far higher bar than an internal tool used by a small team. For high-impact, safety-sensitive, or highly autonomous systems, human-in-the-loop checkpoints are built in from the start. 

4. Design for fairness, privacy, and transparency: We actively test for unintended bias, have strong data guardrails, and favor explainability when decisions meaningfully affect users. These are incorporated from the start, not added on.

5. Design for safe rollout, rollback, and control: Deployments are progressive, with rollback paths, fallback mechanisms, and circuit breakers ready before launch. The ability to safely undo a deployment matters as much as the ability to ship it.

6. Monitor continuously and adapt: Once live, teams must actively monitor quality, drift, latency, cost, and business performance and retrain or recalibrate when the data shifts. A team should always be able to explain how its model is performing now, not just how it performed when it launched.

These principles do more than define how we build. They define what we’re willing to ship and how we stand behind it. In a world where AI systems are increasingly consequential and make real decisions for real travelers and partners, these standards matter. Applied consistently, they build responsible AI that lasts.

Xavi Amatriain is Chief AI and Data Officer at Expedia Group

Xavier will share more details about Expedia’s architecture during his session at VB Transform on July 14 at 11:10 am PT. He will discuss: “Expedia’s blueprint for building autonomous agents for high-stakes transactional systems.”

Interested in attending VB Transform 2026? Register here. A select number of complimentary passes are also available to senior technology leaders. Contact us to get yours.

Welcome to the VentureBeat community!

Our guest posting program is where technical experts share insights and provide neutral, non-vested deep dives on AI, data infrastructure, cybersecurity and other cutting-edge technologies shaping the future of enterprise.

Read more from our guest post program — and check out our guidelines if you’re interested in contributing an article of your own!

A year ago the Ryzen AI Halo, AMD’s tiny new AI workstation, would have offered devs and machine learning enthusiasts an Nvidia DGX Spark-like experience at a fraction of the cost.

Unfortunately for AMD, time and the ongoing memory shortage, which both AMD itself and Nvidia are partially responsible for, hasn’t been kind to the consumer electronics industry.

Launching at a hair under $4,000, the AI Halo is still cheaper than the Spark at its new MSRP of $4,699, but is now a much tougher sell than when you could get the same hardware for as little as $2,000. 

That’s right. The 128 GB AI Halo is based on year-old technology. Its main selling point, and what AMD has spent the past several months getting right, is the packaging. Much like with the Spark, you’re not just buying the machine but all the software and documentation you need to run and fine-tune enterprise-grade models and AI agents like OpenClaw and Cline, locally.

Many will, understandably, balk at the price — $4,000 is a down payment on a car — the system is still one of the most affordable options for those who need more than the 32 GB that the highest-end graphics card can provide. 

Not long ago, building a workstation with 128 GB of video memory would have set you back at least $20,000, and that was before the RAMpocalypse. This puts systems like DGX Spark and AI Halo in a rather unique position.

The Hardware

The Ryzen AI Halo was clearly inspired by the DGX Spark. Measuring in at 5.9 x 5.9 x 1.79 inches, the black and silver system shares a nearly identical form factor to its competitor.

Rather than gold aluminum siding, AMD has opted for a more subdued look with a textured top cover adorned by its logo and an LED light bar that wraps around its perimeter. The chassis itself is well ventilated with intake located along the front of the system sides and heat exhausting out the back.

The back of the system is adorned with four USB-C ports, one of which is dedicated to power, while the remaining three offer connectivity (1x USB 3.2, 2x USB 4.0) for storage and peripherals. The AI Halo supports display out on all three of those ports as well as via HDMI 2.1b . A single RJ45 network port provides 10 Gbps of connectivity for those who prefer wired connectivity over the onboard WiFi 7 radio.

One thing you won’t find on the back of the AI Halo are QSFP ports for high-speed networking. The DGX Spark features a 200 Gbps ConnectX-7 SmartNIC for clustering multiple devices together. The AI Halo does still support clustering if you happen to pick up multiple systems, but with only one such system on hand, we can’t say how big a difference the slower networking actually makes.

AMD’s Ryzen AI 395+, which you may recognize from its codename Strix Halo, sits at the heart of the system. This SoC isn’t new, having been  on the market for more than a year now. In fact, we pitted the Pro variant of the chip running in HP’s Z2 Mini against the DGX Spark’s GB10 SoC back in December 2025.

The chip is equipped with 16 Zen 5 cores clocking up to 5.2 GHz along with an RDNA 3.5 GPU with 40 compute units putting out around 56 teraflops of dense FP16 performance under ideal conditions.

While Strix Halo can be obtained with as little as 32 GB of LPDDR5X memory, the AI Halo is packing 128 GB as standard. That’s enough to run models of up to 200 billion parameters in size, at 4-bit precision that is. Out of the box, our system was configured to share up to 75 percent, or about 96 GB, of that with GPU. However, at least on Linux, you can extend this to nearly the system’s full capacity. 

That memory is connected to the SoC by a 256-bit bus good for about 256 GB/s of bandwidth — more than you’d get on a (non-Pro) Threadripper system.

Bandwidth is a major bottleneck for LLM inference, with token generation directly proportional to how fast the memory actually is, and because the AI Halo’s memory hangs off the GPU, it can take full advantage of it.

While 256 GB/s is a lot for DDR5, it is dwarfed when you compare to the GDDR or HBM found in consumer and datacenter GPUs. The RTX 5090 delivers 1.7 TB/s of bandwidth, making it admittedly high — for models small enough to fit in that card’s 32 GB of VRAM.

We’ll talk about performance in a bit, but this really gets to the hardware’s core value proposition. For most local AI enthusiasts and devs, memory capacity is the biggest bottleneck.

It doesn’t matter how many teraflops your GPU can push or how fast your memory is, if you don’t have enough of it in the first place. At 16-bit precision you need about 2 GB of memory for every billion model parameters. At 8-bits, it’s a 1:1 ratio and, at 4-bits, you need just 512 MB for every billion parameters.

If you’ve toyed around with local LLMs in Ollama or LM Studio before you’re almost certainly running 4-bit weights, which is why you can cram a 20 billion parameter model onto a consumer graphics card with as little as 16 GB of VRAM. 

Unfortunately, there are a lot of AI workloads that aren’t easily quantized or require substantial quantities of memory in addition to what’s used to hold the model weights. But once you venture beyond low precision inference, memory quickly becomes a major constraint. For example, a full fine tune of a modest 7B parameter can easily consume upwards of 100 GB of memory.

This is where systems like the AI Halo or DGX Spark really shine. They may not be the most powerful or the fastest systems, but there’s not much that you’d want to do that you couldn’t thanks to their ample memory capacity.

As we’ve shown in the past, Strix Halo is more than capable of running larger more capable models exceeding 100 billion parameters or fine-tuning models up to 70 billion parameters, something that’s well beyond the means of consumer graphics cards.

What the AI Halo actually buys you

If the chip isn’t new, you might be wondering what exactly the Ryzen AI Halo buys you over another Strix box, like HP’s Z2 Mini G1a we reviewed back in December. Back then, that system retailed for around $3,000. Its price has since surged to nearly $4,900.

If you’re already familiar with AMD’s HIP and ROCm stacks and reasonably comfortable with Linux, the answer is not a lot. AMD even has playbooks specifically for early adopters of its Ryzen AI products. So, if you jumped on a Strix Halo system before DRAM prices hockey sticked, you’re really only missing out on the conveniences that the preinstalled software brings.

With that said, we’re willing to bet most folks considering AI Halo are probably dipping their toes into ML and AMD’s software ecosystem for the first time.

ROCm is a heck of a lot easier to get running on Ryzen APUs and Radeon graphics than it used to be, but we’d be lying if we said that it’s always easy. The same is true of Nvidia and CUDA to a lesser extent. Some steps are easier, while others like GPU passthrough for containers require jumping through additional hoops.

That’s not even to mention PyTorch compatibility, which can vary from app to app. Regardless of which platform you buy into, wrangling dependencies is still a mess.

Both the AI Halo and DGX Spark’s core value prop is helping customers avoid as many of these headaches as possible by combining validated hardware with pre-installed dependencies and well documented playbooks that walk you through common use cases.

In other words, it’s an AI lab in a box.

What’s it like using the AI Halo

The AI Halo ships with your choice of Linux or Windows 11. The review unit AMD provided us with, came equipped with a lightly-modified version of Debian with the 6.18 Linux Kernel, Gnome desktop environment, ROCm 7.13 preinstalled, and a slew of preinstalled AI apps and frameworks, like ComfyUI and vLLM.

For anyone who’s used Linux before, the experience should be quite intuitive. Upon first boot, a startup wizard will guide you through the process of creating your user profile, connecting to the network, and updating the device.

Once you are logged in, AMD’s Ryzen AI Developer Center launches automatically and provides quick access to resources and system settings.

As of this writing, AMD’s developer docs include 19 playbooks covering everything from the basics of running LLMs and image models on the device to building full blown agents with OpenClaw.

We walked through most of these as part of our review process and with a few exceptions we were able to run them with minimal troubleshooting. We did have to ask an LLM for help debugging AMD’s PyTorch fine-tuning scripts. Thankfully, the selection of pre-downloaded models were capable enough to identify the single line fix required to get them running again.

While most of AMD’s playbooks were more than adequate, we found its vLLM getting started guide a little lacking. It was easy enough to get it running —AMD has written a wrapper that abstracts the creation and deployment of the inference server in a Docker container — but the guide doesn’t discuss how to select a model, much less configure it.

vLLM is an incredibly popular inference server broadly deployed in production. This makes it all the more disappointing that AMD’s documentation isn’t more comprehensive.

One bright spot we’d like to highlight is Lemonade Server. The app comes preinstalled and provides an LM Studio or Ollama-like experience tuned specifically for AMD hardware. It’s built atop a number of different model runners including vLLM, Llama.cpp, Whisper.cpp, Stable Diffusion.cpp and others. There is even support for a limited selection of models which will run on the system’s NPU.

Perhaps the most attractive use case for the system is as a host for AI agents.

When AMD announced the system, it was keen to highlight how small local models, like Qwen 3.6-35B-A3B, were now good enough to replace larger proprietary models for many coding workflows.

The company went so far as to claim that, for full-time software devs, the system could save as much as $750/month compared in API expenses they’d pay to a cloud-based LLM. We plan to put those claims to the test in a future article. Beyond AI coding, we also expect the system to be quite popular as a platform for running harnesses like OpenClaw.

Given the software’s significant, not to mention numerous security implications, running it locally with container isolation is probably the safest option, and its large memory capacity means that you’ll have access to larger more capable models.

Performance

In terms of performance, the Ryzen AI Halo is a bit of a mixed bag.

In memory bound applications like LLM inference, the system matches and in some cases narrowly outpaces Nvidia’s more expensive DGX Spark. Hanging the memory off the GPU instead of the CPU benefits the AI Halo here.

In compute bound workloads, like fine tuning, image generation, or batch processing, the gap grows considerably. We plan to dig deeper into how the AI Halo performs in a future article, but, in our initial testing, we don’t see a major uplift in performance compared to our earlier testing.

We’re also not sharing vLLM performance figures for the AI Halo just yet as our initial testing with AMD’s provided build produced results we’re not confident in.

Depending on the workload and precision, you can expect the Spark’s GB10 APU to be anywhere from 2x to 3x quicker in compute-bound AI workloads.

A big piece of this is down to the fact that Strix Halo wasn’t really intended for this use case. AMD’s RDNA 3.5 GPU tech lacks support for floating point precisions lower than FP/BF16. It does offer INT8 support, but only by upcasting to FP16, which means no performance uplift from dropping to lower precision.

On paper, the GB10 delivers roughly twice the 16-bit performance, three times that at FP8 and twice again at FP4. This is one of the biggest critiques of AMD’s current consumer hardware roadmap, and why we continue to see such a wide performance delta. While its software has improved and its datacenter kit supports FP8 and FP4, the AI Halo is stuck on an older microarchitecture.

But, as we mentioned in our initial Strix Halo vs GB10 head-to-head, whether you’ll even notice the performance deficit really depends on what you’re doing.

AI benchmarks, including ours, usually disable prefix caching. This allows us to accurately evaluate the accelerators’ performance, but isn’t representative of how you’d actually use the model.

In a chatbot or AI agent, the prefix caching keeps the accelerator from getting bogged down by caching previously-computed information so that only new data has to be processed. With it disabled, the problem size grows with each prompt processed and each response generated.

We’re currently in the process of developing a series of new tests that take advantage of caching and other functionality, like multi-token-prediction to measure performance in agentic applications like code generation. We look forward to sharing the results of those tests soon.

Should you buy it?

Strix Halo wasn’t a cheap part before RAMageddon and it certainly isn’t now — $4,000 is a lot of money. But for the right person, it’s still a relative bargain.

If you’re interested in learning more about local AI, we recommend starting with what you’ve already got before considering dropping this kind of cash on an AI-first system like the AI Halo.

If usage based APIs are out of the question and your existing graphics card is no longer cutting it, GB for GB the Ryzen AI Halo is still much cheaper than workstation cards from either AMD or Nvidia. For reference, a 96 GB RTX Pro 6000 is much, much faster and offers nearly as much addressable memory as the AI Halo, but has an MSRP of $13,250. Oh, and that’s just for the GPU; you still need to plug it into something with at least that much DDR5 on board.

And so the question becomes how badly do you need the VRAM and how valuable is AMD’s documentation and support? Enthusiasts willing to blaze their own trail might be able to save a buck by picking up an OEM Strix Halo box and configuring it themselves.

On the flip side, for those willing to spend a bit more money, Nvidia’s DGX Spark also offers fantastic documentation and a fair bit more computational grunt, which again means faster fine tuning, image generation, and prompt processing. The number of tok/s is limited by memory bandwidth.

With that said, the DGX Spark is much more of an appliance, which means, if you buy this thinking you’re going to run agents on it and later decide it’s not worth the trouble, it’s less likely to end up collecting dust on the shelf. Because it’s just an x86 PC under the hood, the AI Halo is perfectly capable of running Windows or your preferred Linux distro, if you decide local AI just isn’t for you.

Oh,  and if 128 GB of VRAM isn’t enough for you, AMD has a refreshed version of the system on the way with 192 GB of LPDDR5X memory and slightly higher clocks. ®

Amazon has knocked $100 off the Apple Watch Ultra 3, dropping Apple’s premium smartwatch to $699.99 for a limited time.

Amazon has cut the price of the Apple Watch Ultra 3 to $699.99, delivering a solid $100 discount on Apple’s premium smartwatch. While we’ve seen the wearable dip to as low as $649 this year, today’s offer remains one of the best widely available deals on the current-generation model.

Buy Apple Watch Ultra 3 for $699.99

The $699.99 deal applies to the 49mm GPS + Cellular Apple Watch Ultra 3 with a Black Titanium Case and Black Ocean Band or the Natural Titanium Case with an Anchor Blue Ocean Band. At $100 off MSRP, it’s a compelling opportunity for shoppers who have been waiting for a meaningful price break on Apple’s most capable smartwatch.

Built for outdoor adventures, endurance athletes, and anyone who wants Apple’s most rugged wearable, the Apple Watch Ultra 3 features a durable titanium case, GPS + Cellular functionality, extended battery life, and advanced health and fitness tracking.

The Apple Watch Ultra 3 discount is one of several Apple hardware deals currently available at Amazon. Savings are also available on AirPods, iPads, Macs, and Apple Watch Series 11 models, with even more discounts listed in our Apple Price Guides, where we follow the lowest prices across Apple’s product lineup.

More Apple deals

Offering a rare glimpse at the priorities of a top spy organization, Canada’s Communications Security Establishment said it conducted a handful of state-authorized hacks last year in order to disrupt the operations of drug traffickers, violent extremists, and a ransomware gang.

The disclosures in the Canadian intelligence agency’s annual report underscore some of the main national security threats that face Canada and its closest allies: ranging from the import of illegal drugs to cyberattacks. The spy agency, CSE, is tasked with collecting foreign intelligence, defending government systems, and disrupting online adversaries.

Published last week, the report says the CSE last year carried out three foreign “active cyber operations” — the term agency uses to describe its cyberattacks on overseas operations that threaten Canadian national security and public safety.

One of the operations, per the report, targeted cybercriminals outside of Canada who were brokering the sale of chemicals used to create the synthetic opioid, fentanyl. The CSE collected intelligence on the brokers, then conducted an operation that “disrupted and diminished their ability to operate,” the report said.

Another active operation involved the collection of signals intelligence — data produced from electronics and internet-connected devices — on an overseas extremist group that was spreading violent ideology and recruiting members, including in Canada.

The report said the agency analyzed the group’s organization, reach, and potential vulnerabilities to conduct an operation that “successfully undermined the group’s credibility and limited their ability to radicalize and recruit new members.”

Another operation involved disrupting a ransomware-as-a-service operation that let hackers rent access to a ransomware gang’s infrastructure to launch destructive extortion attacks. The CSE said its signals intelligence unit identified how the gang worked against the healthcare, transportation, and business sectors in Canada, then used an active cyber operation that “rendered the group’s infrastructure inoperable.” The operation also deleted much of the data on the gang’s servers.

The agency said it undertook concurrent “technical disruptions” against 10 of the most significant ransomware gangs targeting Canada to “make parts of their infrastructure unusable.”

The report did not say where the hackers, extremists or the ransomware gang were located, or the specifics of the operations that the CSE used to target them. It’s not uncommon for spy agencies to conduct cyberattacks against their adversaries, but such operations are seldom disclosed or detailed to protect the methods and techniques used.

Fort Meade, Maryland-based Cyber Command, which conducts cyber operations for the U.S. government, regularly carries out “hunt forward” operations that involve sending cyber teams to allied nations to secure their networks and disrupt cyber operations launched by adversaries. The number of U.S.-led hunt forward operations have risen from a few handful during 2018 to more than two dozen during 2025.

Canada’s CSE said it also carried out one defensive cyber operation during the year to target a phishing campaign aimed at Canadian federal government institutions and other important systems. The agency said it disrupted the group’s infrastructure and “degraded their ability” to target Canadians.

Meta-owned chat app WhatsApp started to roll out username reservations for its 3 billion users earlier in June. The username feature is not active, but you can claim your username and start using it whenever the feature becomes available this year.

With usernames, people will be able to share their WhatsApp contact without having to disclose their phone number. This could be useful for people who want others to contact them on WhatsApp, but don’t want to share their information or their phone number. For businesses, it might be easier to share a name than a phone number to their customers.

Here is how you can reserve your username:

• Go to Settings > Account and tap on the Username option under the “Your Account” section
• If you are setting up your username for the first time, you will get a “Create username” option, and then you can type in and choose your username.
• If the username you chose is not available, WhatsApp will suggest some variations if you tap the “suggest a username” option.

WhatsApp is reserving certain usernames of public figures and entities, so you won’t be able to reserve them for yourself. If you already have a Facebook or an Instagram username, you can log in through either of the services and reserve your handle as a username too.

Once you set the username, you can go to the same menu and change it by tapping on the “Edit” button on the top right-hand corner. Alternatively, you can also delete your username.

WhatsApp also allows for an extra layer of protection with a username key. You can limit people who contact you from “Everyone” to “People who know my key” from the username menu. This means that people who know your username will also type in a four-digit key before contacting you for the first time. Users can save the key or generate a new key at any time.

The username feature will go live in the coming weeks. Until then, WhatsApp is only allowing people to claim their usernames to avoid duplication.