🇺🇸 HYSTERIA2 Live Verified Node

United States (US) — HYSTERIA2 HYSTERIA Node

Host: 64.32.13.230:443 • Tested: 12:24:14 AM

Checked Latency 445 ms

Est. Bandwidth 0.0 Mbps

24h Uptime SLA 100%

Exit Consensus US (Verified)

⚡ Direct Connection URI (HYSTERIA2 • United States) Xray-core Verified • 100% Uptime

hysteria2://e4499a62-0cfe-11eb-ad8c-f23c9164ca5d@64.32.13.230:443?sni=53edf574-tmm5c0-tpftcp-13x18.los.hyhuawei.com#%F0%9F%87%BA%F0%9F%87%B8US-freevpnkeys.com-TG-%40yavpn_robot

1. Direct Single Key Copy the URI above into Happ, Incy, v2RayTun, or v2rayNG. Re-tested every 30 min.

2. Free Auto-Updating Subscription Auto-sync fresh working nodes every 30 min: https://freevpnkeys.com/sub/happ

3. Private 10 Gbps Anti-DPI Multi-Key Need zero congestion, 10 Gbps speed & strict ISP whitelist bypass? Get a private key in Telegram bot @yavpn_robot (~$0.05/day).

⚡ Interactive Browser Ping Test

Direct client-to-node round-trip time (RTT) measured in your browser.

👍 Community Health Rating

Does this server currently connect and route traffic from your location?

🚀 1-Click App Import

Instantly add this proxy node to your favorite client application:

Happ ↗

iOS / Android / PC / Mac

v2RayTun ↗

Android / iOS / PC / Mac

Incy ↗

iOS / Android / PC / Mac

v2rayNG ↗

Android

FlClashX / Clash ↗

Windows / macOS / Android

Karing / sing-box ↗

Core / GUI

📊 Recent Verification History

Automated multi-point health probes through Xray-core / libxray (verified every 30 minutes)

24h SLA: 100% (25 probes)

Probe Time	Probe Node	Verdict	Latency (RTT)	Exit IP
Wed, 04 Nov 2026 00:24:14 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	445 ms	2610:150:c001:4:881:c205:3610:340c
Tue, 03 Nov 2026 23:24:15 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	499 ms	2610:150:c001:4:881:c205:3610:340c
Tue, 03 Nov 2026 22:24:15 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	621 ms	2610:150:c001:4:881:c205:3610:340c
Tue, 03 Nov 2026 21:24:14 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	646 ms	2610:150:c001:4:881:c205:3610:340c
Tue, 03 Nov 2026 20:24:14 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	147 ms	2610:150:c001:4:881:c205:3610:340c
Tue, 03 Nov 2026 19:24:15 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	167 ms	2610:150:c001:4:881:c205:3610:340c
Tue, 03 Nov 2026 18:54:15 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	682 ms	2610:150:c001:4:881:c205:3610:340c
Tue, 03 Nov 2026 17:54:14 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	342 ms	2610:150:c001:4:881:c205:3610:340c
Tue, 03 Nov 2026 16:54:14 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	300 ms	2610:150:c001:4:881:c205:3610:340c
Tue, 03 Nov 2026 15:54:15 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	155 ms	2610:150:c001:4:881:c205:3610:340c
Tue, 03 Nov 2026 14:54:15 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	134 ms	2610:150:c001:4:881:c205:3610:340c
Tue, 03 Nov 2026 13:54:14 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	132 ms	2610:150:c001:4:881:c205:3610:340c
Tue, 03 Nov 2026 12:54:14 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	645 ms	2610:150:c001:4:881:c205:3610:340c
Tue, 03 Nov 2026 11:54:14 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	159 ms	2610:150:c001:4:881:c205:3610:340c
Tue, 03 Nov 2026 11:24:14 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	515 ms	2610:150:c001:4:881:c205:3610:340c

⚙️ Protocol Parameter Specification

Verified protocol configuration attributes required for manual client profiles.

Host / Address 64.32.13.230

Port 443

Security Protocol TLS

Transport Type HYSTERIA

SNI (Server Name Indication) 53edf574-tmm5c0-tpftcp-13x18.los.hyhuawei.com

Password e4499a62-0cfe-11eb-ad8c-f23c9164ca5d

TLS Fingerprint 22971419

🛡️

Direct TLS Encrypted Channel (HYSTERIA)

Cryptographic resistance profile and Deep Packet Inspection (DPI) evasion analysis

SNI: Discreet Camouflage Host (Optimized for Evasion) Port 443 (Universal HTTPS Gateway) uTLS: 22971419 Custom Handshake (Active Cloaking)

Standard TLS deployment over HYSTERIA on server 64.32.***.*** delivers dependable international throughput with an uptime rating of 99.6%.

Network Port Analysis: With traffic routed across port 443, data packets pass uninhibited through carrier-grade network address translation gateways worldwide.

