Tuesday, 28 July 2026

Your GPU dashboard says 70% utilization. On paper, the cluster is busy. In practice, a large chunk of that time is spent with your $40,000 accelerators sitting idle, waiting on a file that lives three network hops away on a NAS box. The compute queue is empty, and the pipeline is fine. The problem is that data is just somewhere else. This is the awkward truth underneath most stalled AI projects. The constraint in modern AI infrastructure stopped being storage capacity years ago. Now, it's more about data placement and access. What matters is where files live and how they get to GPUs, along with how much copying happens in between. In that sense, AI infrastructure has become less of a storage capacity problem and more of an operational data problem. The Hammerspace Data Platform takes that as its starting point. It sits between your compute and the storage you already own, from NAS to object stores and even the NVMe drives bolted into your GPU servers. It makes all of that data addressable through a single global namespace. Instead of moving data to wherever the GPUs are, the architecture makes the compute aware of where the data already lives. As a result, rather than treating each storage system as its own operational silo, Hammerspace separates the data layer from the underlying infrastructure, allowing heterogeneous storage, sites, and clouds to operate as part of the same coordinated data environment. Applications and AI pipelines access that data through standard protocols such as NFS, SMB, and S3, without proprietary clients or application rewrites. Fragmentation is the bottleneck, not bandwidth Data fragmentation is a big problem for enterprises embarking on an AI journey. Training sets are scattered across departments, sites and clouds. "The data is in disparate groups and disparate orgs and disparate silos within a company," says Jonathan Flynn, director of applied systems at Hammerspace. "Having the data in a curated data set for you just to go train is rare. It has to be collected. It has to be moved around from system to system, and then the curation needs to happen in order to actually do the training on it." The fragmentation often leaves pipelines copying and staging files between systems that were never designed to talk to each other. None of this shows up on a storage IOPS chart, but it will visibly affect training velocity. According to Gartner, 57% of organizations believe that their data isn't AI ready. Alarmingly, two thirds of executives believe that no one in their organization understands all of the data they've collected and how to access it. That seems hard to swallow, until you recall that Facebook's engineers have admitted the same thing. You can't orchestrate what you can't see. Mike Bloom, who covers AR architecture at Hammerspace, says the default vendor response makes the problem worse. "They'll go to a vendor that will promise them that if they sweep the floor and throw out all of their legacy storage arrays, their brand will solve the problem," he says, adding that's like throwing the baby out with the bath water. "Those data sets that are all over the place? They're not sitting in a corner. They're sitting on legacy storage arrays." The NVMe you already paid for There is also a less obvious idle resource in most AI environments: the NVMe inside the GPU servers themselves. A modern HGX or DGX box ships with eight to sixteen NVMe drives, each hanging off four lanes of PCIe. Almost every orchestration layer treats that capacity as local scratch space, used by one server and invisible to the rest of the cluster. Hammerspace calls this "stranded" capacity, and it is now meaningful. It amounts to hundreds of terabytes per server, with two-petabyte GPU servers on the roadmap. Pull all of it into a shared namespace and you have a new layer that Hammerspace calls Tier 0. It uses storage you already paid for, attached to a network you already deployed. Flynn argues this layer is structurally faster than anything sold as a separate appliance. "Tier one is typically oriented around storage capacity. A 2U box, 24 NVMe, or 40 NVMe with some of the Dell systems in there," he calculates. "That's 96 lanes or 192 lanes of PCI Express, with maybe one or two 400 gigabit NICs, which gives you 16 or 32 lanes. So the over subscription just in the one box is massive." His more provocative claim is that it is also the cheapest tier in the rack. The compute and the network are already there. The drives (at least in the case of customers buying GPU servers) are already in the bill of materials. Compared with racking and stacking a dedicated all-flash array, adding metadata servers and a few data movers to existing GPU nodes barely registers as a procurement event. Assimilating what you already own Ripping and replacing infrastructure takes time most teams don't have. The Hammerspace approach is assimilation, which the company describes as a metadata-only operation: scan the existing NAS, ingest the directory tree into the global namespace, and redirect mounts. The bytes never move. Hammerspace says that fast deployment is a key benefit of this approach. Data access is restored almost immediately, even while assimilation continues in the background. Underneath this, the source-of-truth NetApp, Qumulo or VAST array keeps serving the bytes, while Hammerspace presents a unified view on top. That has practical consequences. If something tagged as a training input changes from being a tier-two archive file to a hot input, a policy (Hammerspace calls this an "objective") can trigger an instance copy onto tier 0 without users having to do anything. "Nobody's running a copy. Nobody's running an rsync command," Flynn says. "It's all orchestrated based in the file system." That same orchestration layer can also support retrieval-augmented generation (RAG), inference, and agentic AI workflows, where distributed enterprise data needs to be continuously curated, governed, and made accessible without relying on large-scale data copying. Once the training job finishes, that tier 0 copy is automatically vacated. The clean-up matters because the alternative (letting a hot tier fill up) creates a quality-of-service problem for everything else trying to land there. "Other architectures that have a hot tier and a cold tier often have an issue where the hot tier becomes congested and that endangers the quality of service for the pipeline," Bloom says. “Rather than requiring organizations to rebuild infrastructure around AI, the Hammerspace approach is designed to operationalize the storage, cloud, and compute environments enterprises already have in place. Standards-based, with some asterisks Hammerspace's positioning leans heavily on the word "standard". The Samsung-Hammerspace submission that landed inside the top 10 of the IO500 10-Node Production benchmark in November 2025 used standard Linux, the upstream NFSv4.2 client, standard NVMe SSDs and IP-over-InfiniBand. There was no proprietary client, and no custom kernel modules. The company submitted its own results to MLPerf Storage v2.0 showing linear scaling out to 420.8 GB/s across 140 GPUs on five nodes with GPU utilisation above 96%. That kind of performance is not achievable with traditional NFS architectures, which struggle with the parallel access patterns common in large-scale AI environments. Instead, Hammerspace runs on parallel NFS (pNFS). Instead of letting a single server handle file metadata transfer alongside data transfer, it creates a layout map that the client can then use to transfer data from multiple servers in parallel. That became the RFC 5661 standard in 2010. Hammerspace was also instrumental in extending pNFS in NFSv4.2 in 2018, introducing the Flex Files extension. This is what lets pNFS work with real-world hetergeneous storage across cloud tiers, legacy files, and multi-site deployments. The larger implication is that open, standards-based infrastructure is no longer inherently at odds with AI-scale performance, challenging the assumption that enterprises must adopt proprietary storage stacks to support large-scale AI workloads. "With the performance improvements that we contribute into the upstream, we're actually seeing a decades-old file system transmute into a parallel access system that can rival WEKA, Lustre, and GPFS," Flynn says. Multi-site and sovereign by default Once a single global namespace spans on-prem arrays, cloud object stores and the NVMe inside GPU boxes, the next questions are jurisdictional. Where can a given file legally live? Who is allowed to copy it? The platform handles this through the same objectives mechanism used for performance tiering. Tag a dataset as EU-only and the orchestration layer will exclude it from North American volumes. Tag it as HIPAA-bound and write-once-read-many rules apply. Because those policies operate at the data layer rather than within individual storage silos, governance persists even as data moves across clouds, sites, and performance tiers. That is becoming increasingly important as AI pipelines, inference workflows, and agentic systems operate across distributed infrastructure rather than within a single environment. That matters more in 2026 than it did two years ago, since such operational flexibility also changes the economics of AI infrastructure expansion. The SSD supply situation has tightened. NAND and DRAM prices climbed through 2024 and into 2025, driven by AI build-out and hyperscaler hoarding. Buying your way out of a data-movement problem by adding another all-flash array is harder when the flash is harder to get. A control plane that understands workload, location and policy together is now a valuable procurement workaround. Real-world usage The most useful data point about whether any of this matters at scale is Meta. The company runs two 24,576-GPU clusters used to train Llama 3 and deploys Hammerspace specifically to enable live job debugging and real-time code propagation across the training pipelines. If a company with effectively unlimited engineering resources still hits a data-movement ceiling at that scale, the enterprises running a fraction of the workload are almost certainly hitting it too, and the standard answer of "buy more GPU" does not address a problem one layer below the compute plane. Flynn put the underlying joke about NFS politely. "The joke I always heard was, NFS is not for speed." That used to be true. The newer claim, that an open, standards-based file system can sit underneath an AI factory and feed it, casts the venerable file protocol in a new light. ICustomers will likely want to see an independent benchmark of this system's performance against the likes of VAST, WekaIO and NetApp in heterogeneous customer environments, using test systems not designed by the vendor. Nevertheless, it looks promising. In the meantime, the data placement architecture conversation is certainly the right one to be having. Sponsored by Hammerspace.

