You're reading the Tuesday, October 27, 2026 edition. Today's briefing →
Toronto
Tuesday, October 27, 2026No. 135

Digital Plumber

Plumbing the information age

AI-curated intelligence for people who run networks. Daily coverage of AIOps, network automation, agentic operations, AI infrastructure, security and the vendors shaping them.

Today's 3 things that matter

Picked by the AI editor
  1. Security·Industry news

    Campaign harvests 70,000 credentials from Fortinet and Palo Alto devices

    Group-IB and NyxLab documented an active campaign targeting internet-facing FortiGate, FortiWeb, and Palo Alto GlobalProtect devices, exploiting CVE-2026-0257 (GlobalProtect auth bypass) and Fortinet flaws to extract 70,000+ exposed network device credentials and LDAP records for persistent network access.

    Why it matters Threat actors are systematically compromising perimeter VPN and firewall devices to steal credentials and establish lasting network presence; any internet-facing Palo Alto or Fortinet device without patched CVE-2026-0257 is actively being targeted and should be treated as compromised until verified clean.

  2. Security·Industry news

    Critical Brotli flaw hits all PAN-OS versions without fix

    Palo Alto Networks confirmed that a critical out-of-bounds write vulnerability in the Brotli compression library affects all PAN-OS versions 10.2–12.2 and Panorama, allowing unauthenticated remote code execution or privilege elevation.

    Why it matters Every Palo Alto firewall and Panorama instance running affected versions is potentially exploitable without authentication; 22.6 million exposed PAN-OS instances are at risk until patches arrive, forcing immediate implementation of network segmentation and access controls on management interfaces.

  3. Routing·Primary source

    Junos BMP flaws let BGP peers crash or root routers

    Two critical October 2026 Junos vulnerabilities reveal BGP Monitoring Protocol as an attack surface via stack overflow.

    Why it matters In environments accepting BGP sessions from customers, peers or transit partners, this represents a materially wider set of potential triggers than typical internal monitoring stations; both vulnerabilities require BMP to be enabled.

Today's briefing

What happened, and why it matters

15 stories · 9 topics · Updated 6:10 AM ET

Terraform adds provider sets for self-service network modules

Terraform Release Notes / HashiCorp · Oct 22, 2026 · Primary source

HashiCorp released Provider Sets feature on October 22, 2026, enabling platform teams to separate provider configuration from module code and expose modules through no-code and self-service workflows. Terraform 1.16.5 shipped as stable release on October 2, 2026.

Why it matters Provider Sets eliminate provider credential duplication across teams and enable self-service infrastructure provisioning without exposing sensitive API keys—reducing operational friction for network engineers using Terraform for cloud and on-prem network resources.

Provider Sets decouple provider authentication and configuration from Terraform modules, allowing platform engineering teams to publish reusable network modules (VPCs, security groups, load balancers, DNS records) that application and network teams can consume through a curated registry without touching provider credentials. This addresses a persistent pain point in network IaC: managing Terraform state for sensitive provider configurations across multiple teams while maintaining least-privilege access. For network automation practitioners, this means platform teams can establish a network module marketplace—e.g., 'secure-vpc-module' or 'firewall-rule-set'—that consuming teams apply declaratively without needing AWS, Azure, or GCP API credentials in their code or CI/CD environment. The feature reduces the compliance and operational burden of sharing Terraform code across enterprise network organizations, particularly relevant for multi-cloud and hybrid cloud network provisioning where different teams manage different infrastructure layers.

Read the original at github.com ↗

LogicMonitor topology maps link packet loss to application impact

Hoop Dev · Oct 22, 2026 · Industry news

LogicMonitor's topology mapping automatically connects network device state changes to dependent application services; when packet loss occurs on a network segment, alert rules group all downstream service impacts into a single incident context.

Why it matters Topology-aware correlation eliminates manual dependency tracing during incidents: engineers and AI agents query a single platform to understand whether a network or application component failed first, cutting MTTR by removing the guesswork phase.

This piece covers the architectural foundation of practical event correlation in modern NOCs. LogicMonitor ingests both infrastructure telemetry (device metrics via SNMP, flow data via NetFlow) and application telemetry (via OpenTelemetry collectors) into a unified topology model. When a network metric breaches a threshold—e.g., packet loss on a switch port—the platform automatically identifies which application services depend on that path and groups all correlated alerts. This is critical because traditional monitoring fires independent alerts for each threshold (high latency, increased error rate, connection exhaustion, downstream timeouts), all describing the same incident but appearing as separate signals. The topology layer transforms this noise into signal: one root cause alert with the dependency chain pre-computed. For operators, this reduces the first thirty minutes of incident response (manual correlation) to seconds of automated insight, freeing engineering time for actual remediation.

