Storage Updates & Release Notes
134 updates curated from 1 source by the Releasebot Team. Last updated: Nov 18, 2026
- Nov 18, 2026
- Date parsed from source:Nov 18, 2026
- First seen by Releasebot:Nov 18, 2026
- Modified by Releasebot:Nov 18, 2026
Custom CA and client certificates (mTLS) for Workers VPC
Storage VPC Services now supports custom certificate authorities and mutual TLS for private services, enabling verified HTTPS and TLS connections with custom CA or client certificates. Configuration is available through Wrangler, the API, and Terraform.
VPC Services can now verify private services that use certificates from your own certificate authority (CA), and authenticate to services that require mutual TLS (mTLS). Previously, Workers VPC only trusted publicly trusted CAs and Cloudflare Origin CA, so connecting to a private CA meant weakening verification with
verify_caor disabled, and origins that required client certificates were unreachable.Upload your CA certificate and client certificate, then reference them from the TLS settings of a VPC Service:
npx wrangler cert upload certificate-authority --ca-cert ./ca.pem --name private-ca npx wrangler cert upload mtls-certificate --cert ./client.pem --key ./client-key.pem --name private-client npx wrangler vpc service create private-db \ --type tcp \ --tcp-port 5432 \ --app-protocol postgresql \ --hostname db.internal.example \ --tunnel-id <TUNNEL_ID> \ --certificate-authority <CA_CERTIFICATE_ID> \ --client-certificate <CLIENT_CERTIFICATE_ID> \ --cert-verification-mode verify_fullYou can use a custom CA, a client certificate, or both. The settings apply to HTTPS connections from http services and to TLS connections from tcp services, including PostgreSQL databases used with Hyperdrive, such as Amazon RDS instances that use the RDS CA bundle.
You can configure custom CA and client certificates with Wrangler 4.164.0 or later, the API, or Terraform provider 5.29.0 or later.
For details, refer to Custom CA and client certificates.
Original source - Nov 13, 2026
- Date parsed from source:Nov 13, 2026
- First seen by Releasebot:Nov 14, 2026
Set spending limits for Workers and Durable Objects
Storage introduces Cloudflare spending limits and email alerts for Workers and Durable Objects, helping users manage costs while choosing whether limits pause usage. Controls are available in the dashboard and through the cf CLI, alongside AI Gateway budgets and account-wide alerts.
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 spending controls.
Set your limits and alerts
In the Cloudflare dashboard ↗︎, select your account and go to Billing > Spend limits. Choose a spending limit, notification email, and alert thresholds for Workers or Durable Objects.
For example, configure a $10 Workers spending limit with email alerts at $5 and $9. To receive alerts while your applications keep running, turn off Block usage.
See when a limit takes effect
The overview shows each product's recorded spend, alert thresholds, and pause status. Email alerts notify you without stopping usage. When a spending limit takes effect, Cloudflare blocks the product's supported operations.
To resume usage, raise the limit above current spend, turn it off, or remove it. Usage also resumes when the next billing period starts.
Usage reporting and blocking take time, so recorded spend can exceed a limit. Read about what counts toward a limit.
Choose alerts, limits, or both
For example, set a $50 spending limit for Workers and a $20 email alert for Durable Objects:
- Durable Objects reaches $20
- Email alert sent
- Usage continues
- Workers reaches $50
- Spending limit takes effect
- New Worker invocations blocked
Set a spending limit with the cf CLI
Install the cf CLI and select your account, then run this command to set a $50 spending limit for Workers usage in the current billing period:
cf billing spend-policies create \ --name 'Workers $50 spending limit' \ --product-id workers \ --enabled true \ --threshold-cents 5000 \ --action usage_blockThe amount is in US cents: 5000 means $50. To set a spending limit for Durable Objects, use --product-id durable_objects and update the name. Limits count usage already recorded in the current billing period.
You can also give this prompt to your coding agent. It will ask which product you want to manage and what spending limit to set, then use the CLI to configure it.
Use spending limits alongside budget alerts
The budget alerts introduced earlier this year notify you about account-wide usage costs without stopping usage. You can keep using them alongside the new product-specific spending limits and email alerts for Workers and Durable Objects.
To configure account-wide alerts, go to Billing > Billable Usage or follow the budget alerts guide.
Read the spending limits and alerts guide to learn how spending limits work and manage limits and alerts through the dashboard or cf CLI.
Original source All of your release notes in one feed
Join Releasebot and get updates from Cloudflare and hundreds of other software products.
- Nov 12, 2026
- Date parsed from source:Nov 12, 2026
- First seen by Releasebot:Nov 13, 2026
AI Search supports D1 databases as a data source (beta)
Storage AI Search now supports D1 databases as data sources, indexing query results as documents and keeping them current through scheduled syncs. Create D1-backed instances from the dashboard, REST API, or Workers binding.
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": "<SERVICE_TOKEN_ID>", "source_params": { "d1": { "query": "SELECT article_id AS id, title, content, category AS meta_category\nFROM articles\nWHERE published = 1" } } }'Learn more in D1 data source.
Original source - Nov 12, 2026
- Date parsed from source:Nov 12, 2026
- First seen by Releasebot:Nov 13, 2026
Export D1 databases with virtual tables
Storage adds D1 database exports for virtual tables, including FTS5 and R*Tree, through a SQLite CLI-only option in the export API and Wrangler. These dumps cannot be imported back into D1.
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.compatibilitytosqlite3_cli_onlyon the D1 export API. The same option is available as the--compatibilityflag onwrangler 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.
curl "https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/d1/database/$DATABASE_ID/export" \ --request POST \ --header "Authorization: Bearer $CLOUDFLARE_API_TOKEN " \ --json '{ "output_format": "polling", "dump_options": { "compatibility": "sqlite3_cli_only" } }'For more information, refer to Export a D1 database with virtual tables.
Original source - Nov 11, 2026
- Date parsed from source:Nov 11, 2026
- First seen by Releasebot:Nov 13, 2026
Improved Request Routing to Durable Objects
Storage improves Cloudflare Durable Object connections by skipping an unnecessary intermediate connection when forwarding records point to another data center, reducing p99 connection latency for affected requests with no code or configuration changes required.
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 a connection to the object. The caller then establishes a direct connection, avoiding the intermediate connection and duplicate acquisition.
Skipping this intermediate connection can reduce p99 connection latency for these relocation-related requests. Actual results depend on your workload and traffic patterns.
No code or configuration changes are required to benefit from this improvement.
To learn more about how Workers connect to Durable Objects, refer to Durable Object namespaces.
Original source Similar to Storage with recent updates:
- Cloudflare AI updates209 release notes · Latest Nov 17, 2026
- ChatGPT updates252 release notes · Latest Nov 16, 2026
- Gemini updates473 release notes · Latest Nov 17, 2026
- OpenAI updates312 release notes · Latest Nov 18, 2026
- Anthropic updates79 release notes · Latest Oct 14, 2026
- OpenAI Models updates54 release notes · Latest Nov 18, 2026
- Nov 11, 2026
- Date parsed from source:Nov 11, 2026
- First seen by Releasebot:Nov 13, 2026
Hyperdrive raises limits for connections and configurations
Storage expands Hyperdrive capacity for Workers Paid customers, raising the account limit to 100 configurations and allowing up to 1,500 origin database connections per configuration. The changes support larger workloads and more concurrent database access.
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 make to your origin database per configuration. Workers Paid customers can now configure up to 1,500 origin connections, increasing the connection pool size available for workloads that need more concurrent database access. You can configure this value via the dashboard, Wrangler, or the REST API.
We recommend setting the origin connection limit lower than your origin database's connection limit.
For more information, refer to Hyperdrive limits and Tune connection pooling.
Original source - Nov 9, 2026
- Date parsed from source:Nov 9, 2026
- First seen by Releasebot:Nov 11, 2026
Improved Durable Object Startup Placement
Storage improves how Cloudflare Durable Objects restart, placing them on their last-used machine when possible to avoid reloading data and potentially reduce cold starts for SQLite-backed objects. The change is live in all regions and requires no customer action.
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.
Original source - Nov 5, 2026
- Date parsed from source:Nov 5, 2026
- First seen by Releasebot:Nov 5, 2026
Automatic retries for Durable Object calls
Storage now automatically retries eligible fetch() and RPC calls to Durable Objects, helping calls recover from brief disruptions without custom retry loops. Developers can configure retry limits and timeouts, while safeguards prevent methods from running twice unless explicitly marked retryable.
The runtime now retries
fetch()and RPC calls to a Durable Object when they fail with a retryable error before reaching it. This applies whether the caller is a Worker or another Durable Object. Short disruptions, such as brief network interruptions, no longer need a retry loop in your code.By default, the runtime retries a call up to four times, and starts no retry more than 10 seconds after the initial call starts. It does not retry errors thrown by your Durable Object code, or errors with
.overloadedset totrue.If the connection drops and the runtime cannot tell whether the Durable Object received the call, it still retries, but the Durable Object rejects the retry if the first attempt arrived. A method never runs twice because of a retry, unless you mark it with
retryable()fromcloudflare:durable-objects:import { DurableObject } from "cloudflare:workers"; import { retryable } from "cloudflare:durable-objects"; export class Cart extends DurableObject { static { retryable(this.prototype.setQuantity); } // Idempotent: a second run sets the same quantity. async setQuantity(itemId, quantity) { await this.ctx.storage.put(itemId, quantity); } // Not retryable: a second run would add another item. async addOne(itemId) { const quantity = (await this.ctx.storage.get(itemId)) ?? 0; await this.ctx.storage.put(itemId, quantity + 1); } }To change the limits for one stub, pass a retry option to
get()orgetByName().maxRetriesaccepts 0 to 10 retries, andtimeoutMsaccepts 500 to 60,000 milliseconds:const stub = env.CART.getByName("user-123", { retry: { maxRetries: 1, timeoutMs: 2000 }, });If you already retry Durable Object calls in your own code, each of your attempts now includes the runtime's retries. Lower your own attempt count, or set
maxRetries: 0on stubs where your code handles retries.To use
retryable()and the retry option, update to Wrangler 4.158.0 or later.For more information, refer to Automatic retries.
Original source - Nov 3, 2026
- Date parsed from source:Nov 3, 2026
- First seen by Releasebot:Nov 3, 2026
Request metrics breakdown by region and HTTP error code
Storage adds regional R2 metrics to compare request activity and errors by HTTP status code in the Cloudflare dashboard.
You can now compare regional activity and errors by HTTP status code on the Metrics page for a R2 bucket in the Cloudflare dashboard.
Go to Bucket metrics ↗
Compare regions
Use Request Distribution by Region to compare request activity and filter by writes, reads, errors, or rate-limited errors (429).
Inspect errors
Use Errors by Status Code to compare error counts and trends.
To troubleshoot errors, refer to the R2 error code reference.
Original source - Oct 30, 2026
- Date parsed from source:Oct 30, 2026
- First seen by Releasebot:Nov 2, 2026
D1 will enforce a maximum query result size of 50 MB
Storage reports that D1 will enforce a 50 MB maximum query result size starting November 4, 2026. Larger results will fail, while REST API imports and exports remain unaffected. Users can reduce results by selecting needed columns or paginating queries.
Beginning Wednesday, November 4, 2026, D1 will enforce a maximum query result size of 50 MB. Queries that return a result larger than 50 MB will fail and return the following error:
D1 query result exceeded the maximum response size limit of 50 MB
The 50 MB limit covers the 99.999th percentile of requests across D1, so most D1 users will not be impacted.
Import and export operations via the REST API are not subject to this limit and will continue to work as they do today.
If your queries return large results, reduce the result size before the enforcement date. For example, select only the columns you need instead of using SELECT *, and paginate large result sets with LIMIT and OFFSET.
For more information, refer to D1 limits and the D1 error list.
Original source - Oct 30, 2026
- Date parsed from source:Oct 30, 2026
- First seen by Releasebot:Nov 2, 2026
Cloudflare WAN supports regional Gateway HTTP inspection
Storage reports that Cloudflare WAN now supports regional Gateway processing for encrypted HTTPS traffic, helping organizations control where TLS decryption and HTTP inspection occur to meet data sovereignty goals.
Cloudflare WAN traffic can now use a Gateway processing region with Regional Services. HTTPS traffic enters a Cloudflare data center (that may be outside the selected region) via an IPsec or GRE tunnel, or through Direct CNI, and remains encrypted until Gateway forwards it to the selected region for TLS decryption and HTTP inspection. This feature gives organizations control over where their sensitive traffic is processed, supporting their data sovereignty goals.
This feature requires unified routing. The processing region applies to Gateway HTTP traffic and does not apply to Gateway DNS or network policy processing.
Contact your account team to configure a processing region. For supported regions, configuration details, and limitations, refer to Data residency for Cloudflare One.
Original source - Oct 30, 2026
- Date parsed from source:Oct 30, 2026
- First seen by Releasebot:Nov 2, 2026
Durable Objects now defer code updates by default
Storage now defers Durable Objects code updates by default, giving active objects up to five minutes to finish work before adopting new code. Teams can configure the delay or deploy updates immediately, helping protect in-flight work and hibernating WebSocket connections.
Durable Objects can stay active across requests, allowing you to run long-running agents, maintain long-lived WebSocket connections and coordinate state across many clients. This is possible because each Durable Object is globally unique, and this means it must run only one version of your code at a time. Previously, when you deployed a change to your Durable Objects code, that change would be applied immediately, which could interrupt in-flight work and terminate open connections.
Durable Objects now defer code updates by default. When you deploy, an active Durable Object can keep running its current code for up to 5 minutes (300 seconds) while it waits to hibernate. This gives in-flight work time to finish. WebSocket connections that use the Hibernation API remain connected when an object adopts new code after hibernating.
For an active Durable Object, a code update follows this flow:
- Default: deferred
- Yes
- No
- Override: immediate
- You deploy new code
- The object can keep running its current code
- Hibernates before the delay ends?
- Starts on the new code on the next request
- The object resets and adopts the new code
CODE UPDATES FOR AN ACTIVE DURABLE OBJECT
To change the delay, add
code_update_strategytodurable_objectsin your Wrangler configuration:{ "durable_objects": { "bindings": [ { "name": "CHAT_ROOM", "class_name": "ChatRoom", }, ], "code_update_strategy": { "mode": "deferred", "max_delay": 60, }, }, }max_delayis in seconds, from 0 to 86400 (24 hours), with millisecond precision. Omit it to use the default of 300 seconds.To set the strategy for a single deployment, pass
--durable-objects-code-update-modewith immediate or deferred . For example, apply an update right away during an incident, or when your deployment tooling calls a Durable Object right after deploying and needs the new code:npx wrangler versions deploy <VERSION_ID>@100% --durable-objects-code-update-mode immediateA deferred code update is best effort and does not guarantee that every operation finishes. The object can still reset before max_delay is reached, for example during a Cloudflare runtime update.
For more information, including how this interacts with gradual deployments and the REST API, refer to Durable Objects code updates.
Original source - Oct 29, 2026
- Date parsed from source:Oct 29, 2026
- First seen by Releasebot:Nov 2, 2026
View your data localization settings in one dashboard page
Storage adds a read-only Cloudflare Data Localization Suite overview that brings regional services, metadata boundary, and key manager settings into one dashboard view, with links to each setting and its documentation.
The Cloudflare dashboard now includes a Data Localization Suite Overview, a read-only view of the data localization settings on your account. It shows your Regional Services, Customer Metadata Boundary, and Geo Key Manager settings in one place, so you no longer need to check several dashboard pages and APIs to see where your traffic is processed and where your logs and private keys are stored.
To find it, go to Application Security > Data Localization Suite, or search for "DLS" in the dashboard.
The Overview has a tab for each product:
- Regional Services: regionalized hostnames (filter by region or zone), regionalized IP bindings, and regionalized Spectrum applications, each with its region.
- Customer Metadata Boundary: whether the boundary is on, the region (US or EU), and whether out-of-region access is allowed.
- Geo Key Manager: every custom certificate with a geo policy, with its hostname, zone, region, and status.
Each item links to the dashboard page where you change its setting, and each tab links to the product's documentation.
To learn more, refer to the Data Localization Suite documentation.
Original source - Oct 23, 2026
- Date parsed from source:Oct 23, 2026
- First seen by Releasebot:Oct 23, 2026
D1 database undelete requests limited to the last 7 days
Storage limits D1 database recovery to the seven days after deletion, with older undelete requests returning an error.
The D1 undelete API now only accepts requests for databases that were deleted within the last 7 days. Requests to undelete a database that was deleted more than 7 days ago will fail and return an error.
If you delete a D1 database by mistake, send the undelete request as soon as possible, and no later than 7 days after deletion.
For more information, refer to the undelete D1 database API reference.
Original source - Oct 21, 2026
- Date parsed from source:Oct 21, 2026
- First seen by Releasebot:Oct 21, 2026
Basin SQL supports OFFSET
Storage’s Basin SQL now supports OFFSET for paginating query results, letting users skip earlier rows alongside LIMIT. Adding ORDER BY on a unique column helps keep page ordering consistent.
Basin SQL is a serverless, distributed SQL engine for querying Apache Iceberg tables in Basin Catalog. It now supports OFFSET, which lets you skip a specified number of rows when retrieving query results.
Use LIMIT to set the page size and OFFSET to skip earlier rows. With a page size of 100, use OFFSET 0 for the first page, OFFSET 100 for the second, and increase the offset by 100 for each later page. Add ORDER BY on a unique column to keep the row order consistent.
For example, this query returns the second page of 100 rows:
SELECT sale_id, total_amount FROM my_namespace.sales_data ORDER BY sale_id LIMIT 100 OFFSET 100For syntax and examples, refer to the OFFSET clause in the Basin SQL reference.
Original source
Curated by the Releasebot team
Releasebot is an aggregator of official product update announcements from hundreds of software vendors and thousands of sources.
Our editorial process involves the manual review and audit of release notes procured with the help of automated systems.