The tech titan previewed a sweeping set of AI advances that it says will reshape how organizations ideate, build, deploy, and govern AI systems.
The post Ignite 2025: Microsoft Showcases AI Lifecycle Vision appeared first on TechRepublic.
A blog post published Tuesday night by Cloudflare cofounder and CEO Matthew Prince has details on what caused its âworst outage since 2019,â pinning the issue to a problem in the Bot Management system that is supposed to control which automated crawlers are allowed to scan particular websites using its CDN.
Cloudflare said last year that about 20 percent of the web runs through its network, which is supposed to share the load to keep websites online in the face of traffic spikes and DDoS attacks. But todayâs crash disconnected many of them, knocking out everything from X to ChatGPT to the well-known outage tracker Downdetector for several hours and resembling recent outages caused by problems with Microsoft Azure and Amazon Web Services.
Cloudflareâs bot controls are supposed to help deal with problems like crawlers scraping information to train generative AI. It also recently announced a system that uses Generative AI to build the âAI Labyrinth, a new mitigation approach that uses AI-generated content to slow down, confuse, and waste the resources of AI Crawlers and other bots that donât respect âno crawlâ directives.â
However, it says the problems today were due to changes to the permissions system of a database, not the generative AI tech, not DNS, and not what Cloudflare initially suspected, a cyberattack or malicious activity like a âhyper-scale DDoS attack.â
According to Prince, the machine learning model behind Bot Management that generates bot scores for the requests that travel over its network has a frequently updated configuration file that helps ID automated requests; however, âA change in our underlying ClickHouse query behaviour that generates this file caused it to have a large number of duplicate âfeatureâ rows.â
Thereâs more detail in the post about what happened next, but the query change caused its ClickHouse database to generate duplicates of information. As the configuration file rapidly grew to exceed preset memory limits, it took down âthe core proxy system that handles traffic processing for our customers, for any traffic that depended on the bots module.â
As a result, companies that used Cloudflareâs rules to block certain bots returned false positives and cut off real traffic, while Cloudflare customers who didnât use the generated bot score in their rules remained online.
For now, it lists four specific plans to keep this kind of problem from happening again, even if the growing centralization of internet services may make these outages inevitable:
| The following originally appears on fast.ai and is reposted here with the authorâs permission. |
Iâve spent decades teaching people to code, building tools that help developers work more effectively, and championing the idea that programming should be accessible to everyone. Through fast.ai, Iâve helped millions learn not just to use AI, but to understand it deeply enough to build things that matter.
But lately, Iâve been deeply concerned. The AI agent revolution promises to make everyone more productive, yet what Iâm seeing is something different: developers abandoning the very practices that lead to understanding, mastery, and software that lasts. When CEOs brag about their teams generating 10,000 lines of AI-written code per day, when junior engineers tell me theyâre âvibe-codingâ their way through problems without understanding the solutions, are we racing toward a future where no one understands how anything works, and competence craters?
I needed to talk to someone who embodies the opposite approach: someone whose code continues to run the world decades after he created it. Thatâs why I called Chris Lattner, cofounder and CEO of Modular AI and creator of LLVM, the Clang compiler, the Swift programming language and the MLIR compiler infrastructure.
Chris and I chatted on Oct 5, 2025, and he kindly let me record the conversation. Iâm glad I did, because it turned out to be thoughtful and inspiring. Check out the video for the full interview.
Read Jeremy’s full thoughts about the episode on his post on fast.ai‘s blog.