Rubber banding in game/on peak packet loss

Forums › 2degrees (including Slingshot, Orcon, Flip, Stuff Fibre, MyRepublic, 2talk and Vocus) › Rubber banding in game/on peak packet loss

1 | ... | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14

455 posts

Ultimate Geek

#1126764 11-Sep-2014 20:34

FireEngine:
kiwikiwi:
disarmyou: I dont know if anyone else is getting it tonight but im getting massive lag spikes.

NA league is pretty shaky tonight actually
Orcon VDSL

Sorry mate but the big jumps here are occurring off our network.

Ahh what a shame. Second tracert on the 2nd hop on euba was kinda abnormally high but if its something off your network then i'll just put it towards bad time since mostly this hasn't been as persistent nor problematic as everyone else is experiencing.

You can also follow me on twitter here @kiwifortw I do twitch streams every now and then at twitch.tv/kiwiforthewin :)

HTTP 404 Sarcasm not found.

FireEngine

1223 posts

Uber Geek

Trusted

#1126766 11-Sep-2014 20:36

disarmyou: Sorry for the delay:

Tracing route to 216.133.234.62 over a maximum of 30 hops

1 1 ms <1 ms 4 ms BoB.Orcon [192.168.0.20]
2 12 ms 19 ms 13 ms 121-99-252-1.bng1.nct.orcon.net.nz [121.99.252.1]
3 9 ms 11 ms 11 ms xe-2-2-0.cre1.nct.orcon.net.nz [121.98.9.141]
4 18 ms 13 ms 9 ms 121.99.12.0
5 136 ms 135 ms 135 ms 38.122.92.162
6 138 ms 137 ms 135 ms te7-4.ccr01.sjc05.atlas.cogentco.com [38.122.92.161]
7 136 ms 135 ms 135 ms te0-4-0-5.ccr22.sjc01.atlas.cogentco.com [154.54.6.205]
8 174 ms 176 ms 174 ms be2161.ccr22.lax01.atlas.cogentco.com [154.54.27.169]
9 148 ms 150 ms 170 ms te8-1.mag01.lax01.atlas.cogentco.com [154.54.28.146]
10 150 ms 147 ms 150 ms 154.24.22.126
11 142 ms 142 ms 143 ms 38.88.244.6
12 141 ms 146 ms 141 ms border2.po2-40g-bbnet2.lax010.pnap.net [216.52.255.93]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Same here, the jump in latency is off the Orcon network.

Regards FireEngine

FireEngine

1223 posts

Uber Geek

Trusted

#1126771 11-Sep-2014 20:44

kiwikiwi: Ahh what a shame. Second tracert on the 2nd hop on euba was kinda abnormally high but if its something off your network then i'll just put it towards bad time since mostly this hasn't been as persistent nor problematic as everyone else is experiencing.

No problem, it is occurring at the same point as for the other user above, I'll have the team look into it with the upstream.

Regards FireEngine

FireEngine

1223 posts

Uber Geek

Trusted

#1126778 11-Sep-2014 20:56

FireEngine:
kiwikiwi: Ahh what a shame. Second tracert on the 2nd hop on euba was kinda abnormally high but if its something off your network then i'll just put it towards bad time since mostly this hasn't been as persistent nor problematic as everyone else is experiencing.

No problem, it is occurring at the same point as for the other user above, I'll have the team look into it with the upstream.

Found it, we had a big spike in traffic to the US, between approx 7pm and 7:20pm, looks like a transient DDOS against a single customer.

Can you retest the tracert?

Regards FireEngine

Jedateach

25 posts

Geek

#1126779 11-Sep-2014 20:57

Twitch cutting in/out now and browsing internationally (eg facebook) has slowed to a crawl, still speedtest/pingtest fine?

Diablo 3 rubber banding, latency from 300-1100 with spikes. (tested quickly just now)

Dota latency to Aus servers a bit higher than usual, 120ish. (from spectating a couple of games)

Americas (battlenet)
C:\Users\Jon>pathping 12.129.209.68

Tracing route to 12.129.209.68 over a maximum of 30 hops

