Operations | Monitoring | ITSM | DevOps | Cloud

Recently I've been to Lisbon's Web Summit conference, a 3 day, 70,000 participants, 15 stages, 800+ speakers event. Even though there was a track called "AI Summit", all the talks were about AI and AI Agents and how the future of the web, business, economy is more and more AI, and how businesses and people should take steps to adapt as soon as possible to an online world managed and operated by Artificial Intelligence.

Struggling with latency, congestion, or compliance issues? Discover when it’s time to move from public internet to private connectivity. Network operations have never demanded more than they do now, leading many network managers to question whether the public internet is enough. While many organizations begin their network journey with VPNs over the public internet, they often bump into limitations quickly and begin exploring the natural next step – private connectivity.

As major incidents like AWS’s October 2025 outage illustrate, modern systems are immensely interconnected. A failure in one can lead to a cascade of downstream problems. In this case, issues with DNS resolution for DynamoDB led to widespread disruptions with other AWS services and, subsequently, thousands of applications and services that rely on that infrastructure.

As cloud applications moved from VMs to containers and then to microservices, the amount of background work needed to keep everything running grew just as quickly. You gain speed and flexibility, but you also end up managing clusters, scaling rules, and capacity choices that don’t really add to the product you’re building. AWS Fargate steps in right there. It lets you run your ECS tasks without looking after any servers at all.

OpenTelemetry now supports maps, heterogeneous arrays, and byte arrays across all signals. Here’s where these new types shine — and where simple primitives still fit naturally. If you’ve been working with OpenTelemetry for a while, you’re likely familiar with the straightforward key-value approach to attributes. It’s simple, fast, and works well with how most telemetry backends store, index, and query data.

Everyone wants to move faster with AI, but few are truly ready for it. This is where organizations can position themselves better as AI readiness isn’t just about algorithms, it’s about whether your data, systems, and teams are prepared to support intelligent automation safely and effectively.

Redgate took the main stage earlier today to open PASS Data Community Summit with our keynote, where we shared our vision for the future of the database development experience – one driven by speed, safety, and the intelligent use of AI. As data estates grow in scale and complexity, and as organizations push to deliver software faster than ever, the role of the database is undergoing significant change.

Yesterday’s widespread Cloudflare outage reminds us how crucial external dependencies are to the stability of our own applications. When a key edge provider like Cloudflare goes down, the impact on your internal monitoring systems can look like a catastrophic, internal system failure triggering a massive storm of alerts and sending engineering teams into frantic, misdirected debugging sessions.

On 2025-11-18 at 11:48 UTC, Cloudflare declared an incident affecting the global network (that also affected OnlineOrNot). OnlineOrNot monitors websites, APIs, web apps, and cron jobs, while providing status pages as well. While we partially mitigated the issue by enabling a fallback to AWS-based monitoring, between 13:00 UTC and 14:33 UTC failing checks went unreported, heartbeat checks over-reported, and status pages were unavailable.

When external providers fail—whether it was CrowdStrike outage last year, AWS outage last month, or the Cloudflare DNS outage yesterday—the symptoms inside your environment often look like internal issues: timeouts, login failures, API errors, service degradation, or sudden spikes in dependency-related alerts. It’s natural for teams to start searching through their own infrastructure first, but none of these symptoms clearly point to your systems as the root cause.