Upvote Upvoted 0 Downvote Downvoted
Ping issues?
posted in Q/A Help
1
#1
jrod
0 Frags – +

I'm using Comanglia's config and for some reason i've started getting better ping to the firepowered mge virginia server and now i'm getting 130 ping to the phoenix one (i normally get 20). I live in California, i have no idea why this is happening to me. It still get good ping to LA servers, and nobody else on the phoenix server is getting ping issues.

I'm using Comanglia's config and for some reason i've started getting better ping to the firepowered mge virginia server and now i'm getting 130 ping to the phoenix one (i normally get 20). I live in California, i have no idea why this is happening to me. It still get good ping to LA servers, and nobody else on the phoenix server is getting ping issues.
posted about 8 years ago
2
#2
daily
3 Frags – +

It sounds like some odd routing issues with your ISP. See what trip your packets take by running a traceroute to the Phoenix server you're talking about. If it moves all around the country instead of taking a somewhat straight trip to your destination (because you're close) then be prepared to call.

It sounds like some odd routing issues with your ISP. See what trip your packets take by running a [url=http://www.passionateaboutit.net/KnowledgeBase/tabid/113/EntryId/52/how-to-perform-a-traceroute-in-microsoft-windows-7.aspx]traceroute[/url] to the Phoenix server you're talking about. If it moves all around the country instead of taking a somewhat straight trip to your destination (because you're close) then be prepared to call.
posted about 8 years ago
3
#3
jrod
0 Frags – +

Ok should i post the information here so that you can see it?

Ok should i post the information here so that you can see it?
posted about 8 years ago
4
#4
daily
1 Frags – +

You can if you'd like, just be sure to remove your IP address from the output. It should be the 2nd hop, right after your local address (which is probably in the 192.168.*.* range).

You can if you'd like, just be sure to remove your IP address from the output. It should be the 2nd hop, right after your local address (which is probably in the 192.168.*.* range).
posted about 8 years ago
5
#5
jrod
0 Frags – +

C:\WINDOWS\System32>tracert 23.235.225.106

Tracing route to e3-1230v2.bl-ash0.1.1.2.5.b3.securedservers.com [23.235.225.106]
over a maximum of 30 hops:

1 2 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 9 ms 5 ms 6 ms **.***.**.*
3 11 ms 8 ms 10 ms 172.102.102.30
4 10 ms 7 ms 9 ms ae8---0.scr01.lsan.ca.frontiernet.net [74.40.3.37]
5 53 ms 54 ms 52 ms ae4---0.scr01.chcg.il.frontiernet.net [74.40.5.177]
6 53 ms 54 ms 54 ms ae0---0.cbr02.chcg.il.frontiernet.net [74.40.5.173]
7 * 60 ms 52 ms lag-105.ear3.Chicago2.Level3.net [4.16.38.117]
8 * * * Request timed out.
9 75 ms 71 ms 70 ms CWIE-LLC.ear2.Washington1.Level3.net [4.59.144.202]
10 * * * Request timed out.
11 * * * Request timed out.
12 70 ms 73 ms 71 ms e3-1230v2.bl-ash0.1.1.2.5.b3.securedservers.com [23.235.225.106]

Trace complete.

C:\WINDOWS\System32>tracert 23.235.225.106

Tracing route to e3-1230v2.bl-ash0.1.1.2.5.b3.securedservers.com [23.235.225.106]
over a maximum of 30 hops:

1 2 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 9 ms 5 ms 6 ms **.***.**.*
3 11 ms 8 ms 10 ms 172.102.102.30
4 10 ms 7 ms 9 ms ae8---0.scr01.lsan.ca.frontiernet.net [74.40.3.37]
5 53 ms 54 ms 52 ms ae4---0.scr01.chcg.il.frontiernet.net [74.40.5.177]
6 53 ms 54 ms 54 ms ae0---0.cbr02.chcg.il.frontiernet.net [74.40.5.173]
7 * 60 ms 52 ms lag-105.ear3.Chicago2.Level3.net [4.16.38.117]
8 * * * Request timed out.
9 75 ms 71 ms 70 ms CWIE-LLC.ear2.Washington1.Level3.net [4.59.144.202]
10 * * * Request timed out.
11 * * * Request timed out.
12 70 ms 73 ms 71 ms e3-1230v2.bl-ash0.1.1.2.5.b3.securedservers.com [23.235.225.106]

Trace complete.
posted about 8 years ago
6
#6
daily
2 Frags – +

It looks like you did a traceroute on the Virginia server.

It looks like you did a traceroute on the Virginia server.
posted about 8 years ago
7
#7
jrod
0 Frags – +

C:\WINDOWS\System32>tracert 198.15.79.195

Tracing route to 198.15.79.195 over a maximum of 30 hops

1 1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 8 ms 4 ms 10 ms **.***.**.*
3 14 ms 18 ms 6 ms 172.102.106.202
4 18 ms 7 ms 7 ms ae8---0.scr02.lsan.ca.frontiernet.net [74.40.3.49]
5 9 ms 8 ms 8 ms ae3---0.scr01.lsan.ca.frontiernet.net [74.40.3.205]
6 54 ms 54 ms 64 ms ae4---0.scr01.chcg.il.frontiernet.net [74.40.5.177]
7 53 ms 54 ms 52 ms ae0---0.cbr02.chcg.il.frontiernet.net [74.40.5.173]
8 * * 54 ms lag-105.ear3.Chicago2.Level3.net [4.16.38.117]
9 * * * Request timed out.
10 115 ms 101 ms 96 ms CWIE-LLC.ear2.Washington1.Level3.net [4.59.144.70]
11 123 ms 120 ms 120 ms 64.38.239.4
12 120 ms 119 ms 119 ms 108.170.0.37
13 * * * Request timed out.
14 119 ms 123 ms 119 ms 198.15.79.195

Trace complete.
sorry lol

C:\WINDOWS\System32>tracert 198.15.79.195

Tracing route to 198.15.79.195 over a maximum of 30 hops

1 1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 8 ms 4 ms 10 ms **.***.**.*
3 14 ms 18 ms 6 ms 172.102.106.202
4 18 ms 7 ms 7 ms ae8---0.scr02.lsan.ca.frontiernet.net [74.40.3.49]
5 9 ms 8 ms 8 ms ae3---0.scr01.lsan.ca.frontiernet.net [74.40.3.205]
6 54 ms 54 ms 64 ms ae4---0.scr01.chcg.il.frontiernet.net [74.40.5.177]
7 53 ms 54 ms 52 ms ae0---0.cbr02.chcg.il.frontiernet.net [74.40.5.173]
8 * * 54 ms lag-105.ear3.Chicago2.Level3.net [4.16.38.117]
9 * * * Request timed out.
10 115 ms 101 ms 96 ms CWIE-LLC.ear2.Washington1.Level3.net [4.59.144.70]
11 123 ms 120 ms 120 ms 64.38.239.4
12 120 ms 119 ms 119 ms 108.170.0.37
13 * * * Request timed out.
14 119 ms 123 ms 119 ms 198.15.79.195

Trace complete.
sorry lol
posted about 8 years ago
8
#8
daily
0 Frags – +

So it looks like you start having issues at hop 8 and possibly 9. Are those results more or less consistent when you run more traceroutes on the same server?

So it looks like you start having issues at hop 8 and possibly 9. Are those results more or less consistent when you run more traceroutes on the same server?
posted about 8 years ago
9
#9
jrod
0 Frags – +

Did it 2 more times

Show Content
C:\WINDOWS\System32>tracert 198.15.79.195

Tracing route to 198.15.79.195 over a maximum of 30 hops

1 2 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 6 ms 7 ms 5 ms
3 10 ms 11 ms 7 ms 172.102.106.202
4 8 ms 7 ms 6 ms ae8---0.scr02.lsan.ca.frontiernet.net [74.40.3.49]
5 10 ms 9 ms 7 ms ae3---0.scr01.lsan.ca.frontiernet.net [74.40.3.205]
6 53 ms 53 ms 68 ms ae4---0.scr01.chcg.il.frontiernet.net [74.40.5.177]
7 61 ms 56 ms 52 ms ae0---0.cbr02.chcg.il.frontiernet.net [74.40.5.173]
8 * 54 ms 54 ms lag-105.ear3.Chicago2.Level3.net [4.16.38.117]
9 * 71 ms 70 ms ae-2-3601.ear2.Washington1.Level3.net [4.69.206.73]
10 71 ms 86 ms 73 ms CWIE-LLC.ear2.Washington1.Level3.net [4.59.144.70]
11 130 ms 124 ms 124 ms 64.38.239.4
12 121 ms 128 ms 119 ms 108.170.0.37
13 * * * Request timed out.
14 118 ms 119 ms 119 ms 198.15.79.195

Trace complete.

C:\WINDOWS\System32>tracert 198.15.79.195

Tracing route to 198.15.79.195 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 5 ms 4 ms 5 ms 47.148.96.1
3 8 ms 7 ms 10 ms 172.102.106.202
4 7 ms 7 ms 7 ms ae8---0.scr02.lsan.ca.frontiernet.net [74.40.3.49]
5 8 ms 7 ms 14 ms ae3---0.scr01.lsan.ca.frontiernet.net [74.40.3.205]
6 52 ms 53 ms 52 ms ae4---0.scr01.chcg.il.frontiernet.net [74.40.5.177]
7 53 ms 56 ms 54 ms ae0---0.cbr02.chcg.il.frontiernet.net [74.40.5.173]
8 53 ms 54 ms 54 ms lag-105.ear3.Chicago2.Level3.net [4.16.38.117]
9 * * * Request timed out.
10 114 ms 97 ms 98 ms CWIE-LLC.ear2.Washington1.Level3.net [4.59.144.70]
11 133 ms 122 ms 123 ms 64.38.239.4
12 128 ms 121 ms 123 ms 108.170.0.37
13 * * * Request timed out.
14 118 ms 118 ms 123 ms 198.15.79.195

Trace complete.
Did it 2 more times
[spoiler]C:\WINDOWS\System32>tracert 198.15.79.195

Tracing route to 198.15.79.195 over a maximum of 30 hops

1 2 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 6 ms 7 ms 5 ms
3 10 ms 11 ms 7 ms 172.102.106.202
4 8 ms 7 ms 6 ms ae8---0.scr02.lsan.ca.frontiernet.net [74.40.3.49]
5 10 ms 9 ms 7 ms ae3---0.scr01.lsan.ca.frontiernet.net [74.40.3.205]
6 53 ms 53 ms 68 ms ae4---0.scr01.chcg.il.frontiernet.net [74.40.5.177]
7 61 ms 56 ms 52 ms ae0---0.cbr02.chcg.il.frontiernet.net [74.40.5.173]
8 * 54 ms 54 ms lag-105.ear3.Chicago2.Level3.net [4.16.38.117]
9 * 71 ms 70 ms ae-2-3601.ear2.Washington1.Level3.net [4.69.206.73]
10 71 ms 86 ms 73 ms CWIE-LLC.ear2.Washington1.Level3.net [4.59.144.70]
11 130 ms 124 ms 124 ms 64.38.239.4
12 121 ms 128 ms 119 ms 108.170.0.37
13 * * * Request timed out.
14 118 ms 119 ms 119 ms 198.15.79.195

Trace complete.


C:\WINDOWS\System32>tracert 198.15.79.195

Tracing route to 198.15.79.195 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 5 ms 4 ms 5 ms 47.148.96.1
3 8 ms 7 ms 10 ms 172.102.106.202
4 7 ms 7 ms 7 ms ae8---0.scr02.lsan.ca.frontiernet.net [74.40.3.49]
5 8 ms 7 ms 14 ms ae3---0.scr01.lsan.ca.frontiernet.net [74.40.3.205]
6 52 ms 53 ms 52 ms ae4---0.scr01.chcg.il.frontiernet.net [74.40.5.177]
7 53 ms 56 ms 54 ms ae0---0.cbr02.chcg.il.frontiernet.net [74.40.5.173]
8 53 ms 54 ms 54 ms lag-105.ear3.Chicago2.Level3.net [4.16.38.117]
9 * * * Request timed out.
10 114 ms 97 ms 98 ms CWIE-LLC.ear2.Washington1.Level3.net [4.59.144.70]
11 133 ms 122 ms 123 ms 64.38.239.4
12 128 ms 121 ms 123 ms 108.170.0.37
13 * * * Request timed out.
14 118 ms 118 ms 123 ms 198.15.79.195

Trace complete.[/spoiler]
posted about 8 years ago
10
#10
daily
0 Frags – +

After looking at this, it's looks like a problem on their (server's) side. You're getting out of your ISP's network just fine.

