OKX Will No Longer Support WebSocket Port 8443
Key points
OKX will discontinue WebSocket connections on port 8443 due to a network upgrade.
- WebSocket connections on port 8443 will be stopped for public internet on October 31, 2026, and for Colo on November 16, 2026.
- Users must remove :8443 from their WebSocket URLs before the specified dates; only the port changes, while the host and path remain the same.
- Port 443 will continue to work on all affected domains, and the REST API is not affected by this change.
A summary by OKX Payback. Check the full text below and the original on OKX for exact terms.
Full announcement (rewritten in plain English)
Hello OKX API users,
OKX will upgrade its network infrastructure, which means WebSocket connections on port 8443 will be disabled. This includes Colo connections:
- Public internet: October 31, 2026
- Colo: November 16, 2026
Changes Overview
Port 443 is already functional on all affected domains, including Colo. Both ports will remain operational until the specified dates. After these dates, connections to port 8443 will not work. This is a significant change.
Domains Affected
- Public internet, production:
ws.okx.com,wseea.okx.com,wsus.okx.com - Public internet, demo trading:
wspap.okx.com,wseeapap.okx.com,wsuspap.okx.com - Colo: all Colo WebSocket connections
This change affects all paths, including /ws/v5/public, /ws/v5/private, /ws/v5/business, and on the Global site, /ws/v5/public-sbe.
Required Action
Please remove :8443 from your WebSocket URLs by October 31, 2026 (for Colo, by November 16, 2026). Only the port will change; the host and path will remain the same. The wss:// protocol uses port 443 by default, and :443 will also work.
- Before:
wss://ws.okx.com:8443/ws/v5/public - After:
wss://ws.okx.com/ws/v5/public
What Remains Unchanged
- REST API
You can find complete technical details in the API changelog for your region:
OKX Payback rewrote this official OKX announcement in plain English. If anything differs, the original announcement on OKX prevails.