0 Jedateach.Home [192.168.20.2]
1 192.168.20.1
2 121-99-252-1.bng1.nct.orcon.net.nz [121.99.252.1]
3 xe-2-2-0.cre1.nct.orcon.net.nz [121.98.9.141]
4 121.99.12.0
5 xe-5-0-0.bar1.SanFrancisco1.Level3.net [4.53.132.217]
6 ae-0-11.bar2.SanFrancisco1.Level3.net [4.69.140.146]
7 * * *
Computing statistics for 150 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Jedateach.Home [192.168.20.2]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.20.1
0/ 100 = 0% |
2 18ms 0/ 100 = 0% 0/ 100 = 0% 121-99-252-1.bng1.nct.orcon.net.nz
[121.99.252.1]
0/ 100 = 0% |
3 19ms 0/ 100 = 0% 0/ 100 = 0% xe-2-2-0.cre1.nct.orcon.net.nz [12
1.98.9.141]
0/ 100 = 0% |
4 22ms 0/ 100 = 0% 0/ 100 = 0% 121.99.12.0
0/ 100 = 0% |
5 174ms 0/ 100 = 0% 0/ 100 = 0% xe-5-0-0.bar1.SanFrancisco1.Level3
.net [4.53.132.217]
0/ 100 = 0% |
6 148ms 0/ 100 = 0% 0/ 100 = 0% ae-0-11.bar2.SanFrancisco1.Level3.
net [4.69.140.146]

Trace complete.

C:\Users\Jon>

C:\Users\Jon>tracert 12.129.209.68

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 <1 ms 1 ms <1 ms 192.168.20.1
2 35 ms 19 ms 25 ms 121-99-252-1.bng1.nct.orcon.net.nz [121.99.252.1
]
3 18 ms 18 ms 18 ms xe-2-2-0.cre1.nct.orcon.net.nz [121.98.9.141]
4 26 ms 25 ms 26 ms 121.99.12.0
5 171 ms 171 ms 171 ms xe-5-0-0.bar1.SanFrancisco1.Level3.net [4.53.132
.217]
6 144 ms 146 ms 144 ms ae-0-11.bar2.SanFrancisco1.Level3.net [4.69.140.
146]
7 * * * Request timed out.
8 * * * Request timed out.
9 147 ms 145 ms 145 ms ae-1-60.edge2.SanJose1.Level3.net [4.69.152.15]

10 151 ms 150 ms 151 ms 192.205.32.209
11 154 ms 154 ms 151 ms cr1.sffca.ip.att.net [12.122.114.6]
12 154 ms 155 ms 155 ms cr1.la2ca.ip.att.net [12.122.3.122]
13 152 ms 151 ms 151 ms gar5.lsrca.ip.att.net [12.122.85.33]
14 152 ms 152 ms 152 ms 12-122-254-226.attens.net [12.122.254.226]
15 151 ms 151 ms 151 ms 206.16.68.42
16 152 ms 151 ms 152 ms paxonix-placeholder.lax1.attens.net [12.129.248.
118]
17 153 ms 152 ms 152 ms 12.129.209.68

Trace complete.

C:\Users\Jon>

Australia

C:\Users\Jon>tracert 103.4.115.248

Tracing route to 103.4.115.248 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.20.1
2 41 ms 27 ms 30 ms 121-99-252-1.bng1.nct.orcon.net.nz [121.99.252.1
]
3 21 ms 19 ms 18 ms xe-2-2-0.cre1.nct.orcon.net.nz [121.98.9.141]
4 18 ms 19 ms 18 ms ge-0-3-0-0.cre1.sky.orcon.net.nz [121.98.9.10]
5 19 ms 21 ms 19 ms vocus1.ape.nzix.net [192.203.154.123]
6 42 ms 44 ms 51 ms ten-0-7-0-2.cor01.alb01.akl.VOCUS.net.nz [114.31
.202.68]
7 43 ms 41 ms 44 ms ten-0-3-0-2.cor03.syd03.nsw.VOCUS.net.au [114.31
.202.85]
8 48 ms 42 ms 42 ms ten-1-0-0.bdr03.syd04.nsw.VOCUS.net.au [175.45.7
2.73]
9 42 ms 44 ms 45 ms as17819.cust.bdr03.syd04.nsw.VOCUS.net.au [175.4
5.73.194]
10 43 ms 42 ms 42 ms 27.111.251.106
11 42 ms 43 ms 41 ms 103.4.115.248

