---
title: Troubleshooting request ECONNRESET errors
description: Understand what ECONNRESET means in Vercel runtime logs, why it happens when calling external APIs, how to diagnose it, and when to contact Vercel Support.
url: "https://vercel.com/kb/guide/troubleshooting-request-econnreset-errors"
published: 2025-11-03
last_updated: 2026-07-16
authors: Gabe Nuñez
install_vercel_plugin: npx plugins add vercel/vercel-plugin
---

## What does ECONNRESET mean?

`ECONNRESET` means _connection reset by peer._ The remote server (or something on the network path) closed the connection unexpectedly. This is usually caused by the external service or a misconfiguration, not by Vercel.

## Common causes

- **Persistent errors**: Usually a setup or configuration issue (wrong protocol, port, or missing allowlist).
  
- **Intermittent errors**: Often external (e.g., provider maintenance, load spikes, or deployment changes). Check provider logs and metrics to correlate timing.
  

**Other possible triggers:**

- Provider timeouts or rate limiting
  
- Protocol/TLS mismatches
  
- IP allowlisting issues (default Vercel egress IPs are dynamic; use [Secure Compute](/docs/secure-compute) or [Static IPs](/docs/connectivity/static-ips) for dedicated IPs)
  
- Running functions far from the provider region (learn to configure your Vercel Function Region [here](/docs/functions/configuring-functions/region)).
  

## Quick steps to diagnose

1. **Check with your provider**: Did they receive the request? (If yes, [proceed to contact Vercel Support](#when-to-contact-vercel-support))
   
2. **Inspect Vercel Runtime Logs**: Look for request details and error timing.
   
3. **Enable NODE\_DEBUG**: Add an environment variable to your project `NODE_DEBUG=http,https,net` to capture detailed network activity.
   
4. **Add timeouts and retries**: Handle transient resets with capped backoff retries.
   
5. **Limit concurrency**: Avoid flooding the provider with parallel requests.
   

## When to contact Vercel Support

If your provider confirms they received the request but you still see `ECONNRESET`, reach out via the [Support Center](/help). Include:

- Deployment URL and function route
  
- Timestamp (UTC) and function region
  
- Runtime (Node.js)
  
- Runtime Logs for the request
  
- Any additional information that the provider can provide about the request
  

## How to reduce future errors

- Place your functions in regions close to your data source
  
- Use [Secure Compute](/docs/secure-compute) or [Static IPs](/docs/connectivity/static-ips) for dedicated egress IPs if your provider requires allowlisting
  
- Always set timeouts, retries, and concurrency limits
  
- Monitor patterns with Observability to spot issues early

## Related Documentation

- [Vercel Functions](/docs/functions)

## More Vercel Functions guides

- [Optimize Runtime Cache on Vercel](/kb/guide/optimize-runtime-cache-reads-on-vercel): Diagnose rising Runtime Cache usage, trace reads to tags and code paths, and reduce avoidable reads while checking write cost and origin traffic.
- [How to stop Vercel Functions from timing out](/kb/guide/what-can-i-do-about-vercel-serverless-functions-timing-out): Vercel Functions that time out usually trace back to a few causes. Learn how Fluid Compute fixes most of them and how to handle the edge cases.
- [The Complete Guide to Vercel Connect](/kb/guide/vercel-connect): Use Vercel Connect to call provider APIs like Slack, GitHub, Linear, Microsoft, Discord, Snowflake, and Salesforce from your agents and services with short-lived, scoped tokens instead of long-lived secrets.

## Reference Architecture

Choose a stack and work through the decisions behind it, with curated documentation, guides, templates, and courses to help you build.

- [Agent stack](/kb/architecture/agents): Build and operate agents with models, tools, and durable workflows.
- [Web applications](/kb/architecture/web): Choose rendering, data, authentication, and caching approaches.
- [Backends](/kb/architecture/backends): Choose a runtime, connect services, and run background work.

[Browse all stacks](/kb/architecture)