Gaming ping on 2degrees

Forums › 2degrees (including Slingshot, Orcon, Flip, Stuff Fibre, MyRepublic, 2talk and Vocus) › Gaming ping on 2degrees

1 | 2 | 3 | 4 | 5 | 6

30 posts

Geek
+1 received by user: 3

#2572008 22-Sep-2020 13:46

hio77:

I have heard reports from a few providers having issues with some of the IX's.

https://status.ix.asn.au/

It would not surprise me if this is related.

Hello :)

On the status page it states this though? All my testing is done in the past 30 mins. I guess it's possible some route changes done to mitigate could still be in place.

Monitoring - The flaps have stopped and the link is stable over 10 hours.

NickMack

977 posts

Ultimate Geek
+1 received by user: 831

Trusted

In memoriam

Lifetime subscriber

#2572010 22-Sep-2020 13:46

hio77:

I have heard reports from a few providers having issues with some of the IX's.

https://status.ix.asn.au/

It would not surprise me if this is related.

I saw reports of a broadcast storm at Megaport in Aust peering exchange.

https://nick.mackechnie.co.nz | NZ ISP latency monitoring - https://smokeping.thenet.gen.nz

hio77

'That VDSL Cat'
13044 posts

Uber Geek
+1 received by user: 3901

ID Verified

Trusted

Lizard Networks

Subscriber

#2572018 22-Sep-2020 13:51

NickMack:

I saw reports of a broadcast storm at Megaport in Aust peering exchange.

Yes those too. i don't have a status page to link out to off the top of my head though, so hearsay :)

#include <std_disclaimer>

Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.

fabianz03

78 posts

Master Geek
+1 received by user: 5

#2572291 22-Sep-2020 18:08

Here's my in-game latency to the North American servers.

As stated before I usually get 210ms to 250ms but recently I've been getting upwards of 300ms latency.

Edit: The game is ESO, PC/NA

yitz

2277 posts

Uber Geek
+1 received by user: 608

#2572310 22-Sep-2020 18:52

fabianz03:

As stated before I usually get 210ms to 250ms but recently I've been getting upwards of 300ms latency.

Post up your traceroute ouput to the NA server, instructions here: https://help.elderscrollsonline.com/app/answers/detail/a_id/30903/

NickMack

977 posts

Ultimate Geek
+1 received by user: 831

Trusted

In memoriam

Lifetime subscriber

#2572311 22-Sep-2020 18:52

hio77:

NickMack:

I saw reports of a broadcast storm at Megaport in Aust peering exchange.

Yes those too. i don't have a status page to link out to off the top of my head though, so hearsay :)

Confirmed hearsay to fact :-)

https://nick.mackechnie.co.nz | NZ ISP latency monitoring - https://smokeping.thenet.gen.nz

Geekzone support

Support Geekzone with one-off or recurring donations Donate via PressPatron.

NickMack

977 posts

Ultimate Geek
+1 received by user: 831

Trusted

In memoriam

Lifetime subscriber

#2572315 22-Sep-2020 18:55

yitz:

fabianz03:

As stated before I usually get 210ms to 250ms but recently I've been getting upwards of 300ms latency.

Post up your traceroute ouput to the NA server, instructions here: https://help.elderscrollsonline.com/app/answers/detail/a_id/30903/

It might be useful to state to what services (IP addresses/FQDN) you are seeing higher latency with in the US to assist 2degrees to investigate further. If you look at this link - https://smokeping.thenet.gen.nz/smokeping/smokeping.cgi?target=2degreesspeedtest.waldorf this service sits on server on the 2degrees network in the US.

Nick.

https://nick.mackechnie.co.nz | NZ ISP latency monitoring - https://smokeping.thenet.gen.nz

Mahon

473 posts

Ultimate Geek
+1 received by user: 214

#2572339 22-Sep-2020 19:48

Latency to LA Blizzard servers is about right at 140-150, however latency to Aus servers is currently the same when it should be about 50ms. Something a bit off.

fabianz03

78 posts

Master Geek
+1 received by user: 5

#2572417 22-Sep-2020 21:42

yitz:

fabianz03:

As stated before I usually get 210ms to 250ms but recently I've been getting upwards of 300ms latency.

Post up your traceroute ouput to the NA server, instructions here: https://help.elderscrollsonline.com/app/answers/detail/a_id/30903/

Followed the instructions and here's what I got. Not sure what it all means but there you go:

Tracing route to 198.20.198.110 over a maximum of 30 hops

