Strange routing to some australian services

Forums › 2degrees (including Slingshot, Orcon, Flip, Stuff Fibre, MyRepublic, 2talk and Vocus) › Strange routing to some australian services

1 | 2 | 3 | 4

2123 posts

Uber Geek

#2796938 18-Oct-2021 10:22

noroad:

That IP has some funky return path routing that is not within 2degress control, they are handing the traffic over at the closest point which is Sydney Peering. Return traffic is controlled by the game companies host. I'd suggest logging it with the game company as 2degrees has limited avenues to have this fixed. (speaking as a Network Architect of a different backbone provider, I can see the same path).

It's not just that one game that is affected

Looking to buy a Tesla? Use my referral link and we both get credits

yitz

2074 posts

Uber Geek

#2796954 18-Oct-2021 10:36

If the latency increase coincided with the Indigo West cable outage starting in the early hours of last Monday then there's probably some brain dead re-routing going on, i.e. GTT Sydney back to 2degrees has to go via SJC interconnect along with rest of traffic originating in Asia Pacific even though it could just go via the Sydney interconnect. Or the re-routing has exposed some routing anomaly. I don't think any other NZ providers use GTT for Asia Pacific routes? I can only assume 2degrees are a customer of GTT.

noroad

949 posts

Ultimate Geek

Trusted

#2796960 18-Oct-2021 10:52

yitz:

If the latency increase coincided with the Indigo West cable outage starting in the early hours of last Monday then there's probably some brain dead re-routing going on, i.e. GTT Sydney back to 2degrees has to go via SJC interconnect along with rest of traffic originating in Asia Pacific even though it could just go via the Sydney interconnect. Or the re-routing has exposed some routing anomaly. I don't think any other NZ providers use GTT for Asia Pacific routes? I can only assume 2degrees are a customer of GTT.

We (Wholesale provider Feenix) don't use GTT and we are seeing the same path. I would say the game company host is using GTT rather than 2degrees.

Obraik

2123 posts

Uber Geek

#2797037 18-Oct-2021 12:35

If that was the case, wouldn't it be affecting the game on all ISPs?

Looking to buy a Tesla? Use my referral link and we both get credits

noroad

949 posts

Ultimate Geek

Trusted

#2797040 18-Oct-2021 12:46

Obraik:

If that was the case, wouldn't it be affecting the game on all ISPs?

it is.

Obraik

2123 posts

Uber Geek

#2797045 18-Oct-2021 12:53

It's not though. On my home 2degrees connection that endpoint that the OP listed has a ping of 133ms while on my corporate internet connection it has a ping of 46ms - even on my phones Vodafone 4G connection it has a ping of 60ms. It's a 2degrees issue.

Looking to buy a Tesla? Use my referral link and we both get credits

MaxineN

Max
1772 posts

Uber Geek

ID Verified

Trusted

Subscriber

#2797050 18-Oct-2021 13:01

noroad:

Obraik:

If that was the case, wouldn't it be affecting the game on all ISPs?

it is.

Gonna disagree.

Vocus says no we're gonna take a direct path and go right to Sydney.

Seeing no mention of GTT either.

(I am not a network expert)

Ramblings from a mysterious lady who's into tech. Warning I may often create zingers.

Equinox IT

Cloud spending continues to surge globally, but most organisations haven’t made the changes necessary to maximise the value and cost-efficiency benefits of their cloud investments. Download the whitepaper From Overspend to Advantage now.

noroad

949 posts

Ultimate Geek

Trusted

#2797055 18-Oct-2021 13:08

Obraik:

It's a 2degrees issue.

Its definitely not a 2degrees issue -

[root@titan ~]# traceroute 103.124.186.201
traceroute to 103.124.186.201 (103.124.186.201), 30 hops max, 60 byte packets
1 103-208-140-185.feenix.co.nz (103.208.140.185) 0.321 ms 0.294 ms 0.376 ms
2 * * *
3 as4826.sydney.megaport.com (103.26.68.248) 25.119 ms 25.110 ms 25.117 ms
4 be115.cor02.syd04.nsw.vocus.network (114.31.192.56) 25.043 ms be115.cor01.syd11.nsw.vocus.network (114.31.192.58) 25.059 ms 25.067 ms
5 be100.bdr02.syd03.nsw.vocus.network (114.31.192.39) 25.034 ms 25.305 ms 25.336 ms
6 static-118.111.255.49.in-addr.VOCUS.net.au (49.255.111.118) 24.889 ms 24.782 ms 24.797 ms
7 ip4.gtt.net (69.174.126.10) 120.514 ms 120.521 ms 120.418 ms
8 oldschool92.runescape.com (103.124.186.201) 120.470 ms 120.447 ms 120.419 ms
[root@titan ~]#

