Regarding Reports on Recent Connection Problems with the NA Data Center

[drebbe]

Comcast, 11PM EST. NTT Hops like usual since server move.

>pathping 204.2.229.10

Tracing route to 204.2.229.10 over a maximum of 30 hops

0 DESKTOP-M42FG6C [192.168.88.233]
1 192.168.88.1
2 ***********
3 te4-2-ur02.shelby.mi.michigan.comcast.net [68.86.121.157]
4 96.108.21.142
5 be-8-ar02.pontiac.mi.michigan.comcast.net [162.151.127.181]
6 be-33668-cr02.350ecermak.il.ibone.comcast.net [68.86.90.45]
7 be-10577-pe03.350ecermak.il.ibone.comcast.net [68.86.86.2]
8 ae-26.a02.chcgil09.us.bb.gin.ntt.net [129.250.66.65]
9 ae-4.r08.chcgil09.us.bb.gin.ntt.net [129.250.4.157]
10 ae-0.r21.chcgil09.us.bb.gin.ntt.net [129.250.2.205]
11 ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
12 ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
13 ae-1.a00.snjsca04.us.bb.gin.ntt.net [129.250.2.228]
14 xe-0-0-42-1.a00.snjsca04.us.ce.gin.ntt.net [129.250.195.42]
15 * 204.2.229.242
16 204.2.229.10

Computing statistics for 400 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 DESKTOP-M42FG6C [192.168.88.233]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.88.1
0/ 100 = 0% |
2 11ms 0/ 100 = 0% 0/ 100 = 0% ***********
0/ 100 = 0% |
3 12ms 0/ 100 = 0% 0/ 100 = 0% te4-2-ur02.shelby.mi.michigan.comcast.net [68.86.121.157]
0/ 100 = 0% |
4 13ms 0/ 100 = 0% 0/ 100 = 0% 96.108.21.142
0/ 100 = 0% |
5 11ms 0/ 100 = 0% 0/ 100 = 0% be-8-ar02.pontiac.mi.michigan.comcast.net [162.151.127.181]
0/ 100 = 0% |
6 18ms 0/ 100 = 0% 0/ 100 = 0% be-33668-cr02.350ecermak.il.ibone.comcast.net [68.86.90.45]
0/ 100 = 0% |
7 17ms 0/ 100 = 0% 0/ 100 = 0% be-10577-pe03.350ecermak.il.ibone.comcast.net [68.86.86.2]
0/ 100 = 0% |
8 20ms 0/ 100 = 0% 0/ 100 = 0% ae-26.a02.chcgil09.us.bb.gin.ntt.net [129.250.66.65]
0/ 100 = 0% |
9 18ms 0/ 100 = 0% 0/ 100 = 0% ae-4.r08.chcgil09.us.bb.gin.ntt.net [129.250.4.157]
0/ 100 = 0% |
10 20ms 0/ 100 = 0% 0/ 100 = 0% ae-0.r21.chcgil09.us.bb.gin.ntt.net [129.250.2.205]
1/ 100 = 1% |
11 184ms 6/ 100 = 6% 5/ 100 = 5% ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
0/ 100 = 0% |
12 185ms 4/ 100 = 4% 3/ 100 = 3% ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
0/ 100 = 0% |
13 188ms 3/ 100 = 3% 2/ 100 = 2% ae-1.a00.snjsca04.us.bb.gin.ntt.net [129.250.2.228]
0/ 100 = 0% |
14 188ms 2/ 100 = 2% 1/ 100 = 1% xe-0-0-42-1.a00.snjsca04.us.ce.gin.ntt.net [129.250.195.42]
0/ 100 = 0% |
15 187ms 1/ 100 = 1% 0/ 100 = 0% 204.2.229.242
3/ 100 = 3% |
16 186ms 4/ 100 = 4% 0/ 100 = 0% 204.2.229.10

Trace complete.

[XenoCranel]

I have not experienced much lag in the last two nights. Anyone else?

[MidnightWonko]

So after seeing someone else using WinMTR, I decided to check it out as well.



I took this over the course of only just a few minutes around 5:55pm Pacific. Notably, it appears that the vast majority of my packets lost are at 204.2.229.242.

EDIT:



The same, except I'd been running it nonstop for about 30 minutes since around 5:55pm Pacific.

I dunno if that helps or not.

EDIT 2: Now at nearly 7:40pm, there's a 12% loss at hop 9, 18% loss at hop 13, and 10% loss at the last hop. That's very discouraging.

[Ladon]

So after seeing someone else using WinMTR, I decided to check it out as well.



I took this over the course of only just a few minutes around 5:55pm Pacific. Notably, it appears that the vast majority of my packets lost are at 204.2.229.242.

EDIT:



The same, except I'd been running it nonstop for about 30 minutes since around 5:55pm Pacific.

I dunno if that helps or not.

EDIT 2: Now at nearly 7:40pm, there's a 12% loss at hop 9, 18% loss at hop 13, and 10% loss at the last hop. That's very discouraging.

Just curious if you are actually seeing major issues in game. One of my static members sees a similar output as you and does not have issues in game. I suspect 204.2.229.242 is an inside edge device and there is likely a stateful firewall in front that is configured to drop ICMP packets under certain conditions, so issues starting here during a trace may not necessarily indicate an actual issue. Your packet loss numbers are pretty clean otherwise as you shouldn't notice any major issues with a 1-3% loss over the 2000 packets you had sent.

[MidnightWonko]

Just curious if you are actually seeing major issues in game. One of my static members sees a similar output as you and does not have issues in game. I suspect 204.2.229.242 is an inside edge device and there is likely a stateful firewall in front that is configured to drop ICMP packets under certain conditions, so issues starting here during a trace may not necessarily indicate an actual issue. Your packet loss numbers are pretty clean otherwise as you shouldn't notice any major issues with a 1-3% loss over the 2000 packets you had sent.

Hard to say, really; with the hideously bad packet loss rate recently, my motivation to play this game has tanked pretty hard. I'll try testing a bit more later on. Hopefully, you're right on that (and I wouldn't doubt it if it's just that one node).

[drebbe]

Just curious if you are actually seeing major issues in game. One of my static members sees a similar output as you and does not have issues in game. I suspect 204.2.229.242 is an inside edge device and there is likely a stateful firewall in front that is configured to drop ICMP packets under certain conditions, so issues starting here during a trace may not necessarily indicate an actual issue. Your packet loss numbers are pretty clean otherwise as you shouldn't notice any major issues with a 1-3% loss over the 2000 packets you had sent.

some people are more sensitive to the rubber banding and lag issue then others. I can confirm when I get rubber banding / lag the packet loss always there and the latency does tend to increase a bit. I'm probably more sensitive to it due to having 20-30ms latency before the server move so I know what a "perfect" connection feels like.

[Callinon]

I have not experienced much lag in the last two nights. Anyone else?

I'm at 200ms latency right now.