TR Forums

Hi guys. I just want to ask about my problem. Last day, when i tracerouted my connection to a game (dota 2) this is my results, and it was very wonderful.

Here is my first tracert result:

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\xXx>tracert 103.28.54.1

Tracing route to sgp-1.valve.net [103.28.54.1]
over a maximum of 30 hops:

1 <2 ms <2 ms <2 ms 192.168.0.1
2 3 ms 2 ms 2 ms 192.168.1.1
3 26 ms 25 ms 25 ms 119.94.96.1.static.pldt.net [49.147.160.1]
4 24 ms 24 ms 24 ms 122.2.135.37.pldt.net [122.2.135.37]
5 47 ms 45 ms 45 ms 210.213.135.17.static.pldt.net [210.213.135.17]

6 46 ms 46 ms 45 ms 210.213.128.29.static.pldt.net [210.213.128.29]

7 45 ms 44 ms 43 ms 210.213.130.9.static.pldt.net [210.213.130.9]
8 84 ms 86 ms 82 ms 203.117.37.81
9 85 ms 85 ms 85 ms an-uts-int12.starhub.net.sg [203.118.15.97]
10 85 ms 86 ms 85 ms 203.118.15.186
11 84 ms 83 ms 84 ms an-ats-loc10.starhub.net.sg [203.118.15.190]
12 86 ms 85 ms 85 203.116.8.22
13 84 ms 85 ms 84 ms sgp-1.valve.net [103.28.54.1]

Trace complete.

C:\Users\xXx>

and my second tracert is here:

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\xXx>tracert 103.28.54.1

Tracing route to sgp-1.valve.net [103.28.54.1]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 1 ms 1 ms 1 ms 192.168.1.1
3 24 ms 22 ms 26 ms dsl.49.148.160.1.pldt.net [49.147.160.1]
4 23 ms 22 ms 23 ms 122.2.135.37.pldt.net [122.2.135.37]
5 45 ms 46 ms 44 ms 210.213.135.17.static.pldt.net [210.213.135.17]

6 45 ms 45 ms 43 ms 210.213.128.33.static.pldt.net [210.213.128.33]

7 43 ms 43 ms 43 ms 210.213.130.9.static.pldt.net [210.213.130.9]
8 231 ms 230 ms 229 ms 203.117.37.81
9 226 ms 232 ms 225 ms an-uts-int12.starhub.net.sg [203.118.15.97]
10 228 ms 227 ms 226 ms 203.118.15.186
11 223 ms 222 ms 222 ms an-ats-loc10.starhub.net.sg [203.118.15.190]
12 * 223 ms * 203.116.8.22
13 223 ms 224 ms 224 ms sgp-1.valve.net [103.28.54.1]

Trace complete.

C:\Users\xXx>


As you can see, the line 3 of both tracerts are showing different ip. Yes, i know that it is my external ip it is dynamic and it has been reset when i put off the modem for about 3 hours, and when it came back, i noticed that it has changed, and i want to get back at that ip address so that i think, i could use the best routing going to starhub using that ip address. i called then my isp if it is possible that they could provide me that ip again, but they said they cant, instead, they instructed me to try again to renew/release my ip or turn off the modem for about 30 seconds then put it on back again. my question is, would it be possible? to get back on that ip? that ip really saves my ping in dota 2.

Now, i know our ISP really serves well in terms of gaming, its just now that they had some difficulties in their servers, lasting for almost 4 months now, they have great product, but poor customer service, thats why im holding on to this hope that there is still good left remaining in their server capacity right now, because their real problem is the capacity of their lines going on to Singapore servers (STARHUB) thats why dota 2 latency is high ping, but the rest of their service is brilliant, its just really dota 2 they are having problems, and they refuse to upgrade, because they dont give a **** to dota players. please help me clarify this if it is possible to get back by any means in this ping? because i also remember i saw a post in another forum that this ip really saved his ass. he said he just release or renew ip until he gets his luck, and then goes in game and play happily. thank you guys...

Actually, the IP at hop 3 is the same in both cases: 49.147.160.1 (the thing in brackets at the end of the line). The only thing that appears to have changed at hop 3 is the reverse DNS entry, which has no effect on latency.

It does look like you went through a different router at hop 6, but that's not where the delay is happening either. The delay appears to be at hop 8. I see no evidence from the output you posted that your dynamic IP even changed; the only things which appear to be different are one hop deep in the network somewhere, and high latency at another router further along the route.

And no, if you're on dynamic IP there isn't anything you can do to force reallocation of a specific IP. Your old IP (assuming it actually changed, I'm not even convinced that it did in your case) has probably been reassigned to someone else already. Even if you reset the modem most DHCP servers will preferentially hand you the same IP again.

Dynamic IP is completely irrelevant anyway since the trace output is indicating that the problem isn't at your end, it is way out in the network. Pldt.net is located in the Philippines and starhub.net.sg is in Singapore; the jump in latency appears to be happening at the point where traffic is being handed off from pldt.net to starhub.net.sg. This really looks like a problem with the backbone link your ISP is using to route traffic to/from Singapore. For whatever reason, that link is slow/congested today (but wasn't yesterday).

If the problem is on the starhub.net.sg side, this may not even be something your ISP has control over...

Unless you are using source-routing, why are aren't, you have exactly no control over the routing choices made from your ISP. And your DHCP assigned IP doesn't matter in the slightest unless it's on a fully different network somehow announced from your ISP on a different way. In theory it is possible, in practice, if you have trouble, you call your ISP and they have to check their link to starhub. Because if you are on pldt, it certainly seems that they had a problem reaching starhub at that particular time.

The cause for that can be anything from a broken link, to congestion, to a oversubscriped or underpowered router. In your case, I would assume some form of either congestion or underpowered router on the starhub side since the higher latency is between hop 7 and 8, which are both the same for your traces. So your assigned IP really doesn't matter one bit, the link and congestion between hop 7 and 8 does.