Today we saw a sudden and global error coming from Safari clients over websocket on a node + ws server hosted on Render. All other browsers had normal behavior, and it didn’t correlate to any code changes. We suspected that this was being caused by alteration of the websocket frames en route, possibly getting modified by Cloudflare or Render before arriving to our server. This was further confirmed by spinning up an instance of our service on GCP, where we do not encounter the error. Is anyone else experiencing anything like this? Was there perhaps a change in Render’s network infra that could be increasing the bytesize of websocket frames?
3 Likes
Hey Josh,
This ended up being an issue our side, covered by https://status.render.com/incidents/62m9yz1rqdp2
Regards
John B
Render Support, UTC+1 
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.