source https://www.theregister.com/ai-and-ml/2026/07/27/ai-has-changed-data-architecture-but-storage-hasnt-caught-up/5255880

Monday, 27 July 2026

Google has created a new taxonomy to describe cybercrime outfits, seemingly abandoning a Microsoft-led effort to create consistent names. The Big G announced its new schema on Saturday in a post that notes its 2022 acquisition of Mandiant and its subsequent incorporation into a new team called the Google Threat Intelligence Group (CTIG). Now that two have become one, Google reckons they need consistent naming conventions to describe cybercrime crews. The result is a two-word schema in which the first word “is a unique and memorable term chosen to represent the specific actor.” If security folk have already applied a particular moniker Google will use it, otherwise it will randomly generate a word “to remove bias.” Google says the second word “categorizes threat clusters by motivation, attribution, or activity type based on which category we consider to be most important for defense and response strategies.” More on that later. Google has decided on the following names: CASTLE to describe crews from the People’s Republic of China ION for threats from Iran NEPTUNE for North Korean attackers RELIC for Russians COMET for cybercrims who aren't backed by a state Google’s post notes that other infosec industry players have developed their own schemas for describing threat actors and says the web giant is therefore “intentionally seeking to keep this system as simple as possible to streamline operations and facilitate mapping to other naming taxonomies.” That’s an odd position, given that in 2025 Microsoft and CrowdStrike tried to spark an industry-wide effort to apply consistent names to threat actors. As we noted at the time, the existence of multiple naming schemas means that researchers often refer to the same group by ten different names. Researchers use the names Seashell Blizzard, IRIDIUM, VOODOO BEAR, BE2, UAC-0113, Blue Echidna, PHANTOM, BlackEnergy Lite, and APT44 to refer to the same entity – Russia's Military Intelligence Unit 74455. With most orgs using multiple security tools and therefore receiving threat intelligence security info from many vendors, users must try to understand which crews they’re trying to defend against. At the time, sources told us Google and Mandiant were keen to adopt the Microsoft-led scheme. Google’s new announcement suggest the relationship either wasn’t consummated or didn’t last. Back to the issue of possible bias, as in 2024 China's National Computer Virus Emergency Response Center (CVERC) complained that western companies choose names like “Typhoon,” “Panda,” or “Dragon” to describe Chinese cybercrime groups. CVERC suggested names that reflect English language idioms, such as “Hurricane” or “Koala” are more appropriate. For what it’s worth, “Koala” is a word from the language spoken by the Darug people, the indigenous tribe who lived around Sydney, Australia, prior to British colonization. Koalas are utterly supine creatures that sleep 18 to 22 hours a day, and a mention of the marsupials may therefore not spur defenders to action, even if the creatures’ habits do perhaps describe the behavior of some sleeper malware. ®

source https://www.theregister.com/security/2026/07/27/google-goes-it-alone-with-a-new-cybercrime-crew-taxonomy/5278749
WHO, ME? Mistakes happen, and when readers of The Register make them, we like to share those tales of woe in a Monday column we call "Who, Me?" It's our guide on how not to get ahead in the modern workplace. This week, meet a reader we'll Regomize as Clay, who in the 1980s was the most junior member of the management team on a Swedish construction site. "We had two site engineers, and they were the only ones with computers," he explained to The Register. This was a time before PCs had become ubiquitous, so Clay was curious about the machines. "One lunch break, I asked the junior engineer if I could try his PC," he told us. The junior had little choice but to comply, so Clay sat down at the machine and used the only command he knew. "It worked," he told Who, Me? "But unfortunately, that command was 'DEL *.*'" Clay had therefore deleted everything in whatever directory the engineer had allowed him to access. "Thankfully, my colleague was very relaxed and forgave me, so I got to keep my job," he told The Register. "But 'DEL *.*' still haunts me!" The moral to this story seems clear: do not under any circumstances let a suit take control of computers! Have you let a user wreak havoc on your machine? If so, click here to send an email to this column, so we can show readers how not to cause chaos on some future Monday. ®

