EAS CLI Network Failure on Windows: ECONNRESET During GraphQL Requests

### Build/Submit details page URL

_No response_

### Summary

What's broken:

EAS CLI fails whenever attempting to communicate with Expo’s API servers (api.expo.dev). All commands that require network communication (such as eas login, eas whoami, and eas build --platform android) fail with a read ECONNRESET error.

The failure occurs before a build is queued, preventing authentication and project uploads.

Error:

### Managed or bare?

Managed workflow

### Environment

EAS CLI version:
[Check by running: eas --version]
Latest available version at time of issue

Node version:
Tested on Node 24.x and Node 20.x LTS

Platform(s):
Android (affects all commands requiring Expo API access)

Expo SDK version:
[Your current SDK version]

EAS Build details page URL:
N/A — build is never created due to API connection failure

Operating System:
Windows 10/11

### Error output

request to https://api.expo.dev/graphql failed, reason: read ECONNRESET
Error: GraphQL request failed.

### Reproducible demo or steps to reproduce from a blank project

Steps to reproduce the issue:

Navigate to project directory in Command Prompt or PowerShell

Run: eas login

Enter credentials

Connection fails with ECONNRESET

OR

Run: eas build --platform android

Build configuration starts

Network request to Expo GraphQL API fails

Build terminates with ECONNRESET

This happens consistently regardless of:

Reinstalling Node.js

Downgrading Node versions (Node 24 → Node 20 LTS)

Clearing npm cache

Reinstalling eas-cli

Using EXPO_TOKEN authentication instead of login

Disabling IPv6

Using NODE_OPTIONS=--dns-result-order=ipv4first

Restarting the PC

Restarting the router