Just because "it works on ISP X and not ISP Y" does not mean ISP X has any control over the reverse path traffic. The Internet is a collection of 860,552 (as of last week) ipv4 networks (and 71,880 ISP ASN's) networks interconnected together. Your ISP controls a very small part of it.

Obraik

2123 posts

Uber Geek

#2797063 18-Oct-2021 13:32

Yeah, but it's also not just this Runescape game server that's an issue. AWS endpoints are also suffering increased latency. AWS in Singapore currently has a latency of around 293ms on my home 2degrees connection whereas on the other connections I mentioned it's sitting around 130ms - prior to last week the latency via 2degrees to this location was around the same. Similar story with AWS Korea, AWS Tokyo, etc

Looking to buy a Tesla? Use my referral link and we both get credits

noroad

949 posts

Ultimate Geek

Trusted

#2797067 18-Oct-2021 13:35

Obraik:

Yeah, but it's also not just this Runescape game server that's an issue. AWS endpoints are also suffering increased latency. AWS in Singapore currently has a latency of around 293ms on my home 2degrees connection whereas on the other connections I mentioned it's sitting around 130ms - prior to last week the latency via 2degrees to this location was around the same. Similar story with AWS Korea, AWS Tokyo, etc

Yea, the Indigo West cable (Sydney-Singapore) has been down since the 11th, ETA for repair is supposed to be some time today, hopefully.

yitz

2074 posts

Uber Geek

#2797095 18-Oct-2021 14:03

In the case of Old School Runescape, Vocus 9790 have peerings with both Level 3 and GTT so have good chance of short routes. Spark and Vodafone both have Level 3 peering and have direct routes too. It is when you don't have a direct relationship with Level 3 or GTT then the chances are higher of a bad route. But in saying that even Devoli are good via Telstra...

2degrees had a lot of Asian traffic coming in via Singapore/Hong Kong link via Perth to Sydney through GTT before the cable went out, that is say they had some sort of transit arrangement... so one can only assume they do have a relationship with GTT in Sydney. If OSRS also use GTT then it's all a bit sad really that there is no direct route.

yitz

2074 posts

Uber Geek

#2797098 18-Oct-2021 14:07

By the way that www.globaltraceroute.com site is quite handy, you can run traceroutes from RIPE Atlas nodes behind many NZ providers.

Mahon

473 posts

Ultimate Geek

#2798085 20-Oct-2021 11:06

Traffic routing seems to have returned to normal last night. Good job.

Obraik

2123 posts

Uber Geek

#2798205 20-Oct-2021 15:14

While the endpoint mentioned by OP now looks good, I'm still getting terrible latency to locations in SEA (AWS locations in this case). "dynamodb.ap-southeast-1.amazonaws.com" is an example for Singapore:

Tracing route to dynamodb.ap-southeast-1.amazonaws.com [52.94.11.144]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms edge.fortress.local [192.168.0.202]
2 3 ms 5 ms 6 ms 12.7.69.111.static.snap.net.nz [111.69.7.12]
3 * * * Request timed out.
4 45 ms 40 ms 40 ms ip4.gtt.net [67.199.137.170]
5 40 ms 40 ms 41 ms ip4.gtt.net [67.199.137.169]
6 255 ms 255 ms 255 ms xe-5-2-3.cr0-tyo1.ip4.gtt.net [141.136.105.62]
7 203 ms 202 ms 202 ms 16509.tyo.equinix.com [203.190.230.116]
8 231 ms 231 ms 236 ms 54.239.53.192
9 * * * Request timed out.
10 232 ms 231 ms 230 ms 54.239.52.99
11 229 ms 230 ms 233 ms 52.95.30.12
12 * * * Request timed out.
13 288 ms 288 ms 288 ms 150.222.244.87
14 * * * Request timed out.
15 290 ms 289 ms 289 ms 52.93.8.110
16 284 ms 283 ms 283 ms 52.93.8.119
17 283 ms 284 ms 283 ms 52.93.10.81
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 290 ms 288 ms 290 ms 52.94.11.144

Looking to buy a Tesla? Use my referral link and we both get credits

Josh12345

16 posts

Geek

#2798223 20-Oct-2021 15:43

While I'm glad this seems to be resolved for some people, I'm the OP of this thread and am still seeing the same issue. I have a static IP in the 123.255.x.x range and am still seeing the same behavior I originally posted.

Tracing route to l3ausy5-bond0-5.jagex.com [103.124.186.201]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms fritz.box [192.168.178.1]
2 7 ms <1 ms 1 ms 226.7.69.111.static.snap.net.nz [111.69.7.226]
3 * * * Request timed out.
4 55 ms 52 ms 44 ms as23655.sydney.megaport.com [103.26.68.14]
5 45 ms 45 ms 45 ms as4826.sydney.megaport.com [103.26.68.248]
6 56 ms 44 ms 44 ms be115.cor02.syd04.nsw.vocus.network [114.31.192.56]
7 45 ms 44 ms 45 ms be101.bdr02.syd03.nsw.vocus.network [114.31.192.37]
8 45 ms 45 ms 45 ms static-118.111.255.49.in-addr.VOCUS.net.au [49.255.111.118]
9 133 ms 131 ms 132 ms ip4.gtt.net [69.174.126.10]
10 132 ms 131 ms 132 ms oldschool92.runescape.com [103.124.186.201]

Any further updates would be appreciated.

1 | 2 | 3 | 4