source https://www.theregister.com/software/2026/07/27/manager-showed-off-his-dos-prowess-with-a-command-that-wiped-data/5278057
The 13th flight of SpaceX’s Starship made it off the launchpad on Friday and ticked off just about everything on the company’s to-do list. After delays and engine replacements, Elon Musk’s colosso-launcher took to the skies at beer-o’clock on Friday evening – 5:51PM Texas time. One hour, five minutes and 21 seconds later, Starship made a controlled splashdown in the Indian Ocean, where it floated after landing. SpaceX says it was able to gather critical data on the performance of Starship’s heatshield, and that the craft made “a dynamic banking move to mimic the trajectory that future missions returning to Starbase will fly.” Gathering data on Starship’s heatshield performance will help SpaceX ensure the craft is re-usable. Simulating missions that land at Starbase, SpaceX’s Texas home, builds toward future missions that launch and land at the same facility, speeding turnarounds for re-usable hardware. The test flight also saw SpaceX test a new routine for de-orbiting the Super Heavy booster used to hoist Starship into space. “The booster successfully completed the high thrust portion of the boostback burn with all 33 engines, the first time with a Super Heavy V3, before ending the burn early,” SpaceX said. “It attempted to relight its engines for the landing burn, with a subset successfully igniting before experiencing a hard splashdown in the Gulf.” That part of the mission didn’t go perfectly, as SpaceX hoped for a softer landing and more engines lighting to make it possible. Once Super Heavy and Starship separated, the latter vehicle used its six Raptor engines to reach desired speed and orbit. It then deployed 20 Starlink V3 satellites. SpaceX crew verified the sats worked and half a dozen of them got a look at Starship’s heatshield. While the satellites were functional, SpaceX did not intend them to form part of the Starlink constellation and allowed them to re-enter Earth’s atmosphere. Or as the company’s mission report put it, the satellites “demised upon reentry approximately 20 minutes after deployment.” Starship performed one more trick on its way back to Earth, by starting one of its Raptor engines while coasting through space. The success of that test again demonstrated tech that will be needed for future missions, in this case flights that push Starship into sustainable orbit – or allow it to reach a trajectory capable of reaching the Moon, as NASA envisages will be the case for future Artemis missions that land humans on Earth’s permanent natural satellite. SpaceX boss Elon Musk said he hopes the next Starship test flight will see the Super Heavy booster caught by robot arms at Starbase, another step towards improved reusability and turnaround times between flights. ®

source https://www.theregister.com/science/2026/07/27/spacex-just-about-nails-starship-test-flight-13/5278725
ASIA IN BRIEF Taiwanese mega-manufacturer Foxconn has adopted Singaporean hyperconverged infrastructure vendor (HCI) Arcrfra for some GPU virtualization workloads and to replace VMware in some remote offices. Arcfra launched in 2024 and the next year earned a place on analyst firm Gartner’s Market Guide for Full-Stack HCI Software. Last week, Arcfra launched an update to its Neutree model-as-a-service platform, adding native GPU virtualization and model governance capabilities. The company said Foxconn has adopted Neutree “to modernize distributed factory infrastructure and improve how AI models were delivered, managed, and observed across environments.” The Taiwanese giant has also used Neutree to “accelerate model deployment, improve operational visibility, and build a scalable foundation for future AI and intelligent manufacturing workloads.” Foxconn considers AI a critical part of its plans: The Register last year heard chairman Young Liu hail generative AI’s potential to vastly improve the company’s factories. The Register asked Arcfra to detail its relationship with Foxconn and the HCI upstart pointed us to this case study that states “Foxconn's global branch companies relied on traditional VMware virtualization for their IT systems. This legacy setup was becoming increasingly difficult to manage and scale across a distributed global footprint [and] led to high construction costs and a significant increase in operations and maintenance overhead.” Foxconn apparently deployed Arcfra “across its branch factories in Mainland China, Taiwan, Vietnam, and North America” and uses the Singaporean platform for critical intranet, manufacturing management, ERP and production line management systems. Arcfra also hosts Foxconn's DevTest environments and Virtual Desktop Infrastructure workloads. “The legacy VMware virtualization + SAN storage architecture was successfully replaced, providing a modern, scalable foundation ready to accommodate future business growth and technology adoption,” Arcfra claims. The Register asked Foxconn for further information about its decision, but has not received a response at the time of publication. VMware’s owner, Broadcom, changed strategy to target large entities like Foxconn. Broadcom says the overwhelming majority of its target customers have adopted its flagship Cloud Foundation suite, but The Register has also noted many big-name dissenters, among them Tesco, Western Union, Allstate Insurance – and now Foxconn. Better news for Broadcom In better news for Broadcom, the chip design side of the business has struck a $200 billion deal with Samsung’s memory and foundry businesses. “On the memory front, Samsung and Broadcom plan to pursue a strategic collaboration for the supply of industry-leading memory solutions, including High Bandwidth Memory (HBM), supporting Broadcom’s next-generation AI accelerators,” states Samsung’s announcement of the deal. “In foundry, the companies’ collaboration focuses on Samsung’s 2-nanometer (nm) and below process technologies for Broadcom’s products, including Wireless Broadband Communications (WBC) solutions. The collaboration is expected to extend to advanced packaging technologies built on Samsung’s 2nm process, including 2.3D and 2.5D integration, to enable higher-performance and more power-efficient AI and networking silicon.” “By combining Samsung’s memory and foundry expertise with Broadcom’s AI and connectivity leadership, we aim to continue to deliver technologies that power the next generation of AI infrastructure,” said Charlie Kawwas, the president of Broadcom’s Semiconductor Solutions Group. Broadcom has a huge order book for custom accelerators and needs foundry capacity to build those products and its other offerings. Given the global shortage of fabrication capacity, and Samsung’s status as arguably the world’s second-most-sophisticated fab operator, Broadcom has every reason to be happy it has secured access to the manufacturing resources it needs. Infosys names next CEO Indian tech services giant Infosys last week named Ashiss Kumar Dash as its next CEO. Infosys says Dash is currently “global head for a business portfolio that comprises over 12 industry verticals.” He will replace current Managing Director and CEO Salil Parekh on April 1, 2027. Parekh led the company for nine years. The change is an orderly handover rather than a vote of no confidence in Parekh, although Infosys last week posted [PDF] its Q1 results which included a forecast of revenue growth of between 1.5 and 3 percent, down from previous guidance of possible 3.5 percent growth for the full financial year. The company said its previous guidance assumed an economic upswing that hasn’t happened. India orders takedown for Jack Dorsey’s Bluetooth social network Twitter founder Jack Dorsey has used the renamed platform to share an order from the government of India that requires GitHub to take down BitChat – the decentralized peer-to-peer messaging app that can use Bluetooth mesh networks for offline communication. The order Dorsey shared justifies the takedown request on grounds that Delhi has powers to compel communications services providers to cease service to prevent public disorder, riots, or terrorism, but that authorities can’t act against decentralized messaging infrastructure. At the time of writing, The Register was able to access the BitChat repo. “The government of India does not like technologies like BitChat and wants it taken down,” Dorsey wrote. China fines Trip.com operator $770m for monopoly practices China’s State Administration for Market Regulation on Saturday announced it has fined the Trip.com Group $770 million for monopolistic practices. Beijing went after Trip.com for the behavior of its Ctrip brand, which targets Chinese-speaking customers. The regulator alleged that Ctrip “forced hotel merchants to accept exclusive cooperation agreements and manipulated hotel prices through technological means, thus exacerbating the industry's ‘involutionary’ competition.” The fine may interest regulators around the world, because Trip.com and its sub-brand Skyscanner are popular outside China. ®

