Hi All,
I was hoping that someone that knows more than me regarding how routing works could clarify and teach me how does it actually work.
Problem:
So I have been playing Warface (online game) for many years and I always had 120 - 140ms ping to the servers.
About a month ago I realised my ping is 220ms and just left it thinking it will fix itself, but a week later it is 330ms.
It has been 330ms for the last month and nothing has changed. So I contact Warface customer support with the Diagnostics files and we realise with the traceroute that at hop 10 the ping goes up and does not have anything to do with Warface and the problem lies with my ISP.
Naturally, I contact my ISP with the same traceroute files and the explanation from Warface customer support, 3-hour phone call and multiple tests later my ISP said they are sorry the problem is not in their hands.
Clarification:
I live in New Zealand and the game server is in Singapore.
This is the traceroute results (excluding the addresses as I don't know if I can post it):
Tracing route to singapore.ping.wf.my.com
1 <1ms 1ms * <--- Me in NZ
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 141ms 141ms 144ms <--- In the US
9 162ms 162ms 162ms <--- In the US
10 * * * Request timed out.
11 360ms 360ms 360ms
12 331ms 331ms 340ms
13 331ms 332ms 331ms
14 332ms 332ms 333ms
15 331ms 331ms 331ms <--- Game in SG
Where everything goes wrong is it is routing from NZ, all the way to the US, and then all the way back to Singapore.
I am not sure if it did rout all the way to the US in the past when I had 140ms ping as I did not test it back then.
*Note: the first server in the US (line 8) has a DNS name related to my ISP
My Tests:
So if it is not my ISP causing the problem, then surely all other ISP's should have the same results.
So I did the same traceroute with other ISP's and they did not route all the way to the US and the ping was 140ms.
So how can my ISP tell me that it is not them and the problem is elsewhere?
Who decides what route my connection should take?
Why would it be 140ms one moment and then it is 330ms if nothing has changed?
I just don't understand why does it not route to Australia, then over to Singapore as that is the most direct line.
And who decides the route, the ISP, the Backbone Providers?
My System Info:
The following has been done within this month of trying to fix and test things:
Looking forward to hearing from you guys.
Kind Regards,
JPDiamond
I was hoping that someone that knows more than me regarding how routing works could clarify and teach me how does it actually work.
Problem:
So I have been playing Warface (online game) for many years and I always had 120 - 140ms ping to the servers.
About a month ago I realised my ping is 220ms and just left it thinking it will fix itself, but a week later it is 330ms.
It has been 330ms for the last month and nothing has changed. So I contact Warface customer support with the Diagnostics files and we realise with the traceroute that at hop 10 the ping goes up and does not have anything to do with Warface and the problem lies with my ISP.
Naturally, I contact my ISP with the same traceroute files and the explanation from Warface customer support, 3-hour phone call and multiple tests later my ISP said they are sorry the problem is not in their hands.
Clarification:
I live in New Zealand and the game server is in Singapore.
This is the traceroute results (excluding the addresses as I don't know if I can post it):
Tracing route to singapore.ping.wf.my.com
1 <1ms 1ms * <--- Me in NZ
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 141ms 141ms 144ms <--- In the US
9 162ms 162ms 162ms <--- In the US
10 * * * Request timed out.
11 360ms 360ms 360ms
12 331ms 331ms 340ms
13 331ms 332ms 331ms
14 332ms 332ms 333ms
15 331ms 331ms 331ms <--- Game in SG
Where everything goes wrong is it is routing from NZ, all the way to the US, and then all the way back to Singapore.
I am not sure if it did rout all the way to the US in the past when I had 140ms ping as I did not test it back then.
*Note: the first server in the US (line 8) has a DNS name related to my ISP
My Tests:
So if it is not my ISP causing the problem, then surely all other ISP's should have the same results.
So I did the same traceroute with other ISP's and they did not route all the way to the US and the ping was 140ms.
So how can my ISP tell me that it is not them and the problem is elsewhere?
Who decides what route my connection should take?
Why would it be 140ms one moment and then it is 330ms if nothing has changed?
I just don't understand why does it not route to Australia, then over to Singapore as that is the most direct line.
And who decides the route, the ISP, the Backbone Providers?
My System Info:
- Windows 10 Home
- MSI GE72 2QF Apache Pro
- Intel Core i7-5700HQ
- 16GB RAM
- Intel HD Graphics 5600
- NVIDIA GeForce GTX 970M
- Killer E2200 Network Card
- Cat6 Ethernet Cable
- NetComm Wireless Dual Band AC1600
- Gigabit Fiber Line
The following has been done within this month of trying to fix and test things:
- I have done a fresh windows re-install
- All drivers are up to date
- The router has been factory reset and set up from scratch
- ISP has given me a new Public IP
Looking forward to hearing from you guys.
Kind Regards,
JPDiamond