Read the original at hoop.dev ↗

Observability data floods tools that still cannot explain outages

Cloud Security Alliance · Oct 20, 2026 · Industry news

Modern observability systems generate terabytes of telemetry (metrics, logs, traces) but lack semantic relationships between components; without topology and causality modeling, operators manually reconstruct incident chains across disparate tools.

Why it matters Event correlation and digital twin approaches address observability's core gap: raw telemetry volume hasn't reduced MTTR because operators still spend 30+ minutes manually connecting the dots between independent data streams during incidents.

This analysis articulates why observability alone is insufficient for NOC operations in 2026. Traditional monitoring platforms excel at visibility into individual component behavior (per-service latency, per-database query time, per-network-device CPU), but leave operators to manually answer the critical question during incidents: which component failed first, and how did the failure cascade? The telemetry volume has exploded—metrics, logs, traces, events, profiles—yet incident resolution times haven't improved proportionally because the data lacks inherent semantic structure. Operators must manually reconstruct dependency chains: they see a payment service timing out, check upstream databases, find connection pool exhaustion, trace back to network latency, finally discovering a switch misconfiguration. This manual work is what event correlation and digital twins pre-compute: the relationships (which services depend on which infrastructure) and causality models (how failures propagate). The piece underscores why NOC teams are moving toward unified observability platforms that compute topology and correlation natively, rather than bolting correlation on top of siloed tools.

Read the original at cloudsecurityalliance.org ↗

Innovorbs launches practice for private GPU cluster networking

EIN Presswire / CIOInfluence · Oct 22, 2026 · Primary source

Innovorbs announced an AI data center infrastructure practice for enterprises building private GPU clusters, covering RoCEv2 on 400G/800G Ethernet, NVIDIA Quantum InfiniBand (NDR/XDR), and emerging Ultra Ethernet Consortium standards across NVIDIA Spectrum-X, Arista, Cisco Nexus, and Juniper QFX platforms.

Why it matters Provides practitioners a systems-integration reference for building lossless AI fabrics: concrete guidance on fabric topology choices, congestion control (PFC/ECN/DCQCN), adaptive routing, and rail-optimized non-blocking Clos designs for 130 kW racks.

Innovorbs, a managed services provider based in Houston, launched a dedicated practice for designing, deploying, and operating GPU compute environments on-premises or in colocation. The offering addresses a gap for enterprises: AI workloads require specialized networking and cooling that differ fundamentally from traditional enterprise infrastructure. For back-end GPU-to-GPU fabric, Innovorbs designs around RoCEv2 on 400G and 800G Ethernet with Priority Flow Control, Explicit Congestion Notification, and DCQCN congestion control, using adaptive routing and rail-optimized non-blocking Clos topologies. It supports NVIDIA Spectrum-X, Arista, Cisco Nexus, and Juniper QFX for Ethernet deployments, and NVIDIA Quantum InfiniBand (NDR and XDR) for tightly coupled training clusters. The practice also integrates front-end networking (BGP EVPN-VXLAN), NVMe-oF storage, and facilities engineering for 40–130 kW pods. Critically, Innovorbs notes it will support Ultra Ethernet Consortium (UEC) transport as that standard reaches production—a signal that UEC adoption for private AI infrastructure is moving from research to operational readiness. The framework treats fabric, storage path, and cooling as a co-designed system, addressing the reality that GPU clusters run at rated performance only when all layers align.

Read the original at einnews.com ↗

Junos BMP flaws let BGP peers crash or root routers

DEV Community · Oct 26, 2026 · Primary source

Two critical October 2026 Junos vulnerabilities reveal BGP Monitoring Protocol as an attack surface via stack overflow. CVE-2026-33789 is a stack-based buffer overflow in rpd allowing an unauthenticated BGP peer to cause denial of service and potential root-level command execution via crafted BGP route updates when BMP is enabled.

Why it matters In environments accepting BGP sessions from customers, peers or transit partners, this represents a materially wider set of potential triggers than typical internal monitoring stations; both vulnerabilities require BMP to be enabled.