source https://www.theregister.com/virtualization/2026/07/27/foxconn-drops-vmware-adopts-hyperconverged-upstart-arcrfra-for-workloads-including-ai/5278684

Sunday, 26 July 2026

GitHub and PyPI (Python Package Index) have introduced a time-based mechanism in the Dependabot dependency management tool to protect against supply-chain attacks and to limit their impact. [...]

source https://www.bleepingcomputer.com/news/security/github-pypi-add-time-absed-defenses-against-supply-chain-attacks/
President Trump has expanded his Ratepayer Protection Pledge to include power companies, datacenter developers, cooperatives, and state governments, saying the move will shield consumers from rising energy costs driven by the datacenter boom. In a speech at the Environmental Protection Agency (EPA) HQ in Washington, Trump said the pledge will now extend across the full chain of parties whose decisions determine household bills. This includes the utilities that supply power, the developers that build the facilities, and the state authorities that regulate energy rates and infrastructure. "We're here today to continue the incredible progress we're making in communities nationwide to ensure that as new datacenters go up, and they're going up all over, electricity bills for American families will actually come down," he declared. The Ratepayer Protection Pledge was created earlier this year, partly as a response to growing anti-datacenter sentiment among ordinary Americans, especially those who were seeing their utility bills jump. Much of the concern stems from the need for energy firms to invest heavily in new generation capacity and grid upgrades to serve the facilities being built, many for the AI market. The original signatories of the pledge – the "Munificent 7" of Amazon, Google, Meta, Microsoft, OpenAI, Oracle, and xAI – agreed to cover the full cost of any extra resources required to satisfy their energy demands. But as was pointed out at the time, these hyperscalers do not set the rates ultimately paid by consumers; utilities and state regulators play crucial roles there. The expanded pledge now brings those parties into the tent. According to the White House, more than 200 additional utilities, datacenter developers, cooperatives, and states have now joined the pledge. The White House claims the pledge covers roughly 80 percent of the power delivered to American homes and businesses, supposedly protecting 263 million people when a datacenter is built nearby. Trump went on to say that many datacenter developers will have to generate their own power on site, effectively turning themselves into utilities. "It's hard to believe, but you need double the electricity that we have right now, maybe even more than that, to really fulfill what you want to do," Trump said. "We're leading China [in AI] by a lot, and using our old grid would not have worked. And I came up with the idea that you build your own plant. This way nobody can complain," he added. The Reg believes many datacenter operators were already generating their own on-site power before Trump claimed responsibility for the idea. "We're insisting that AI datacenters and big tech companies pay their own way. And that's what they're doing, and they're happy to do it, because this way, they're going to be able to function, and function brilliantly. They're going to have a lot of electricity left over and they'll put that into the grid, so we'll actually end up with more electricity," Trump claimed. But as The Register pointed out previously, the text of the Ratepayer Protection Pledge makes no mention of enforcement. There are no apparent penalties should any of the signatories fail to prevent consumer bills rising because of demand from AI datacenters, so this appears to be very much a voluntary agreement. We asked the White House and the EPA what actions might be taken if signatories to the pledge were found to be failing in their commitments, and will update if we get a response. The measure seems likely to be put to the test, as the latest data from Synergy Research estimates the total capacity of US datacenters will double over the next three years, driven by an aggressive build-out by hyperscale operators. The pipeline of future large facilities known to the research biz currently stands at almost 1,500 worldwide, with almost half of those in America. That represents around 45 gigawatts of extra IT capacity set to be added over the next few years. Synergy chief analyst John Dinsdale says that availability of power and rising local concerns over server farms are crimping many new plans for facilities. "But it is also clear that datacenter developers will continue to find ways around those issues and that booming demand will continue to drive aggressive capacity growth. Over the next five years, the US will continue to account for well over half of the world's operational datacenter capacity." ®

