Cloud intelligence

Cloudflare’s support portal and live chat became unavailable during a helpdesk provider outage on September 16, 2026. The company warned that customers could struggle to submit or view tickets and face delayed responses. Emergency phone support remained available for P1 and emergency cases, but could also be slow. Cloudflare reported a fix at 13:34 UTC and resolution at 14:58 UTC.

Cloudflare reported delayed notification emails for some customers on September 16, 2026, while saying webhook and PagerDuty notifications were unaffected. Its status notice opened an investigation at 08:33 UTC and marked the incident resolved at 08:50 UTC. The reported issue concerned dispatching email alerts, rather than a failure across every notification channel.

Vercel's September 16 Is Agentic update lets readers view audit checks by site type: content, business, app or commerce. Each view emphasizes different requirements, such as checkout standards for commerce or authentication for apps. Switching views does not change the score or require a rescan. A page metadata setting selects the default view; otherwise, the service infers one.

Cloudflare's September 16 update lets Python Workers connect to PostgreSQL and MySQL through Hyperdrive. Its linked setup guide requires a compatibility date of September 8, 2026 or later and recommends asyncpg for PostgreSQL and aiomysql for MySQL. The guide also identifies a limitation: synchronous SQLAlchemy ORMs are supported, but asynchronous SQLAlchemy ORMs are not yet supported.

You can now stream Workflow instance events via WorkflowInstance.subscribe() and the GET /subscribe API endpoint. Workers and HTTP clients can react to workflow and step events, including attempts, sleeps, waits, and rollbacks, without polling for instance status. A subscription first streams the entire event history of the Workflow instance. After streaming past events, the subscription waits for new events as the instance runs. You can use filter to receive only specific event types or cursor to start a subscription at a specific event. Use .subscribe() to update Workflow status in user-facing dashboards, send notifications when steps complete, or trigger follow-up work for specific events.

A September 15 Vercel case study describes Delphi moving its Python backend onto the platform alongside its frontend. Delphi says its team now deploys to production more than 100 times daily using feature flags. Workflows handles long-running processing and Queues handles background jobs, including knowledge ingestion. These are customer and vendor accounts of the migration, rather than independently measured results.

Supabase has published monitoring-agent setups for health, security, performance and capacity, each with a defined scope and reporting instructions. Its plugin now pairs skills with an MCP server whose query_logs tool exposes structured logs across Supabase services. Teams can adapt the supplied prompts for scheduled agent environments and their existing work-tracking integrations, choosing a role and configuring the agent in their own environment.

Vercel doubled the storage included with each Sandbox from 32 GB to 64 GB in its September 11 update. The capacity applies to sandboxes using managed images, custom images and the deprecated runtime configuration. Vercel positions the extra space for larger repositories, dependencies, build output, disk-heavy data work and agent tasks that need more local storage.

A three-person engineering team runs Featured's AI-assisted public-relations tools across three brands, according to Vercel's September 11 customer story. Featured migrated 374 Sanity sites from AWS Elastic Beanstalk and uses AI Gateway to route requests across 17 models. The company says its agents deliver more than 100,000 media pitches monthly, with Workflow SDK handling the long-running monitoring and qualification jobs behind them.

Pro and Enterprise teams gained tighter control over Vercel Connect in a September 11 update. Team owners can restrict connector creation and management to owners and members with the Connector Manager extended permission. Connectors give applications and agents access to external services through team-managed credentials; the restriction is enabled in the team's Connector Permissions settings.

Vercel's September 10 FastAPI update moves eligible frontend and StaticFiles content onto its CDN during builds, avoiding a function invocation for those requests. Route declaration order still decides whether an earlier application route takes precedence. Frontends protected by dependencies and static files behind middleware stay on the function by default, preserving checks that the CDN cannot perform.

Vercel reported on September 10 that grouping CDN routing metadata into indexed files cut its measured 99th-percentile lookup time from 215.8 to 19.1 milliseconds. The roughly 200 KB groups warm multiple paths in one fetch while parsing only the requested record. These are Vercel's production measurements from August 5–12; deployments built after July 17 already use the format, while older ones need redeployment.

Vercel expanded Sandbox from four to all 20 compute regions in its September 10 announcement. Every plan can choose a region, helping teams place workloads near their data or within approved geographies. Ordered failover regions are limited to Pro and Enterprise. Existing sandboxes keep their original location, the default remains iad1, and Vercel says CPU and memory prices vary by region.

