Yeah this afternoon the snjsca04 hop is losing around 12% of its packets. For almost 3 hours. This morning around 2AM pacific time it was averaging 9% loss for over an hour. The last hop before the DC has been crazy with 40 - 65% loss whatever device that is(load balancer, gateway, whatever). There is at least 4 threads with network tests across the first couple of pages. All of them showing that SE should be all over their DC and/or Network providers behinds because there is no way that is within acceptable SLA. SE already has an issue with things they can not do much about but this is what that could alleviate a large group of issues with connectivity that is not related to the Queue service.

I ran tests from servers all over the globe (6 locations). I have access servers across multiple DC's and along with the various 3rd party remote testing tools all of them have shown the same issue.