Trace complete.

C:\Users\Jon>pathping 103.4.115.248

Tracing route to 103.4.115.248 over a maximum of 30 hops

0 Jedateach.Home [192.168.20.2]
1 192.168.20.1
2 121-99-252-1.bng1.nct.orcon.net.nz [121.99.252.1]
3 xe-2-2-0.cre1.nct.orcon.net.nz [121.98.9.141]
4 ge-0-3-0-0.cre1.sky.orcon.net.nz [121.98.9.10]
5 vocus1.ape.nzix.net [192.203.154.123]
6 ten-0-7-0-2.cor01.alb01.akl.VOCUS.net.nz [114.31.202.68]
7 ten-0-3-0-2.cor03.syd03.nsw.VOCUS.net.au [114.31.202.85]
8 ten-1-0-0.bdr03.syd04.nsw.VOCUS.net.au [175.45.72.73]
9 as17819.cust.bdr03.syd04.nsw.VOCUS.net.au [175.45.73.194]
10 27.111.251.106
11 103.4.115.248

Computing statistics for 275 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Jedateach.Home [192.168.20.2]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.20.1
0/ 100 = 0% |
2 19ms 0/ 100 = 0% 0/ 100 = 0% 121-99-252-1.bng1.nct.orcon.net.nz
[121.99.252.1]
0/ 100 = 0% |
3 19ms 0/ 100 = 0% 0/ 100 = 0% xe-2-2-0.cre1.nct.orcon.net.nz [12
1.98.9.141]
0/ 100 = 0% |
4 19ms 0/ 100 = 0% 0/ 100 = 0% ge-0-3-0-0.cre1.sky.orcon.net.nz [
121.98.9.10]
0/ 100 = 0% |
5 19ms 0/ 100 = 0% 0/ 100 = 0% vocus1.ape.nzix.net [192.203.154.1
23]
0/ 100 = 0% |
6 21ms 0/ 100 = 0% 0/ 100 = 0% ten-0-7-0-2.cor01.alb01.akl.VOCUS.
net.nz [114.31.202.68]
0/ 100 = 0% |
7 43ms 0/ 100 = 0% 0/ 100 = 0% ten-0-3-0-2.cor03.syd03.nsw.VOCUS.
net.au [114.31.202.85]
0/ 100 = 0% |
8 43ms 0/ 100 = 0% 0/ 100 = 0% ten-1-0-0.bdr03.syd04.nsw.VOCUS.ne
t.au [175.45.72.73]
0/ 100 = 0% |
9 46ms 0/ 100 = 0% 0/ 100 = 0% as17819.cust.bdr03.syd04.nsw.VOCUS
.net.au [175.45.73.194]
1/ 100 = 1% |
10 --- 100/ 100 =100% 99/ 100 = 99% 27.111.251.106
0/ 100 = 0% |
11 43ms 1/ 100 = 1% 0/ 100 = 0% 103.4.115.248

Trace complete.

C:\Users\Jon>

Anything else want me to lookup/try?

Was gonna lay in bed and watch Gameshow League on twitch, but cutting out heaps kind of ruins it.

FireEngine

1223 posts

Uber Geek

Trusted

#1126784 11-Sep-2014 21:04

Jedateach: Anything else want me to lookup/try?

Not tonight but the changes we have made means we are confident a change going in tonight will resolve the on-network cause of rubber-banding.

You will see a notice on our website that refers to Wellington and Christchurch users being affected by the engineering work as an outage but the results of the work should improve all users experience.

I will update tomorrow morning on the change going in or if we had any issues but we are doing our very best to get the improvements in before the weekend.

Regards FireEngine

Jedateach

25 posts

Geek

#1126786 11-Sep-2014 21:06

Ok :) thanks for update

GoodSync

