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

8 posts

Wannabe Geek

#2599331 7-Nov-2020 00:09

Apex Legends player here.

I am also experiencing high latency and spikes on Singapore servers ever since I started playing 3 months ago, non of my other squad mates had any issues (they are on other ISP).

When it gets bad enough it's literally a slideshow, and was thinking to quit playing because of it.

Finally today I had enough, quick search on the internet and ended up here, did a tracert and the result exactly like others here.

AliExpress

Shop now on AliExpress (affiliate link).

Batman

Mad Scientist
29690 posts

Uber Geek

Trusted

Lifetime subscriber

#2599355 7-Nov-2020 07:23

how do i do a tracert when gaming on xbox? thanks

humandan

8 posts

Wannabe Geek

#2600582 9-Nov-2020 17:26

Any updates?

I will say, last night, playing on SNG servers - Ping was 330ms consistently. At one point, maybe 2 am it went to 120ms for a bit. As of right now I'm at 330ms ping.

Grimnz

16 posts

Geek

#2600682 9-Nov-2020 20:14

As of tonight my ping is 160ms on modern warfare,jumped on ww2 to make sure and everyone else is fine but me.Usually sit on 50 -60 .Also modern warfare usually reports 0 packet loss tonight 10 - 15 % packet loss

NickMack

944 posts

Ultimate Geek

Trusted

Lifetime subscriber

#2600692 9-Nov-2020 20:54

@pwner - Rob can you please provide an update here?

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

Grimnz

16 posts

Geek

#2600738 9-Nov-2020 22:47

Hey Mr mack , Glad to see your still around !

pwner

423 posts

Ultimate Geek

Trusted

2degrees

#2600742 9-Nov-2020 22:56

We are still working with our upstream supplier to correct some routing issues.
I will push them again for an update

Any posts are personal comments and not that of my employer

NickMack

944 posts

Ultimate Geek

Trusted

Lifetime subscriber

#2600789 10-Nov-2020 08:46

pwner: We are still working with our upstream supplier to correct some routing issues.
I will push them again for an update

Thanks Rob

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

NickMack

944 posts

Ultimate Geek

Trusted

Lifetime subscriber

#2605931 18-Nov-2020 12:05

NickMack:

pwner: We are still working with our upstream supplier to correct some routing issues.
I will push them again for an update

Thanks Rob

Hi @pwner,

How's your upstream coming along with peering changes?

Nick.

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

NickMack

944 posts

Ultimate Geek

Trusted

Lifetime subscriber

#2610936 26-Nov-2020 09:06

Hi 2degrees,

Any update on this, it's been over a month since this was raised? @pwner @morganbrowne

Nick.

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

pwner

423 posts

Ultimate Geek

Trusted

2degrees

#2610964 26-Nov-2020 09:56

Sorry for the lack of update on this, it is proving to be a harder fix than first anticipated due to the way the company that hosts Apex Legends peers internationally. As NickMack has shown latency to other singapore addresses is far better than Apex Legends.

We are actively working with new upstream providers to improve our reach into Asia, unfortunately this takes a bit more time.

Any posts are personal comments and not that of my employer

humandan

8 posts

Wannabe Geek

#2616411 4-Dec-2020 17:42

It may be useful to note, so I'll also mention that Tokyo servers have the same ping as Singapore - at least the ones you actually play on and not the GCEs that you have the option to connect to (I rarely get matches on the GCEs otherwise I would be able to see my ping is as shown in the pregame menu.)

The game's server list on the start screen shows the GCEs at 130ms ping for Singapore (normal), with the Singapore 1 server itself being 300 ping - this being likely the actual server you play on.

This is the same for Tokyo. The three Tokyo GCE (1, 2, 3) servers are all 150ms ping however the "Tokyo" server itself is 300ms. "Tokyo 1" and "Tokyo 2" are 237ms.

I don't know how useful this information is but I felt to share that it's not just an issue with the Singapore server on Apex. I also do not know much about what is actually going on behind the scenes with servers and whatnot, and you obviously already know this, but it's a little odd to see this:

Los Angeles, California?: 4 138 ms 137 ms 137 ms TWODEGREES-svc063403-ic344202.c.telia.net [62.115.175.227]
Los Angeles, California: 5 158 ms 138 ms 138 ms las-b24-link.telia.net [62.115.175.226]
LA -> Singapore?: 6 138 ms 137 ms 138 ms singaporetelecom-ic-335365-las-b24.c.telia.net [62.115.8.203]
Singapore: 7 315 ms 315 ms 315 ms 203.208.172.153

Anyone able to explain, to a simpleton, why it's going to Los Angeles in the first place for Singapore (and most likely Tokyo too).

pwner

423 posts

Ultimate Geek

Trusted

2degrees

#2617219 7-Dec-2020 09:02

humandan:

It may be useful to note, so I'll also mention that Tokyo servers have the same ping as Singapore - at least the ones you actually play on and not the GCEs that you have the option to connect to (I rarely get matches on the GCEs otherwise I would be able to see my ping is as shown in the pregame menu.)

The game's server list on the start screen shows the GCEs at 130ms ping for Singapore (normal), with the Singapore 1 server itself being 300 ping - this being likely the actual server you play on.

This is the same for Tokyo. The three Tokyo GCE (1, 2, 3) servers are all 150ms ping however the "Tokyo" server itself is 300ms. "Tokyo 1" and "Tokyo 2" are 237ms.

I don't know how useful this information is but I felt to share that it's not just an issue with the Singapore server on Apex. I also do not know much about what is actually going on behind the scenes with servers and whatnot, and you obviously already know this, but it's a little odd to see this:

