For those wondering, we were doing fine on patch day. Though, now that we're coming on the weekend, we're back to our localized problems with NTT.
1 3 ms 3 ms 3 ms
2 * * * Request timed out.
3 11 ms 11 ms 9 ms lag-61.dtr01athnga.netops.charter.com
4 10 ms 11 ms 9 ms lag-19.hcr01athogakn.netops.charter.com
5 13 ms 12 ms 13 ms lag-204.crr02sghlga.netops.charter.com
6 13 ms 14 ms 13 ms lag-20.rcr01sghlgaao.netops.charter.com
7 13 ms 13 ms 36 ms lag-403-10.atlngamq46w-bcr00.netops.charter.com
8 14 ms 17 ms 12 ms lag-806.bpr03atlngamq.netops.charter.com
9 14 ms 17 ms 15 ms atl-b24-link.ip.twelve99.net
10 16 ms 15 ms 15 ms ae-2.a03.atlnga05.us.bb.gin.ntt.net
11 35 ms 27 ms 29 ms ae-2.r26.atlnga05.us.bb.gin.ntt.net
12 30 ms 31 ms 29 ms ae-4.r27.asbnva02.us.bb.gin.ntt.net
13 30 ms 31 ms 32 ms ae-0.r26.asbnva02.us.bb.gin.ntt.net
14 108 ms 79 ms 89 ms ae-10.r26.snjsca04.us.bb.gin.ntt.net
15 * 83 ms 97 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net
16 83 ms * * xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net
17 * * * Request timed out.
18 83 ms 82 ms 83 ms
I'm not sure what's going on here because it seems like there's a major problem with Sacramento again, now with it timing out. I even checked ARRStatus and the ping is relatively bad between all data centers, being 100+ ms. And for the moderators, I am connected directly to my modem and did a few tracert commands to make sure it wasn't just a blip since I was also lagging hard during Enuo(making it almost unplayable in an EX Raid Setting).
While I understand the previous thread for this was moved to Closed Concerns, I think this should stay as an ongoing so we can report.
Continue reading...
1 3 ms 3 ms 3 ms
2 * * * Request timed out.
3 11 ms 11 ms 9 ms lag-61.dtr01athnga.netops.charter.com
4 10 ms 11 ms 9 ms lag-19.hcr01athogakn.netops.charter.com
5 13 ms 12 ms 13 ms lag-204.crr02sghlga.netops.charter.com
6 13 ms 14 ms 13 ms lag-20.rcr01sghlgaao.netops.charter.com
7 13 ms 13 ms 36 ms lag-403-10.atlngamq46w-bcr00.netops.charter.com
8 14 ms 17 ms 12 ms lag-806.bpr03atlngamq.netops.charter.com
9 14 ms 17 ms 15 ms atl-b24-link.ip.twelve99.net
10 16 ms 15 ms 15 ms ae-2.a03.atlnga05.us.bb.gin.ntt.net
11 35 ms 27 ms 29 ms ae-2.r26.atlnga05.us.bb.gin.ntt.net
12 30 ms 31 ms 29 ms ae-4.r27.asbnva02.us.bb.gin.ntt.net
13 30 ms 31 ms 32 ms ae-0.r26.asbnva02.us.bb.gin.ntt.net
14 108 ms 79 ms 89 ms ae-10.r26.snjsca04.us.bb.gin.ntt.net
15 * 83 ms 97 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net
16 83 ms * * xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net
17 * * * Request timed out.
18 83 ms 82 ms 83 ms
I'm not sure what's going on here because it seems like there's a major problem with Sacramento again, now with it timing out. I even checked ARRStatus and the ping is relatively bad between all data centers, being 100+ ms. And for the moderators, I am connected directly to my modem and did a few tracert commands to make sure it wasn't just a blip since I was also lagging hard during Enuo(making it almost unplayable in an EX Raid Setting).
While I understand the previous thread for this was moved to Closed Concerns, I think this should stay as an ongoing so we can report.
Continue reading...