I have the info you requested. What is the best way to send it to you?
As of 10:45 pm PST 9/04/2018
Tracing route to ec2-52-1-4-124.compute-1.amazonaws.com [52.1.4.124]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms noe- Wifi [192.168.1.1]
2 6 ms 9 ms 7 ms 10.34.192.1
3 8 ms 6 ms 7 ms COX-68-12-9-162-static.coxinet.net [68.12.9.162]
4 7 ms 8 ms 7 ms COX-68-12-9-162-static.coxinet.net [68.12.9.162]
5 14 ms 14 ms 13 ms dalsbprj02-ae1.0.rd.dl.cox.net [68.1.5.140]
6 13 ms 13 ms 14 ms 52.95.218.94
7 33 ms 16 ms 33 ms 176.32.124.215
8 14 ms 13 ms 14 ms 176.32.125.231
9 * * * Request timed out.
10 55 ms 51 ms 51 ms 54.239.43.206
11 46 ms 48 ms 47 ms 72.21.222.251
12 * * * Request timed out.
13 60 ms 65 ms 61 ms 54.239.108.188
14 49 ms 47 ms 48 ms 54.239.110.184
15 64 ms 87 ms 66 ms 54.239.110.181
16 45 ms 48 ms 48 ms 54.239.108.131
17 47 ms 47 ms 47 ms 52.93.24.22
18 47 ms 47 ms 47 ms 52.93.24.17
19 * * * Request timed out.
20 * * * Request timed out.
say this is a location in virginia, about a month ago it was only connecting to boca raton florida, don't know what that ip is anymore or if it's even in use anymore.
Mark, here's one of ours
Would more tracing routes be helpful? If so, we have others. Thanks so much!
Looking more closely at your specific issue, I see that a field escalation was put in and a node split is needed as your node has high utilization at peak hours.
Brian
Cox Support Forum Moderator
That's what we suspected was needed, but haven't gotten confirmation that it will actually happen and how long it will take. If you have any of that info, it would be greatly appreciated. I know it sounds like a silly issue because it's mostly about a game, but our son was picked up by a professional eSports organization and if he can't stream at home he will need to move-- not quite ready for that. Thank you!
im in san diego, fortnite is always giving me packet loss, ive had 3 techs come out, last tech REPLACED everything, wire that goes to the telephone poll even internet cable and tv cables around the house, still have bad packet loss and time outs on fortnite
There were multiple ip's so I traced all of them with that had Fortnite's PID:
Tracing route to ec2-34-199-96-60.compute-1.amazonaws.com [34.199.96.60]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 2 ms 2 ms 2 ms ip68-107-57-129.sd.sd.cox.net [68.107.57.129]
3 1 ms 1 ms 1 ms ip68-101-129-110.sd.sd.cox.net [68.101.129.110]
4 2 ms 3 ms 2 ms visthbrc01-get0702.sd.sd.cox.net [68.6.8.119]
5 36 ms 31 ms 32 ms dalsbbrj02-ae3.0.rd.dl.cox.net [68.1.5.134]
6 32 ms 31 ms 32 ms 52.46.167.210
7 34 ms 42 ms 40 ms 54.239.105.99
8 32 ms 32 ms 31 ms 176.32.125.157
9 * * * Request timed out.
10 67 ms 73 ms 68 ms 54.239.46.14
11 65 ms 65 ms 64 ms 54.239.42.188
12 * * * Request timed out.
13 67 ms 65 ms 68 ms 54.239.108.112
14 * * * Request timed out.
15 84 ms 78 ms 70 ms 52.93.27.21
16 65 ms 65 ms 64 ms 52.93.25.108
17 * * * Request timed out.
18 64 ms 64 ms 64 ms 52.93.24.99
19 * * * Request timed out.
20 * * * 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.
Tracing route to ec2-34-199-162-219.compute-1.amazonaws.com [34.199.162.219]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.1.1
2 2 ms 1 ms 2 ms ip68-107-57-129.sd.sd.cox.net [68.107.57.129]
3 1 ms 1 ms 1 ms ip68-101-129-110.sd.sd.cox.net [68.101.129.110]
4 2 ms 2 ms 2 ms visthbrc01-get0702.sd.sd.cox.net [68.6.8.119]
5 32 ms 32 ms 33 ms dalsbprj02-ae2.0.rd.dl.cox.net [68.1.2.121]
6 32 ms 32 ms 32 ms 52.46.167.212
7 50 ms 33 ms 45 ms 54.239.105.117
8 31 ms 32 ms 32 ms 176.32.125.169
9 * * * Request timed out.
10 67 ms 70 ms 70 ms 54.239.46.4
11 65 ms 65 ms 65 ms 54.239.43.176
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 84 ms 66 ms 78 ms 52.93.27.87
16 65 ms 64 ms 65 ms 54.239.111.71
17 66 ms 66 ms 66 ms 52.93.25.28
18 64 ms 65 ms 64 ms 52.93.25.25
19 * * * Request timed out.
20 * * * 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.
Tracing route to ec2-34-207-38-109.compute-1.amazonaws.com [34.207.38.109]
over a maximum of 30 hops:
1 <1 ms 1 ms <1 ms 192.168.1.1
2 2 ms 1 ms 1 ms ip68-107-57-129.sd.sd.cox.net [68.107.57.129]
3 2 ms 1 ms 1 ms ip68-101-129-110.sd.sd.cox.net [68.101.129.110]
4 3 ms 4 ms 3 ms visthbrc01-get0702.sd.sd.cox.net [68.6.8.119]
5 33 ms 33 ms 32 ms dalsbbrj02-ae3.0.rd.dl.cox.net [68.1.5.134]
6 32 ms 32 ms 34 ms 72.21.221.202
7 52 ms 45 ms 35 ms 176.32.125.174
8 31 ms 31 ms 32 ms 176.32.125.239
9 * * * Request timed out.
10 75 ms 66 ms 72 ms 54.239.46.8
11 65 ms 64 ms 65 ms 54.239.42.188
12 * * * Request timed out.
13 83 ms 71 ms 102 ms 54.239.108.184
14 * * * Request timed out.
15 77 ms 76 ms 75 ms 52.93.27.3
16 71 ms 67 ms 64 ms 52.93.25.106
17 66 ms 66 ms 65 ms 52.93.27.199
18 64 ms 64 ms 64 ms 205.251.244.67
19 * * * Request timed out.
20 * * * 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.