source https://www.theregister.com/on-prem/2026/07/26/trump-expands-voluntary-pledge-to-keep-datacenter-costs-off-household-power-bills/5278346
This week marks 15 years since a Space Shuttle last returned from orbit and the end of NASA's Space Shuttle program. Space Shuttle Atlantis landed at the Shuttle Landing Facility (SLF) at Kennedy Space Center 15 years ago this week, marking the final mission for the program. STS-135 was originally designated STS-335, the Launch On Need (LON) mission for the previous STS-134 flight of Space Shuttle Endeavour. LON missions had been a feature of the Space Shuttle program following the Columbia disaster. If a Space Shuttle was damaged, another could be launched at short notice to rescue the crew. NASA assigned Launch On Need flights separate STS-3xx designations, so the rescue mission for STS-116 was STS-317, STS-117 was STS-318, and so on. There were exceptions (a notable one was the STS-125 Hubble servicing mission, which had STS-400 ready to go if anything went wrong), but the Space Shuttle program should have ended with STS-134. However, lawmakers and NASA managers opted to make STS-135 the final Space Shuttle mission. There could be no Launch On Need mission waiting in the wings this time around – the Space Shuttle program was being wound down – so the crew would have had to come down from the International Space Station (ISS) aboard Soyuz capsules if Atlantis could not return to Earth safely. There were also only four crew members, a figure not seen since the STS-6 mission of Challenger in 1983. The crew was commanded by Christopher Ferguson, who would later join Boeing's Commercial Crew Program and was assigned to (although did not fly) Boeing's calamity capsule, the Starliner. The pilot for STS-135 was Douglas Hurley, who went on to fly the first crewed test flight of SpaceX's Crew Dragon in 2020. Rounding out the crew were mission specialists Sandra Magnus and Rex Walheim. The launch occurred on July 8, 2011, and Atlantis returned from orbit on July 21, bringing the Space Shuttle program to a conclusion. It wasn't, however, the end of crewed spaceflight for the US, although the gap that followed was considerably greater than expected or hoped. After the Space Shuttle retired, the US was dependent on Russia for getting its astronauts to and from the ISS. NASA later awarded Commercial Crew contracts to SpaceX and Boeing to restore launches from US soil, but it took SpaceX until 2020 to get the first humans to the outpost, and Boeing until 2024. The latter's mission was marked by ignominy due to failures and faults during the mission that meant managers opted to send the capsule back to Earth empty from the ISS and have the Starliner flight test crew return in 2025 aboard a SpaceX vehicle. NASA and Boeing have yet to set a definitive date for when a crew might venture to the ISS once again aboard Starliner. All of which, 15 years after a Space Shuttle returned from orbit for the last time, has left the US space agency in a bit of a pickle. Instead of depending on the Space Shuttle, the plan was to reduce risk and add redundancy to US capabilities with two providers, but things haven't worked out that way. To make matters worse, there is uncertainty about how much longer SpaceX will continue to fly the Crew Dragon beyond its contracted missions. The vehicle is reusable, but no more are planned to be manufactured, and SpaceX reckons that each should be good for 15 flights, with some refurbishment. This should be enough to get through to the end of the ISS program and beyond, but in the longer term an alternative will be required. For SpaceX, this will likely be Starship. The fate of the Space Shuttles themselves is also not completely set. Atlantis has been staged in a facility at Kennedy Space Center as if in orbit, and the California Science Center has mounted Space Shuttle Endeavour on an external tank and solid rocket boosters, as though ready for launch. The fate of Space Shuttle Discovery is, however, uncertain. Certain lawmakers would very much like to transport the retired orbiter from the Smithsonian's Steven F. Udvar-Hazy Center in Virginia to Houston, Texas. For others, well, there's always a used Orion capsule. ®

source https://www.theregister.com/science/2026/07/26/the-last-space-shuttle-returned-to-earth-15-years-ago/5277279
Steam discussion forums are being abused in ClickFix attacks that pretend to be fixes for game and computer problems but actually infect devices with cryptominers. [...]

source https://www.bleepingcomputer.com/news/security/steam-forum-clickfix-attacks-infect-gamers-with-xmrig-cryptominers/

Saturday, 25 July 2026

OnTrac parcel delivery company is informing that hackers breached its corporate network and may have accessed personal details belonging to its customers. [...]

source https://www.bleepingcomputer.com/news/security/ontrac-notifies-customers-of-data-breach-after-network-hack/
A threat actor used the open-source Hermes AI agent in unattended "YOLO" mode to automate post-exploitation activity during an alleged breach of Thailand's Ministry of Finance. [...]

source https://www.bleepingcomputer.com/news/security/hermes-ai-agent-used-to-automate-attack-on-thai-finance-ministry/
The FreeBSD project froze its ports repository on Wednesday. The reason turns out to be a slightly embarrassing Git-related oopsie where a version of Copilot got uploaded somewhere it should not have been. The announcement of the 2026 Ports Repository Freeze went out on July 21 and remained in effect the following day, as explained in a message on the freebsd-announce mailing list. The mail delicately skirted around exactly what happened: « The commit in question severed our ports tree mirroring to github.com due to their filesize hard limit of 100MB, and introduced a blob of questionable licensing into the repository history. » The offending commit is this one. It’s not a disaster; the problem is that the Ports repository is automatically mirrored to various places, including a read-only Github mirror – and as Github’s docs say, “GitHub blocks files larger than 100 MiB.” There is already an official FreeBSD port of Copilot, but FreeBSD terminology is slightly confusing here: the “port” is effectively a sort of package that allows the Linux binary to run inside FreeBSD’s Linux emulation, called the Linuxulator. It isn't a native FreeBSD version of Copilot, and the package is not meant to include the actual Copilot CLI binary – partly because that is under its own custom license. That’s what FreeBSD’s Kyle Evans meant by “questionable licensing”. We don’t blame anyone for using any available resources to help with using GitHub. Navigating Linux, FreeBSD, and worst of all Git is hard, especially the last one. Git is aptly named – it’s not an acronym, it’s a real word: someone annoying or unpleasant. It is, however, now more or less the de facto standard version control system of the FOSS world. Despite not being a developer, the Reg FOSS desk worked with Git on a daily basis for over four years – blame the Docs as Code philosophy – and developed a deep and abiding dislike for it. It’s not just us: it’s in an XKCD comic, so it must be true. (This vulture has directly lived the experience described in that comic.) Personally, we always found Git much harder work than the tar command. It should come as no surprise that multiple teams are working on compatible alternatives. A Game of Thrones Trees Just the day before some FreeBSD developer’s regrettably public mishap, a new version of one of those alternatives appeared: Game of Trees version 0.127. Game of Trees, known as Got for short, is a Git-compatible version control system (VCS) developed by contributors to the OpenBSD Project. It’s been in development since 2019, and we feel that the project has a nice line in self-deprecation – starting with the homepage’s project description: “a version control system which prioritizes ease of use and simplicity over flexibility.” This is, we suspect, in response to Git’s self-description, which says that it is “designed to handle everything from small to very large projects with speed and efficiency.” We also like the Got project goals and especially the FAQ, which really does not beat about the bush: « Does Got aim to replace Git? No. Got does not aim to replace Git. Got can be used instead of Git (for some tasks), or in addition to Git. If you are already using Git and are happy with it, you don’t need Got. » And even more succinctly, under the anchor “pointless”: « What’s the point of all this? Why not just use Git? If you are wondering why Got even exists, you can just ignore it. » Got isn’t the only tool that aims to remain compatible with Git, but simplify the experience. Gitless is another, which describes itself as “a simple version control system built on top of Git,” and says that it’s “easy to learn and use.” Unfortunately, development seems to have gone quiet: the last release appeared the same year that Got appeared. Another (and even younger) Git-compatible VCS is Jujutsu, often called just “Jj”, and not to be confused with the traditional Japanese martial art Jiu Jitsu. Jujutsu the VCS has lots of documentation, but if it has a weakness, it's that it rather assumes that you already know your way around VCS use in general and Git in particular. If that’s not the case for you, you might find Jujutsu for Everyone by Remo Senekowitsch more helpful. ®