0 DesktopPC [192.168.1.19]
1 192.168.1.1
2 100.69.255.254
3 198.18.10.205
4 167.10.69.111.static.snap.net.nz [111.69.10.167]
5 as23655.auckland.megaport.com [43.243.22.49]
6 as4826.auckland.megaport.com [43.243.22.18]
7 be101.bdr01.akl03.akl.nz.vocus.network [114.31.202.40]
8 be2.cor01.syd11.nsw.vocus.network [114.31.202.56]
9 be100.bdr01.syd11.nsw.vocus.network [114.31.192.81]
10 49.255.93.14
11 po110.bs-b.sech-syd3.netarch.akamai.com [23.57.108.245]
12 a72-52-1-155.deploy.static.akamaitechnologies.com [72.52.1.155]
13 ae121.access-a.sech-syd3.netarch.akamai.com [23.57.108.251]
14 a72-52-63-152.deploy.static.akamaitechnologies.com [72.52.63.152]
15 * * *
Computing statistics for 350 seconds...

I've also pinged the US server on cmd and it timed out on all four attempts.

Not sure why it's behaving like this.

edit: ran a tracert and here's the result

Tracing route to 198.20.198.110 over a maximum of 30 hops

1 2 ms 2 ms 2 ms 192.168.1.1
2 8 ms 11 ms 23 ms 100.69.255.254
3 9 ms 7 ms 6 ms 198.18.10.205
4 7 ms 5 ms 9 ms 167.10.69.111.static.snap.net.nz [111.69.10.167]
5 9 ms 5 ms 11 ms as23655.auckland.megaport.com [43.243.22.49]
6 10 ms 8 ms 10 ms as4826.auckland.megaport.com [43.243.22.18]
7 31 ms 32 ms 29 ms be101.bdr01.akl03.akl.nz.vocus.network [114.31.202.40]
8 29 ms 33 ms 30 ms be2.cor01.syd11.nsw.vocus.network [114.31.202.56]
9 33 ms 33 ms 32 ms be100.bdr01.syd11.nsw.vocus.network [114.31.192.81]
10 31 ms 30 ms 30 ms 49.255.93.14
11 33 ms 30 ms 30 ms po110.bs-b.sech-syd3.netarch.akamai.com [23.57.108.245]
12 31 ms 30 ms 30 ms a72-52-1-155.deploy.static.akamaitechnologies.com [72.52.1.155]
13 30 ms 32 ms 30 ms ae121.access-a.sech-syd3.netarch.akamai.com [23.57.108.251]
14 34 ms 30 ms 31 ms a72-52-63-152.deploy.static.akamaitechnologies.com [72.52.63.152]
15 * * * Request timed out.
16 *

edit 2:

just logged in to the game and its showing 300ms+

the devs did push an update yesterday and conveniently the problem started yesterday so maybe this issue is update-related? or simply a graphical error?

Erebus

2 posts

Wannabe Geek
+1 received by user: 4

#2572440 22-Sep-2020 22:43

Confirming something is a bit off. Tarkov OCE server in Sydney is usually 25-30ms for me (based in Auckland), currently in game is 130+.

Traceroute:

Tracing route to 103.101.129.105 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms fritz.box [192.168.178.1]
2 3 ms 2 ms 2 ms 41.7.69.111.static.snap.net.nz [111.69.7.41]
3 1 ms 2 ms 2 ms 198.18.10.197
4 2 ms 2 ms 2 ms 163.10.69.111.static.snap.net.nz [111.69.10.163]
5 * * * Request timed out.
6 25 ms 25 ms 25 ms ip4.gtt.net [67.199.137.166]
7 25 ms 26 ms 25 ms ip4.gtt.net [67.199.137.165]
8 124 ms 124 ms 173 ms 141.136.110.154
9 125 ms 125 ms 124 ms as4637.sin10.ip4.gtt.net [183.182.80.170]
10 125 ms 126 ms 127 ms i-94.sgcn-core01.telstraglobal.net [202.84.225.237]
11 126 ms 126 ms 126 ms i-15051.sgpl-core02.telstraglobal.net [202.84.140.166]
12 127 ms 125 ms 124 ms i-15350.pthp-core02.telstraglobal.net [202.84.140.37]
13 123 ms 122 ms 123 ms bundle-ether5.pie-core10.perth.telstra.net [203.50.9.1]
14 126 ms 127 ms 126 ms bundle-ether3.way-core10.adelaide.telstra.net [203.50.6.234]
15 129 ms 126 ms 126 ms bundle-ether16.exi-core10.melbourne.telstra.net [203.50.6.231]
16 128 ms 128 ms 127 ms bundle-ether12.chw-core10.sydney.telstra.net [203.50.11.124]
17 126 ms 127 ms 127 ms bundle-ether1.chw-edge903.sydney.telstra.net [203.50.11.177]
18 127 ms 126 ms 126 ms bundle-ether2.ken-edge903.sydney.telstra.net [203.50.11.174]
19 126 ms 126 ms 126 ms lea2773954.lnk.telstra.net [110.145.184.118]
20 126 ms 126 ms 126 ms po-1.ce02.syd-10.au.leaseweb.net [103.101.131.7]
21 126 ms 126 ms 126 ms 103.101.129.105

