|
There's probably a node somewhere out there in the US or downtown TO that's giving people trouble:
Tracing route to airsoftcanada.com [168.235.83.126]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 6 ms 6 ms 6 ms 199.47.125.1
3 7 ms 6 ms 6 ms 10.15.32.1
4 9 ms 7 ms 6 ms xe-5-2-1-80.cr0-tor1.ip4.gtt.net [77.67.71.105]
5 19 ms 19 ms 20 ms xe-3-0-0.cr8-nyc3.ip4.gtt.net [89.149.183.46]
6 * * * Request timed out.
7 * * * Request timed out.
8 22 ms 18 ms 20 ms 168.235.83.126
Trace complete.
I've been having this problem lately too with not just ASC but google as well. There's a rogers node somewhere that's being overloaded, but I don't know the proper channels nor the right people to contact to ameliorate the problem.
Tracing route to google.ca [172.217.2.131]
over a maximum of 30 hops:
1 <1 ms 1 ms <1 ms 192.168.1.1
2 6 ms 6 ms 6 ms 199.47.125.1
3 6 ms 6 ms 6 ms 10.15.32.1
4 7 ms 6 ms 6 ms google.ip4.torontointernetxchange.net [206.108.34.6]
5 39 ms 59 ms 6 ms 209.85.242.13
6 12 ms 6 ms 6 ms 209.85.250.7
7 6 ms 6 ms 6 ms yyz08s14-in-f3.1e100.net [172.217.2.131]
Trace complete.
It's 12:37 am right now so it's off peak and the problem's not present at the moment... but sometimes hops 5-6 have problems.
If anyone else is tech savvy and knows something else that might be happening... please let me know.
|