Visitor
•
1 Message
Issue with backend routing causing unstable pings in games - Path of Exile 2
When attempting to identify a stuttering issue within the game, I started to look into the network route that is being used to connect to the Path of Exile servers. This is happening when attempting to connect to any of their servers throughout the US.
When connecting to their CA server - 64.87.41.97 this is the tracert that the network path takes.
Tracing route to 64.87.41.97 over a maximum of 30 hops
1 1 ms <1 ms <1 ms 10.0.0.1
2 8 ms 8 ms 9 ms 96.120.102.101
3 13 ms 10 ms 12 ms po-310-1257-rur201.burien.wa.seattle.comcast.net [24.153.84.69]
4 11 ms 10 ms 10 ms po-200-xar01.burien.wa.seattle.comcast.net [69.139.162.49]
5 10 ms 9 ms 9 ms be-302-arsc1.burien.wa.seattle.comcast.net [24.124.128.110]
6 14 ms 12 ms 12 ms be-36111-cs01.portland.or.ibone.comcast.net [68.86.94.129]
7 17 ms 15 ms 15 ms be-2213-pe13.seattle.wa.ibone.comcast.net [96.110.44.86]
8 * * * Request timed out.
9 19 ms 17 ms 15 ms 108.162.243.47
10 16 ms 15 ms * 172.71.149.25
11 16 ms 19 ms * 172.71.149.75
12 16 ms 16 ms 19 ms 172.71.149.146
13 * * * Request timed out.
14 * * * Request timed out.
15 32 ms 31 ms * 38.120.133.39
16 * * * Request timed out.
17 32 ms 32 ms 34 ms 64.87.41.97
Note that it goes from Burien WA, to Portland OR, then Back to Seattle WA.
When connecting to their Texas Server - 64.87.51.92 this is the tracert that the network path takes.
Tracing route to 64.87.51.92 over a maximum of 30 hops
1 1 ms 1 ms <1 ms 10.0.0.1
2 9 ms 8 ms 8 ms 96.120.102.101
3 9 ms 8 ms 10 ms po-310-1258-rur202.burien.wa.seattle.comcast.net [24.153.84.85]
4 9 ms 8 ms 9 ms po-2-rur201.burien.wa.seattle.comcast.net [69.139.162.105]
5 9 ms 8 ms 10 ms po-200-xar01.burien.wa.seattle.comcast.net [69.139.162.49]
6 9 ms 10 ms 10 ms be-302-arsc1.burien.wa.seattle.comcast.net [24.124.128.110]
7 12 ms 13 ms 13 ms be-36121-cs02.portland.or.ibone.comcast.net [68.86.94.133]
8 20 ms 18 ms * be-2413-pe13.seattle.wa.ibone.comcast.net [96.110.44.94]
9 * * * Request timed out.
10 17 ms 20 ms * 108.162.243.19
11 15 ms 15 ms 16 ms 108.162.244.17
12 19 ms 16 ms 18 ms 162.159.120.35
13 16 ms 14 ms * 108.162.244.89
14 * * * Request timed out.
15 61 ms 72 ms 59 ms 173.233.144.248
16 73 ms 71 ms 60 ms 38.142.84.82
17 59 ms 59 ms 73 ms 209.192.208.69
18 61 ms 61 ms 59 ms 64.87.51.92
When connecting to their Washington DC server - 64.87.52.143
Tracing route to 64.87.52.143 over a maximum of 30 hops
1 1 ms <1 ms <1 ms 10.0.0.1
2 10 ms 21 ms 8 ms 96.120.102.101
3 9 ms 10 ms 13 ms po-310-1257-rur201.burien.wa.seattle.comcast.net [24.153.84.69]
4 9 ms 12 ms 10 ms po-200-xar01.burien.wa.seattle.comcast.net [69.139.162.49]
5 12 ms 10 ms 9 ms be-302-arsc1.burien.wa.seattle.comcast.net [24.124.128.110]
6 12 ms 13 ms 12 ms be-36141-cs04.portland.or.ibone.comcast.net [68.86.94.141]
7 16 ms 18 ms 17 ms be-2413-pe13.seattle.wa.ibone.comcast.net [96.110.44.94]
8 * * * Request timed out.
9 16 ms 16 ms 17 ms 108.162.243.35
10 17 ms 16 ms 16 ms 172.71.145.58
11 17 ms 15 ms 17 ms 172.71.145.212
12 22 ms 15 ms 14 ms 172.71.145.105
13 * * * Request timed out.
14 85 ms 98 ms 84 ms 209.192.153.246
15 97 ms 88 ms * 38.88.214.47
16 * * * Request timed out.
17 97 ms 102 ms 85 ms 64.87.52.143
The routing through portland is occuring no matter where I connect to. It is adding delays to the network and there is no reason to add the 300+ mile round trip to every network packet.
This is all on Xfinity's backend routing. Please correct this.
No Responses!