If I had to venture a guess, I would guess that because steemit.com/wspa is now issuing 301 redirects to the new websocket endpoint, your websocket client is out of spec and isn't following those redirects to the new wss://steemd.steemit.com websocket endpoint.

If indeed that is the issue (it has bit others today), having either a working HTTP client implementation, or running your own steemd would solve this problem.

If this isn't the issue you're describing, a list of steps to reproduce would be helpful so we can squash the bug.