Reverence.6915 Posted May 1, 2018 Share Posted May 1, 2018 Hoping some of the ANet techies can help with this one. Tracing route to ec2-35-153-76-204.compute-1.amazonaws.com [35.153.76.204]over a maximum of 30 hops:1 1 ms 1 ms 1 ms 192.168.0.12 26 ms 7 ms 7 ms static-n49-176-176-1.bla2.nsw.optusnet.com.au [49.176.176.1]3 Request timed out.4 9 ms 7 ms 8 ms 198.142.250.1975 8 ms 8 ms 8 ms 198.142.139.1146 Request timed out.7 Request timed out.8 Request timed out.9 194 ms 206 ms 231 ms 80.81.69.15310 208 ms 218 ms 208 ms ge-3-1-0.0.pjr02.lax002.flagtel.com [85.95.27.181]11 294 ms 299 ms 279 ms ae2.0.pjr02.nyc005.flagtel.com [85.95.26.13]12 Request timed out.13 Request timed out.14 Request timed out.15 Request timed out.16 Request timed out.17 Request timed out.18 289 ms 296 ms 285 ms 54.239.110.22919 284 ms 293 ms 285 ms 54.239.111.8520 Request timed out.21 Request timed out.22 Request timed out.23 Request timed out.24 Request timed out.25 Request timed out.26 Request timed out.27 Request timed out.28 Request timed out.29 Request timed out.30 * Request timed out.Trace complete Link to comment Share on other sites More sharing options...
Reverence.6915 Posted May 1, 2018 Author Share Posted May 1, 2018 It's just been super frustrating having my ping doubled since the last week or so. It's been so bad I can barely play Link to comment Share on other sites More sharing options...
Dayra.7405 Posted May 1, 2018 Share Posted May 1, 2018 49.176.176.1 - Sidney85.95.26.13 - UK54.239.111.85 - US(whois „IP“ )Looks like someone route's you wrongly 2/3 instead of 1/3 around the world.And that's not ANet‘s responsibility ;) Complain at your INet Provider. Link to comment Share on other sites More sharing options...
Inculpatus cedo.9234 Posted May 1, 2018 Share Posted May 1, 2018 For an individualized response, you would need to contact the Tech CS Team via the 'Support' link above/below.Good luck. Link to comment Share on other sites More sharing options...
Pepper.3901 Posted May 6, 2018 Share Posted May 6, 2018 @Reverence.6915 said:Hoping some of the ANet techies can help with this one. Tracing route to ec2-35-153-76-204.compute-1.amazonaws.com [35.153.76.204]over a maximum of 30 hops:1 1 ms 1 ms 1 ms 192.168.0.12 26 ms 7 ms 7 ms static-n49-176-176-1.bla2.nsw.optusnet.com.au [49.176.176.1]3 Request timed out.4 9 ms 7 ms 8 ms 198.142.250.1975 8 ms 8 ms 8 ms 198.142.139.1146 Request timed out.7 Request timed out.8 Request timed out.9 194 ms 206 ms 231 ms 80.81.69.15310 208 ms 218 ms 208 ms ge-3-1-0.0.pjr02.lax002.flagtel.com [85.95.27.181]11 294 ms 299 ms 279 ms ae2.0.pjr02.nyc005.flagtel.com [85.95.26.13]12 Request timed out.13 Request timed out.14 Request timed out.15 Request timed out.16 Request timed out.17 Request timed out.18 289 ms 296 ms 285 ms 54.239.110.22919 284 ms 293 ms 285 ms 54.239.111.8520 Request timed out.21 Request timed out.22 Request timed out.23 Request timed out.24 Request timed out.25 Request timed out.26 Request timed out.27 Request timed out.28 Request timed out.29 Request timed out.30 * Request timed out.Trace complete+1My traceroutes look about the same several times a week. Few traceroutes can even complete - the timeouts are nutso. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.