# Routing (disambiguation) Routing is a computing concept encompassing URL routing, IP routing, and geo-routing. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Ktor 3.6.0 Is Now Available! DevFeed: [Ktor 3.6.0 Is Now Available!]() Original publisher: [Read original article]() Author: Simon Vergauwen Published: 2026-09-18T10:45:56Z Content type: release Language: en Sources: [The JetBrains Blog]() Topics: [Ktor](), [Kotlin](), [Netty](), [Authentication](), [HTTP](), [openid](), [multiplatform](), [clients](), [Routing (disambiguation)]() Tags: [authentication](), [clients](), [http](), [http-3](), [kotlin](), [kotlin-multiplatform](), [ktor](), [news](), [openid](), [quic](), [release](), [releases](), [routing](), [server]() ### AI overview Ktor 3.6.0 introduces experimental typed authentication with OpenID Connect support and HTTP/3 over QUIC for the Netty engine. The release also improves routing, request handling, and Kotlin Multiplatform client defaults. ### Source excerpt Ktor 3.6.0 is here! This release is full of new experimental features, including typed authentication capabilities with specialized support for OpenID Connect and HTTP/3 support for the Netty engine. There are also a few quality-of-life improvements for routing and request handling, more convenient defaults for Kotlin Multiplatform clients, and more. Check out What's new in [...] ## How to Migrate a Legacy Monolith Incrementally Without a Big-Bang Rewrite DevFeed: [How to Migrate a Legacy Monolith Incrementally Without a Big-Bang Rewrite]() Original publisher: [Read original article]() Author: Hugo Teijiz Published: 2026-09-17T23:27:03Z Content type: tutorial Language: en Sources: [freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More]() Topics: [Legacy Modernization](), [migration](), [Refactoring](), [Testing](), [Integration testing](), [observability](), [Routing (disambiguation)](), [Transactions](), [TypeScript](), [API](), [service](), [Dependency injection]() Tags: [artificial-intelligence](), [how-to](), [incremental](), [integration-testing](), [legacy](), [legacy-code](), [migrate](), [migration](), [monolith](), [refactoring](), [rewrite](), [routing](), [software-architecture](), [transactions]() ### AI overview A tutorial on migrating a legacy monolith incrementally by moving one business capability at a time. It covers characterization tests, boundaries between legacy and new code, parallel implementations, progressive traffic, observability, rollback paths, data ownership, and removing migrated behavior. ### Source excerpt Large legacy migrations often fail long before the final cutover. The failure usually starts when the migration is framed as a single event. Move the application. Move the database. Move all the users ## Dense vs. MoE Models: Active Parameters, Throughput, and When to Choose Each DevFeed: [Dense vs. MoE Models: Active Parameters, Throughput, and When to Choose Each]() Original publisher: [Read original article]() Author: Elizabeth Goodman Published: 2026-09-15T17:00:11Z Content type: article Language: en Sources: [NVIDIA Developer](), [NVIDIA Technical Blog]() Topics: [Mixture of Experts (MoE)](), [Nemotron](), [Routing (disambiguation)]() Tags: [agentic-ai-generative-ai](), [ai-inference](), [architecture](), [cost](), [data-center-cloud](), [deployment](), [llms](), [memory](), [mixture-of-experts-moe](), [models](), [moe](), [nemo](), [nemotron](), [performance](), [router](), [routing](), [tokens]() ### AI overview This article explains how dense and Mixture-of-Experts models activate parameters, compares their effects on throughput, memory cost, and serving complexity, and discusses when each architecture fits different deployment constraints. It uses Nemotron 3.5 Lightning as an example of an MoE model. ### Source excerpt How can a 30B-parameter model activate only 3B parameters per token, and still use the capacity of the larger model? Nemotron 3.5 Lightning illustrates the... ## Replica-aware routing public beta DevFeed: [Replica-aware routing public beta]() Original publisher: [Read original article]() Author: Amy Chen; Jan Mensch Published: 2026-09-15T13:15:00Z Content type: release Language: en Sources: [ClickHouse Blog]() Topics: [clickhouse](), [Routing (disambiguation)](), [Replication](), [Caching]() Tags: [cache](), [clickhouse](), [consistency](), [replication](), [routing]() ### AI overview ClickHouse introduces replica-aware routing in Public Beta for Enterprise customers. The feature routes requests to the same replica, allowing continued access to temporary tables and named sessions and supporting read-after-write consistency over HTTP or the native protocol. ### Source excerpt Temporary tables and named sessions live on a single ClickHouse replica, so a follow-up query routed elsewhere can't see them. Replica-aware routing pins your requests to the same replica over HTTP or the native protocol -- and here's how we built it. ## Accelerating Dropless MoE Training in JAX with NVIDIA Transformer Engine DevFeed: [Accelerating Dropless MoE Training in JAX with NVIDIA Transformer Engine]() Original publisher: [Read original article]() Author: Tanya Lenz Published: 2026-09-14T16:39:15Z Content type: article Language: en Sources: [NVIDIA Developer](), [NVIDIA Technical Blog]() Topics: [Mixture of Experts (MoE)](), [Artificial Intelligence](), [GPU](), [Large Language Model](), [Nvidia](), [Routing (disambiguation)](), [GB200](), [Network](), [Python](), [deepseek](), [mixtral](), [qwen]() Tags: [agentic-ai-generative-ai](), [ai](), [communication](), [deepseek](), [developer-tools-techniques](), [gb200](), [gpu](), [mixtral](), [mixture-of-experts-moe](), [mlops](), [moe](), [networks](), [nvfp4](), [nvidia](), [performance](), [python](), [qwen](), [router](), [routing](), [tensors](), [token](), [tokens](), [training-ai-models]() ### AI overview This article explains how NVIDIA Transformer Engine and JAX kernel optimizations accelerate dropless Mixture of Experts (MoE) training. It describes bottlenecks from token routing, expert dispatch and gathering, all-to-all communication, and ragged expert matrix operations. In DeepSeek-V3 training on NVIDIA GB200, the optimized approach increased performance from 103 to 1,068 TFLOPS per GPU, a 10.4x improvement. ### Source excerpt Mixture of experts (MoE) has become one of the defining architectural trends in large-scale AI model training. DeepSeek, Qwen, and Mixtral are examples of MoE... ## Chinese AI models dominate OpenRouter's US token consumption. It can now guarantee that traffic stays entirely in the US. DevFeed: [Chinese AI models dominate OpenRouter's US token consumption. It can now guarantee that traffic stays entirely in the US.]() Original publisher: [Read original article]() Author: Paul Sawers Published: 2026-09-14T13:59:33Z Content type: news Language: en Sources: [The New Stack]() Topics: [AI Models](), [Routing (disambiguation)](), [Security](), [data](), [Availability](), [hugging face](), [Nvidia](), [Nemotron](), [OpenAI]() Tags: [ai](), [ai-infrastructure](), [ai-models](), [availability](), [data](), [hugging-face](), [large-language-models](), [models](), [nemotron](), [nvidia](), [openai](), [routing](), [security]() ### AI overview OpenRouter has launched US in-region routing for business and enterprise customers. Requests sent through its US endpoint are decrypted, processed, and served entirely inside the United States, or rejected if that cannot be guaranteed. The feature addresses concerns about data location when businesses use open-weight models, including models developed in China. ### Source excerpt Everyone knows the open-weight model pitch by now: companies can download the weights, customize them, run them on infrastructure of The post Chinese AI models dominate OpenRouter's US token consumption. It can now guarantee that traffic stays entirely in the US. appeared first on The New Stack. ## Agent Gateway: The Next Evolution of the API Gateway DevFeed: [Agent Gateway: The Next Evolution of the API Gateway]() Original publisher: [Read original article]() Author: Gbadebo Bello Published: 2026-09-10T16:00:00Z Content type: article Language: en Sources: [Postman Blog]() Topics: [API](), [AI Agent](), [Architecture & Design](), [Artificial Intelligence](), [Routing (disambiguation)](), [Authentication](), [Authorization](), [observability]() Tags: [agent-gateway](), [ai](), [ai-agents](), [api](), [api-101](), [api-gateway](), [architecture](), [authorization](), [editor-s-picks](), [fabric-gateway](), [general](), [llm-gateway](), [mcp](), [mcp-gateway](), [observability](), [routing]() ### AI overview The article explains the emergence of the Agent Gateway as an architectural component for AI agents. It contrasts traditional API Gateways, which authenticate, govern, route, and deliver requests from clients that already know which API to call, with the needs of AI agents, which receive goals and may require broader governance across agentic workflows. ### Source excerpt API gateways are evolving for AI agents. Learn how the agent gateway governs identity, tools, memory, and policy across agentic workflows. Get early access. The post Agent Gateway: The Next Evolution of the API Gateway appeared first on Postman Blog. ## How we cut CDN metadata lookup latency by 91% DevFeed: [How we cut CDN metadata lookup latency by 91%]() Original publisher: [Read original article]() Author: Luba Kravchenko Published: 2026-09-10T00:00:00Z Content type: article Language: en Sources: [Vercel News]() Topics: [Latency](), [Vercel](), [Caching](), [Routing (disambiguation)](), [API](), [React Native]() Tags: [api](), [cache](), [cdn](), [deployment](), [latency](), [routing](), [vercel]() ### AI overview Vercel describes how it reduced P99 CDN metadata lookup latency by 91%. The team replaced per-path metadata fetching with bounded shards that group metadata for many paths, improving cache reuse across routing lookups while controlling data-fetching costs. The article also explains how framework routing rules, Build Output API outputs, Bloom filters, and exact metadata lookups work together to select the correct response. ### Source excerpt Every request to Vercel passes through our CDN, which executes on average over 80 million routing instructions per second. Part of that work is looking up metadata to determine which paths exist and how to serve them. When that metadata isn't cached, the CDN has to fetch it before it can serve the response. We used to fetch and cache metadata one path at a time, retrieving only what each lookup needed. That seemed efficient at the time, but large deployments can contain hundreds of thousands of paths, each with its own cache entry. Every new deployment introduced fresh metadata, making cache misses a recurring cost for large sites that deployed frequently. Fetching more metadata at once made these lookups faster. By grouping paths together, each fetch could populate the cache for many subsequent lookups. But fetching too much introduced its own costs. Through production experiments, we found a balance that cut P99 metadata lookup latency by 91% and made deployments faster along the way. How the CDN finds the right route The path in a request doesn't always match the path of the content or function that serves it. Framework routing rules connect the two. A request for /blog/hello-world, for example, might resolve to the dynamic route /blog/[slug]. A request for that page's React Server Component payload might resolve to /blog/[slug].rsc. As the CDN applies these rules, it may need to check several target paths to find the right response. The framework describes those routes during a build. With framework-defined infrastructure, application code declares which outputs are static, which need Functions, and which responses can be cached or regenerated. Frameworks translate that intent into Build Output API outputs, and Vercel generates the routing metadata the CDN reads. At request time, the CDN needs to determine which target paths exist and retrieve their metadata. The Bloom filters we added to global routing rule out paths that definitely don't exist. Remaining paths ## Indian backbones need AS\_PATH filters DevFeed: [Indian backbones need AS\_PATH filters]() Original publisher: [Read original article]() Published: 2026-09-07T20:11:07Z Content type: opinion Language: en Sources: [Personal blog of Anurag Bhatia]() Topics: [BGP](), [Routing (disambiguation)](), [networking](), [Security]() Tags: [airtel](), [as4755](), [as55836](), [as9498](), [bgp](), [india](), [jio](), [network](), [rcom](), [routing](), [tata-comm]() ### AI overview The article argues that route leaks are a longstanding security problem for India's routing infrastructure. It explains limitations of IRR AS-SETs, discusses ASPA and AS_PATH filters or peer lock, and questions whether major Indian backbones can consistently apply those filters because of indirect routing and smaller downstream networks. ### Source excerpt The security of India's routing infrastructure is something that isn't discussed as much as cybersecurity, software vulnerabilities, etc. Part of the blame for that has to go to our industry, which is relatively closed when it comes to sharing incidents and also lacks good documentation on the deployment side of things. Some of these things came to light after the RCom (AS18101) BGP hijack of Telegram prefixes in June 2026. One silent problem for a long time has been route leaks. BGP route leak Route leaks happen when a network ends up announcing a route to a BGP adjacency where it is not supposed to announce that route. Take, for example, a network "leaking" routes learnt from a peer to transit, or vice versa. One can filter downstreams which are small, but it's very hard to filter large downstream networks which have further downstreams, or if one is far removed from that ASN. IRR AS-SETs exist for this reason, but they have not worked well due to tooling challenges. Furthermore, IRR (Internet Routing Registry) by design is a public register where one "publishes intent" before actually doing that in BGP, and then anyone can match the intent with the state in BGP. New tech ASPA will help address this issue, but it's new, vendor support is still in the development phase and it will take its own adoption time. AS_PATH filters / Peer lock This is older tech which can play a very effective role in controlling leaks. If network A decides to peer with network B, they both can agree to announce all routes to each other over the peering & agree to reject each other's ASN from all other BGP sessions. It's a common practice between large transit-free Tier-1 networks as well as major backbones and is often referred to by the fancy name of "peer lock". In India, I doubt backbones like Airtel, Jio, and Tata Comm can have AS_PATH filters rejecting each other from everywhere except direct sessions because there is some indirect routing visible all the time. It could be because of ## BGP-Free Core with SR-MPLS DevFeed: [BGP-Free Core with SR-MPLS]() Original publisher: [Read original article]() Published: 2026-09-03T05:30:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [SR-MPLS](), [BGP](), [networking](), [Network](), [Routing (disambiguation)](), [Containers](), [Linux](), [GitHub]() Tags: [bgp](), [containers](), [edge](), [examples](), [github](), [is-is](), [linux](), [mpls](), [netlab](), [network](), [router](), [routing](), [sr-mpls]() ### AI overview This article demonstrates how to build a BGP-free transport core with SR-MPLS using netlab. It describes a lab topology with IS-IS, BGP, Linux container hosts, and PE routers, then shows how SR-MPLS labels provide end-to-end connectivity without BGP routes on the core router. ### Source excerpt The beauty of SR-MPLS is that it's a drop-in replacement for the traditional (LDP- or RSVP-based) MPLS control plane. For example, you could replace LDP with SR-MPLS in a network using MPLS to implement a BGP-free transport core, and it just keeps working. This scenario was the first "fun" scenario in the ITNOG10 Segment Routing workshop. The core network uses the same topology as in the previous examples; I added two hosts and BGP routing. Simplest possible network using a BGP-free core Read more ... ## The IRR Landscape: What RPKI Can Replace DevFeed: [The IRR Landscape: What RPKI Can Replace]() Original publisher: [Read original article]() Author: Matthias Wichtlhuber Published: 2026-09-01T12:20:33Z Content type: article Language: en Sources: [RIPE Labs]() Topics: [BGP](), [Routing Security](), [Routing (disambiguation)](), [Databases](), [Internet]() Tags: [analysis](), [bgp](), [competition](), [data](), [database](), [ixps](), [measurements](), [overview](), [research](), [routing](), [routing-security](), [rpki](), [series]() ### AI overview This article analyzes which parts of the Internet Route Registry landscape can safely be replaced by RPKI using traffic and route-server data from AMS-IX and DE-CIX. It concludes that third-party ROUTE(6) objects can largely be phased out, while third-party AS-SETs remain important for BGP filter generation. ### Source excerpt In the third part of our IRR landscape series, we use traffic measurements from AMS-IX and DE-CIX to assess which parts of the IRR landscape can safely be replaced with RPKI. Third-party ROUTE(6) objects can largely be phased out, while third-party AS-SETs remain essential for BGP filter generation. ## Symfony 8.1.6 released DevFeed: [Symfony 8.1.6 released]() Original publisher: [Read original article]() Author: Fabien Potencier Published: 2026-08-30T21:44:04Z Content type: release Language: en Sources: [Symfony Blog]() Topics: [Symfony](), [bug](), [Security](), [Process](), [Routing (disambiguation)](), [cURL](), [PHP]() Tags: [bug](), [php](), [process](), [release](), [routing](), [security](), [symfony]() ### AI overview Symfony 8.1.6 is released with fixes across HttpClient, HttpFoundation, Security, Process, Routing, and other components. The update addresses issues including decompression bombs, malformed security parameters, subprocess environment handling, URL matching, and cookie validation. ### Source excerpt Symfony 8.1.6 has just been released. Read the Symfony upgrade guide to learn more about upgrading Symfony and use the SymfonyInsight upgrade reports to detect the code you will need to change in your project. Tip... ## Symfony 7.4.18 released DevFeed: [Symfony 7.4.18 released]() Original publisher: [Read original article]() Author: Fabien Potencier Published: 2026-08-30T21:39:49Z Content type: release Language: en Sources: [Symfony Blog]() Topics: [Symfony](), [bug](), [Security](), [Processes](), [Routing (disambiguation)]() Tags: [bug](), [process](), [release](), [routing](), [security](), [symfony]() ### AI overview Symfony 7.4.18 has been released with fixes across components including HttpClient, Security, Process, Routing, HttpFoundation, and Filesystem. ### Source excerpt Symfony 7.4.18 has just been released. Read the Symfony upgrade guide to learn more about upgrading Symfony and use the SymfonyInsight upgrade reports to detect the code you will need to change in your project. Tip... ## Detecting Replica Lag That Breaks Read-Your-Writes Consistency DevFeed: [Detecting Replica Lag That Breaks Read-Your-Writes Consistency]() Original publisher: [Read original article]() Author: hello@ankit-rana.com Published: 2026-08-28T00:00:00Z Content type: tutorial Language: en Sources: [Ankit Rana | Mechanical Sympathy]() Topics: [Replication](), [Routing (disambiguation)]() Tags: [checkout](), [consistency](), [lag](), [metric](), [observability](), [postgresql](), [primary](), [read-replica](), [read-replicas](), [replica-lag](), [replication](), [routing]() ### AI overview This article explains how read replicas can break read-your-writes behavior when applications do not route related reads to the primary or wait for replication. It compares byte lag with time lag, explains why idle systems can hide failures, and discusses replay delays caused by write bursts and long-running replica queries. ### Source excerpt Byte lag between primary and replica reads zero on an idle primary even when replication is completely stuck, so the metric that looks healthiest is the one that hides the failure. Time lag measured from the last replayed transaction is the signal that stays honest. Adding a read replica silently removes read-your-writes, which means any flow that writes and then reads back needs either primary routing or an explicit wait for the replica to reach that write's log position. ## \[Hands-on\] Turn Scientific Figures Into Structured Data with Mistral OCR DevFeed: [\[Hands-on\] Turn Scientific Figures Into Structured Data with Mistral OCR]() Original publisher: [Read original article]() Author: Avi Chawla Published: 2026-08-26T21:06:26Z Content type: tutorial Language: en Sources: [Daily Dose of Data Science]() Topics: [Artificial Intelligence](), [Routing (disambiguation)](), [incident](), [context window](), [FIRST](), [Google](), [SDKs]() Tags: [code](), [mistral](), [ocr]() ### AI overview The supplied excerpts discuss coordinating multiple agents and people through shared channels. They describe the limits of role-based handoffs, including duplicated work, lost context, and invisible negative results, and present Switch as a way to preserve shared reports and threads. The title and body appear to describe different subjects. ### Source excerpt A full walkthrough of the extraction schema, with code. ## Python projects now support routing rules DevFeed: [Python projects now support routing rules]() Original publisher: [Read original article]() Author: Ricardo Gonzalez Published: 2026-08-26T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [Routing (disambiguation)](), [Python](), [FastAPI](), [Django](), [Flask](), [Command-line interface](), [SDKs](), [Deployment](), [CI/CD](), [REST API]() Tags: [api](), [automation](), [ci-cd](), [cli](), [deployment](), [python](), [rest-api](), [routing](), [sdk](), [vercel]() ### AI overview Vercel now supports routing rules for Python projects, allowing response headers and request rewrites to internal paths for FastAPI, Django, and Flask applications. Rules are evaluated by the Vercel CDN before requests reach the application and can take effect immediately without a new deployment. ### Source excerpt Python projects can now use routing rules to set response headers or rewrite requests to internal paths, including apps built with FastAPI, Django, and Flask. The Vercel CDN evaluates rules before requests reach your application, so changes apply without a new deployment. For example, this FastAPI app serves a /new route: To send requests for /old to that route, create a rewrite from the CDN tab in your project dashboard or with the Vercel CLI: Published rules take effect immediately across all regions, and you can roll back to a previous version from the History tab. You can also manage rules from Python with the vercel SDK, which wraps the Vercel REST API. add_route stages the rule, and update_route_version publishes it: Rewrites can also be defined in vercel.json: Project-level rules live outside your deployment and are evaluated before its routes, so a published rule takes precedence over a vercel.json rewrite for the same path. Each surface fits a different workflow: How you define it Takes effect Best for CDN tab in the dashboard On publish Editing and testing rules visually Vercel CLI On publish One-off changes from the terminal vercel Python SDK or REST API On publish Automation and CI/CD vercel.json On each deployment Rewrites that ship with the application code Update Vercel CLI to the latest version and read the routing documentation to get started. Read more ## Multivendor SR-MPLS DevFeed: [Multivendor SR-MPLS]() Original publisher: [Read original article]() Published: 2026-08-25T05:44:00Z Content type: tutorial Language: en Sources: [ipSpace.net blog]() Topics: [SR-MPLS](), [networking](), [Routing (disambiguation)](), [IS-IS](), [GitHub]() Tags: [github](), [installation](), [is-is](), [mpls](), [netlab](), [network](), [routing](), [sr-mpls]() ### AI overview This tutorial demonstrates a multivendor SR-MPLS network built with netlab using Arista EOS, FRRouting, and SR Linux. It explains vendor-specific Segment Routing Global Block ranges, prefix segments, and MPLS LFIB label swapping, then outlines how to launch the lab through GitHub Codespaces. ### Source excerpt Summer is almost over, and it's time to resume regular programming with the next example from the Segment Routing workshop I had at ITNOG10: multi-vendor SR-MPLS. I used the same lab topology as in the previous examples but deployed Arista EOS on PE1, FRRouting on P, and SR Linux on PE21 Read more ... ## Do IXPs make the Internet faster? It's complicated DevFeed: [Do IXPs make the Internet faster? It's complicated]() Original publisher: [Read original article]() Author: Dan Fidler Published: 2026-08-23T23:05:33Z Content type: article Language: en Sources: [APNIC Blog]() Topics: [Internet](), [networking](), [Latency](), [Network](), [Low Latency](), [Streaming](), [Caching](), [Cloud](), [Resilience](), [Routing (disambiguation)](), [datasets]() Tags: [australia](), [cloud](), [content](), [cost](), [events](), [global](), [infrastructure](), [internet](), [ixps](), [latency](), [local](), [low-latency](), [netflix](), [network](), [networks](), [performance](), [resilience](), [routing](), [streaming](), [tech-matters](), [technology](), [thailand](), [thainog]() ### AI overview IXPs do not make the Internet uniformly faster. Their impact depends on how performance is defined, where content is hosted or cached, the type of exchange, and the surrounding network conditions. The article examines latency, throughput, streaming quality, reliability, routing, and the changing meaning of keeping traffic local. ### Source excerpt IXPs shape latency, cost, resilience, and the spread of new technologies, not just Internet speed. As the Internet evolves, the role of IXPs continues to expand, as highlighted in this BPF 2026 panel discussion. ## Microfrontends previews now link across repositories DevFeed: [Microfrontends previews now link across repositories]() Original publisher: [Read original article]() Author: Tim White Published: 2026-08-21T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [Git](), [Deployment](), [Routing (disambiguation)]() Tags: [deployment](), [feature](), [git](), [routing](), [update](), [vercel]() ### AI overview Vercel Microfrontends can now link Preview Deployments across separate repositories when corresponding Git branch names match exactly. The feature is enabled by default for new Microfrontends groups and can be managed in Microfrontends settings. ### Source excerpt Microfrontends can now link Preview Deployments across repositories when their Git branch names match exactly. In a monorepo, projects share the same Git repository, commits, and branches, so Vercel can automatically link their previews. Cross-repository projects have separate commit histories and branches in separate repositories. With this update, Vercel matches Git-connected projects by branch name and links their corresponding previews. For example, when you preview the new-checkout branch of one project, requests to other projects in the Microfrontends group will use their new-checkout previews when available. This makes it easier to review coordinated changes across repositories in one preview experience. This feature is enabled by default for new Microfrontends groups. You can manage it in your Microfrontends settings. Learn more about how deployment routing works for Microfrontends. Read more ## Online index migration and shard scaling in OpenSearch with the AOSC plugin DevFeed: [Online index migration and shard scaling in OpenSearch with the AOSC plugin]() Original publisher: [Read original article]() Author: Arpit Singla Published: 2026-08-18T21:56:28Z Content type: article Language: en Sources: [OpenSearch]() Topics: [Amazon OpenSearch Service](), [migration](), [Open Source](), [Routing (disambiguation)]() Tags: [blog](), [mapping](), [migration](), [open-source](), [opensearch](), [pipeline](), [plugin](), [production](), [reconciliation](), [routing](), [schema](), [technical](), [workflow]() ### AI overview This article introduces Automatic Online Schema Change (AOSC), an open-source OpenSearch plugin for migrating live indexes to pre-created targets with different mappings, settings, shard counts, or document shapes. It backfills existing documents, replays operations made during migration, and switches an alias after a short write block, while documenting its scaling behavior and limitations. ### Source excerpt Learn how the open-source AOSC plugin migrates live OpenSearch indexes--changing mappings, settings, or shard counts--without losing writes or requiring downtime. The post Online index migration and shard scaling in OpenSearch with the AOSC plugin appeared first on OpenSearch. ## BGP Role model: tracking the adoption of RFC 9234 DevFeed: [BGP Role model: tracking the adoption of RFC 9234]() Original publisher: [Read original article]() Author: Mingwei Zhang Published: 2026-08-18T15:21:32Z Content type: article Language: en Sources: [Cloudflare Blog]() Topics: [BGP](), [networking](), [Networks](), [Routing (disambiguation)](), [Protocol (disambiguation)](), [Cloudflare](), [Monitoring]() Tags: [analysis](), [bgp](), [cloudflare](), [internet](), [monitoring](), [network](), [networks](), [research](), [router](), [routing](), [routing-security](), [rpki]() ### AI overview This article examines the adoption of RFC 9234, which uses BGP Roles and the Only to Customer (OTC) attribute to help routers prevent and detect route leaks. Cloudflare measured deployment through its global peering presence and found that two large Tier-1 networks were stripping OTC attributes from forwarded routes. ### Source excerpt RFC 9234 lets routers reject route leaks on their own, using BGP Roles and the Only to Customer attribute. We measured who has deployed it, and found two Tier 1 networks unexpectedly stripping OTC. ## Exploring the BGP Neighbor CONNECT State DevFeed: [Exploring the BGP Neighbor CONNECT State]() Original publisher: [Read original article]() Published: 2026-08-18T05:16:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [BGP](), [networking](), [Finite-state machine](), [Routing (disambiguation)]() Tags: [bgp](), [blog-post](), [debug](), [routing]() ### AI overview An exploration of how Cisco IOS/XE presents the BGP neighbor CONNECT state during an incoming TCP session. The article tests several lab scenarios involving passive neighbors, static discard routes, ACLs, and suppressed ICMP unreachable messages, finding that CONNECT appears in BGP debugging output while the neighbor remains Idle in the displayed operational state. ### Source excerpt Sakar left an interesting comment on my The Curious Case of the BGP Connect State blog post, claiming that Cisco IOS/XE goes through a CONNECT state when opening an incoming BGP session. I wanted to double-check this behavior, so I needed a scenario where one router would keep sending TCP SYN requests, the other would not (or we wouldn't learn anything), and the two routers could not communicate (or they'd quickly go into the OPEN state). Here's my first attempt at meeting those requirements: Read more ... ## The Checks That Lied DevFeed: [The Checks That Lied]() Original publisher: [Read original article]() Author: EduuhMuraya Published: 2026-08-14T00:00:00Z Content type: article Language: en Sources: [EduuhMuraya]() Topics: [networking](), [Firewall](), [Routing (disambiguation)](), [Networks](), [Pi-hole]() Tags: [automation](), [dns](), [firewall](), [infrastructure](), [network](), [opnsense](), [proxmox](), [routing](), [security](), [server](), [servers]() ### AI overview A home-network segmentation test produced misleading green results because the checks did not reliably measure the firewall or connectivity. The article describes routing around the firewall through a dual-homed Proxmox host and a DNS check that treated resolver failures as successful output. ### Source excerpt I segmented my network, wrote tests to prove it, and watched the tests pass while measuring nothing at all. Then the same disease turned up in my home automation, and left a freezer switched off for thirteen hours in a house full of green ticks. ## Kimwolf v7: An Evolution of the Kimwolf Botnet DevFeed: [Kimwolf v7: An Evolution of the Kimwolf Botnet]() Original publisher: [Read original article]() Author: Asher Davila, Chris Navarrete and Doel Santos Published: 2026-08-11T10:00:16Z Content type: article Language: en Sources: [Unit 42]() Topics: [Kimwolf v7](), [Android](), [DDoS](), [Internet of things](), [C2](), [Ethereum Name Service (ENS)](), [Malware](), [Cybercrime](), [Ethereum](), [Blockchain](), [Routing (disambiguation)](), [Threat Hunting & Intel]() Tags: [android](), [android-apk](), [blockchain](), [c2](), [ddos](), [devices](), [ethereum](), [http](), [iot-botnets](), [kimwolf-v7](), [linux](), [malware](), [network](), [networks](), [resilience](), [routing](), [rpc](), [spoofing](), [threat-research]() ### AI overview Kimwolf v7 is an Android and IoT botnet variant that adds HTTP/2-based DDoS flooding with browser fingerprinting, Ethereum Name Service resolution for C2 addresses, and Tor-backed routing to improve infrastructure resilience. The article also describes its targeting of Android TV devices and exploitation of unauthenticated ADB instances. ### Source excerpt Discover how Kimwolf v7 targets Android IoT devices with HTTP/2 DDoS fingerprinting, Ethereum ENS C2 resolution and Tor backup routing. The post Kimwolf v7: An Evolution of the Kimwolf Botnet appeared first on Unit 42. [Next page]()