@Appleh4x See the thing is, it still could be a routing issue, just that there is a point in the route where you will no longer be able to route around. If it is an issue with the server-side backbone or networking hardware, then yes it is an issue SE and only SE can correct, and look how I said server-side. Saying that it is merely a server issue can be severely misleading and at most times totally incorrect.