GoodSync. Easily back up and sync your files with GoodSync. Simple and secure file backup and synchronisation software will ensure that your files are never lost (affiliate link).

kiwikiwi

455 posts

Ultimate Geek

#1126789 11-Sep-2014 21:09

FireEngine:
FireEngine:
kiwikiwi: Ahh what a shame. Second tracert on the 2nd hop on euba was kinda abnormally high but if its something off your network then i'll just put it towards bad time since mostly this hasn't been as persistent nor problematic as everyone else is experiencing.

No problem, it is occurring at the same point as for the other user above, I'll have the team look into it with the upstream.

Found it, we had a big spike in traffic to the US, between approx 7pm and 7:20pm, looks like a transient DDOS against a single customer.

Can you retest the tracert?

Ping is still unusually high and packet loss was minor but it was there and this is to NA, it was creepy around 164-180 randomly

You can also follow me on twitter here @kiwifortw I do twitch streams every now and then at twitch.tv/kiwiforthewin :)

HTTP 404 Sarcasm not found.

PassiveFever81

367 posts

Ultimate Geek

#1126812 11-Sep-2014 21:49

The past couple nights and right now, trying to play BF4, getting 10-20% packet loss in and 1-2% out and 170ish pings (normally 0% loss 60ish ping) - Xbox One using system performance test in Battlefield 4 playing on a 20 player TDM server, same packet loss etc in 64P conquest too...

I gave up gaming a while back due to poor performance to Australia... Really amazed it still isn't fixed...

FireEngine

1223 posts

Uber Geek

Trusted

#1126890 12-Sep-2014 06:57

FireEngine:
Jedateach: Anything else want me to lookup/try?

Not tonight but the changes we have made means we are confident a change going in tonight will resolve the on-network cause of rubber-banding.

You will see a notice on our website that refers to Wellington and Christchurch users being affected by the engineering work as an outage but the results of the work should improve all users experience.

I will update tomorrow morning on the change going in or if we had any issues but we are doing our very best to get the improvements in before the weekend.

Regrettably we didn't get the change in, some customers appeared negatively impacted by the change so we had to roll it back. We will review today and I'll update once we have a new change date.

Regards FireEngine

FireEngine

1223 posts

Uber Geek

Trusted

#1127235 12-Sep-2014 14:11

Hi All, We have been putting that change back in successfully today, some users will have seen very short outage and possibly had to restart their modems as per the advice on our network status page. Normally we would have waited to do this work on the next overnight slot next week but we were keen to get this in before what looks like a wet weekend.

Thanks - feedback appreciated on this evenings experience as always.

Regards FireEngine

aphocus

37 posts

Geek

#1127353 12-Sep-2014 17:37

FireEngine: Hi All, We have been putting that change back in successfully today, some users will have seen very short outage and possibly had to restart their modems as per the advice on our network status page. Normally we would have waited to do this work on the next overnight slot next week but we were keen to get this in before what looks like a wet weekend.

Thanks - feedback appreciated on this evenings experience as always.

Thanks for the work, Looks like everything has been better recently, though I haven't been able to test the 3pm issues again yet, hopefully it was just a random occurrence.

Though it would be nice if you performed your maintenance a little later, ruined a rather epic game of AOEII last night.

FireEngine

1223 posts

Uber Geek

Trusted

#1127358 12-Sep-2014 17:53

aphocus: Though it would be nice if you performed your maintenance a little later, ruined a rather epic game of AOEII last night.

Sorry about that, we didn't have complete freedom of choice about the start time.

Regards FireEngine

PassiveFever81

367 posts

Ultimate Geek

#1127453 12-Sep-2014 20:38

Should things be running better now? Still getting a huge amount of packet loss and pings going up and down in BF4 on the X1...

Edit: Tethered my Xbox One to my 3G on my smartphone, had a higher ping, but no packet loss what so ever through out a match.

So glad Orcon won't be my ISP at the end of the month...

jaiki33

6 posts

Wannabe Geek

#1127458 12-Sep-2014 20:45

Still getting issues on diablo, league of legends and streaming the web as well.

1 | ... | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14