![]() ![]() ![]() |
|
Does anyone know if there are news on the 2Degrees fibre service status for Wellington? Our gaming sessions in League of Legend and Fall guy have been dropping quite frequently today 😅. Using ethernet cable for connection
We shall be grateful if you guys could help us out 😬
Stacy88:
Does anyone know if there are news on the 2Degrees fibre service status for Wellington? Our gaming sessions in League of Legend and Fall guy have been dropping quite frequently today 😅. Using ethernet cable for connection
We shall be grateful if you guys could help us out 😬
OK in Island Bay.
No dropouts, good local latency and speed.
"There are no known issues on the 2degrees Broadband Network"
Sideface
Thanks for this. We've just been in a few games and the problem seems to have faded away :D. Thanks
Resurrecting this thread - I am having nasty ping issues with Apex Legends' Singapore 1 server. The two Google Cloud Engine-backed servers in Singapore are fine, and connection via Spark (on my mobile) is also fine with a ping closer to 120ms.
Traceroute below:
Tracing route to 72.5.161.228 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms fritz.box [192.168.1.1]
2 2 ms 1 ms 1 ms 12.7.69.111.static.snap.net.nz [111.69.7.12]
3 * * * Request timed out.
4 143 ms 142 ms 142 ms TWODEGREES-svc063403-ic344202.c.telia.net [62.115.175.227]
5 143 ms 151 ms 144 ms las-b24-link.telia.net [62.115.175.226]
6 144 ms 142 ms 187 ms singaporetelecom-ic-335365-las-b24.c.telia.net [62.115.8.203]
7 324 ms 324 ms 324 ms 203.208.173.81
8 328 ms 327 ms 327 ms 203.208.172.93
9 334 ms 335 ms 332 ms 203.208.177.10
10 332 ms 332 ms 334 ms border1.xe-0-1-1.bbnet1.sin001.pnap.net [202.58.8.8]
11 341 ms 348 ms 340 ms edge1.ae1-edgenet.sin003.pnap.net [202.58.9.14]
12 329 ms 329 ms 329 ms 202.58.10.198
13 340 ms 340 ms 340 ms 72.5.161.228
Am also having bad ping issues to Singapore on Apex.
Traceroute:
1 <1 ms <1 ms <1 ms fritz.box [192.168.178.1]
2 20 ms 1 ms 1 ms 54.7.69.111.static.snap.net.nz [111.69.7.54]
3 * * * Request timed out.
4 138 ms 138 ms 138 ms TWODEGREES-svc063403-ic344202.c.telia.net [62.115.175.227]
5 138 ms 137 ms 138 ms las-b24-link.telia.net [62.115.175.226]
6 140 ms 138 ms 138 ms singaporetelecom-ic-335365-las-b24.c.telia.net [62.115.8.203]
7 322 ms 325 ms 321 ms 203.208.171.9
8 334 ms 334 ms 333 ms 203.208.172.93
9 322 ms 322 ms 321 ms 203.208.177.10
10 323 ms 322 ms 323 ms border1.xe-0-1-1.bbnet1.sin001.pnap.net [202.58.8.8]
11 327 ms 326 ms 327 ms edge1.ae1-edgenet.sin003.pnap.net [202.58.9.14]
12 327 ms 327 ms 327 ms 202.58.10.198
13 327 ms 326 ms 326 ms 72.5.161.228
spronkey:
Resurrecting this thread - I am having nasty ping issues with Apex Legends' Singapore 1 server. The two Google Cloud Engine-backed servers in Singapore are fine, and connection via Spark (on my mobile) is also fine with a ping closer to 120ms.
Traceroute below:
Tracing route to 72.5.161.228 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms fritz.box [192.168.1.1]
2 2 ms 1 ms 1 ms 12.7.69.111.static.snap.net.nz [111.69.7.12]
3 * * * Request timed out.
4 143 ms 142 ms 142 ms TWODEGREES-svc063403-ic344202.c.telia.net [62.115.175.227]
5 143 ms 151 ms 144 ms las-b24-link.telia.net [62.115.175.226]
6 144 ms 142 ms 187 ms singaporetelecom-ic-335365-las-b24.c.telia.net [62.115.8.203]
7 324 ms 324 ms 324 ms 203.208.173.81
8 328 ms 327 ms 327 ms 203.208.172.93
9 334 ms 335 ms 332 ms 203.208.177.10
10 332 ms 332 ms 334 ms border1.xe-0-1-1.bbnet1.sin001.pnap.net [202.58.8.8]
11 341 ms 348 ms 340 ms edge1.ae1-edgenet.sin003.pnap.net [202.58.9.14]
12 329 ms 329 ms 329 ms 202.58.10.198
13 340 ms 340 ms 340 ms 72.5.161.228
Did some research, a year old answer is in this thread. 2degrees routes through the US because AU - SG is expensive. I remember playing Apex a year ago and not having any of these issues. They've cut corners, sad. I bet the original price drop (I think the plan was $110 then they made it $100 or so), to try an undermine other ISPs is part of the explanation as to why we had to be stuffed over like this. Frustrating. Apex has no competitive base in OCE and the alternative is ping like I'm playing in the US.
humandan:
spronkey:
Resurrecting this thread - I am having nasty ping issues with Apex Legends' Singapore 1 server. The two Google Cloud Engine-backed servers in Singapore are fine, and connection via Spark (on my mobile) is also fine with a ping closer to 120ms.
Traceroute below:
Tracing route to 72.5.161.228 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms fritz.box [192.168.1.1]
2 2 ms 1 ms 1 ms 12.7.69.111.static.snap.net.nz [111.69.7.12]
3 * * * Request timed out.
4 143 ms 142 ms 142 ms TWODEGREES-svc063403-ic344202.c.telia.net [62.115.175.227]
5 143 ms 151 ms 144 ms las-b24-link.telia.net [62.115.175.226]
6 144 ms 142 ms 187 ms singaporetelecom-ic-335365-las-b24.c.telia.net [62.115.8.203]
7 324 ms 324 ms 324 ms 203.208.173.81
8 328 ms 327 ms 327 ms 203.208.172.93
9 334 ms 335 ms 332 ms 203.208.177.10
10 332 ms 332 ms 334 ms border1.xe-0-1-1.bbnet1.sin001.pnap.net [202.58.8.8]
11 341 ms 348 ms 340 ms edge1.ae1-edgenet.sin003.pnap.net [202.58.9.14]
12 329 ms 329 ms 329 ms 202.58.10.198
13 340 ms 340 ms 340 ms 72.5.161.228
Did some research, a year old answer is in this thread. 2degrees routes through the US because AU - SG is expensive. I remember playing Apex a year ago and not having any of these issues. They've cut corners, sad. I bet the original price drop (I think the plan was $110 then they made it $100 or so), to try an undermine other ISPs is part of the explanation as to why we had to be stuffed over like this. Frustrating. Apex has no competitive base in OCE and the alternative is ping like I'm playing in the US.
Hiya,
Do we know if this has 'changed' and have anything to compare against?
2degrees now have better routing into Asia via some Australian paths/peering - @2degreescare @morganbrowne - Can someone please investigate routing to 72.5.161.228 and whether anything can be done for this?
My tracing results are as follows:
nick@thenet-rs04:~$ traceroute --resolve-hostnames 72.5.161.228
traceroute to 72.5.161.228 (72.5.161.228), 64 hops max
1 202.124.98.41 (thenet.gen.nz) 0.916ms * 1.328ms
2 111.69.7.12 (12.7.69.111.static.snap.net.nz) 3.417ms 2.733ms 2.636ms
3 * * *
4 62.115.175.227 (twodegrees-svc063403-ic344202.c.telia.net) 144.441ms 142 .966ms 143.108ms
5 62.115.175.226 (las-b24-link.telia.net) 144.353ms 143.183ms 143.083ms
6 62.115.8.203 (singaporetelecom-ic-335365-las-b24.c.telia.net) 143.799ms 163.406ms 143.119ms
7 203.208.171.117 (203.208.171.117) 144.713ms 143.639ms 143.708ms
8 203.208.172.145 (203.208.172.145) 321.727ms 320.303ms 320.010ms
9 203.208.182.253 (203.208.182.253) 326.055ms 325.458ms 325.502ms
10 203.208.158.185 (203.208.158.185) 326.675ms 325.210ms 325.404ms
11 202.58.9.14 (edge1.ae1-edgenet.sin003.pnap.net) 322.131ms 320.937ms 321 .643ms
12 202.58.10.198 (202.58.10.198) 340.940ms 339.781ms 339.470ms
13 * * *
14 * * *
15 202.58.10.198 (202.58.10.198) 337.173ms 336.676ms 336.959ms
16 * * *
17 * * *
18 * * *
19 * * *
20 * 72.5.161.228 (72.5.161.228) 333.163ms 332.590ms
nick@thenet-rs04:~$
Nick.
https://nick.mackechnie.co.nz | NZ ISP latency monitoring - https://smokeping.thenet.gen.nz
morganbrowne:
@nickmack Will chat to the network team and let you know :)
Thanks muchly - I've added monitoring to this address so we can see the progress/monitor over time - https://smokeping.thenet.gen.nz/smokeping/smokeping.cgi?target=gaming.apexlegends01
Nick
https://nick.mackechnie.co.nz | NZ ISP latency monitoring - https://smokeping.thenet.gen.nz
morganbrowne:
@nickmack Will chat to the network team and let you know :)
Hi Morgan,
Do you have any updates on this one please?
Nick.
https://nick.mackechnie.co.nz | NZ ISP latency monitoring - https://smokeping.thenet.gen.nz
NickMack:
morganbrowne:
@nickmack Will chat to the network team and let you know :)
Hi Morgan,
Do you have any updates on this one please?
Nick.
Hey Nick,
The issue has been identified and raised to an upstream carrier - they have raised a change to address the issue. When I have more info/solution I'll let you know. :)
Morgan Browne - 2degrees Social & Digital Media Manager.
I'm in the comms team. If you would love some help from our 100% Kiwi-based customer care team, please call them on 0800 022 022.
i find that whatever i game, 50ms to sydney is a big handicap. firstly i'm not a top player, but at 50ms i can't do anything, my opponent always gets me first, and when i am sure i got them either i miss or the server doesn't register (indicating they've moved on).
sob
Batman:
i find that whatever i game, 50ms to sydney is a big handicap. firstly i'm not a top player, but at 50ms i can't do anything, my opponent always gets me first, and when i am sure i got them either i miss or the server doesn't register (indicating they've moved on).
sob
Hey Batman,
I'm seeing 42ms (which 2d/Snap has consistently deliver for years) roundtrip to Sydney, if you are seeing more than that it's more likely to do with where the games are cached/hosted... kind of tough beating the laws of physics :-)
Nick.
https://nick.mackechnie.co.nz | NZ ISP latency monitoring - https://smokeping.thenet.gen.nz
NickMack:
Batman:
i find that whatever i game, 50ms to sydney is a big handicap. firstly i'm not a top player, but at 50ms i can't do anything, my opponent always gets me first, and when i am sure i got them either i miss or the server doesn't register (indicating they've moved on).
sob
Hey Batman,
I'm seeing 42ms (which 2d/Snap has consistently deliver for years) roundtrip to Sydney, if you are seeing more than that it's more likely to do with where the games are cached/hosted... kind of tough beating the laws of physics :-)
Nick.
That is from Christchurch as well, AKL and HLZ are ~20-25ms
Any posts are personal comments and not that of my employer
To me, I'm hoping this is abnormal. Knowing from experience, as I have played Apex Legends on Singapore servers during Season 3 and 4. These issues were not present at the time, from memory.
I'm a little worried that other games may have the same issues and thus the process will need to be repeated of using tracert on the IPs and posting the results on Geekzone for a solution to be made, I am glad a quick response is there but I'm sure this is the last thing a gaming customer would want to have to deal with when they're playing games (PUBG was unplayable due to CGNAT which required a phone call to sort out, for example).
Anyways, I'm hoping this can be fixed - as if gameplay wasn't bad enough on 130ms, now try 300!
|
![]() ![]() ![]() |