100% Packet Loss

Forums › 2degrees (including Slingshot, Orcon, Flip, Stuff Fibre, MyRepublic, 2talk and Vocus) › 100% Packet Loss

Plenon

7 posts

Wannabe Geek

#196289 25-May-2016 21:20

Hey guys,

I've just purchased Overwatch and have not been able to get a connection to the server. Upon further checking, it seems that I am having a packet loss at the 3rd hop. I have port-forwarded the router (Fritzbox 7490), disabled my firewall + antivirus (Windows Defender + Firewall), flushed the DNS, power-cycled and factory-reset the router; but the issue still persists. I've contacted Blizzard but they've told me to check with the ISP. 2degrees claimed that they have no issue with the IP for overwatch so I am kinda tearing my head out on what I can do.

I've included the MTR and path ping information to better showcase the situation:

Tracing route to 37.244.0.3 over a maximum of 30 hops

0 192.168.178.35
1 192.168.178.1
2 111.69.35.57
3 * * *
Computing statistics for 50 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 192.168.178.35
3/ 100 = 3% |
1 53ms 3/ 100 = 3% 0/ 100 = 0% 192.168.178.1
38/ 100 = 38% |
2 10ms 41/ 100 = 41% 0/ 100 = 0% 111.69.35.57

Trace complete.

Would be great if anyone here has an answer.

Thanks!

Talkiet

4819 posts

Uber Geek
+1 received by user: 3934

Trusted

#1559713 25-May-2016 21:27

The 3rd hop isn't responding, but the 4th and etc hops are... This is an entirely normal thing to happen and is very unlikely to be related to your problem.

Sorry I have no idea about what Overwatch is or how 2D have built their network.

Cheers - N

Please note all comments are from my own brain and don't necessarily represent the position or opinions of my employer, previous employers, colleagues, friends or pets.

backfiah

227 posts

Master Geek
+1 received by user: 104

#1559716 25-May-2016 21:31

Not all routers will choose to reply to ICMP ping requests (which is what traceroute is also using), but this doesn't mean they aren't forwarding the rest of your IP traffic successfully. The ping loss rate to the destination is the thing you're concerned with in this case (and it seems fine, at almost 0%).

Jiriteach

1139 posts

Uber Geek
+1 received by user: 373

ID Verified

Trusted

Lifetime subscriber

#1559718 25-May-2016 21:35

Your problem is nothing to do with the packet loss on the 3rd hop and doesn't look to be a problem with the 2degrees network either. I can get to that server OK. I am on 2degrees UFB in Wellington.

GRINDOR:~ jxs$ traceroute 37.244.0.3
traceroute to 37.244.0.3 (37.244.0.3), 64 hops max, 52 byte packets

1 fritz.box (192.168.178.1) 130.391 ms 3.755 ms 2.195 ms
2 69.7.69.111.static.snap.net.nz (111.69.7.69) 3.960 ms 3.797 ms 3.962 ms
3 * * *
4 two-degrees.bar1.sanfrancisco1.level3.net (4.16.192.146) 138.508 ms 137.566 ms 137.764 ms
5 xe-4-2-0.bar1.sanfrancisco1.level3.net (4.16.192.145) 138.996 ms 139.113 ms 140.165 ms
6 ae-0-11.bar2.sanfrancisco1.level3.net (4.69.140.146) 139.148 ms 140.289 ms 140.063 ms
7 * * *
8 blizzard-en.bar2.sanfrancisco1.level3.net (4.16.82.162) 142.640 ms !X * 14

Maybe its intermittent issues with the Blizzard servers?

-- opinions expressed by me are solely my own. ie - personal

hyperman

418 posts

Ultimate Geek
+1 received by user: 101

#1559724 25-May-2016 21:50

Tracing route to 37.244.0.3 over a maximum of 30 hops

1    <1 ms    <1 ms    <1 ms 192.168.0.254
2   104 ms    15 ms    15 ms default-rdns.callplus.co.nz [60.234.8.54]
3    17 ms    16 ms    16 ms pts-n.cpcak4-r1.tranzpeer.net [101.98.5.20]
4    17 ms    17 ms    17 ms pts-s.cpcak4-r1.tranzpeer.net [101.98.5.21]
5     *        *        *     Request timed out.
6     *        *        *     Request timed out.
7     *        *        *     Request timed out.
8     *        *        *     Request timed out.
9     *        *        *     Request timed out.
10   145 ms   145 ms   145 ms eqix-ix-la1.blizzard.com [206.223.123.52]
11   153 ms   154 ms   153 ms 37.244.0.3

Trace complete.

as said before not all routers respond to ICMP so that is not your issue

The views expressed by me are not necessarily those of my employer