source https://www.theregister.com/os-platforms/2026/07/24/dev-accidentally-commits-copilot-binary-to-freebsd-ports-repo/5278458
Hackers are changing the DNS settings on Wi-Fi devices at hotels and conference centers to redirect users to fake Microsoft 365 login pages. [...]

source https://www.bleepingcomputer.com/news/security/hackers-hijack-hotel-wi-fi-dns-to-steal-microsoft-365-accounts/

Friday, 24 July 2026

A new Dolphin X remote access trojan claims to use an AI-powered profiling feature to score and rank infected users, helping cybercriminals identify which victims should be targeted first. [...]

source https://www.bleepingcomputer.com/news/security/new-dolphin-x-malware-uses-ai-to-rank-high-value-targets/
You can take your vibe-coded project elsewhere. Codeberg, a volunteer-run code hosting community, has decided that AI-authored software is no longer welcome. On Thursday, Codeberg announced that the members of Codeberg e.V., the Berlin-based non-profit overseeing the code hosting service, had voted to ban "vibe-coded projects" and declared that Codeberg would not use users’ code or data for AI training due to its impact on Free, Libre and Open Source Software (FLOSS). The vote follows ongoing efforts by Codeberg to prevent automated software (bots) from taxing its infrastructure with excessive network requests. Authors Bastian Greshake Tzovaras, Otto Richter, and William Zijl argue that AI companies are shifting costs to others and damaging online communities in the process. "LLMs are so costly that companies externalize the costs on a massive scale – on those who don't use them and society at large," they wrote in a blog post. "Increased hardware prices, energy use and environmental damage – we all pay for it!" They point to the cost of Codeberg's SSD and memory hardware as an example, noting that a drive that only a few years ago cost €700 (~$800) now costs €3,700 (~$4,200) – if it's even in stock. The result is that Codeberg has been forced to raise prices. The authors also call out the proliferation of projects that often involve a solo developer "working with a statistical machine that turns energy into code." They fault these folks for not having any community and argue it's unreasonable for Codeberg to spend its limited CI/CD and storage resources on ghost projects. But the vote isn't simply about unfair resource consumption. It reflects broader unease among Codeberg members about the damage AI coding models are doing to the FLOSS community. AI-driven price hikes, they contend, are broadening the digital divide by making personal computers less affordable, forcing more people toward corporate-owned cloud services. And beyond the environmental harm of increased water and energy use, the Codeberg authors argue that LLM use is undermining the foundation of trust and community that makes FLOSS work. "The widespread use of LLMs in FLOSS is instead becoming a multidimensional attack on the trust between contributors and the very idea of convivial collaboration itself," they state. LLMs magnify maintainers' workloads, create confusion around whether projects will be maintained, and "lead to 'license laundering', where copyleft code is stripped of its reciprocity requirements by 'generating' it out of the training data." "As we want to center on human collaboration, we will not actively support or engage in the creation of LLMs and will not put our limited resources to use for storing single-use software that would pollute our FLOSS commons," the authors conclude. As a consequence of the community vote, projects developed and maintained mostly by an AI agent are no longer welcome at Codeberg and are urged to move to other hosting options. This is reflected in amended Terms of Use language: "You must not share projects that mostly consist of code written by 'generative AI'-tools (including services such as Claude, OpenAI Codex). Such projects having an unclear copyright status … and furthermore have little safeguards to ensure that they do not include harmful code." Enforcement of the ban seems unlikely, however, unless a project draws attention to itself, given Codeberg's statements about limited resources and its overburdened workforce. Support for the vibe-coding ban was substantial but not overwhelming, with some celebrating the decision and others condemning it. Among Codeberg members, 358 voted in favor, 144 voted against, and 14 abstained. About half the active members voted. "I think this is a very bad move, and the people behind Codeberg should re-consider their stance," said Armin Ronacher, creator of Flask and one of the co-founders of AI agent biz Earendil. On its way toward Free, Libre, and Open Source Software equilibrium, Codeberg also decided to ban cryptocurrency projects, citing a similar move by SourceHut in 2023. A proposed amendment to make it Codeberg's stated purpose "to oppose discrimination and promote a diverse FOSS community" passed with a two-thirds vote but is not yet merged. The protection extended to philosophical outlook does not cover belief in AI. ®

source https://www.theregister.com/ai-and-ml/2026/07/23/codeberg-gives-vibe-coded-projects-the-toss-promotes-human-floss/5277717
Origin Energy has confirmed that an unauthorized party accessed and subsequently leaked customer data online, exposing sensitive personally identifiable information (PII), among others. [...]

source https://www.bleepingcomputer.com/news/security/australian-energy-provider-origin-says-data-breach-exposes-client-data/
A malvertising campaign on the Bing search service is pushing a fake Claude desktop app installer hosted on a legitimate Claude.ai domain to deliver the SectopRAT malware. [...]

source https://www.bleepingcomputer.com/news/security/fake-claude-app-promoted-by-bing-ads-pushes-sectoprat-malware/

Thursday, 23 July 2026

South Korea disclosed that hackers breached the National Diplomatic Academy's online education system for ten months and stole personal information belonging to current and former employees of the Ministry of Foreign Affairs (MFA), including overseas diplomats. [...]

source https://www.bleepingcomputer.com/news/security/south-korea-discloses-data-breach-impacting-diplomats-worldwide/

What happens when programmers get to vote on a complete ban on slopcoded software on their code platform? Members of Codeberg were asked to vote on a proposal to completely ban slopcoded projects from Codeberg, and in what should not be a surprising outcome to anyone not overcome with “AI” hysteria, the vast majority voted in favour of the complete ban: over 70% of Codeberg members voted to ban slopcoded projects entirely (358 in favour, 144 against, 14 abstentions).

Of course, this is not a surprising outcome. Stripped down, programming is a form of artistic expression, and programming is no different than writing, painting, composing, or any other artistic endeavour. I think it’s safe to say writers, painters, composers, and similar creatives are against “AI”, so it’s only natural programmers feel the same; poll after poll shows the overwhelming majority of respondents – usually well over 70-80% – are against “AI”.

The pro-“AI” accounts on OSNews often try to paint my anti-“AI” position as extremist, but in reality, I’m just voicing how 70-80% of people clearly state they feel. I have zero skin in this game, zero outside pressure to please any bosses to get that promotion, zero pressure to conform to avoid getting laid off, zero pressure to not contradict upper-management. I can speak freely, openly, and without fear of retaliation. And as Nikhil Suresh explains in his harrowing from-the-trenches article AI Mania Is Eviscerating Global Decision-Making, that’s a massive asset.