Vercel's September 9 update extends free Vercel Authentication protection to production deployments on every plan. Visitors must sign in with an account authorized for the project. Teams can apply protection to all deployments and make that setting the default for new projects. Deployment Protection Exceptions are also free, allowing selected preview domains to remain publicly accessible.

Vercel's September 9 pricing update lets Pro teams buy Password Protection for individual projects at $20 per project each month. Visitors must enter the team's chosen password before viewing protected deployments. The option previously required a $150 monthly team-wide add-on. Teams enable it in Deployment Protection settings and can disable it to stop future charges for that project.

Vercel's September 9 CLI update brings release announcements into the terminal for developers and coding agents. The changelog command returns five recent entries with their complete Markdown by default, with options to change the limit, search by keyword or produce JSON for scripts. The feature requires Vercel CLI 59.6.0 or later.

Vercel added in-chat provider connections to v0 on September 9, beginning with Resend, Amazon OpenSearch, MongoDB Atlas, Algolia and Clerk. When a prompt needs one of these services, v0 offers a connection card and then configures the required environment variables. Vercel says it also loads a provider's published agent skills automatically, when available, to guide generated code.

Vercel's September 8 release note says its deployment step became about 10% faster after it replaced separate routing metadata uploads for each function path with one combined manifest. The company reports an average saving of one second, with large applications saving up to 12 seconds. The optimization applies automatically to all builds and requires no project changes.

Vercel reported on September 8 that Sandbox domain lookups fell from a median 62 milliseconds to 3.4 milliseconds after routing moved from one central store to nearby regional replicas. The change affects public domains created through sandbox.domain() and is applied automatically. Vercel says pricing is unchanged; the reported 18-fold improvement measures domain lookup latency, rather than an entire application's response time.

Vercel introduced Flat Rate CDN for Pro teams on September 8, replacing usage billing for covered CDN resources with a monthly capacity tier shared across projects. Vercel says temporary spikes will not raise that period's bill, but sustained growth can change the next month's tier. New Pro teams receive it by default; existing teams can opt in or retain usage-based billing.

Vercel made Flat Rate CDN generally available for Pro teams on September 8. The included tier provides one million requests and one terabyte of transfer, shared across a team's projects; larger tiers cost extra. Vercel says temporary excess traffic continues without additional billing under its fair-use rules. Coverage includes CDN requests, specified transfers and related observability events, rather than every platform charge.

Miniflare v5 prepares Cloudflare local development tooling for the upcoming cf CLI. Miniflare powers local Workers development behind wrangler dev, the Cloudflare Vite plugin, and @cloudflare/vitest-plugin. Most projects should use those tools instead of depending on Miniflare directly, and Miniflare v5 will not require any action. The most significant change is a new configuration shape which aligns Miniflare with cloudflare.config.ts, the programmatic Cloudflare configuration format now available for testing. Other breaking changes include: Removed deprecated APIs and options, such as legacy alpha D1 bindings. Removed now-unused, internal APIs like wrappedBindings Removed Miniflare's built-in module discovery; higher-level tools like Wrangler and the Vite plugin should be providing the module graph. Moved local-only /cdn-cgi routes under /cdn-cgi/local.

You can now deploy Workers with larger dependencies, heavier frameworks, and more code without hitting size limits. When you deploy a Worker, Wrangler bundles your code and compresses it before uploading. Previously, Cloudflare checked that compressed size and rejected deploys over 3 MB (Free) or 10 MB (Paid). That limit has been removed. Cloudflare now only checks the uncompressed size of your bundle, which is 64 MiB across all plans. To check your Worker's bundle size before deploying: wrangler deploy --outdir bundled/ --dry-run Total Upload: 259.61 KiB / gzip: 47.23 KiB The Total Upload value is your uncompressed bundle size. This is what counts against the 64 MiB limit. The gzip value is shown for reference but is no longer a limit. For more information, refer to the Worker size limits documentation.

You can now manage Email Routing rules that route emails to Workers from your Wrangler configuration. Add literal addresses or a catch-all address to the top-level addresses field: { "$schema": "./node_modules/wrangler/config-schema.json", "name": "invoice-handler", "main": "src/index.ts", // Set this to today's date "compatibility_date": "2026-10-02", "addresses": [ "invoice@yourdomain.com" ] } name = "invoice-handler" main = "src/index.ts" # Set this to today's date compatibility_date = "2026-10-02" addresses = ["invoice@yourdomain.com"] When you run wrangler deploy, Wrangler creates rules for new addresses, updates existing rules managed by the Worker, and removes managed rules that are no longer in the configuration. Wrangler shows the planned changes and asks for confirmation before applying potentially destructive changes.