Mabrooke frequent disconnects

Technical Support
1

TRACEROUTE:
traceroute to 180.190.50.26 (180.190.50.26), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.269 ms 0.269 ms 0.271 ms Blizzard(24.105.18.3) 0.514 ms 0.648 ms 0.775 ms
3 137.221.105.16 (137.221.105.16) 0.562 ms 0.575 ms 0.714 ms
4 137.221.66.18 (137.221.66.18) 0.644 ms 0.647 ms 0.648 ms
5 137.221.83.66 (137.221.83.66) 30.195 ms 30.217 ms 30.232 ms
6 137.221.65.68 (137.221.65.68) 30.037 ms 30.130 ms 30.117 ms
7 137.221.65.1 (137.221.65.1) 30.091 ms 30.101 ms 30.392 ms
8 137.221.65.7 (137.221.65.7) 30.529 ms 30.527 ms 30.527 ms
9 137.221.65.116 (137.221.65.116) 30.464 ms 30.485 ms 30.489 ms
10 137.221.65.41 (137.221.65.41) 30.282 ms 30.168 ms 30.108 ms
11 137.221.73.32 (137.221.73.32) 30.196 ms 30.470 ms 30.366 ms
12 six.globe.com.ph (206.81.80.208) 29.880 ms 29.793 ms 30.043 ms
13 120.28.10.13 (120.28.10.13) 155.607 ms 155.744 ms 155.891 ms
14 * * *
15 120.28.190.2 (120.28.190.2) 158.855 ms 158.788 ms 158.789 ms

29/05/2019 15:25:08 UTC

PING:
PING 180.190.50.26 (180.190.50.26) 56(84) bytes of data.

— 180.190.50.26 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2999ms

29/05/2019 15:25:08 UTC

MTR:
Start: Wed May 29 15:25:08 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.3 0.2 0.4 0.0 Blizzard 0.0% 10 0.7 0.7 0.5 1.0 0.0
3.|-- 137.221.105.16 0.0% 10 0.8 0.7 0.6 0.8 0.0
4.|-- 137.221.66.18 0.0% 10 4.1 1.0 0.5 4.1 1.1
5.|-- 137.221.83.66 0.0% 10 81.6 35.3 30.1 81.6 16.3
6.|-- 137.221.65.68 0.0% 10 30.3 31.4 30.1 42.6 3.9
7.|-- 137.221.65.1 0.0% 10 30.4 36.4 30.1 75.7 14.7
8.|-- 137.221.65.7 0.0% 10 30.3 32.6 30.1 49.9 6.2
9.|-- 137.221.65.116 0.0% 10 30.4 31.7 30.1 44.6 4.5
10.|-- 137.221.65.41 0.0% 10 30.4 30.4 30.1 31.2 0.0
11.|-- 137.221.73.32 0.0% 10 30.2 32.3 30.2 49.8 6.1
12.|-- six.globe.com.ph 0.0% 10 29.8 30.0 29.8 30.1 0.0
13.|-- 120.28.10.13 60.0% 10 155.7 155.7 155.7 155.8 0.0
14.|-- 120.28.190.1 90.0% 10 158.0 158.0 158.0 158.0 0.0
15.|-- 120.28.190.2 0.0% 10 158.8 159.1 158.8 161.0 0.5
16.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

29/05/2019 15:25:08 UTC

2

Read about 30 tickets on this. Did all the “troubleshooting” that was suggested. Did not work. Restarted computer, modem, updated Windows and Drivers, etc. I paid for this game and I can’t play it. Can I just cancel and you return my money? This is a breach of contract. I paid for it and I should be able to play. If I can’t play, then just return my money.

1 Like
3

Hey there,

Going over the Looking Glass results, the connection time seems very good. It looks like local security settings might be blocking part of the test, so it may show packet loss but that is not real packet loss.

I’m not seeing reports from other users on the same ISP, and the overall connection speeds and packet counts from the ISP both look good. So I’m wondering if this issue is more local.

Would it be possible to reply back with a winMTR test?

4

Yes I did that. Diablo, Hearthstone, and Starcraft all working well except Overwatch. Do you think its’ still my/our network problem? Do want to admit now its’ the OW servers / problem?

5

That’s hard to assess without the correct network test. You should report back with a WinMTR.

WinMTR instructions (click to expand/collapse)

Follow the support documentation for WinMTR. If you’re unable to get into a game for the IP address, then use an IP from the table provided on that page that matches your region. Run the test until you encounter the issue again, or for at least 10 minutes.

Share your results in a reply:

  1. Click the “Copy Text to clipboard” button after you’ve finished the test per the instructions.
  2. Paste the text in a reply, then highlight the pasted text and click </> on the post editor.
  3. Break any links by adding a space before .com, .net, etc.
6

Did that already. I already mentioned that.

7

That was a looking glass test, which is a snapshot of the connection, instead of an average over time, which is what a WinMTR will show.