Operations | Monitoring | ITSM | DevOps | Cloud

There have been TWO major kernel vulnerabilities announced this week. Copy-Fail (CVE-2026-31431) was announced on April 30th. Dirty Frag (CVE-2026-43284), also known as 'Copy Fail 2: Electric Boogaloo' announced literally hours ago. Both have already been patched on Cycle, and our users can receive this update simply by restarting their nodes. The Linux patch was released less than an two hours ago, and we're the first to get it to our customers.

Getting a certificate from a CA is a solved problem (ACME). Distributing it to the rest of your infrastructure is not. Your F5 has its own API. Your Palo Alto has a different one. Azure Key Vault is a third thing entirely, and the appliance in the back of the rack only has an SSH interface.

Drop a JAR on the JVM. Get distributed tracing, RxJava context propagation, log-trace correlation, and Vert.x internal metrics. No code changes. No Maven dependency. Java 8–21. Inside the design of last9/vertx-opentelemetry v2.3.4. Prathamesh works as an evangelist at Last9, runs SRE stories - where SRE and DevOps folks share their stories, and maintains o11y.wiki - a glossary of all terms related to observability.

Key takeaway: Granting AI agents unrestricted access to cloud infrastructure is an unacceptable security risk. Upsun provides a "zero-trust" framework by utilizing isolated, production-perfect preview environments that allow AI to be productive without the risk of a hallucinated production outage.

If an AI agent in your development workflow needed to spin up a test environment tonight, how many manual steps would stand between the request and the environment being ready? By early 2026, AI agents have transitioned from simple code assistants to first-class platform citizens. They are running test suites, analyzing performance, and triggering deployments.

A few weeks ago, a group of engineering leaders I trade notes with got into it over a question none... A few weeks ago, a group of engineering leaders I trade notes with got into it over a question none of us has a clean answer to: How much should you let an engineer spend on AI? One SVP at a company of similar size and stage is in calibration mode and capping engineers at $200 per month. Hit the cap, you can self-bump by $100. Hit that, you need your manager. I told the thread our number. $5,000.

I’ve been doing this for over thirty years. Sysadmin, ops lead, global teams, and more data centre migrations than I’d like to admit. Site to site, P2V, V2V, cloud, hybrid, all of it. Every migration gets sold as a clean, well-planned transition. None of them are. They go wrong in very predictable ways. Not because moving infrastructure is especially difficult, but because nobody ever has a clear, current view of what’s actually running, what’s changed, and what still matters.