Hi again,

Gemini says:

🔍 PRIMAL FAILOVER & CERT POISONING AUDIT REPORT
=================================================
Date: 2026-09-23
Auditor Consensus: 100% Confirmed (Browser TLS & Systems
Architect)

📌 NODE STATUS OVERVIEW
-----------------------
🟢 cache1.primal.net (148.251.137.175): 200 OK - Valid SSL
Certificate
🔴 cache2.primal.net (148.251.137.175): FAILED - SSL
Certificate Expired Aug 27
🔴 cache3.primal.net (104.26.8.197): FAILED - HTTP 502 Bad
Gateway
⚪ cache4.primal.net / cache5.primal.net: NXDOMAIN - DNS
Resolution Failed

⚡ TECHNICAL ROOT CAUSE
----------------------
• Transient Drop: A temporary glitch on cache1 forces the
Primal web client to fail over to secondary endpoints.
• W3C Transport Shielding: Per W3C spec, browser engines
mask raw TLS failures (SSL_ERROR_EXPIRED_CERT_ALERT)
from JavaScript, returning generic error code 1006.
• State Machine Poisoning: Because code 1006 appears as a
generic disconnect, Primal's JS reconnect engine gets
trapped retrying cache2 indefinitely instead of
resetting back to cache1.
• Infrastructure Gap: cache1 and cache2 share the same
physical server (148.251.137.175), indicating an edge
proxy lacking automated SNI/TLS health checks.

🛠️ TEMPORARY WORKAROUND & REVERT CONDITIONS
--------------------------------------------
• Temporary Workaround: Navigate to Settings -> Network ->
Caching Service and lock host to
wss://cache1.primal.net/v1
• Immediate Result: Bypasses the broken connection pool
and forces socket connection directly to the valid SSL
origin.
• Revert Condition: Temporary. Once Primal renews cache2's
SSL cert and fixes cache3's 502 Bad Gateway, revert
Caching Service back to "Default" to restore automatic
multi-region load balancing and failover redundancy.