BGP Monitoring Protocol exists to copy routing information from a router to a monitoring station as a telemetry feature, but two October 2026 Junos vulnerabilities demonstrate that features designed only to listen are not necessarily low-risk. CVE-2026-33789 is a stack-based buffer overflow in the routing protocol daemon of Juniper Networks Junos OS and Junos OS Evolved, with a CVSS v4.0 base score of 9.2. The crafted input arrives through BMP route monitoring; CVE-2026-33789 is exploitable by an unauthenticated BGP peer, which in environments accepting BGP sessions from customers or transit partners represents a materially wider set of potential triggers than typical internal monitoring stations. Remediation requires patching to the fixed build; where BMP is not operationally required, disabling it removes the specific attack path and serves as a reasonable interim control.

Read the original at dev.to ↗

Eight eMudhra intermediate CA keys were trivially breakable

Microsoft Security Response Center · Oct 26, 2026 · Primary source

Eight eMudhra intermediate CA private keys (six for TLS, two for code signing) were compromised with catastrophically weak entropy (3-8 bits instead of 384), allowing attackers to trivially recover keys and forge trusted certificates for any domain. Microsoft removed seven certificates from Windows and Edge trust lists; browsers blocked all eight intermediates.

Why it matters Docker containers and CI/CD pipelines built before October 20 with bundled CA trust stores still trust eMudhra certs and require deliberate rebuild; all outbound TLS connections from pre-October 20 container images remain within attack surface until remediated.

On October 17, a security researcher discovered eight eMudhra intermediate certificates with private keys so weak that recovery took under one second. The researcher published one private key (value: 4) to demonstrate compromise. Six intermediates could issue TLS certificates for arbitrary domains; two could sign code. No evidence shows fraudulent end-entity certificates were issued, but any system trusting the affected roots remained vulnerable to man-in-the-middle attacks. Mozilla blocked via OneCRL on October 17; Google Chrome and Apple followed within days. Microsoft issued an out-of-band Windows update on October 26 removing seven eMudhra roots and planned Edge removal for October 27. eMudhra announced exit from the SSL/TLS business on October 22. The critical remediation task for infrastructure teams: rebuild container images with CA bundles dated after October 20, audit mTLS endpoint configurations for eMudhra trust, verify downstream systems (embedded systems, legacy software, CI/CD agents) received updated trust stores, and test that certificate pinning does not inadvertently pin compromised intermediates.

Read the original at microsoft.com ↗

Critical Brotli flaw hits all PAN-OS versions without fix

Cybersecurity News · Oct 27, 2026 · Industry news

Palo Alto Networks confirmed that a critical out-of-bounds write vulnerability in the Brotli compression library affects all PAN-OS versions 10.2–12.2 and Panorama, allowing unauthenticated remote code execution or privilege elevation. Company provided no fix release date as of October 26.

Why it matters Every Palo Alto firewall and Panorama instance running affected versions is potentially exploitable without authentication; 22.6 million exposed PAN-OS instances are at risk until patches arrive, forcing immediate implementation of network segmentation and access controls on management interfaces.

Palo Alto published advisory on October 26 confirming that Brotli vulnerability CVE-2026-111497 (CVSS 8.1, rated Critical) affects PAN-OS 10.2, 11.1, 11.2, 12.1, 12.2 and Panorama. The flaw permits unauthenticated attackers to corrupt memory, disclose sensitive data, trigger denial of service, or execute code with elevated privileges. Cloud NGFW, Prisma Access, and GlobalProtect app are not affected. Fortinet confirmed FortiOS, FortiManager, FortiAnalyzer, FortiWeb, and FortiMail are unaffected; Cisco reports no affected products. With no fix release date announced, Palo Alto recommended interim mitigations: restrict management interface access to trusted jump hosts via network ACLs, enable Threat Prevention signature (Threat ID 543004) on PHP servers behind affected firewalls, and monitor for emergency patch announcements. This is a high-impact vulnerability for any organization with internet-facing or DMZ-deployed PAN-OS appliances. Treat immediate network isolation of affected devices' management planes as mandatory pending patch availability.

Read the original at cybersecuritynews.com ↗

Campaign harvests 70,000 credentials from Fortinet and Palo Alto devices

Cybersecurity News · Oct 22, 2026 · Industry news

