RDP is a lot more resilient than HTTP/S. There are built in mechanisms into RDP that allows it to simply delay or queue messages until net connection resumes, and then it pushes them all to keep you in pace. HTTP/S and the processes we use do not have that redundancy. I would assume that it is either a routing issue, or you are having issues with packet loss. I doubt it's a complete network disconnect, but I suppose it's possible.