Cheers

pwner

423 posts

Ultimate Geek
+1 received by user: 96

Trusted

2degrees

#2572506 23-Sep-2020 08:38

Thanks for the info, I will pass this on to get investigated and fixed.

Any posts are personal comments and not that of my employer

New World

Shop on-line at New World now for your groceries (affiliate link).

Mahon

473 posts

Ultimate Geek
+1 received by user: 214

#2572689 23-Sep-2020 11:27

Seems to be fixed now!

DoucheBagz

30 posts

Geek
+1 received by user: 3

#2572698 23-Sep-2020 11:42

Awesome, looks like its back to normal. Cheers guys!

Is there any chance to figure out whats happening with the connection to the Tarkov Singapore server? I normally play on a VPN to achieve the 120ms to SG, but for some reason, even with the routing changes its still 240ms+

Being able to play without the VPN would be amazing.

Tracing route to 103.254.154.234 over a maximum of 30 hops

1 1 ms 1 ms <1 ms OpenWrt.lan [192.168.1.1]
2 4 ms 5 ms 3 ms 41.7.69.111.static.snap.net.nz [111.69.7.41]
3 * * * Request timed out.
4 26 ms 26 ms 26 ms ip4.gtt.net [67.199.137.166]
5 28 ms 26 ms 25 ms ip4.gtt.net [67.199.137.165]
6 126 ms 126 ms 126 ms 141.136.110.158
7 * * * Request timed out.
8 248 ms 248 ms 248 ms be-101.br02.sin-10.sg.leaseweb.net [31.31.38.125]
9 243 ms 245 ms 245 ms po-2.ce02.sin-11.sg.leaseweb.net [103.254.152.187]

Any help would be hugely appreciated :)

fabianz03

78 posts

Master Geek
+1 received by user: 5

#2573107 23-Sep-2020 22:09

Happy to report that ESO latency has been resolved. back to 190ms-ish again.

DoucheBagz

30 posts

Geek
+1 received by user: 3

#2574774 27-Sep-2020 03:32

Hello,

One more problem to report if possible. Peering with OVH in the US has gone completely bonkers. To West coast US, its going Syd > Singapore > EU > US.

You can see from OVHs monitoring that there is an issue.

http://pdx1-hil.smokeping.ovh.net/smokeping?target=APAC.AS23655

Cheers!

1 1 ms 1 ms 2 ms OpenWrt.lan [192.168.20.1]
2 4 ms 3 ms 3 ms 41.7.69.111.static.snap.net.nz [111.69.7.41]
3 * * * Request timed out.
4 25 ms 26 ms 25 ms ip4.gtt.net [67.199.137.170]
5 27 ms 27 ms 25 ms ip4.gtt.net [67.199.137.169]
6 125 ms 126 ms 150 ms 141.136.110.158
7 124 ms 125 ms 126 ms be3257.ccr21.sin01.atlas.cogentco.com [154.54.140.9]
8 265 ms 266 ms 265 ms be2435.ccr21.mrs01.atlas.cogentco.com [154.54.2.109]
9 269 ms 269 ms 268 ms 130.117.49.153
10 264 ms 264 ms 264 ms 154.54.38.66
11 * * * Request timed out.
12 263 ms 263 ms 264 ms be105.par-gsw-sbb1-nc5.fr.eu [94.23.122.245]
13 * * * Request timed out.
14 265 ms 265 ms 263 ms be105.par-gsw-sbb1-nc5.fr.eu [94.23.122.245]
15 286 ms 268 ms 268 ms be102.rbx-g2-nc5.fr.eu [94.23.122.214]
16 * * * Request timed out.
17 269 ms 267 ms 268 ms 192.99.146.133
18 275 ms 275 ms 276 ms be102.bhs-g2-nc5.qc.ca [192.99.146.138]
19 281 ms 279 ms 280 ms be100-1324.chi-5-a9.il.us [192.99.146.141]
20 278 ms 279 ms 279 ms 198.27.73.226
21 294 ms 295 ms 293 ms 142.44.208.9
22 295 ms 295 ms 293 ms pdx1-hil1-g2-nc5.il.us [142.44.208.229]
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 294 ms 293 ms 295 ms 147.135.37.183

Trace complete.

1 | 2 | 3 | 4 | 5 | 6