Group-IB and NyxLab documented an active campaign targeting internet-facing FortiGate, FortiWeb, and Palo Alto GlobalProtect devices, exploiting CVE-2026-0257 (GlobalProtect auth bypass) and Fortinet flaws to extract 70,000+ exposed network device credentials and LDAP records for persistent network access.

Why it matters Threat actors are systematically compromising perimeter VPN and firewall devices to steal credentials and establish lasting network presence; any internet-facing Palo Alto or Fortinet device without patched CVE-2026-0257 is actively being targeted and should be treated as compromised until verified clean.

Group-IB researchers published findings on October 21, 2026, showing operators conduct bulk scans for exposed Fortinet and Palo Alto devices, then exploit known vulnerabilities to harvest credentials. Campaign identified 70,000+ exposed credentials including network device logins, VPN accounts, and LDAP records. CVE-2026-0257 (GlobalProtect authentication bypass) allows unauthorized VPN connections under specific PAN-OS configurations; Palo Alto's advisory recommends following remediation guidance with three specific exploit IP addresses listed. Fortinet products affected by path traversal and other flaws documented in CVE-2025-64446. This campaign represents active, ongoing threat targeting perimeter security devices. Network teams must immediately verify patches for CVE-2026-0257 are installed on all GlobalProtect portals and gateways, rotate credentials for any device with exposed management interfaces, review VPN access logs for anomalous connections, and implement network segmentation to isolate perimeter devices from internal systems.

Read the original at cybersecuritynews.com ↗

People Moves

2 stories

Darktrace names new chief product and technology officers

Darktrace Newsroom · Oct 22, 2026 · Primary source

Behavioral security company Darktrace announced appointments of Issy Richards as Chief Product Officer and Stephen Pickman as Chief Technology Officer, both joining the Executive Leadership Team reporting to CEO Ed Jennings. Richards will lead the global product organization while Pickman will oversee research and development.

Why it matters Establishes product and R&D leadership focused on enterprise AI and autonomous threat response capabilities, relevant to security practitioners evaluating behavioral detection platforms.

Darktrace's announcement reflects the company's strategic focus on securing enterprise AI and AI agents amid rapidly evolving threat landscapes. Both executives were central to developing Darktrace / SECURE AI, the company's product for discovering AI use across enterprises and understanding human and agent behavior. Richards, who joined Darktrace in May 2025, will lead the global product organization and sharpen product strategy. Pickman will oversee research and development, leading the engineering effort to bring new technology to market at speed. Their promotions expand leadership capacity across product strategy, engineering, and research as Darktrace strengthens its core behavioral security platform. The appointments come as organizations face growing complexity in hybrid cloud infrastructure and the expanding attack surface created by AI adoption. For security operations leaders, these appointments signal leadership continuity and emphasis on product velocity for AI-aware threat detection and autonomous response across enterprise networks and infrastructure.

Read the original at darktrace.com ↗

Outcomex names Michael van Zoggel chief executive

Outcomex Newsroom · Oct 22, 2026 · Primary source

Australian technology services firm Outcomex appointed Michael van Zoggel as Chief Executive Officer after 14 years under founder Marco Delgado, who transitioned to Founder and Chairman. Delgado has been pivoting to other ventures including AI and IoT startups while maintaining strategic oversight of Outcomex.

Why it matters Leadership transition in a regional infrastructure and cyber services provider reflects broader industry focus on cyber security, managed services, and AI advisory—key growth areas for NetOps and infrastructure practitioners.

Van Zoggel, who joined Outcomex in 2014 and has served as Managing Director since 2020, assumes full CEO responsibility for the organization. The leadership change reflects Outcomex's strategic pivot toward cyber security, managed services, and AI-related advisory work while maintaining core infrastructure and managed services operations. Founder Marco Delgado, who established Outcomex in 2012, transitions to Founder and Chairman to focus on strategic guidance, long-term partnerships, and growth initiatives. Delgado remains active across a portfolio of ventures including 365mesh (an Australian AI and IoT company he founded in 2021) and newer startups Lucendus and ThreatCanary. The reshuffle includes promotion of Ben Blaschka to Chief Revenue Officer and Holly Garbutt to National Sales Manager. For infrastructure services practitioners and buyers, this transition signals continued investment in the Australian technology services sector's evolution toward integrated cyber, cloud, and AI capability delivery.

Read the original at datacenternews.asia ↗

Canadian carriers shift capex toward AI data centres and fibre