SNI Masking Analysis (53edf574-tmm5c0-tpftcp-13x18.los.hyhuawei.com): This discreet camouflage choice (53edf574-tmm5c0-tpftcp-13x18.los.hyhuawei.com) provides superior operational security for users circumventing severe digital censorship.

uTLS Handshake Security Analysis (22971419): Configured 22971419 parameters ensure client handshakes adhere to accepted cryptographic conventions without alerting middlebox monitors.

Client Handshake Masking (uTLS): Configured 22971419 parameters ensure client handshakes adhere to accepted cryptographic conventions without alerting middlebox monitors.

❓ Frequently Asked Questions for Node #22971419

How does node #N bypass state-level censorship and firewall restrictions? ▼

Standard TLS deployment over HYSTERIA on server 64.32.***.*** delivers dependable international throughput with an uptime rating of 99.6%. Located in Netherlands and peered with Tier-1 International Carrier, it sustains verified 99.6% reliability with low response times around 58 ms.

What client software is recommended to connect to this HYSTERIA2 configuration? ▼

We advise using proven clients supporting modern protocols: Happ, Incy (incy.cc), v2RayTun, Clash Meta (Mihomo), Sing-box, v2rayNG, and Streisand. Each platform supports direct QR scanning and instant URI import.

Can this node unblock restricted artificial intelligence platforms and global 4K media? ▼

Yes. Routing through Tier-1 International Carrier in Netherlands provides pristine residential or clean datacenter egress. Verified nodes reliably bypass regional barriers on OpenAI ChatGPT, Anthropic Claude, Google Gemini, YouTube Premium, and Netflix without captcha challenges.

How do port 443 and domain masking perform under heavy censorship in Iran and China? ▼

With traffic routed across port 443, data packets pass uninhibited through carrier-grade network address translation gateways worldwide. This discreet camouflage choice (53edf574-tmm5c0-tpftcp-13x18.los.hyhuawei.com) provides superior operational security for users circumventing severe digital censorship. This architecture ensures dependable transit across restricted carriers such as MCI, Irancell, and China Telecom.

What steps should I take if node #N (64.32.***.***) experiences a connection timeout? ▼

Our automated probing infrastructure validates public keys continuously. If this endpoint becomes unreachable, import our dynamic subscription URL (/sub/happ/all or /sub/clash/all) to maintain an always-updated list of responsive proxy nodes.

🌐 7-Service Geocheck & Regional Consensus

Authentic multi-provider exit node audit across 16 GeoIP databases, RIPE/ASN, proxycheck.io v3, CDN PoP, AI APIs, and Stash probes.

GeoCheck v1.4 ⏱ 13.27s

1. Exit IP & Autonomous System (Identity) 🇺🇸 US

Public Exit IPv4: 2610:150:c001:4:881:c205:3610:340c

Network (ASN / Org): AS46844 · Sharktech

BGP Prefix / Subnet: —

Node Location: Las Vegas, Nevada — 🇺🇸 US

2. IP Address Reputation (proxycheck.io v3) Hosting

Address Class: 🖥️ Hosting / Datacenter

Risk Score:

20 / 100 (95% conf)

Detection Flags:

hosting

Operator / Provider: Sharktech

3. Geolocation Consensus (IPv4)

Providers tallied: 19

🇺🇸 US United States

100% (19/19)

🔓 4. Service Availability & Anti-Bot Checks (Stash Checks)

Service	Status	Region	Technical Detail	RTT
ChatGPT (web)	● available	—	—	1616 ms
ChatGPT (app)	● available	—	—	1891 ms
YouTube Premium	● available	—	—	1723 ms
Netflix	● available	🇺🇸 US	full catalogue	2902 ms
Claude	● available	🇺🇸 US	Anthropic API reachable	472 ms
TikTok	● available	—	—	2072 ms
Gemini	● available	—	—	1575 ms
NotebookLM	● blocked	—	not offered in this country	—

🤖 5. AI Model API Endpoints (Direct Probe)

AI Endpoint	Vendor	State	HTTP	Detail	RTT
OpenAI	OpenAI	● reachable	401	answered, credentials not supplied	1615 ms
Anthropic	Anthropic	● reachable	401	answered, credentials not supplied	1604 ms
Google Gemini	Google	● reachable	403	answered, credentials not supplied	2077 ms
DeepSeek	DeepSeek	● reachable	401	answered, credentials not supplied	1822 ms
Qwen (Singapore)	Alibaba	● reachable	401	answered, credentials not supplied	2093 ms
Qwen (Beijing)	Alibaba	● reachable	401	answered, credentials not supplied	2093 ms
Kimi / Moonshot	Moonshot	● error	—	request failed	—
Zhipu GLM	Zhipu	● reachable	401	answered, credentials not supplied	1528 ms