Pro and Enterprise customers now have the ability to temporarily disable all automatic system mitigations, including DDoS mitigations, by the Vercel Firewall.

We strongly recommend against disabling protections. However, if you feel like the protections are blocking legitimate traffic this feature presents a break-glass option. This may be particularly applicable if you have a proxy in front of Vercel that provides DDoS protection and which may interfere with Vercel's protection.

To temporarily disable system mitigations, visit the Firewall tab within the Vercel dashboard and click the ellipsis menu at the top right to access additional options. Once you confirm that you would like to temporarily disable all system mitigations, all traffic to your project will bypass Vercel Firewall system DDoS mitigations for a period of 24 hours.

Vercel Firewall's system defenses are automatically enabled for all projects on all plans, mitigating billions of malicious connection attempts every week, and preventing resource abuse. Customers must exercise extreme caution when disabling automated defenses as no attack will be blocked.

Please note that you are responsible for all usage fees incurred when using this feature, including illegitimate traffic that may otherwise have been blocked.

Learn more about Vercel Firewall's automatic DDoS mitigation.

Starting today, Node.js version 22 is available as the runtime for your builds and functions leveraging Node. To use version 22, go to Project Settings > General > Node.js Version and select 22.x. This is also the default version for new projects.

Node.js 22 highlights:

• Improved Stream performance: higher default water mark provides performance boosts across the board at the cost of slightly higher memory usage

• Improved AbortSignal performance: optimized AbortSignal creation improves performance in fetch and the test runner

• Improved Buffer performance: significant improvements to the Buffer.copy and Buffer.write methods lead to overall performance boost

• Improved CJS interop with ESM: added support for require()ing synchronous ESM module graphs

The current version used by Vercel is 22.11.0 and will automatically update minor and patch releases. Therefore, only the major version (22.x) is guaranteed.

Read our Node.js runtime documentation to learn more.

Streaming is now supported and will soon be enabled by default in Vercel Functions for the Python runtime, allowing functions to send data to the client as it’s generated rather than waiting for the full response. This is particularly useful for AI applications.

This change will be rolled out progressively. Starting today, it will apply to all new projects and will take effect for all existing projects on January 5, 2025. On this date, projects using Log Drains will be migrated, and streaming responses will impact the format and frequency of runtime logs.

To enable streaming as the default for your Vercel Functions using Python, add the VERCEL_FORCE_PYTHON_STREAMING=1 environment variable in your project. Streaming will then be enabled on your next production deployment.

For more information, read the Python streaming documentation or get started with our template.