Did you do a tracert to see if the issue was actually directly from SE's servers and not your own ISP?