TelecomLead · Oct 26, 2026 · Industry news

Bell, Rogers, and Telus are shifting capital investment toward 5G standalone, fiber broadband, FWA, and AI infrastructure as traditional mobile revenue slows. Bell plans a 300 MW AI facility near Regina; Telus targets 150 MW across three BC sites with 60,000 GPUs; Rogers launched 5G standalone in 2020 and 5G RedCap nationwide in 2025.

Why it matters Canadian telcos' aggressive AI compute infrastructure buildout creates new demand drivers for fiber and data center capacity, shifting operational spending priorities and creating network architecture implications for AI workload distribution.

Bell Canada, Rogers, and Telus are prioritizing 5G standalone, fiber broadband, fixed wireless access (FWA), enterprise connectivity and AI infrastructure investment. Bell invested nearly CAD23 billion between 2020 and 2024, and is planning a 300 MW AI facility near Regina. Telus plans CAD66 billion in connectivity and AI infrastructure investment by 2030, with plans to expand AI computing infrastructure across three British Columbia sites targeting 150 MW by 2032 and 60,000 GPUs when fully operational. These operators are investing in AI-enabled network management, automation and computing infrastructure to strengthen their competitive positions. This represents a structural shift in telecom capex allocation where AI compute infrastructure now competes with traditional network upgrades for capital, and network architects must design for both geographic distribution of GPU resources and the interconnect requirements between compute centers and customer-facing infrastructure.

Read the original at telecomlead.com ↗

Comcast AIOps platform self-heals 77 percent of alarms

FutureNet World · Oct 23, 2026 · Industry news

Comcast's Octave platform recognizes different conditions and demands using billions of telemetry data points to make real-time decisions, improving service reliability and increasing network capacity by 35%. The AIOps platform self-heals roughly 77% of platform alarms via automation.

Why it matters Demonstrates measurable ROI from edge intelligence and AIOps automation at scale—specific capacity gains and alarm reduction metrics provide benchmarks for operators evaluating AI-driven network operations investments.

Comcast's Octave platform, developed as a proof-of-concept to address pandemic access constraints, operates at the edge by recognizing different conditions and demands across premises using billions of telemetry data points multiple times daily for real-time decisions. The system is transparent to customers, improves service reliability and resiliency, and increases network capacity by 35%. The company built an AIOps platform to handle the logic behind billions of daily data points, learning to identify failure patterns and deploying automation for self-healing; today roughly 77% of platform alarms are completely self-healed via this AIOps platform. Comcast also built a device called XMF, which monitors over 1 million kilometres of fibre across the entire network using AI to detect any interruption. The article demonstrates concrete operational benefits from AIOps at cable scale, showing that edge intelligence and closed-loop automation deliver measurable capacity and MTTR improvements.

Read the original at futurenetworld.net ↗

New RFCs extend PCEP to segment routing multipath

RFC Editor · Oct 26, 2026 · Primary source

RFC 10066 defines PCEP extensions to signal multiple forwarding paths with a single LSP for load balancing and redundancy. RFC 10067 extends this to group two unidirectional SR LSPs into associated bidirectional SR LSPs for both co-routed and non-co-routed paths.

Why it matters Operators can now build redundant, load-balanced SR policies that support multipath forwarding and bidirectional path association, enabling carrier-grade redundancy with simplified configuration.

RFC 10066 defines PCEP extensions to signal multipath information, associating multiple forwarding paths with a single PCEP LSP for load balancing and redundancy across diverse paths. The extensions are generic for both stateless and stateful PCEP. Their primary application is Segment Routing Policy, where a Candidate Path can contain multiple segment lists, enabling weighted or equal-cost load balancing. If the reverse segment list is co-routed with the forward segment list, then the PM/BFD session traverses the same links in both directions, enabling failure detection in both directions. RFC 10067 extends PCEP to allow grouping two unidirectional SR LSPs into associated bidirectional SR LSPs, utilizing RFC 10066's procedure to carry multiple EROs and associated reverse path EROs. These RFCs enable operators to implement carrier-grade redundancy and load-balancing in segment routing environments without separate reverse path signaling.

Read the original at rfc-editor.org ↗

Regulators shift scrutiny from AI models to autonomous agents

Ashford Publishing · Oct 25, 2026 · Analysis

