Jan 14 2013, 04:19 AM
Feb 08 2013, 04:00 PM
Matt, post: 83885, member: 178 Wrote:There's been multiple undersea cables cut. The eta on cable repairs is sometime this month.Yeah, now i know. Bison told me when i posted here.
Double post
Matt, post: 83625, member: 178 Wrote:An update for Sako.Matt sako's trace route again ping not fixed still.
1 <1 ms <1 ms <1 ms 192.168.2.1
2 10 ms 20 ms 10 ms 121.96.4.31
3 30 ms 31 ms 31 ms 121.96.7.34
4 31 ms 29 ms 29 ms 121.96.7.34
5 30 ms 34 ms 33 ms 121.96.7.17
6 140 ms 144 ms 124 ms 121.96.7.21
7 30 ms 41 ms 30 ms 202.78.119.9
8 253 ms 272 ms 264 ms gige-g4-9.core1.lax2.he.net [184.105.79.89]
9 * * * Request timed out.
10 220 ms 261 ms 220 ms ae7.bbr02.cs01.lax01.networklayer.com [173.192.1
8.167]
11 260 ms 235 ms 231 ms ae0.bbr02.eq01.sjc02.networklayer.com [173.192.1
8.150]
12 223 ms 221 ms 222 ms ae0.bbr01.eq01.tok01.networklayer.com [50.97.18.
161]
13 217 ms 217 ms 266 ms ae7.bbr02.eq01.tok01.networklayer.com [50.97.18.
163]
14 224 ms 222 ms 223 ms ae0.bbr01.pn01.hkg01.networklayer.com [50.97.18.
167]
15 217 ms 218 ms 219 ms ae7.bbr02.pn01.hkg01.networklayer.com [50.97.18.
175]
16 251 ms 253 ms 251 ms ae0.bbr02.eq01.sng02.networklayer.com [50.97.18.
172]
17 247 ms 247 ms 261 ms ae6.dar01.sr03.sng01.networklayer.com [50.97.18.
201]
18 253 ms 254 ms 251 ms po1.fcr01.sr03.sng01.networklayer.com [174.133.1
18.131]
19 252 ms 251 ms 251 ms 119.81.28.242-static.reverse.softlayer.com [119.
81.28.242]
Trace complete.
Feb 09 2013, 05:22 AM
idk why but nowadays i am getting a bit lesser ping in the asia server.....it WAS always 600+ before not its 350-450.......(i know it is also not low ping...
Feb 09 2013, 06:10 AM
Trace route it if you're curious, your old trace route is still here so you will be able to see whats changed.
Manky I don't think the cable repairs have been complete yet as I am also still getting high ping.
Manky I don't think the cable repairs have been complete yet as I am also still getting high ping.
Feb 09 2013, 01:10 PM
Matt, post: 85871, member: 178 Wrote:Trace route it if you're curious, your old trace route is still here so you will be able to see whats changed.oh okay, i thought cables were repaired.
Manky I don't think the cable repairs have been complete yet as I am also still getting high ping.
Feb 09 2013, 02:53 PM
Tracing route to 119.81.28.240-static.reverse.softlayer.com [119.81.28.240]
over a maximum of 30 hops:
1 <1 ms 1 ms <1 ms dsldevice.domain.name [192.168.1.1]
2 23 ms 25 ms 21 ms 115.147.68.1
3 30 ms 24 ms 23 ms 124.217.124.165
4 24 ms 23 ms 24 ms 124.217.126.153
5 23 ms 23 ms 23 ms 124.217.126.162
6 26 ms 24 ms 24 ms 202.138.144.197
7 23 ms 25 ms 23 ms 202.138.145.245
8 23 ms 23 ms 26 ms 202.138.145.250
9 45 ms 45 ms 46 ms 202.138.145.205
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 115 ms 105 ms 106 ms 119.81.28.240-static.reverse.softlayer.com [119.
81.28.240]
my ping is now back to 100-115ms. I guess the route to LA is gone now.
over a maximum of 30 hops:
1 <1 ms 1 ms <1 ms dsldevice.domain.name [192.168.1.1]
2 23 ms 25 ms 21 ms 115.147.68.1
3 30 ms 24 ms 23 ms 124.217.124.165
4 24 ms 23 ms 24 ms 124.217.126.153
5 23 ms 23 ms 23 ms 124.217.126.162
6 26 ms 24 ms 24 ms 202.138.144.197
7 23 ms 25 ms 23 ms 202.138.145.245
8 23 ms 23 ms 26 ms 202.138.145.250
9 45 ms 45 ms 46 ms 202.138.145.205
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 115 ms 105 ms 106 ms 119.81.28.240-static.reverse.softlayer.com [119.
81.28.240]
my ping is now back to 100-115ms. I guess the route to LA is gone now.
Feb 10 2013, 02:39 AM
ALING KURING SARI SARI STORE, post: 85890, member: 1732 Wrote:Tracing route to 119.81.28.240-static.reverse.softlayer.com [119.81.28.240]are you sure they will not take that route again ? there are isps that do random routing o.O
over a maximum of 30 hops:
1 <1 ms 1 ms <1 ms dsldevice.domain.name [192.168.1.1]
2 23 ms 25 ms 21 ms 115.147.68.1
3 30 ms 24 ms 23 ms 124.217.124.165
4 24 ms 23 ms 24 ms 124.217.126.153
5 23 ms 23 ms 23 ms 124.217.126.162
6 26 ms 24 ms 24 ms 202.138.144.197
7 23 ms 25 ms 23 ms 202.138.145.245
8 23 ms 23 ms 26 ms 202.138.145.250
9 45 ms 45 ms 46 ms 202.138.145.205
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 115 ms 105 ms 106 ms 119.81.28.240-static.reverse.softlayer.com [119.
81.28.240]
my ping is now back to 100-115ms. I guess the route to LA is gone now.
Double post
Matt, post: 85871, member: 178 Wrote:Trace route it if you're curious, your old trace route is still here so you will be able to see whats changed.but matt i don't understand why KOYA's ping is fixed but not Sako's. As both live in [SIZE=30px]Philippines[/SIZE]
Manky I don't think the cable repairs have been complete yet as I am also still getting high ping.
Feb 10 2013, 03:43 AM
it has been the same for two weeks now, so i don't know in the future
Feb 10 2013, 04:15 AM
Manky maybe Sako should try contacting the ISP. If they're on different ISP's doesn't mean they will use the same path to the server.
Feb 10 2013, 02:42 PM
Matt, post: 85914, member: 178 Wrote:Manky maybe Sako should try contacting the ISP. If they're on different ISP's doesn't mean they will use the same path to the server.Her ping is fixed now is yours?