Status as far as blizzard is concerned is, not their internet, not their issue. You’d think Microsoft had more pull, but I guess not these days.
My only problem with the blizzard explanation is they only let you pathping west coast or central, and both find blizzards server six-blizzardonline-net at 206"period"82"period"82"period"122, its after that they diffe. Central dies right there, west makes it several more hops. So it resolves correctly, and its seeming more like blizzard is not handling the traffic correctly from this ISP now, rather than some transport path is wrecking it.
from this website - us"period"battle"period"net/support/en/article/7871
Central
C:\Users\Tech9>pathping 24"period"105"period"62"period"129
Tracing route to 24"period"105"period"62"period"129 over a maximum of 30 hops
0 DESKTOP-JE1FG14"period"lan [192"period"168"period"86"period"29]
1 192"period"168"period"86"period"1
2 24-113-64-1"period"wavecable"period"com [24"period"113"period"64"period"1]
3 agg1-pohe-a-be150"period"bb"period"as11404"period"net [174"period"127"period"182"period"18]
4 be6"period"cr1-pohe-b"period"bb"period"as11404"period"net [174"period"127"period"148"period"177]
5 be4"period"cr2-sea-b"period"bb"period"as11404"period"net [174"period"127"period"137"period"16]
6 six"period"blizzardonline"period"net [206"period"81"period"81"period"122]
7 * * *
Computing statistics for 150 seconds"period"“period”“period”
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 DESKTOP-JE1FG14"period"lan [192"period"168"period"86"period"29]
0/ 100 = 0% |
1 2ms 0/ 100 = 0% 0/ 100 = 0% 192"period"168"period"86"period"1
0/ 100 = 0% |
2 31ms 0/ 100 = 0% 0/ 100 = 0% 24-113-64-1"period"wavecable"period"com [24"period"113"period"64"period"1]
0/ 100 = 0% |
3 27ms 0/ 100 = 0% 0/ 100 = 0% agg1-pohe-a-be150"period"bb"period"as11404"period"net [174"period"127"period"182"period"18]
0/ 100 = 0% |
4 30ms 0/ 100 = 0% 0/ 100 = 0% be6"period"cr1-pohe-b"period"bb"period"as11404"period"net [174"period"127"period"148"period"177]
0/ 100 = 0% |
5 34ms 0/ 100 = 0% 0/ 100 = 0% be4"period"cr2-sea-b"period"bb"period"as11404"period"net [174"period"127"period"137"period"16]
100/ 100 =100% |
6 — 100/ 100 =100% 0/ 100 = 0% six"period"blizzardonline"period"net [206"period"81"period"81"period"122]
Trace complete.
=====================================================================
West
C:\Users\Tech9>pathping 137"period"221"period"105"period"2
Tracing route to 137"period"221"period"105"period"2 over a maximum of 30 hops
0 DESKTOP-JE1FG14"period"lan [192"period"168"period"86"period"29]
1 192"period"168"period"86"period"1
2 24-113-64-1"period"wavecable"period"com [24"period"113"period"64"period"1]
3 174"period"127"period"183"period"70
4 be4"period"cr2-sea-b"period"bb"period"as11404"period"net [174"period"127"period"137"period"16]
5 six"period"blizzardonline"period"net [206"period"81"period"81"period"122]
6 ae1-br01-eqse2"period"as57976"period"net [137"period"221"period"73"period"33]
7 xe-0-0-0-1-br01-eqsv5"period"as57976"period"net [137"period"221"period"65"period"40]
8 et-0-0-29-br02-eqsv5"period"as57976"period"net [137"period"221"period"65"period"117]
9 xe-0-0-1-1-br02-eqla1"period"as57976"period"net [137"period"221"period"65"period"6]
10 et-0-0-29-br01-eqla1"period"as57976"period"net [137"period"221"period"65"period"0]
11 * * *
Computing statistics for 250 seconds"period"“period”“period”
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 DESKTOP-JE1FG14"period"lan [192"period"168"period"86"period"29]
0/ 100 = 0% |
1 1ms 0/ 100 = 0% 0/ 100 = 0% 192"period"168"period"86"period"1
0/ 100 = 0% |
2 30ms 0/ 100 = 0% 0/ 100 = 0% 24-113-64-1"period"wavecable"period"com [24"period"113"period"64"period"1]
0/ 100 = 0% |
3 27ms 0/ 100 = 0% 0/ 100 = 0% 174"period"127"period"183"period"70
0/ 100 = 0% |
4 31ms 0/ 100 = 0% 0/ 100 = 0% be4"period"cr2-sea-b"period"bb"period"as11404"period"net [174"period"127"period"137"period"16]
0/ 100 = 0% |
5 — 100/ 100 =100% 100/ 100 =100% six"period"blizzardonline"period"net [206"period"81"period"81"period"122]
0/ 100 = 0% |
6 59ms 0/ 100 = 0% 0/ 100 = 0% ae1-br01-eqse2"period"as57976"period"net [137"period"221"period"73"period"33]
0/ 100 = 0% |
7 56ms 0/ 100 = 0% 0/ 100 = 0% xe-0-0-0-1-br01-eqsv5"period"as57976"period"net [137"period"221"period"65"period"40]
0/ 100 = 0% |
8 50ms 0/ 100 = 0% 0/ 100 = 0% et-0-0-29-br02-eqsv5"period"as57976"period"net [137"period"221"period"65"period"117]
0/ 100 = 0% |
9 61ms 0/ 100 = 0% 0/ 100 = 0% xe-0-0-1-1-br02-eqla1"period"as57976"period"net [137"period"221"period"65"period"6]
0/ 100 = 0% |
10 225ms 0/ 100 = 0% 0/ 100 = 0% et-0-0-29-br01-eqla1"period"as57976"period"net [137"period"221"period"65"period"0]
Trace complete.
i dunno, that looks more like Blizzard needs to check something on their end. You can’t ping their server either way, but one way goes past their first server and one does not, none of them are losing packets to that server though and it resolves correctly. Granted i do not work for blizzard, or their server hosts, or Astound, but something seems off.
Note these forums wont let me post a URL even though I just pasted text from a tool and their OWN diagnostic website. If you need something from here, copy all, paste into notepad, and set “period” to be replaced by .
You can’t fix stupid but you can work around it sometimes…