BlazingCDN does not support WebSockets. Our service is optimized for HTTP(S) content delivery (including video streaming/VOD, large file delivery, and HTTP-based API/static content). WebSocket connections require long-lived, bidirectional TCP sessions, which do not align with BlazingCDN’s current architecture and SLA.
What this means in practice
If your product uses WebSockets for:
-
real-time events (chat, presence, market quotes, live dashboards),
-
push notifications/signaling,
-
real-time gaming,
-
IoT/telemetry with a persistent connection,
BlazingCDN will not be able to proxy or accelerate those connections.
Why we don’t support WebSockets
WebSockets create long-lived connections that:
-
require specialized session management at the edge,
-
are sensitive to timeouts, load balancing, and reconnect behavior,
-
reduce resource predictability and complicate CDN-level security policies.
BlazingCDN is focused on high-efficiency delivery of HTTP(S) traffic and video streaming.