Los Angeles, California?: 4 138 ms 137 ms 137 ms TWODEGREES-svc063403-ic344202.c.telia.net [62.115.175.227]
Los Angeles, California: 5 158 ms 138 ms 138 ms las-b24-link.telia.net [62.115.175.226]
LA -> Singapore?: 6 138 ms 137 ms 138 ms singaporetelecom-ic-335365-las-b24.c.telia.net [62.115.8.203]
Singapore: 7 315 ms 315 ms 315 ms 203.208.172.153

Anyone able to explain, to a simpleton, why it's going to Los Angeles in the first place for Singapore (and most likely Tokyo too).

Thanks Humandan

This shows the interesting issue, the GCE servers are peered locally in Singapore so we are able to get direct routing to them, but the other servers aren't connected in the same way and are presenting to our international transit partners in the US only even though they are actually in Singapore or Japan.

Any posts are personal comments and not that of my employer

thudb

10 posts

Wannabe Geek

#2618005 8-Dec-2020 10:54

Anyone else finding Fortnite Oceania pings are now at ~100ms whereas they were ~20ms? Is this a 2Degrees issue?

--------

tracert qosping-aws-ap-southeast-2.ol.epicgames.com

Tracing route to qosping-aws-ap-southeast-2.ol.epicgames.com [13.210.108.126]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms RT-AC68U-9F88 [192.168.1.1]
2 2 ms 3 ms 3 ms 100.69.255.254
3 2 ms 2 ms 3 ms 198.18.10.205
4 3 ms 3 ms 3 ms 167.10.69.111.static.snap.net.nz [111.69.10.167]
5 102 ms 103 ms 103 ms 99.82.179.91
6 103 ms 103 ms 103 ms 99.82.179.90
7 * * * Request timed out.
8 103 ms 103 ms 103 ms 150.222.112.161
9 104 ms 105 ms 105 ms 150.222.112.172
10 103 ms 103 ms 104 ms 52.95.36.127
11 103 ms 104 ms 103 ms 52.95.38.160
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 102 ms 103 ms 103 ms ec2-13-210-108-126.ap-southeast-2.compute.amazonaws.com [13.210.108.126]

Trace complete.

NickMack

944 posts

Ultimate Geek

Trusted

Lifetime subscriber

#2618006 8-Dec-2020 11:02

thudb:

Anyone else finding Fortnite Oceania pings are now at ~100ms whereas they were ~20ms? Is this a 2Degrees issue?

--------

tracert qosping-aws-ap-southeast-2.ol.epicgames.com

Tracing route to qosping-aws-ap-southeast-2.ol.epicgames.com [13.210.108.126]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms RT-AC68U-9F88 [192.168.1.1]
2 2 ms 3 ms 3 ms 100.69.255.254
3 2 ms 2 ms 3 ms 198.18.10.205
4 3 ms 3 ms 3 ms 167.10.69.111.static.snap.net.nz [111.69.10.167]
5 102 ms 103 ms 103 ms 99.82.179.91
6 103 ms 103 ms 103 ms 99.82.179.90
7 * * * Request timed out.
8 103 ms 103 ms 103 ms 150.222.112.161
9 104 ms 105 ms 105 ms 150.222.112.172
10 103 ms 103 ms 104 ms 52.95.36.127
11 103 ms 104 ms 103 ms 52.95.38.160
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 102 ms 103 ms 103 ms ec2-13-210-108-126.ap-southeast-2.compute.amazonaws.com [13.210.108.126]

Trace complete.

From 2degrees network

nick@thenet-rs04:~$ ping qosping-aws-ap-southeast-2.ol.epicgames.com
PING qosping-aws-ap-southeast-2.ol.epicgames.com (13.210.108.126) 56(84) bytes of data.
64 bytes from ec2-13-210-108-126.ap-southeast-2.compute.amazonaws.com (13.210.108.126): icmp_seq=1 ttl=51 time=41.2 ms
64 bytes from ec2-13-210-108-126.ap-southeast-2.compute.amazonaws.com (13.210.108.126): icmp_seq=2 ttl=51 time=40.7 ms
64 bytes from ec2-13-210-108-126.ap-southeast-2.compute.amazonaws.com (13.210.108.126): icmp_seq=3 ttl=51 time=40.4 ms
64 bytes from ec2-13-210-108-126.ap-southeast-2.compute.amazonaws.com (13.210.108.126): icmp_seq=4 ttl=51 time=40.5 ms
64 bytes from ec2-13-210-108-126.ap-southeast-2.compute.amazonaws.com (13.210.108.126): icmp_seq=5 ttl=51 time=40.3 ms
^C
--- qosping-aws-ap-southeast-2.ol.epicgames.com ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4005ms
rtt min/avg/max/mdev = 40.376/40.678/41.296/0.373 ms

From Voyager

ping qosping-aws-ap-southeast-2.ol.epicgames.com

Pinging qosping-aws-ap-southeast-2.ol.epicgames.com [13.210.108.126] with 32 bytes of data:
Reply from 13.210.108.126: bytes=32 time=48ms TTL=44
Reply from 13.210.108.126: bytes=32 time=48ms TTL=44
Reply from 13.210.108.126: bytes=32 time=48ms TTL=44
Reply from 13.210.108.126: bytes=32 time=48ms TTL=44

Ping statistics for 13.210.108.126:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 48ms, Maximum = 48ms, Average = 48ms

Ping time looks better for me via 2degrees - Are you a CGNAT customer?

Nick

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

1 | 2 | 3 | 4 | 5 | 6