The vast majority of people – including your friends, family, and co-workers – really hate “AI”. You can either accept this, or be left behind.



source https://www.osnews.com/story/145583/codebergs-programmer-user-base-overwhelmingly-votes-to-ban-slopcoded-projects-form-its-platform/
After cutting over 4,000 jobs due to AI, fintech biz Block is back with Buzz, a shared workspace where humans and bots can collaborate in ways that are more auditable, sovereign, and secure than what you can do in chat tools such as Slack. Block's human-bot co-op is built upon a turducken of tech jargon: The platform is free and open source. It's based on the decentralized Nostr protocol, so there's cryptographic identity. It's "sovereign," a naively optimistic term readers of Neal Stephenson's Snow Crash should recognize, which in this context means self-hostable. And it's intended as a replacement for Slack, GitHub, and various other communication and collaboration tools. If "Buzz" sounds familiar, that's because Google used that name in a social media faceplant more than 15 years ago. For those who missed the first go-around, Google Buzz, a failed social media service, gave rise to Google+, also a failed social media service. Block appears to believe that a decade and a half is sufficient for a brand cleanse. The project's GitHub repo offers a more apologetic assessment: "Yes, it's another AI-adjacent developer tool. We're sorry. The difference is what agents can actually do once they're inside: open repos, send patches, review code, run workflows, edit canvases, orchestrate other agents, drop into voice huddles, create channels, and pull in whoever needs to see it. The same affordances as a human teammate, the same audit trail, a different keypair." You can already sic software agents on collaborative workspaces. Block's main insight is that it would be useful to link AI agents with cryptographic identities. Others have already arrived at that conclusion. Hence OWASP's Agent Name Service, DNS for AI Discovery, Estonia's digital IDs for agents, and so on. But Buzz's badging of humans and bots with cryptographic key pairs is bound to tick governance boxes. "Every company is going to need a place where humans and agents work together," said Bradley Axen, head of AI capabilities at Block, in a statement. "The question is whether that place is proprietary or open. We built Buzz because we believe it should be open." Moat-seeking tech incumbents would probably disagree about the need for openness, even though they're fond of using the word without applying it. We note that OpenAI sells closed AI. And Anthropic's decision to disallow third-party tools from using Claude subscriptions highlights the seemingly inevitable path from openness to barriers when revenue is at stake. What's more, it's not obvious that every company will need people and bots in the same space. There's a strong case for keeping humans and agents apart because they work at different speeds. Git at least was built for handling many distributed code edits, pull requests, and merges. It's hard to see how people and bots can share a text-based communication space unless the bots are rate-limited or just talk among themselves. "The bet is that one community can do what teams currently fake with chat, forges, bots, CI dashboards, release tools, search indexes, and a pile of glue code," Block's Buzz developers state. "Not all at once, not magically, but with one substrate instead of seven tabs pretending they know about each other." If tools for these sorts of things didn't already exist, and no large tech companies had designs on this space, Buzz might face less daunting odds. But it's worth a shot. ®

source https://www.theregister.com/ai-and-ml/2026/07/22/fresh-off-ai-layoffs-block-now-wants-to-whack-slack-with-agent-human-collab-tool/5276529

Wednesday, 22 July 2026

The US military is adding autonomous gun-based counter-drone systems intended to reduce its reliance on expensive interceptor missiles. They also have the potential to kill humans. Defense robotics firm Allen Control Systems (ACS) announced a deal with the US Marine Corps on Monday to get its Bullfrog autonomous weapon system attached to the Light Marine Air Defense Integrated System (L-MADIS) expeditionary counter-drone platform. L-MADIS consists of pairs of off-road vehicles, one carrying a suite of sensors and the other slated to be outfitted with a Bullfrog autonomous weapon station. Videos on ACS’ YouTube page demonstrate the Bullfrog in action, taking down a number of small drones in demonstrations over the past couple of years. While we didn't hear back from ACS about the Bullfrog's capabilities to target manned vehicles and troops, a short video on the company's channel also shows a Bullfrog unit switching from targeting aerial drones to ground targets with ease. This suggests that Bullfrog systems aren't just capable of knocking drones out of the sky. They are also fully capable of - and lack any software protections against - the fully autonomous targeting and killing of humans with complete autonomy. Bullfrog systems are a little different from your typical AI-controlled counter-drone systems in that they’re not built with an attached weapon, but are designed to slot in “any legacy or modern firearm” in order to turn them into systems able to “detect, track, and defeat incoming threats at a fraction of the cost of even the least expensive kinetic interceptors.” In other words, ACS claims it's cheaper to build a system that can adapt existing military firearms than to invest in a purpose-built counter-drone weapon system. Bullfrog units provide the AI, computer vision, and precision aiming robotics to take out drones, while the military only has to plug in its own hardware. There are several variants of the Bullfrog available from ACS, with units designed for everything from the M240 machine gun to the M2 50-caliber machine gun. The company is currently working on M230 chain gun and M134 minigun variants as well. In the case of the Marine Corps contract, it appears the service is taking on some M240 variants based on a link in ACS’s press release to the M240-variant’s page. The M240, the smallest of the weapons designed for the Bullfrog, fires up to 850 7.62×51 mm NATO rounds per minute and is effective up to 800 meters in the Bullfrog. The Bullfrog M240 is capable of taking down drones up to DoD Group 3, meaning anything with a max gross takeoff weight less than 1,320 lbs, able to operate as high as 18,000 feet above sea level, and with an airspeed of less than 250 knots. The DoD grouping goes up to Group 5, which includes some of the military's largest drones, such as the RQ-4 Global Hawk. The US Army and US Navy are both already fielding Bullfrog units, making the Marines the third branch to get their hands on the system. ACS cited the proliferation of cheap drones in the Russia/Ukraine conflict and in the Middle East as a need for comparable cheap counter drone tech. ®

source https://www.theregister.com/offbeat/2026/07/21/us-marines-latest-anti-drone-toy-is-an-ai-turret-that-uses-regular-machine-guns/5275691
The Anubis ransomware gang has claimed responsibility for the cyberattack on Coca-Cola's Fairlife dairy subsidiary, threatening to publish allegedly stolen corporate data unless the company pays a ransom. [...]

