# Network architectures The organization of network devices and services to meet the connectivity needs of client devices. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## The TailscaleUp-date DevFeed: [The TailscaleUp-date]() Original publisher: [Read original article]() Author: Ross Kukulinski Published: 2026-08-24T14:30:00Z Content type: news Language: en Sources: [Blog on Tailscale]() Topics: [networking](), [AI Bots](), [Network architectures]() Tags: [ai](), [ai-agent](), [ai-gateway](), [api](), [api-keys](), [automation](), [databases](), [event](), [identity](), [infrastructure](), [logs](), [networking](), [security]() ### AI overview Tailscale previews TailscaleUp announcements focused on secure, identity-based connectivity and governed access for AI systems, services, and sensitive infrastructure. ### Source excerpt A preview of what we're building--and what we'll share at TailscaleUp. ## Data Center Fabrics High Level Overview DevFeed: [Data Center Fabrics High Level Overview]() Original publisher: [Read original article]() Author: j2sw Published: 2026-06-17T12:30:00Z Content type: tutorial Language: en Sources: [Justin Wilson (j2sw)]() Topics: [data centers](), [Network architectures](), [networking](), [Latency]() Tags: [architecture](), [data-center](), [ecmp](), [internet-architecture](), [latency](), [leaf-switch](), [network](), [servers](), [spine-switch](), [storage](), [vxlan]() ### AI overview This article explains data center fabrics as networks that connect servers, storage systems, and other network devices. It describes the common leaf-and-spine architecture, the roles of leaf and spine switches, packet movement, and how multiple paths provide bandwidth and predictable latency. ### Source excerpt A data center fabric connects servers, storage, and network devices using a leaf-spine architecture designed for high bandwidth and predictable latency. Learn how packets move through a fabric, why ECMP matters, and how modern data centers support virtualization, cloud, and AI workloads. The post Data Center Fabrics High Level Overview appeared first on Justin Wilson (j2sw). ## How we shipped 15 Tbps for OpenAI in 90 days (Session 1 of 3) DevFeed: [How we shipped 15 Tbps for OpenAI in 90 days (Session 1 of 3)]() Original publisher: [Read original article]() Author: Sridhar Rajarao Published: 2026-06-08T00:00:00Z Content type: article Language: en Sources: [Sridhar Rajarao]() Topics: [cloud-infrastructure](), [Network architectures](), [Network Configuration](), [OpenAI]() Tags: [architecture](), [gpu](), [network](), [network-configuration](), [object-storage](), [openai](), [platform-engineering](), [production](), [region](), [scale](), [service](), [sre](), [storage](), [teams]() ### AI overview Session 1 describes how a team closed the architecture for OpenAI's second Object Storage instance in the same physical region as its primary. The production system was designed for 15 Tbps of GPU-fleet traffic and a three-month delivery timeline, with major architecture decisions completed in one week. ### Source excerpt OpenAI wanted a second Object Storage instance, in customer-facing production, at 15 Tbps, in three months. Session 1 covers the first week: closing the architecture. ## How flat is replacing fat in AWS data center networks DevFeed: [How flat is replacing fat in AWS data center networks]() Original publisher: [Read original article]() Author: Giacomo Bernardi; Ratul Mahajan; Seshadhri Comandur Published: 2026-05-28T10:30:00Z Content type: article Language: en Sources: [Amazon Science homepage]() Topics: [networking](), [Network architectures]() Tags: [aws](), [aws-data-center-network-architecture](), [cloud-and-systems](), [data-center](), [fat-tree-network-replacement](), [flat-network-topology](), [network-design](), [networking](), [networks](), [quasi-random-network-topology](), [resilience](), [routing]() ### AI overview The article describes AWS's scalable flat data-center network, using quasi-random topology and ShuffleBoxes to replace conventional fat-tree designs. ### Source excerpt "Quasi-random" network topologies and new passive optical components called ShuffleBoxes make more-efficient flat networks as practical as traditional "fat-tree" networks. ## Laravel Cloud Incident Report: February 20, 2026 DevFeed: [Laravel Cloud Incident Report: February 20, 2026]() Original publisher: [Read original article]() Author: Laravel Team Published: 2026-02-20T15:20:00Z Content type: article Language: en Sources: [Laravel Blog]() Topics: [incident](), [Network architectures](), [Network Services]() Tags: [api](), [bgp](), [cloud-services](), [cloudflare](), [incident](), [infrastructure](), [laravel](), [outage]() ### AI overview Laravel Cloud reports a roughly 3-hour, 15-minute connectivity outage caused by Cloudflare withdrawing IP prefix advertisements. Applications and infrastructure remained operational, but users could not reach affected services; Laravel Cloud plans additional IP-announcement failover protection. ### Source excerpt ## Summary On February 20, 2026, [Laravel Cloud](https://laravel.com/blog/one-minute-or-less-how-we-built-laravel-clouds-architecture) experienced a connectivity outage lasting approximately 3 hours... ## exploits.club Weekly(ish) Newsletter 94 - P20 VMWare Bugs, ExpDev With LLMs, Pixel 0-Click Bugs, and More DevFeed: [exploits.club Weekly(ish) Newsletter 94 - P20 VMWare Bugs, ExpDev With LLMs, Pixel 0-Click Bugs, and More]() Original publisher: [Read original article]() Author: exploits.club Published: 2026-01-30T16:00:22Z Content type: article Language: en Sources: [exploits.club]() Topics: [Security](), [Exploit](), [Large Language Model](), [Artificial Intelligence](), [Code](), [Claude](), [ChatGPT](), [Network architectures](), [P2P](), [Open Source](), [Linux]() Tags: [ai](), [chatgpt](), [code](), [exploit](), [linux](), [llms](), [network](), [open-source](), [peer](), [poc](), [rce](), [remote-code-execution](), [security]() ### AI overview This newsletter surveys recent security research, including experiments using Claude and ChatGPT to generate proofs of concept for QuickJS vulnerabilities, a wormable remote code execution chain in Command & Conquer, a MediaTek bootloader exploit, and VMware workstation research. ### Source excerpt Good morning friends....been a minute. But we are SO back. Annnnnyways 👇 In Case You Missed It... RE//verse Tickets Still On Sale - If you were just at DistrictCon, escape the snow-pocalypse to Florida next month OffensiveCon CFP - 30 days to get-em submitted! Resources And Write-Ups ## Introducing Nested Learning: A new ML paradigm for continual learning DevFeed: [Introducing Nested Learning: A new ML paradigm for continual learning]() Original publisher: [Read original article]() Published: 2025-11-07T17:37:22Z Content type: article Language: en Sources: [The latest research from Google]() Topics: [Machine Learning & Artificial Intelligence](), [Optimization](), [Network architectures](), [Neural Network](), [LLMs](), [Google](), [Algorithms & Theory]() Tags: [algorithms-theory](), [architectures](), [generative-ai](), [google](), [large-language-models-llms](), [machine-intelligence](), [machine-learning](), [neurips](), [optimization](), [research]() ### AI overview Google Research introduces Nested Learning, a machine learning approach for continual learning that represents a model as interconnected, nested optimization problems. The approach aims to reduce catastrophic forgetting by jointly treating model architecture and training rules as multiple optimization levels with distinct information flows and update rates. ### Source excerpt Algorithms & Theory ## Finding Source Routing Paths DevFeed: [Finding Source Routing Paths]() Original publisher: [Read original article]() Published: 2025-06-13T06:10:00Z Content type: tutorial Language: en Sources: [ipSpace.net blog]() Topics: [networking](), [Software-defined networking](), [Network architectures](), [IS-IS]() Tags: [is-is](), [management](), [network](), [networking](), [networking-fundamentals](), [ospf](), [protocol](), [routing](), [sdn](), [software]() ### AI overview This tutorial explains how source-routing paths are determined and installed across networks. It examines centralized controller-based routing, SDN and OpenFlow, and segment routing with Path Computation Elements, then compares these approaches with older virtual-circuit provisioning systems. ### Source excerpt In the previous blog post, we discussed the generic steps that network devices (or a centralized controller) must take to discover paths across a network. Today, we'll see how these principles are applied in source routing, one of the three main ways to move packets across a network. Brief recap: In source routing, the sender has to specify the (loose or strict) path a packet should take across the network. The sender thus needs a mechanism to determine that path, and as always, there are numerous solutions to this challenge. We'll explore a few of them, using the sample topology shown in the following diagram. Read more ... ## netlab 2.0: Routers, Hosts, Gateways and Bridges DevFeed: [netlab 2.0: Routers, Hosts, Gateways and Bridges]() Original publisher: [Read original article]() Published: 2025-06-11T06:20:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [networking](), [Network architectures](), [Routing (disambiguation)](), [BGP](), [Cisco](), [Containers](), [Test coverage]() Tags: [bgp](), [bridge](), [cisco](), [container](), [netlab](), [network](), [router](), [routing](), [test-coverage]() ### AI overview The article explains how netlab 2.0 models routers, hosts, gateways, and bridges in network topologies. It describes their forwarding behavior, loopback interfaces, routing choices, IPv6 router advertisements, VLAN support, and possible uses of Cisco IOS, Arista EOS, BGP, and container-based devices. ### Source excerpt In a previous blog post, I explained how you can use bridges in a netlab topology to create custom LAN segments. Netlab supports two other node roles (host and router), and we'll eventually add gateways. netlab assumes that most network devices are routers (it considers a firewall to be a router in disguise), apart from Linux hosts, but you can always change what a node is with the role node attribute: Read more ... ## Network Design Lesson: Split Functionality Across Devices When Appropriate DevFeed: [Network Design Lesson: Split Functionality Across Devices When Appropriate]() Original publisher: [Read original article]() Published: 2024-05-29T06:33:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [Network design](), [Network architectures]() Tags: [bugs](), [network](), [network-design](), [worth-reading]() ### AI overview The article argues that network designs can be simpler and less costly when required functionality is divided across multiple devices instead of being crammed into one device. ### Source excerpt Tom Limoncelli wrote another must-read masterpiece: sometimes you'll save time if you make two trips instead of one. The same lesson applies to network design: cramming too many features into a single device will inevitably result in complex, hard-to-understand configurations and weird bugs. Sometimes, it's cheaper to split the required functionality across multiple devices.