I think it's just a waiting game. Maybe tomorrow or even sooner it'll go back to normal.

After looking at this, it's looks like a problem on their (server's) side. You're getting out of your ISP's network just fine.

I think it's just a waiting game. Maybe tomorrow or even sooner it'll go back to normal.
posted about 8 years ago
11
#11
jrod
0 Frags – +
dailyAfter looking at this, it's looks like a problem on their (server's) side. You're getting out of your ISP's network just fine.

I think it's just a waiting game. Maybe tomorrow or even sooner it'll go back to normal.

Thank you, it's all better now, back at 20 ping.

[quote=daily]After looking at this, it's looks like a problem on their (server's) side. You're getting out of your ISP's network just fine.

I think it's just a waiting game. Maybe tomorrow or even sooner it'll go back to normal.[/quote]
Thank you, it's all better now, back at 20 ping.
posted about 8 years ago
12
#12
daily
0 Frags – +
VulcandailyAfter looking at this, it's looks like a problem on their (server's) side. You're getting out of your ISP's network just fine.

I think it's just a waiting game. Maybe tomorrow or even sooner it'll go back to normal.Thank you, it's all better now, back at 20 ping.

Good to hear. Frag on.

[quote=Vulcan][quote=daily]After looking at this, it's looks like a problem on their (server's) side. You're getting out of your ISP's network just fine.

I think it's just a waiting game. Maybe tomorrow or even sooner it'll go back to normal.[/quote]
Thank you, it's all better now, back at 20 ping.[/quote]

Good to hear. Frag on.
posted about 8 years ago
Please sign in through STEAM to post a comment.