source https://www.bleepingcomputer.com/news/security/anubis-ransomware-claims-coca-cola-fairlife-attack-threatens-data-leak/
Iran's Islamic Revolutionary Guard Corps (IRGC) claims it hit an AWS datacenter in Bahrain months after taking it offline for the first time, in a move it claimed as retaliation for a US attack on a nuclear plant that was under construction. The IRGC said in a statement on Tuesday that it had struck back at what it called the "child-killing US Army" by attacking Amazon infrastructure in Bahrain, claiming AWS's "central data infrastructure" had been "destroyed" after being hit by "several cruise missiles," according to Google Translate. The IRGC said the claimed strike was retaliation for what Iran described as a US attack on the under-construction Darkhovin nuclear facility. A look at the AWS Health Dashboard shows that there are definitely issues in Bahrain and the UAE, with issues in both regions being blamed on the US-Iranian conflict. While the status of AWS me-central-1 (UAE) is just “unable to reliably support customer applications,” me-south-1 (Bahrain) is said to be “currently unavailable.” The last update to the state of AWS services in Bahrain and the UAE in the open issues area of the Dashboard was on April 30, and the Service History tab shows that every single AWS service in Bahrain has been offline for months. Per our previous reporting, Iranian state-affiliated media claimed that strikes on AWS infrastructure in Bahrain and the UAE were deliberate, after US and Israeli attacks on Iran in late February. AWS-hosted providers including Snowflake and Red Hat subsequently urged affected customers to fail over or move workloads to other regions after the facilities were damaged. AWS waived all usage-related charges for March 2026 in its me-central-1 region in the UAE following the attacks on its infrastructure. Iran has also reportedly designated facilities associated with Google, IBM, Microsoft, Nvidia, Oracle, and Palantir as legitimate targets for retaliatory strikes, citing their alleged support for US military operations. The fact that services in Bahrain have been unavailable for months, and continue to be offline, makes it challenging for El Reg to confirm the legitimacy of Iranian claims it hit the site again. We’ve reached out to AWS to learn more, but didn’t hear back. ®

source https://www.theregister.com/off-prem/2026/07/21/iran-says-its-struck-offline-aws-facility-in-bahrain-again/5275762

Tuesday, 21 July 2026

Weekend Warriors vs Spike Squad — Shreewoods Weekend Volleyball, 18 July 2026 (4K)

Weekend Warriors vs Spike Squad — spike at the net, Shree Woods, Siddartha Nagar, Dhanori, Pune (18 July 2026)
Weekend Warriors vs Spike Squad — spike at the net, Shree Woods, Siddartha Nagar, Dhanori, Pune (18 July 2026)

Another cracking weekend of local volleyball at Shree Woods, Siddartha Nagar, Dhanori, Pune. On 18 July 2026, Weekend Warriors squared off against Spike Squad in a full, end-to-end match — big spikes, stubborn blocks, scrambling digs and some genuinely long rallies on the red-clay court. We filmed it all in 4K and cut it into the full set below so you can relive the game however you like.

The story of the match

This one had everything grassroots volleyball does best — no officials, no timeouts, just two sides going all out. The attackers went up hard at the net, the back line kept balls alive that had no business staying up, and the rallies kept building until someone finally put the ball down. Watch the Best Plays Montage for the highlights, then the Full Match for the complete flow of the game, and drop into Slow-Motion to see the spikes frame by frame.

Weekend Warriors vs Spike Squad — airborne attack, Shree Woods, Siddartha Nagar, Dhanori, Pune (18 July 2026)
Weekend Warriors vs Spike Squad — airborne attack, Shree Woods, Siddartha Nagar, Dhanori, Pune (18 July 2026)

The players and the community spirit

What keeps this going is the crowd of regulars — friends, neighbours and passers-by from Dhanori who turn up every weekend to play or cheer. No club fees, no gatekeeping: just show up, rotate in, and play. The photos below are pulled straight from the 4K footage.

Community weekend volleyball — Shree Woods, Siddartha Nagar, Dhanori, Pune
Community weekend volleyball — Shree Woods, Siddartha Nagar, Dhanori, Pune

How we film and produce every match

Every match is shot in 4K, then cut into a full edit, a slow-motion breakdown, a best-plays montage and a highlights reel — with the spikes, blocks and long rallies pulled out frame by frame for the gallery.

Weekend Warriors vs Spike Squad — rally in full swing
Weekend Warriors vs Spike Squad — rally in full swing

Watch every version (4K)

📸 Every best play — the full gallery (226 shots)

Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot Weekend Warriors vs Spike Squad volleyball 18 July 2026 action shot

Tap any photo to open the full-resolution 4K still.

Reel-format stills (9:16)

Weekend Warriors vs Spike Squad vertical still Weekend Warriors vs Spike Squad vertical still Weekend Warriors vs Spike Squad vertical still Weekend Warriors vs Spike Squad vertical still Weekend Warriors vs Spike Squad vertical still Weekend Warriors vs Spike Squad vertical still Weekend Warriors vs Spike Squad vertical still Weekend Warriors vs Spike Squad vertical still Weekend Warriors vs Spike Squad vertical still Weekend Warriors vs Spike Squad vertical still Weekend Warriors vs Spike Squad vertical still Weekend Warriors vs Spike Squad vertical still Weekend Warriors vs Spike Squad vertical still Weekend Warriors vs Spike Squad vertical still Weekend Warriors vs Spike Squad vertical still Weekend Warriors vs Spike Squad vertical still Weekend Warriors vs Spike Squad vertical still Weekend Warriors vs Spike Squad vertical still Weekend Warriors vs Spike Squad vertical still Weekend Warriors vs Spike Squad vertical still Weekend Warriors vs Spike Squad vertical still Weekend Warriors vs Spike Squad vertical still Weekend Warriors vs Spike Squad vertical still Weekend Warriors vs Spike Squad vertical still Weekend Warriors vs Spike Squad vertical still Weekend Warriors vs Spike Squad vertical still Weekend Warriors vs Spike Squad vertical still Weekend Warriors vs Spike Squad vertical still Weekend Warriors vs Spike Squad vertical still Weekend Warriors vs Spike Squad vertical still Weekend Warriors vs Spike Squad vertical still Weekend Warriors vs Spike Squad vertical still Weekend Warriors vs Spike Squad vertical still

Playlists

Come play with us 🏐

We play every Saturday & Sunday — mornings 8:00 AM and evenings 4:30 PM — at Shree Woods, Siddartha Nagar, Dhanori, Pune (Google Maps). All levels welcome. Subscribe to Explore NY Stream for a fresh local volleyball match every weekend, plus daily Shorts of the best spikes and rallies.

About

Privacy Policy

ShortNewsWeb

Blog Archive

Recent Comments

Popular Posts

Translate

My Blog List

Popular

System Admin Share

Total Pageviews