# cdn Published articles for cdn. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Researchers link the RubyHack campaign to alleged OpenAI-connected agents, while RubyGems disputes key claims DevFeed: [Researchers link the RubyHack campaign to alleged OpenAI-connected agents, while RubyGems disputes key claims]() Original publisher: [Read original article]() Author: amaksimovv (CodeScoring) Published: 2026-09-16T15:08:49Z Content type: news Language: ru Sources: [Tagir Valeev]() Topics: [rubygems](), [Ruby](), [OpenAI](), [legacy](), [API]() Tags: [api](), [appsec](), [cdn](), [gemstuffer](), [legacy](), [load](), [openai](), [ruby](), [rubydoc](), [rubygems](), [rubyhack](), [tag-070ecaaf0eda](), [tag-64251c106897](), [yard]() ### AI overview Researchers from Nightingale Collective linked the RubyHack campaign in RubyGems to alleged internal OpenAI agents. The article describes malicious code executed during RubyDoc documentation builds, data collection from British municipal websites, attempts to obtain RubyGems API keys, and a caching flaw involving legacy keys. RubyGems said it could not independently identify the package creators and found no evidence that чужие keys were successfully obtained. ### Source excerpt 11 сентября исследователи Nightingale Collective опубликовали разбор RubyHack и связали майскую кампанию в RubyGems с внутренними агентами OpenAI. По их версии, скрипты внутри пакетов запускали код в инфраструктуре RubyDoc, собирали открытые данные с сайтов британских муниципалитетов и публиковали результаты обратно в реестр. В нескольких образцах исследователи также обнаружили попытки получить чужие API-ключи RubyGems. Команда RubyGems не смогла независимо установить, кем именно были созданы пакеты, и не нашла доказательств успешного получения чужих ключей. Во время майской кампании она отозвала вредоносные пакеты и на четыре дня остановила регистрацию новых пользователей. Одной из точек входа стала обычная сборка документации. В пакет добавляли .yardopts - файл параметров генератора YARD - с указанием загрузить Ruby-скрипт. Когда для пакета запрашивали документацию на RubyDoc, сборщик обрабатывал этот файл и запускал вложенный код. Такое поведение соответствует механике самого YARD: параметр --load загружает указанный Ruby-файл перед выполнением команды. Запущенный скрипт обращался к муниципальным сайтам, сохранял ответы, собирал из них новый .gem-архив и отправлял его в RubyGems со встроенным ключом. В результате реестр использовался как канал передачи и хранения собранных данных. Установка такого пакета множеством разработчиков для работы этой схемы не требовалась: достаточно было исполнения кода в сервисе сборки документации. Отдельные пакеты обращались к старому endpoint выдачи API-ключей. В нём действовала ошибка кэширования: при определённых условиях CDN мог сохранить ответ с legacy-ключом и до часа отдавать его следующим запросам на том же узле. RubyGems исправил проблему 9 июля, очистил кэш, отозвал legacy-ключи и затем отключил старый endpoint. Читать далее ## Minimizing the length of regular expressions, in practice DevFeed: [Minimizing the length of regular expressions, in practice]() Original publisher: [Read original article]() Author: Khan Academy Published: 2016-05-23T22:00:00Z Content type: tutorial Language: en Sources: [Khan Academy]() Topics: [Algorithms, Complexity](), [Regular expression](), [Programming](), [cloud-infrastructure]() Tags: [algorithms](), [cdn](), [configuration](), [engineering](), [google](), [hosting](), [infrastructure](), [news](), [re](), [repository](), [software-engineering]() ### AI overview Craig Silverstein explains how Khan Academy needed a compact regular expression to distinguish static URLs from dynamic URLs for CDN routing. The article describes why simple patterns were unsuitable, reports that a naive generated expression reached 402,025 characters, and introduces a second approach that reduced the length to 2,400 characters. ### Source excerpt By Craig Silverstein The problem Software engineering interviews tend to be full of "algorithms" questions, because they're easy ... Read more ## How Khan Academy Scaled to 2.5x Traffic During the Coronavirus Pandemic DevFeed: [How Khan Academy Scaled to 2.5x Traffic During the Coronavirus Pandemic]() Original publisher: [Read original article]() Author: Khan Academy Published: 2020-05-09T22:00:00Z Content type: article Language: en Sources: [Khan Academy]() Topics: [Scalability](), [Architecture & Design](), [Serverless](), [Caching](), [Google Cloud Platform (GCP)](), [Load Balancing]() Tags: [architecture](), [caching](), [cdn](), [engineering](), [gcp](), [google-cloud](), [load-balancing](), [news](), [scalability](), [serverless](), [web]() ### AI overview Marta Kosarchyn explains how Khan Academy handled site usage reaching 2.5 times the previous year's level during the coronavirus pandemic. The article attributes the scalability to Google Cloud services, serverless infrastructure, Datastore, Memcache, Fastly CDN caching, and advance preparation. ### Source excerpt By Marta Kosarchyn Talk about rapid scaling... A few months ago I posted some thoughts on scaling and ... Read more ## Cloudflare Tests Cache Transcoding to Reduce Storage Requirements DevFeed: [Cloudflare Tests Cache Transcoding to Reduce Storage Requirements]() Original publisher: [Read original article]() Author: Renato Losio Published: 2026-09-13T10:35:00Z Content type: news Language: en Sources: [InfoQ]() Topics: [Caching](), [Transcodings](), [cloud-infrastructure](), [Pingora]() Tags: [architecture-design](), [cache](), [caching](), [cdn](), [cloud](), [cloudflare](), [cloudflare-cache-transcoding](), [compression](), [cpu](), [data-centers](), [development](), [edge-computing](), [news](), [pingora](), [rust](), [storage]() ### AI overview Cloudflare is testing Cache Transcoding, a prototype that Zstandard-compresses eligible uncompressed text before it is stored in cache. The approach aims to increase effective cache capacity and reduce inter-data-center transfer, with configurable CPU and storage trade-offs. ### Source excerpt Cloudflare recently described a prototype called Cache Transcoding that compresses eligible cache content, mainly uncompressed text such as HTML, JSON, CSS, and JavaScript, using Zstandard before storing it on disk. The hyperscaler estimates that the approach could provide petabytes of additional effective cache capacity, although broader testing is still needed. By Renato Losio ## FastAPI frontends and static files served from the CDN DevFeed: [FastAPI frontends and static files served from the CDN]() Original publisher: [Read original article]() Author: Daniel Park Published: 2026-09-10T17:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [FastAPI](), [Vercel](), [Front end](), [mount]() Tags: [cdn](), [frontend](), [mount](), [tool](), [vercel]() ### AI overview Vercel now promotes FastAPI frontends and static files served through app.frontend() or StaticFiles to the Vercel CDN at build time, allowing matching requests to bypass Vercel Functions. Route precedence is preserved, while dependency-protected frontends and middleware-protected static files remain on the function unless configured otherwise. ### Source excerpt FastAPI frontends and static files, served with app.frontend() or StaticFiles, are now promoted to the Vercel CDN at build time. Requests for those paths are served directly from the CDN, without invoking your Vercel Function. FastAPI evaluates routes in declaration order. A route declared before a StaticFiles mount takes priority over any CDN file at that path. This precedence is preserved. Promoted source directories remain in the function bundle so the app can read from them at runtime. To exclude them and serve only from the CDN, set tool.vercel.fastapi.static.exclude = true in pyproject.toml. Frontends guarded by dependencies are kept on the function as the CDN cannot run dependency checks. Similarly, static files which sit behind middleware are also kept on the function. To override this and always promote to CDN, set tool.vercel.fastapi.static.cdn = true. To opt out of the CDN entirely, set it to false instead. For more information see the Vercel FastAPI documentation. Read more ## 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 ## The Internet's New Edge Builders DevFeed: [The Internet's New Edge Builders]() Original publisher: [Read original article]() Author: Arman Obosyan Published: 2026-09-08T06:55:03Z Content type: article Language: en Sources: [RIPE Labs]() Topics: [Internet](), [Cloud](), [Networks](), [Network](), [amazon](), [Google](), [Meta](), [Microsoft]() Tags: [amazon](), [architecture](), [article](), [atlas](), [cdn](), [cloud](), [google](), [infrastructure](), [internet](), [internet-infrastructure](), [measurements](), [meta](), [microsoft](), [network](), [networks](), [peering](), [research](), [systems]() ### AI overview The article examines how content and cloud platforms are moving from operating private backbones toward controlling delivery infrastructure closer to users. It discusses the changing role of traditional CDNs, public measurements of international bandwidth, private interconnection and caches within access networks, and what Google and Meta deployments reveal about network operators. ### Source excerpt After building private backbones, content and cloud platforms are now moving closer to users. In doing so, they are taking on delivery roles once associated mainly with independent CDNs. ## Video Streaming Technology: Protocols, Codecs, CDNs, and 2026 Trends DevFeed: [Video Streaming Technology: Protocols, Codecs, CDNs, and 2026 Trends]() Original publisher: [Read original article]() Author: Jon Whitehead Published: 2026-09-08T01:00:42Z Content type: tutorial Language: en Sources: [DaCast]() Topics: [Streaming](), [5G](), [Artificial Intelligence](), [Low Latency](), [real-time](), [WebRTC](), [Virtual reality]() Tags: [access-control](), [ai](), [cdn](), [encryption](), [guide](), [latency](), [low-latency](), [streaming](), [technology](), [the-video-experts-blog](), [video](), [video-streaming]() ### AI overview This guide explains how video streaming works, covering data encoding, delivery through content delivery networks, decoding by video players, streaming protocols, codecs, and security. It also discusses AI-driven tools, low-latency streaming, 5G, edge computing, virtual reality, and business applications in 2026. ### Source excerpt By Dacast Editorial Team | Reviewed by Jon Whitehead, COO at Dacast | Updated September 2026 Video streaming technology has revolutionized the way businesses and individuals share and consume content. Whether it's live streaming a product launch, hosting virtual events, delivering training sessions, or providing entertainment through on-demand video services, streaming technology is now an [...] The post The Definitive Guide to Video Streaming Technology in 2026 appeared first on Dacast. ## Your Agent Speaks MCP. Give It a Computer. DevFeed: [Your Agent Speaks MCP. Give It a Computer.]() Original publisher: [Read original article]() Published: 2026-09-03T00:00:00Z Content type: article Language: en Sources: [The Fly Blog]() Topics: [MSP MCP](), [AI Bots]() Tags: [agents](), [api](), [auth](), [cdn](), [claude](), [claude-code](), [cli](), [close-to-users](), [cloud](), [codex](), [cursor](), [deploy-app-servers](), [docker](), [elixir](), [filesystems](), [fly](), [fly-io](), [gemini](), [heroku-alternative](), [heroku-competitor](), [hosting](), [i](), [mcp](), [mcp-server](), [networking](), [postgresql-clusters](), [servers](), [skills]() ### AI overview The article presents Sprites as disposable cloud computers for coding agents and explains using their API through MCP. It argues that MCP transport and progressive capability disclosure can work together, including through plugins and skills. ### Source excerpt Sprites are disposable cloud computers. They appear instantly, always include durable filesystems, and cost practically nothing when idle. They're the best and safest place on the Internet to run agents and we want you to create dozens of them. Sprites are a place to run agents; the first thing you should think to do with a new Sprite is to type claude (or gemini or codex). We've put a lot of effort into making sure coding agents feel safe and happy when they're on Sprites, because, to (probably) quote John von Neumann, "happy agents are productive agents." What's less obvious about Sprites is that they're great tools for agents. Want three different versions of a new feature? A test environment? An ensemble of cooperating services? It's super handy to be able to start your prompts, "On a new Sprite, do...". The Sprites API is simple, discoverable, and designed for this use case. The only real question is how your agent reaches it. For most of you the answer is MCP, and the setup is already written. You Don't Have To Pick There's an argument going around that MCP is the wrong way to extend an agent, and that command line tools and discoverable APIs are the Right Way. Half of that argument is correct, and it's the important half, so let's take it seriously. Dumping thirty tool descriptions into a context window is a bad way to teach anything. Not every Sprite command matters in every session, and cramming them all in signals to the model that they all matter to you. If you're not using network policies, gemini shouldn't burn a single token learning to configure them. Capabilities should reveal themselves progressively, the way they do when an agent works out a CLI one subcommand at a time. The wrong half is treating that as a case against MCP. Progressive disclosure is a question of what you say to the model. MCP is a question of how the bytes get there: transport, auth, structured results, a tool the model can call instead of a command whose flags it has to guess. Tho ## Encrypted Client Hello (ECH) is now supported on Vercel CDN DevFeed: [Encrypted Client Hello (ECH) is now supported on Vercel CDN]() Original publisher: [Read original article]() Author: Faryal Siddiqui Published: 2026-08-14T16:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Cryptography]() Tags: [cdn](), [chrome](), [dns](), [edge](), [encryption](), [firefox](), [tls](), [vercel]() ### AI overview Vercel CDN now supports Encrypted Client Hello for domains managed by Vercel DNS, encrypting SNI during the TLS handshake. The rollout begins selectively in the US for limited TLDs and will expand over time. ### Source excerpt Vercel CDN now supports Encrypted Client Hello (ECH) for domains managed by Vercel DNS. ECH encrypts the Server Name Indication (SNI) in the TLS handshake, the last part of an HTTPS connection that revealed which hostname a client was connecting to. With ECH, network observers see a connection to Vercel's shared ECH hostname, vercel-ech.com. ECH is managed at the platform level and automatically enabled selectively where supported, starting in the US for a limited number of TLDs, and expanding to more TLDs and regions over time. Recent versions of Chrome, Edge, and Firefox support Encrypted Client Hello. Learn more about ECH and how Vercel CDN protects your application in the CDN encryption documentation. Read more ## New setup page after domain checkout DevFeed: [New setup page after domain checkout]() Original publisher: [Read original article]() Author: Can Temizyurek Published: 2026-08-05T17:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [Routing (disambiguation)](), [Caching](), [DDoS](), [Firewall](), [Amazon Route 53](), [Git](), [Template]() Tags: [cache](), [cdn](), [checkout](), [ddos](), [dns](), [firewall](), [git](), [google](), [routing](), [vercel]() ### AI overview Vercel has introduced a post-checkout setup page for domain purchases. It tracks registration status and provides guided actions for deploying or connecting projects, proxying or redirecting existing sites, and configuring email DNS records. ### Source excerpt Buying a domain on Vercel now takes you to a setup page that tracks registration live, with direct paths to deploy a new project, connect an existing one, proxy or redirect a site you already run, or set up email. Registration can take a few minutes. Each setup action unlocks as soon as the domain is ready. If registration fails, the page shows what went wrong and the status of your refund. Deploy a new project or connect an existing one Deploy something opens project creation with the domain preselected. Connect a Git repository, prompt with v0, or start from a template, and the domain is attached when the project deploys. Connect an existing project attaches the domain to a project you pick from your team. Proxy or redirect a site you already run Enter an origin to proxy traffic to, and requests to the domain route through Vercel's CDN. Vercel will cache applicable requests at the edge, and Vercel Firewall's automated DDoS protections will automatically run. Enter a URL to redirect, and visitors are forwarded there. In both cases, Vercel creates a project to handle the routing and configures it for you. Set up email with DNS presets Choose your email provider and Vercel adds the DNS records it needs. Presets are available for Google Workspace, Outlook, iCloud, Proton Mail, Zoho, Mailgun, and ImprovMX. There's also a preset for using the domain as your Bluesky handle. If you'd rather configure records yourself, Manage DNS records opens the domain's DNS records page. Search for a domain at vercel.com/domains to get started. Read more ## Next.js 16.3 support on Vercel DevFeed: [Next.js 16.3 support on Vercel]() Original publisher: [Read original article]() Author: Mark Knichel Published: 2026-08-04T07:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Next.js](), [telemetry]() Tags: [cache](), [cdn](), [next-js](), [observability](), [performance](), [release](), [routing](), [support](), [vercel]() ### AI overview Vercel adds full support for Next.js 16.3, including immutable static asset reuse, leaner prefetching, faster route resolution, and additional observability. The article reports reduced prefetch and CDN requests, lower static-content transfer, and faster deployments for upgraded applications. ### Source excerpt Yesterday the Next.js team announced the release of Next.js 16.3, with leaner prefetching, immutable static assets, and instant navigations. As part of this release, we worked with the Next.js team to fully support 16.3 on Vercel, including better performance and additional observability. Applications that have upgraded have seen: Fewer prefetch requests: Apps upgrading from 16.2 to 16.3 saw 45% fewer prefetch requests on average, with some seeing reductions over 70%. Lower static asset costs: With immutable static assets, upgraded apps saw 17% fewer CDN requests and 24% fewer bytes transferred for static content, and up to 60% global TTFB reductions for frequently deployed projects. Faster routing at scale: Routing metadata improvements in the critical serving path deliver ~2x faster p99 route resolution for large sites. Platform improvements Next.js 16.3 ships leaner prefetching and enables immutable static assets by default. Supporting both meant changing the platform too, in how it caches static assets, resolves routes, and surfaces what happened in production. Immutable static assets Vercel now supports reusing immutable static assets across deployments for Next.js. Immutable static assets can't suffer from version skew, even for projects without Skew Protection enabled, and the browser cache survives redeploys. Because Next.js uses query-parameter-based Skew Protection, this change cut CDN requests by 17% and bytes transferred by 24% for static content. Deployments also complete up to 30% faster on average, since unchanged assets skip re-upload. In Next.js 16.3, immutable static assets are enabled by default. Next.js 16.3 outputs immutable content-addressed static assets under the public path /_next/static/immutable/*. The Vercel CDN uses this prefix to differentiate immutable static assets from other static assets. If you're a framework author and want to implement this in your own toolchain, see the immutable static files section of the Build Output API docs ## Server-Timing response headers will pass through to the client DevFeed: [Server-Timing response headers will pass through to the client]() Original publisher: [Read original article]() Author: Steven Salat Published: 2026-07-30T12:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [Caching](), [browser](), [API](), [Back end]() Tags: [2026](), [api](), [backend](), [browser](), [cache](), [cdn](), [performance](), [vercel]() ### AI overview Vercel's CDN will pass the Server-Timing response header through to clients starting August 10, 2026. This enables backend metrics such as database query time and cache hits to appear in browser network panels and through the Performance API. ### Source excerpt On August 10, 2026, Vercel's CDN will stop stripping the Server-Timing response header and begin passing it through to the client. Use Server-Timing to report backend metrics like database query time and cache hits. These values appear in the browser's network panel and as PerformanceServerTiming entries through the Performance API. If you want to keep the current behavior, where the header is stripped from every response, you can add a transform in vercel.json: Learn more about the Performance API and Server Timing. Read more ## Turn And Face The Strange DevFeed: [Turn And Face The Strange]() Original publisher: [Read original article]() Published: 2026-07-24T00:00:00Z Content type: article Language: en Sources: [The Fly Blog]() Topics: [AI Chat]() Tags: [agents](), [ai](), [cdn](), [close-to-users](), [cloud](), [cloud-infrastructure](), [coding](), [deploy-app-servers](), [docker](), [elixir](), [fly](), [fly-io](), [heroku-alternative](), [heroku-competitor](), [hosting](), [i](), [networking](), [postgresql-clusters](), [servers](), [software-development]() ### AI overview Fly.io says it is raising more money, launching a new iteration of Sprites--computers for agents--and refocusing the company around that product as AI reshapes software development. ### Source excerpt We're Fly.io, a public cloud platform that is both our favorite way to put an app on the Internet and our favorite way to safely let a frontier agent coding harness cook. This is a post about our company, the future, and Sprites, which are computers for agents that you can check out right now. This is a complicated post. So I need you to promise me something: if you read past this introduction, you'll read the whole rest of the way through. It's an honor thing. A couple months back, Theo Browne ran a video rating the "best place to host a new application in 2026". Theo tends to say nice things about us. He did this time too. But then he concluded by saying that of all the providers he pays attention to, we were the one he was least confident would be around by the end of the year. Well, fuck. Theo startled us, because we're in the middle of a run of strong quarters that have included the best financial months in the company's history. But that take has been rattling around in my brain. It whacked me right on a raw nerve, about what we're doing and where we're going as a company. Honestly, I should've seen this coming. Fly.io has been motoring along this year, but I've coasted a bit, letting the company smolder in an unresolved identity crisis. I'm going to overshare some more in a second, but I won't leave you hanging. So: we've raised a bunch more money. We're launching a new iteration of Sprites, and focusing the company on them and the problem they solve. And I'm tagging in Scott Johnston as CEO. Product-Market Fit I started Fly.io with two clear principles that probably don't matter anymore. The first is that Internet applications work best when they're fast, and that happens when they're deployed close to users. I learned this over many years of working at Ars Technica, and started Fly.io in part to scratch an itch. It was our mantra over the first several years of the company. The second is that cloud infrastructure is too complicated. Developers need platform ## Runtime logs now show cache reasons DevFeed: [Runtime logs now show cache reasons]() Original publisher: [Read original article]() Author: Shina Patel Published: 2026-07-17T01:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [telemetry](), [Grafana]() Tags: [cache](), [cdn](), [cli](), [debug](), [logs](), [metrics](), [vercel]() ### AI overview Vercel runtime logs now display cache reasons for cacheable CDN responses, helping developers diagnose cache misses and improve hit rates. The reason is available in the Logs tab and through selected CLI commands. ### Source excerpt Runtime logs now show a Cache Reason explaining why a request wasn't a fresh cache hit, for example a time-based or tag-based revalidation. Use cache reasons to debug misses and improve your hit rate. Cache reasons appear for any response the CDN can cache, including ISR, Partial Prerendering, and functions that set a Cache-Control header with directives like stale-while-revalidate. Responses rendered dynamically on every request don't have a cache reason. Cache status Possible reasons MISS Cold, Request collapsed, Error BYPASS Draft Mode, Prerender Bypass, Crawler STALE Time-based revalidation, Tag-based invalidation, Revalidation error REVALIDATED Tag-based deletion Open the Logs tab and select a request to see the reason alongside its cache status. Each status and reason links to its entry in the Cache Status and Reasons reference. From the CLI Cache reason is available in vercel logs, vercel metrics, and Vercel plugin's cdn-caching skill: Learn more about cache statuses and reasons. Read more ## Optimized CDN caching and deploying of immutable static assets DevFeed: [Optimized CDN caching and deploying of immutable static assets]() Original publisher: [Read original article]() Author: Niklas Mischkulnig Published: 2026-07-17T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [Caching](), [Cache](), [Optimization](), [Next.js](), [toolchain]() Tags: [cache](), [caching](), [cdn](), [next-js](), [optimization](), [toolchain](), [vercel]() ### AI overview Vercel now reuses immutable, content-addressed static assets across deployments for supported frameworks. The zero-configuration optimization reduces CDN requests and transferred bytes, speeds deployments, and can significantly lower global time to first byte. Next.js 16.3 preview and later support it by default, with additional framework support planned. ### Source excerpt Vercel now reuses static files across deployments for frameworks that output content-addressed assets. It's zero-config: Vercel uses Framework-defined infrastructure to manage these immutable files alongside your code changes, handling the hard parts like hash collisions, file lifecycles, and efficient routing. This brings several benefits: Lower costs and improved cache hit rates -- For frameworks using query-parameter-based Skew Protection (such as Next.js), we saw 17% fewer CDN requests and 24% fewer bytes transferred for static content. Faster Deployments -- Deployments complete up to 30% faster on average. Faster Time to First Byte -- Immutable assets can remain cached across deployments, giving frequently deployed projects up to a 60% reduction in global TTFB. Vercel's supported frameworks will automatically take advantage of this optimization, even for projects without Skew Protection enabled. Next.js 16.3 preview and later already have it enabled out of the box, and support for additional frameworks (including Nitro) is coming soon. No configuration is required: upgrading to a supported framework version is all you need to do. If you're a framework author and want to implement this in your own toolchain, see the immutable static files section of the Build Output API docs. Read more ## Vercel Blob now supports consistent reads on private storage DevFeed: [Vercel Blob now supports consistent reads on private storage]() Original publisher: [Read original article]() Author: Agustin Falco Published: 2026-07-14T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [Cache](), [SDKs](), [cloud-infrastructure](), [JSON]() Tags: [cache](), [cdn](), [documentation](), [json](), [sdk](), [vercel]() ### AI overview Vercel Blob now supports consistent reads for private storage. Passing useCache: false to get() or presignUrl() bypasses cached reads so the result reflects the latest write, although the request takes longer and incurs Fast Origin Transfer. The same behavior can be enabled directly on a private blob URL with a cache=0 query parameter. ### Source excerpt Vercel Blob now supports consistent reads on private storage. Pass useCache: false to get() or presignUrl() for a read that reflects the latest write. A blob written to a fresh pathname has no existing cached entry, so reads reflect the latest write immediately. When you overwrite a blob at an existing pathname, readers might see the cached version for up to 60 seconds. When a read must reflect the latest write, like an agent's memory file, a session transcript, or a scheduled JSON report, pass useCache: false. These reads bypass the CDN, take longer than cached reads, and incur Fast Origin Transfer. You can also bypass the cache without the SDK. Under the hood, useCache: false adds a cache=0 query parameter to the request. You can set it yourself on a private blob URL: Install the latest @vercel/blob SDK for consistent reads: Learn more in the consistent reads documentation. Read more ## Vercel and Shopify are rebuilding Hydrogen DevFeed: [Vercel and Shopify are rebuilding Hydrogen]() Original publisher: [Read original article]() Author: Amelia Charles Published: 2026-06-30T04:00:00Z Content type: news Language: en Sources: [Vercel News]() Topics: [modern web development](), [SDKs](), [Web Development]() Tags: [api](), [cdn](), [javascript](), [next-js](), [open-source](), [react](), [shopify](), [svelte](), [vercel]() ### AI overview Vercel and Shopify are rebuilding Hydrogen as an open-source, runtime-agnostic toolkit for headless storefronts. It centralizes Shopify API utilities, cart state, and server-side integrations while supporting frameworks including React, Next.js, Nuxt, and Svelte. ### Source excerpt Hydrogen made headless storefronts easy to ship, but not portable. At Vercel Ship 26 in New York, we announced that we are working with Shopify to rebuild it from the ground up, a shared bet on a more open web. The new version is open source and runtime agnostic, meaning it can run anywhere JavaScript does. You can build with Svelte, Nuxt, Next.js or even bring your own custom framework. Our strategy includes three layers: core, client and server. The core Core is the JavaScript we all used to write for the Shopify API, and never shared. Now it lives in one place. Take formatMoney. The open web already solved most of this with Intl.NumberFormat. But the Shopify API doesn't hand you a number. It responds with a custom type, MoneyV2, and the amount is a signed decimal number serialized as a string. The result is the same, but you're not writing or maintaining the glue code anymore. When the API changes, the upgrade is trivial. Centralize the core and you fix each bug once, ship improvements to everyone, and get back to building. The client Rendering what the core returns involves the same repeated decisions. Cart state is the obvious one. Anyone who's built a commerce app has written a version of this. Different code every time, all chasing the same things. With Hydrogen, the client layer now handles the cart. State management becomes one import. Centralize this and you get the best practices for free, so you can spend your time on the parts that are actually yours to build. It's available for React today on the Hydrogen preview branch, with more frameworks coming. The server Developers need full-stack access to build storefronts that scale without sacrificing performance. Static content should serve instantly from a CDN while dynamic data like inventory streams in. The open-source community solved this with frameworks like Next.js, Nuxt, and SvelteKit: full-stack capabilities with no lock-in to a proprietary runtime. Say your storefront caches product queries with on ## HTTP 206 Partial Content Explained DevFeed: [HTTP 206 Partial Content Explained]() Original publisher: [Read original article]() Author: j2sw Published: 2026-06-26T11:37:15Z Content type: tutorial Language: en Sources: [Justin Wilson (j2sw)]() Topics: [HTTP](), [client](), [browser](), [file](), [servers](), [Cache]() Tags: [browser](), [cache](), [cdn](), [client](), [file](), [http](), [http-206](), [http-codes](), [internet-architecture](), [large-files](), [range](), [request](), [server](), [video](), [web-servers](), [web-troubleshooting]() ### AI overview This tutorial explains HTTP 206 Partial Content, a successful response used when a client requests only part of a file or other resource. It describes byte-range requests, the Range and Content-Range headers, and uses such as video playback, resumable downloads, and cache or CDN handling. ### Source excerpt A browser does not always need the whole file at once. Sometimes it only needs a slice of the file. That slice might be the next part of a video or a chunk of a large object sitting behind a CDN. When that happens, the client can request a byte range instead of requesting the ... Read more The post HTTP 206 Partial Content Explained appeared first on Justin Wilson (j2sw). ## Reduce CDN log costs with searchable archives DevFeed: [Reduce CDN log costs with searchable archives]() Original publisher: [Read original article]() Author: Rufina Mariam Published: 2026-06-26T00:00:00Z Content type: tutorial Language: en Sources: [Datadog | The Monitor blog]() Topics: [archive search](), [telemetry](), [incident](), [Amazon S3]() Tags: [amazon-s3](), [archive-search](), [cdn](), [cost](), [devsecops](), [incident](), [log-management](), [logs](), [observability-pipelines](), [storage]() ### AI overview The article presents a cost-conscious approach to retaining high-volume CDN logs: route raw logs to object storage with Observability Pipelines, retain key signals in Datadog, and use Archive Search for historical investigations. ### Source excerpt Route high-volume CDN logs to low-cost object storage with Observability Pipelines and search them with Archive Search--without a second tool. ## Building Agents that Don't Break Themselves DevFeed: [Building Agents that Don't Break Themselves]() Original publisher: [Read original article]() Published: 2026-06-08T00:00:00Z Content type: tutorial Language: en Sources: [The Fly Blog]() Topics: [AI Bots]() Tags: [agent](), [agents](), [ai](), [api](), [bash](), [cdn](), [close-to-users](), [deploy-app-servers](), [docker](), [elixir](), [fly](), [fly-io](), [heroku-alternative](), [heroku-competitor](), [hosting](), [i](), [networking](), [node-js](), [postgresql-clusters](), [sandbox](), [sandboxes](), [servers]() ### AI overview A tutorial on keeping long-lived AI agents safe by separating the agent process from risky shell execution. It recommends running each potentially destructive task in an isolated, disposable Sprite rather than letting the agent execute commands in its own environment. ### Source excerpt Building agents is fun. Rebuilding agents that break themselves... less so. A lot of Fly people are building agents with less of a penchant for self-destruction by teaching their agents to do anything risky in a Sprite. You get an agent that stays alive long enough to actually use its snazzy self-improvement features, and you can allow your agent to try things that would otherwise be battleship-scale footguns. Here's how to do it. Brains vs Hands Your agent would be pretty useless without a shell, because this is where it does agent things. Run the test suite, apply the migration, install the dependency, delete the temp files. Unfortunately, your agent's shell access is also what tends to ruin your afternoon, simply because "delete the temp files" and "delete the wrong files" are one fat-fingered glob apart, and as we're frequently warned, AI can make mistakes. This is why we have sandboxes. But a lot of people default to putting an agent that's going to do potentially scary work in a sandbox. This comes with a long list of tradeoffs that you really don't have to make, because where your agent lives and where it runs code are two entirely separate considerations. PPE for agent workers. The agent process is a loop. It calls a model, reads the response, picks a tool, rinse and repeat. It's a long-lived process that only becomes more competent and less stupid if memory, skills and history persist. So a Fly Machine that sleeps when idle and wakes on a message, a small VPS. Your laptop while you iterate. These are all fine homes for a loop calling an API, which doesn't need a blast shield. It's when you want your agent to execute that things get hairy. bash -c + whatever string the model just produced needs to be run in a padded room. Somewhere where the agent's code can't break itself or anything connected to it. And if your agent is doing more work than you are, you're going to want a whole facility of padded rooms that can be thrown away and rebuilt on a whim. One Sprit ## Mapping major CDNs across the globe DevFeed: [Mapping major CDNs across the globe]() Original publisher: [Read original article]() Published: 2026-06-06T13:17:04Z Content type: article Language: en Sources: [Personal blog of Anurag Bhatia]() Topics: [BGP](), [networking](), [Networks](), [Routing (disambiguation)](), [TLS (Transport Layer Security)](), [data](), [Amazon Web Services](), [Google](), [Netflix](), [Microsoft](), [Pingora]() Tags: [akamai](), [apple](), [aws](), [bgp](), [cdn](), [data](), [dns](), [facebook](), [fna](), [ggc](), [google](), [major](), [mapping](), [microsoft](), [netflix](), [networks](), [oca](), [routing](), [tls]() ### AI overview This article maps major content delivery networks worldwide by examining routed IP prefixes, open port 443 services, TLS certificate names, autonomous system numbers, and geographic data. It reports global and India-specific coverage figures for Google GGC, Facebook FNA/MNA, Netflix, Akamai, Apple, Microsoft, and AWS CloudFront, while noting that certificate-based identification may miss some deployments. ### Source excerpt In Dec 2022 I mapped popular CDNs like Google GGC, Facebook FNA, Akamai, etc. across Indian networks (post here). Since it's been close to 4 years now, I wanted to do that again. This time, I decided to expand the scope to the entire globe instead of just the Indian networks. Mapping logic The logic here is simple: get unique prefixes from the global routing table, break them into /24s, uniquely sort out /24s, and this gives all routed IP addresses in the world in batches of /24s (256 IPs). Next, identify the ones with an open port 443 and then connect to each of them to figure out the TLS certificate common name. Next, map those IP addresses to AS numbers, locations, etc., using Maxmind's GeoIP Lite databases. Essentially, I am using the BGP routing table instead of scanning the entire 0.0.0.0/0 to avoid scanning for prefixes which are not routed in the global table as well as reserved private IPs, etc. Global stats CDN Provider No. unique ASNs TLS domain Details list URL Google GGC 4247 googlevideo.com csv & json Netflix OCA 2903 oca.nflxvideo.net, assets.nflxext.com csv & json Facebook FNA 2548 'fbcdn.net', fna.whatsapp.net csv & json Akamai 1094 edgesuite.net, edgekey.net, akamaized.net, akamaihd.net, akamaized.net, akamai.net csv & json Microsoft 1655 microsoft.com csv & json Apple 974 apple.com & itunes.apple.com csv & json AWS Cloudfront 217 *.amazonaws.com & *.awsstatic.com csv & json ASN-CDN Mapping table I have mapped ASNs with the presence of each of these CDNs like last time. This makes it easy to read the data instead of going through each of the files separately. Full data in Google Sheet link here and raw CSV is also published here. Notes: Facebook FNA serving Facebook with *.fbcdn.net is almost the same if I look for *.fna.whatsapp.net. Apple seems to have presence in over 236 locations with PCH/Woodynet for hosting their DNS over HTTPS endpoint: doh.dns.apple.com (detailed list here) GGC has a global coverage across 215 countries across the world, f ## Flat Rate CDN in Limited Beta DevFeed: [Flat Rate CDN in Limited Beta]() Original publisher: [Read original article]() Author: Mery Kaftar Published: 2026-05-19T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel]() Tags: [cdn](), [pricing](), [products](), [vercel]() ### AI overview Vercel has launched Flat Rate CDN in limited beta for Pro teams, replacing usage-based CDN pricing with a fixed monthly fee and eliminating overage charges from temporary traffic spikes. ### Source excerpt Flat Rate CDN is now available in Limited Beta for Pro teams. It replaces usage-based CDN pricing with a fixed monthly fee. Viral posts, unfiltered bots, or misconfigured routes can turn a normal month into a surprise bill. Flat Rate CDN makes your cost predictable. Fixed monthly price: Pay a fixed amount for Vercel CDN each month, regardless of traffic and usage. Covers spikes across Vercel CDN: Edge Requests, Fast Data Transfer, and other products are no longer metered. No overages: Your bill will never increase because of temporary usage spikes. Flat Rate CDN is a good fit for teams with unpredictable CDN bills, individual builders who don't want a usage spike to break the bank, and growing businesses that need to know their CDN costs before the month starts. Pro teams can join the waitlist for early access and to help shape the GA release. Read more ## Firewall-mitigated traffic is free on Vercel DevFeed: [Firewall-mitigated traffic is free on Vercel]() Original publisher: [Read original article]() Author: Pranav Kanchi Published: 2026-05-18T20:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Firewall](), [web applications]() Tags: [cdn](), [cost](), [ddos](), [firewall](), [vercel]() ### AI overview Vercel Firewall now waives CDN request and Fast Data Transfer charges for traffic that its WAF denies, challenges, or rate-limits. The change applies automatically to all projects using Vercel Firewall. ### Source excerpt Vercel Firewall now waives CDN Requests and Fast Data Transfer for any traffic denied, challenged, or rate-limited by Web Application Firewall (WAF). Vercel has always provided unlimited DDoS mitigation at no cost. Vercel WAF, included in CDN cost, gives you custom rules, managed rules, and rate limiting for bad traffic that isn't DDoS. With this change, you don't pay for requests or bandwidth that WAF denies, challenges, or rate-limits. That means no surprise bill when a scraper hammers your product pages, a credential-stuffing botnet hits your login route, or a bot abuses an expensive endpoint. The waiver applies automatically to every project using Vercel Firewall and no configuration is required. Learn how to implement WAF rules in the Firewall documentation. Read more [Next page]()