In October 2026, regulators shifted focus from AI model regulation to agentic AI—software that plans and takes actions on its own—and companies' governance has not kept pace. The UK's ICO opened a call for evidence on agentic AI, and an IBM study found 80% of large EMEA firms experienced an AI incident reach the board in the past year.

Why it matters The EU pushed its strictest AI rules back by over a year with fixed deadlines, while the U.S. continues debating federal preemption of state laws.

After two years of model-focused regulation, the regulatory target in October 2026 shifted to AI agents—autonomous software systems that plan and execute actions independently. Governance frameworks have lagged behind adoption. The UK Information Commissioner's Office launched a call for evidence on agentic AI, closing November 20, 2026. Separately, an IBM study indicated that 80% of large companies in EMEA regions reported AI-related incidents escalating to board level in the past year. The EU's amended AI Act entered force with confirmed dates, while the United States remains contested over whether federal rules should preempt differing state laws. The FRONTIER Act (introduced July 2026) would set rules for frontier model developers and preempt some state laws; state regulations like California's SB 53 remain enforceable in parallel.

Read the original at ashford-publishing.com ↗

Beijing orders job-impact reviews for some AI projects

Automating Government Insights · Oct 26, 2026 · Analysis

Beijing ordered AI job-impact reviews for some projects, requiring employment risk assessments alongside project review for AI in labor-intensive industries, while mandating AI deployment first in labor-shortage or hazardous work areas. Italy's AI Decree (179/2026) took effect, prohibiting employment decisions solely on automated processing; a natural person must retain effective autonomous decision-making power on hiring, discipline, and termination.

Why it matters China's employment-impact screening and Italy's human-decision mandate signal jurisdictional divergence in agentic AI governance—key for multiregional enterprise deployment and compliance planning.

China's directive instructs AI deployment prioritization toward labor-shortage and high-risk work sectors, with cautious handling of adoption pace in labor-intensive industries. It requires employment risk assessments for AI in market-access fields that may cause significant displacement, cross-agency data sharing to monitor labor effects, and directs data labeling and terminal manufacturing toward central and western provinces. Italy's decree, effective October 27, 2026, mandates that employment decisions—hiring, discipline, changes, evaluation, and termination—cannot rest solely on automated processing; an individual with genuine autonomous authority must decide. Worker consent cannot waive this requirement. These moves reflect growing geographic segmentation in AI governance frameworks, with material implications for enterprise compliance across jurisdictions.

Read the original at automatinggovernmentinsights.substack.com ↗
Nothing in today's briefing matches that.

Listening

Podcasts and talks
  • Packet Pushers

    TNO078: Designing Networks for Operations

    Scott Robohn welcomes Bruce Davie and Larry Peterson from Systems Approach to discuss the new edition of Computer Networks: A Systems Approach and their blog post on reality-based network operations, exploring the contrast between clean-slate tooling and pragmatic heterogeneous vendor environments.

  • Packet Pushers

    HN847: Building Trust In The Agentic NOC

    Network engineers express legitimate concerns about non-deterministic AI behavior in operations. The episode examines the trust gap as the networking industry embeds agentic functions into production NOCs despite valid misgivings around explainability and governance.

  • Network World

    Cisco Announces OT Security Practitioner Certification for IT/OT Convergence

    Cisco announced the OT Security Practitioner certification on October 20, 2026, targeting early-career professionals entering operational technology security. Training launches November 5, 2026; exam (810-115 OTSEC) available February 3, 2027. The credential focuses on ICS architectures, network segmentation, traffic monitoring, and incident response.

  • DevOps.com

    Recursive Flint: 40B Open-Weight Coding Model for Local Agentic Workflows

    Recursive released Flint on October 21, 2026: a 40-billion-parameter open-weight mixture-of-experts coding model with 2.5 billion active parameters per token, designed to run locally on laptops and GPUs. Built by Recursive's Eureka Machine automated research system in under four months; open under Apache 2.0; scores competitive on agentic coding benchmarks.

Vendor Radar

Last 7 days · arrows compare with the 7 before

What changed this week

Last 7 days vs the 7 before

Biggest moves

Trending topics

agent · observability · OpenTelemetry · automation · Agentic AI · MCP · AIOps · RAG · Kubernetes · NetDevOps · SRE · inference

Get the daily briefing

Today's 3 things that matter and every story with why it matters, in your inbox each morning. Free, and you can unsubscribe at any time. Prefer a reader? Follow the RSS feed.