workerd v1.20261118.1
workerd 日次リリース。CompressionStream / DecompressionStream が brotli に対応したほか、lazy stdio モジュールや Python (Pyodide) 起動の最適化など。
原文を読む →workerd 日次リリース。CompressionStream / DecompressionStream が brotli に対応したほか、lazy stdio モジュールや Python (Pyodide) 起動の最適化など。
原文を読む →Workers VPC が独自CA証明書の検証と mTLS クライアント証明書に対応。プライベートCAのサービスへ検証を弱めずに接続でき、クライアント証明書必須のオリジンにも到達可能になった。証明書は wrangler cert upload で登録して VPC Service の TLS 設定から参照する。
原文を読む →Quad9 がフランスから撤退を迫られた件を取り上げ、パブリックDNSリゾルバにコンテンツフィルタを義務付けることの技術的・制度的な問題を論じた記事。
原文を読む →Wrangler 4.164.0。Workers VPC サービスの作成・更新で独自CA/クライアント証明書の参照と検証モード指定が可能に。同日の Changelog の mTLS 対応に合わせた CLI 側の対応。
原文を読む →workerd 日次リリース。WebSocket.bufferedAmount を追加。CPU制限をマイクロタスクで報告する変更は一旦リバートされた。
原文を読む →AI Search がインデックス時にファイルを自動要約し、要約・トピック・キーワードをメタデータとして保存するようになった。検索精度の向上が狙い。
原文を読む →新しい Cloudflare CLI「cf」1.0.0-rc.1 が公開。9月末からベータだった次世代 CLI が正式版候補になり、自分のプロジェクトで試すことが推奨されている。
原文を読む →Zero Trust の User Risk Scoring にタイムライン表示を追加。リスク行動をトリガー単位で時系列に追え、調査時にイベント同士の関係を把握しやすくなった。
原文を読む →You can now give each Cloudflare One Appliance in a high availability (HA) site its own default gateway on a static WAN. Before this change, both appliances in an HA pair shared the same WAN gateway. Now each appliance can connect to its own Internet circuit, such as a different ISP for each appliance, with its own static IP and gateway. In the dashboard, when you configure a static WAN on an HA site, enter the secondary appliance's gateway in the new Secondary gateway address field, next to Primary gateway address . In the API, set static_addressing.secondary_gateway_address when you create o
原文を読む →Cloudflare Images が入力フォーマットに TIFF を追加。出版・EC でマスター形式として使われる TIFF をそのまま投入し、ブラウザ向けに最適化配信できる。
原文を読む →## What's Changed * [build] clean up Rust to speed up remote builds by @fhanau in https://github.com/cloudflare/workerd/pull/8425 * Bound module fallback redirects in the legacy module registry by @littledivy in https://github.com/cloudflare/workerd/pull/8467 * kj-rs-tokio: fire already-due KJ timers without sleeping by @danlapid in https://github.com/cloudflare/workerd/pull/8476 **Full Changelog**: https://github.com/cloudflare/workerd/compare/v1.20261115.1...v1.20261116.1
原文を読む →You can now develop and test Artifacts locally. Create repos, import Git repositories over HTTPS, issue repo tokens, and clone or push with Git on your machine before deploying to Cloudflare's global network. Local repos are separate from your deployed repos, so you can test changes without affecting production data. Local repos also emit the same Artifacts events as production when a repo is created, imported, forked, or deleted, or when a repo token is created or revoked. This lets you test the Workflows that react to them before you deploy. To use local repos when you run your Worker locall
原文を読む →Cloudflare One now includes Periodic Beaconing Traffic as a risk behavior. It analyzes Gateway HTTP traffic for regular check-ins to the same destination. Cloudflare flags a user after more than 30 contacts to the same destination in six hours. Contacts must be evenly spaced, from 10 seconds to about 12 minutes apart. Few other users in your organization contact that destination. Detection uses traffic behavior only. It does not use threat intelligence, categories, or reputation. Malware can check in with a command-and-control (C2) server this way, but legitimate software also checks in regula
原文を読む →## What's Changed * Rust JSG: bound jsg_traced!( X ) by HoldsNoGcReferences by @littledivy in https://github.com/cloudflare/workerd/pull/8401 * Detach a Rust JSG resource's Rcs before its Drop runs by @littledivy in https://github.com/cloudflare/workerd/pull/8403 **Full Changelog**: https://github.com/cloudflare/workerd/compare/v1.20261114.1...v1.20261115.1
原文を読む →## What's Changed * dtor-throw-during-unwind fixes by @mikea in https://github.com/cloudflare/workerd/pull/8170 * Clearer cluster error messages and an owner record test that can fail by @piscisaureus in https://github.com/cloudflare/workerd/pull/8414 * Report a conditional bucket write refused on a retry as of unknown outcome by @piscisaureus in https://github.com/cloudflare/workerd/pull/8372 * Default-initialize TestFixture::SetupParams' bools by @danlapid in https://github.com/cloudflare/workerd/pull/8396 * Never run a cron occurrence twice on a clock that is behind by @piscisaureus in http
原文を読む →Kitesurf, our experimental browser engine for AI agents, is now open source. Inspect the code, run it locally, or deploy your own instance on Cloudflare Workers.
原文を読む →AI-orchestrated penetration testing platforms like ARTEX have become increasingly powerful tools enabling effective attacks on exposed infrastructure. Here we share Cloudflare’s observations and recommended countermeasures.
原文を読む →You can now test Browser Run Quick Actions locally. Under npx wrangler dev , the browser binding's .quickAction() method runs against a Chrome instance on your machine. Before, .quickAction() worked only in remote mode, and local calls failed with The RPC receiver does not implement the method "quickAction" . Note There are currently two limitations in the local simulation: The json action is emulated. It requires an AI model to extract data, and the model is not available locally, so the action returns placeholder data that matches your schema. The Kitesurf browser is not supported yet. For d
原文を読む →Spend Management adds opt-in spending caps for Cloudflare Workers and Durable Objects, and more products soon. Here is how we built the metering pipeline that turns usage into runtime decisions.
原文を読む →You can now set spending limits for Workers and Durable Objects to help control unexpected usage costs, or receive email alerts while your applications keep running. Support for more products is coming soon. Use these controls alongside AI Gateway spend limits to manage compute and AI inference costs across your application. AI Gateway supports per-user and per-model budgets for Workers AI and other AI providers, applied to requests routed through your gateway. Workers and Durable Objects limits apply across your account for the current subscription billing period. Each product has its own spe
原文を読む →Starting with Cloudflare Terraform provider ↗︎ v5.29.0, you can manage AI Search instances in any namespace , not only default . The cloudflare_ai_search_instance resource has a new namespace argument. It defaults to default , so existing configurations keep managing the same instances. resource "cloudflare_ai_search_namespace" "support" { account_id = var . account_id name = "support" } resource "cloudflare_ai_search_instance" "docs" { account_id = var . account_id id = "docs" namespace = cloudflare_ai_search_namespace . support . name } You can import existing instances and namespaces: terra
原文を読む →AI Search can now use a D1 database as a data source. AI Search runs a read-only query that you provide and indexes each returned row as a separate document. Scheduled syncs keep the index current as rows are added, changed, or removed. Create D1-backed instances from the dashboard, the REST API, or the Workers binding. curl -X POST "https://api.cloudflare.com/client/v4/accounts/<ACCOUNT_ID>/ai-search/namespaces/default/instances" \ -H "Authorization: Bearer <API_TOKEN>" \ -H "Content-Type: application/json" \ --data '{ "id": "help-center", "type": "d1", "source": "<D1_DATABASE_ID>", "token_id
原文を読む →You can now manage AI Security for Apps with Terraform. Version 5.29.0 of the Terraform Cloudflare provider adds two resources: cloudflare_ai_security ↗︎ : Turns AI Security for Apps on or off for a zone. cloudflare_ai_security_custom_topics ↗︎ : Defines the custom topics that AI Security for Apps scores each prompt against. For example: resource "cloudflare_ai_security" "zone_ai_security" { zone_id = var . cloudflare_zone_id enabled = true } resource "cloudflare_ai_security_custom_topics" "zone_custom_topics" { zone_id = var . cloudflare_zone_id topics = [ { label = "competitors" topic = "see
原文を読む →Payload logging now supports WAF custom rules. Enterprise customers can configure an account-level public key, or a zone-level public key that takes precedence, to encrypt matched payloads for supported managed rules and custom rules. This release does not add payload logging support for rate limiting rules. Refer to Configure payload logging via API for configuration details.
原文を読む →Starting from version 2026.11.0 , Cloudflare Tunnel extends the URL normalization introduced in 2026.10.0 . Normalization now handles semicolon-delimited path parameters before matching ingress rules. This improves security for tunnels with rules that require Cloudflare Access validation. The URL path sent to your origin stays the same. Starting 2027-02-08, new cloudflared releases will turn on URL normalization by default. This replaces the previously announced date of 2027-01-25, giving you time to test the updated behavior. Upgrade to version 2026.11.0 or later and test your path-based rout
原文を読む →You can now export a D1 database that contains virtual tables, such as full-text search tables using SQLite's FTS5 module ↗︎ or spatial index tables using the R*Tree module. Previously, export failed for any database containing virtual tables. To include virtual tables in the dump, set dump_options.compatibility to sqlite3_cli_only on the D1 export API . The same option is available as the --compatibility flag on wrangler d1 export . Import is not supported This dump targets the SQLite CLI only. You cannot import it back into D1. Use the standard export for databases without virtual tables. cu
原文を読む →@cf/google/embeddinggemma-2 is now available on Workers AI. EmbeddingGemma 2 is an open multimodal embedding model from Google DeepMind. It maps text (including code), images, video, and audio into a single 768-dimensional vector space, so you can search a mixed collection of products, documents, and media with one text query. Key capabilities: Multimodal : Embed text, images, video, audio, or any combination of them in one input. Every embedding shares the same vector space. Multilingual and code : Understands more than 100 languages and improves code retrieval over the original EmbeddingGemm
原文を読む →Cloudflare Rules supports three new hash functions: sha1() , md5() , and sha512() . Use them to compute hashes for systems that require these algorithms. Like the existing sha256() function, each accepts a string or byte array and returns raw bytes: Function Algorithm Output length md5() MD5 16 bytes sha1() SHA-1 20 bytes sha512() SHA-512 64 bytes For example, combine sha512() with encode_base64() to produce a Base64-encoded hash: encode_base64(sha512("hello world")) For details, refer to the sha1() , md5() , and sha512() function references.
原文を読む →Kitesurf ↗︎ , Cloudflare's browser engine for AI agents, is now open source on GitHub ↗︎ under the Apache 2.0 license. You can inspect the source, run it locally, and deploy your own instance to your Cloudflare account. Kitesurf runs entirely on Cloudflare Workers. It parses HTML, applies CSS, executes page JavaScript, and renders screenshots without a browser container. It supports the Chrome DevTools Protocol (CDP), so you can connect clients such as Puppeteer. Kitesurf is still experimental and under heavy development . The team continues to improve web standards support, rendering fidelity
原文を読む →@cf/thinkingmachines/inkling-2-small is now available on Workers AI. Inkling 2 Small is the second generation of Inkling models from Thinking Machines Lab, and the first frontier open model from a US lab on Workers AI. Inkling 2 Small is more capable than the previous generation. It is a multimodal Mixture-of-Experts model with 594B total parameters and 18B active parameters. Thinking Machines trained it much faster than previous models because of improvements to their pre-training and infrastructure. Inkling 2 Small works well for: Agentic coding : Plan, write, and edit code across multi-step
原文を読む →RealtimeKit auth tokens now support custom validity windows, and you can revoke a single token. When your backend adds a participant to a meeting, it gets back an auth token that the participant's app uses to join. Previously, every token was valid for 100 days from the moment it was issued. Now you can choose when a token starts and stops working, for example only during a scheduled class or interview, so a shared link stops working once the session is over. Pass not_before and expires_on in the token object when you add a participant : Required API token permissions At least one of the follo
原文を読む →You can now add noise cancellation to RealtimeKit web apps with the new @cloudflare/realtimekit-noise-cancellation package. RealtimeKit is a high-level SDK for adding real-time audio and video components, such as video meetings, to your web or mobile app. Install the package: if (!customElements.get("nb-pm-restore")) { customElements.define( "nb-pm-restore", class extends HTMLElement { connectedCallback() { const card = this.closest("[data-nb-pm]"); if (!card) return; let saved; try { saved = sessionStorage.getItem("ui-pm-tab"); } catch { return; } if (!saved) return; const tabs = card.querySe
原文を読む →Cloudflare is building an experimental consensus service using a never-before-deployed consensus algorithm, QuePaxa. In this post we explain how QuePaxa works and why we chose it.
原文を読む →Wrangler 4.160.0 and Cloudflare CLI ( cf ) 1.0.0-beta.29 support custom headers for Cloudflare API requests. Use CLOUDFLARE_API_HEADERS to add headers or override most generated values, with the exception of protected body and transport headers. For example, to send X-Custom-Header: value , set: export CLOUDFLARE_API_HEADERS = '{"X-Custom-Header":"value"}' Then run your Wrangler or cf command. For usage and restrictions, refer to the Wrangler environment variable reference and Cloudflare CLI environment variable reference .
原文を読む →Cloudflare has reduced the number of round trips needed to connect to a Durable Object when a location lookup follows a forwarding record to another data center. When an object's destination isn't cached in Cloudflare's network, the first data center contacted may have a forwarding record pointing to another data center. Previously, the first data center acquired a connection to the object at the destination and proxied it back to the caller. The caller then established its own direct connection to the object. Now, the first data center returns the destination directly, without first acquiring
原文を読む →Customers on a Workers Paid plan can now create up to 100 Hyperdrive configurations, up from 25, and configure up to 1,500 origin database connections per configuration, up from 100. Configuration limit The configuration limit is the maximum number of Hyperdrive configurations you can create per account. Workers Paid customers can now create up to 100 configurations, allowing more workloads to take advantage of connection pooling and query caching across different databases. Origin connection limit The origin connection limit is the maximum number of database connections that Hyperdrive can ma
原文を読む →You can now serve your Worker's static assets from a URL path prefix, such as example.com/blog/ , without changing your build output. Previously, to serve assets from /blog/ , you had to nest your files in a matching blog directory. Now, set assets.base_path in your Wrangler configuration file, or worker.assets.basePath in cloudflare.config.ts , and keep your files at the root of your asset directory. Use Wrangler 4.148.0 ↗︎ or later. With cloudflare.config.ts , use cf 1.0.0-beta.13 ↗︎ or later. For example, this configuration serves your built assets from /blog/ : The following content appear
原文を読む →GitHub secret scanning automatically detects Cloudflare Access service token secrets exposed in public repositories and reports them to Cloudflare. Access then disables the affected token and emails account administrators. Other secret scanning tools can identify Access service tokens using their consistent Client Secret format: cfast_ , followed by 40 alphanumeric characters and an eight-character hexadecimal checksum. For tools that support custom detection rules, use this regular expression to find possible secrets: cfast_[A-Za-z0-9]{40}[a-f0-9]{8} This pattern applies to Client Secrets cre
原文を読む →The Web Assets > Operations page now includes metric-focused views for traffic, errors, latency, response size, and security. Each view surfaces the relevant metrics and supports server-side sorting, making it easier to prioritize operations in large inventories. Refer to Endpoint Management for more information about managing and analyzing operations.
原文を読む →You can now add a collaborative whiteboard to RealtimeKit meetings with the Whiteboard plugin , which Cloudflare hosts and runs for you. RealtimeKit provides SDKs for running live audio and video meetings in your app. Many companies use it today to run online education and interview platforms, where participants often need a shared whiteboard to work through ideas together. You add the Whiteboard plugin with the same plugins API you use for your own plugins. Load it in an iframe , with the participant's auth token after # in the URL: const WHITEBOARD_URL = "https://whiteboard-v2.plugins.realti
原文を読む →A new Beta release for the Windows Cloudflare One Client is now available on the beta releases downloads page . This release includes the following highlights: Added automatic endpoint selection for Global Acceleration. When Global Acceleration is enabled for an organization, the client connects to the Global Acceleration endpoints while the device is in the acceleration region and to the standard anycast endpoints otherwise, and reconnects when a network change moves the device between them without requiring action from the user. The Connectivity page shows which tunnel and API endpoints are
原文を読む →A new Beta release for the macOS Cloudflare One Client is now available on the beta releases downloads page . This release includes the following highlights: macOS 15.0 is now the minimum supported version. This release does not run on macOS 14. Added automatic endpoint selection for Global Acceleration. When Global Acceleration is enabled for an organization, the client connects to the Global Acceleration endpoints while the device is in the acceleration region and to the standard anycast endpoints otherwise, and reconnects when a network change moves the device between them without requiring
原文を読む →A new GA release for the Windows Cloudflare One Client is now available on the stable releases downloads page . This hotfix addresses an issue building trusted certificate chains.
原文を読む →A new GA release for the Linux Cloudflare One Client is now available on the stable releases downloads page . This hotfix addresses an issue building trusted certificate chains.
原文を読む →A new GA release for the macOS Cloudflare One Client is now available on the stable releases downloads page . This hotfix addresses an issue building trusted certificate chains.
原文を読む →Generating MP4 downloads from Cloudflare Stream is now up to 40% faster, with no changes to your implementation required. This improvement is most impactful for on-demand videos over 1 minute in duration. You can generate an MP4 download in the Dashboard, with the cf , the Cloudflare CLI CLI, or by sending a POST request. cf cli sh cf stream videos downloads create default --identifier " $VIDEO_UID " Create download bash curl "https://api.cloudflare.com/client/v4/accounts/ $ACCOUNT_ID /stream/ $IDENTIFIER /downloads/default" \ --request POST \ --header "Authorization: Bearer $CLOUDFLARE_API_TO
原文を読む →You can now set a concurrency limit on an individual Workflow to cap how many of its instances run at the same time. Use it to protect a database or third-party API that slows down or rejects requests past a certain number of concurrent connections, or to distribute load more evenly across your Workflows so that one high-volume Workflow does not use all of your account's concurrency. For example, to allow only 10 instances of a Workflow to run at a time, set concurrency.limit on its workflows binding and redeploy: { "workflows" : [ { "name" : "my-workflow" , "binding" : "MY_WORKFLOW" , "class_
原文を読む →Flagship now has an official Rust SDK. Use it to evaluate feature flags from async Rust server applications through OpenFeature, with the same targeting rules and percentage rollouts as the other Flagship SDKs. Install the cloudflare-flagship ↗︎ crate: cargo add cloudflare-flagship Then register the provider and evaluate a flag: let options = FlagshipClientOptions :: builder () . app_id ( "<APP_ID>" ) . account_id ( "<ACCOUNT_ID>" ) . auth_token ( "<API_TOKEN>" ) . build () ? ; let mut api = OpenFeature :: default (); api . set_provider ( FlagshipServerProvider :: new (options) ? ) .await ; le
原文を読む →When you connect a GitHub repository to Workers Builds or Pages , the accounts and repositories you can pick from are now based on your own GitHub account, so the list reflects the repositories you work with on GitHub. Previously, the list was based on the Cloudflare Workers & Pages GitHub App installations linked to your Cloudflare account, so it could include repositories that you cannot access on GitHub. The list now shows: Your own GitHub account, if the app is installed on it. GitHub organizations that have the app installed, where you can access at least one repository. The repositories
原文を読む →A new GA release for the Linux Cloudflare One Client is now available on the stable releases downloads page . This hotfix addresses an issue building trusted certificate chains.
原文を読む →A new GA release for the macOS Cloudflare One Client is now available on the stable releases downloads page . This hotfix addresses an issue building trusted certificate chains.
原文を読む →A new GA release for the Windows Cloudflare One Client is now available on the stable releases downloads page . This hotfix addresses an issue building trusted certificate chains.
原文を読む →Cloudflare is distributing the first $301,300 of the Vite Ecosystem Fund to open source projects and maintainers. The recipients were chosen by a panel of Vite stack core team members, including maintainers not employed by Cloudflare.
原文を読む →Cloudflare has improved how it chooses where to start a Durable Object after the object has been inactive. Reactivated Durable Objects now start on the machine that last ran them whenever possible, so their data doesn't need to be loaded again. This can make cold starts less frequent for SQLite-backed Durable Objects that are reactivated soon after going idle. Actual results depend on your workload and traffic patterns. The change is live in all regions. No action is needed by customers to see benefits from this change. To learn more about how Durable Objects are placed, refer to Data location
原文を読む →Run the Codex agent loop in a Cloudflare Durable Object with this experimental Agents SDK example ↗︎ . Conversations, files, and completed model and tool results persist across restarts, allowing the agent to recover after interruptions. The example adapts Codex’s Rust turn-processing code ↗︎ to WebAssembly and uses Agents SDK capabilities for storage and recovery. The harness combines Agents SDK capabilities for durable execution: Tasks journals model calls and tool execution. Completed steps reuse their recorded results after a restart. Interrupted steps can run again. Sessions stores conver
原文を読む →Markdown for Agents is generally available, with new tools to monitor conversions and investigate partial or failed output. In the Cloudflare dashboard, select your zone and go to Agent Readiness > Markdown for Agents : Analytics shows conversion outcomes, estimated token reduction, top converted pages, top user agents, failure reasons, content limits, and pages with partial or failed conversions. Logs provides sampled conversion events with outcome, failure reason, and content-limit filters. Playground requests Markdown for a page on your zone and compares it with HTML. Inspect the Markdown,
原文を読む →You can now run Exo agents on Cloudflare, with Durable Objects coordinating conversations and Cloudflare Sandboxes running Linux tools. Define an agent in Markdown, then use Exo's CLI or HTTP API to run it. After deploying the Cloudflare adapter and configuring your Exo provider ↗︎ , add an openai vault credential and save this definition as agent.md : --- harness : basic model : name : gpt-6.1-sol credential : openai --- Help the user with their task. Run the agent against your Cloudflare deployment with Exo's CLI: exo --provider cloudflare agent run --agent-file agent.md The Exo project main
原文を読む →You can now run Nanocode ↗︎ coding agents in Cloudflare Durable Objects , with persistent session history and recovery after interruptions. Nanocode's Rust engine runs as WebAssembly and implements Codex and Claude Code prompt and tool conventions. Its Cloudflare host saves turn progress and tool results in SQLite and uses alarms to resume pending work. The Nanocode project maintains the host independently of Cloudflare; it does not require the Agents SDK. Start with the reference Worker ↗︎ and follow Nanocode on Workers for setup, models, and recovery limits.
原文を読む →Cloudflare now adds the Partitioned attribute to the __cf_bm cookie on compatible HTTPS requests. The attribute is added only when the cookie can also be issued with SameSite=None and Secure . When users access your content through an <iframe> on another site, the browser handles __cf_bm as a third-party cookie. Browser privacy controls may block third-party cookies. Adding Partitioned allows the __cf_bm cookie to persist within that top-level site. This means that Bot Management can preserve continuity across requests, even when your content is embedded on another site. For more information,
原文を読む →Email security now has a unified search bar for investigations. It replaces the Email Screener side modal and makes searches easier to refine. Search with keywords or field:value filters. Autocomplete suggests filters and values as you type. Add terms and press Enter to refine results, or select From , To , Disposition , Status , or Threat type values in results. Narrow results with a date preset or custom range. This feature is available to all Email security customers.
原文を読む →The Cloudflare Radar Bots Directory ↗︎ now uses BotBase , Cloudflare's catalog of the bots and agents it tracks, and has a new design matching the Radar homepage. Each bot page has a new Identity section showing the bot's access level, content use, Web Bot Auth verification, and user agents. Bot operators are also searchable from the Radar site search. API The List bots and Get bot details endpoints now describe each bot with: categories : a bot can now have more than one category. Categories follow BotBase's groups, which add COMMERCE , and some older categories are now part of broader groups
原文を読む →Cryptographic protocols like Privacy Pass help keep web sites safe from abuse while keeping their users private. This post looks at the quantum threat to these protocols, and some new post-quantum cryptography that may help close the gap.
原文を読む →AI Gateway now shows usage activity for your stored provider keys. Use this information to review credentials for rotation or removal. In Provider Keys , keys are grouped by provider with masked previews, aliases, and last-used and last-updated dates. The Key security section highlights keys with recorded activity older than 90 days. You can review these keys and delete them after checking their dependencies. Usage tracking starts November 2026. For details on storing, rotating, and removing provider keys, refer to Bring your own keys .
原文を読む →AI agents act for millions, but servers see intermediaries that strip user visibility. This post defines the problem space and introduces a collaborative approach to safely identifying, allowing, and managing this automated traffic.
原文を読む →Personal AI agents have changed how users interact with the web, blurring the lines between automated and human traffic. Learn how Cloudflare gives site owners visibility and control to manage personal agent access.
原文を読む →Zero Wire on Cloudflare Radar pairs plain-language briefings with global attack telemetry and remediation steps. Triage critical CVEs faster and decide how to protect your infrastructure.
原文を読む →Zone setting changes used to rebuild entire DNS zones, even ones with tens of millions of records. Here is how we built a planner that picks the smallest safe build, cutting full builds by 40%, peak memory by 85%, and halving build delay.
原文を読む →Four, just four: that’s the key to break into any unpatched connection on the Internet that is using eMudhra certificates. Here’s how we quickly patched Cloudflare, what evidence we can see of attempted exploitation, and how much of the rest of the Internet remains exposed.
原文を読む →Public traffic to private origins, with WAF, bot management, caching, and Workers, is now available to every customer with Cloudflare One connectivity.
原文を読む →Cloudflare mitigated over 8,200 DDoS attacks per hour in Q3 2026 as attackers shifted to shorter, high-frequency strikes. Explore the latest threat data, including the collapse of CLDAP vectors and the impact of recent botnet takedowns.
原文を読む →We are launching a PHP Capture the Flag challenge integrated with our Bug Bounty program to test our WAF protections. Security researchers are invited to bypass our defenses and capture the flag to help make the Internet safer.
原文を読む →該当する記事がありません。