Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
24/7 office asia servers
#41
This isn't our problem, your ISP needs to fix this problem. They are doing bad routing to our datacenter. We have many people from this region with good ping to these servers.
#42
Matt, post: 92500, member: 178 Wrote:This isn't our problem, your ISP needs to fix this problem. They are doing bad routing to our datacenter. We have many people from this region with good ping to these servers.
Matt our ISP people dont know whats mean by routing then.....
#43
How do you expect us to fix it then? Out datacenter can only fix their side, they can't demand your ISP to do anything.
#44
My ping is fixed now, in Philippines i don't know how it did lol
Just Go With IT. √

 Why are you even looking here? scroll down if you can.
#45
Matt take a look at this, a tracert from my friend who is in Mumbai using MTNL.

Quote:C:\Users\Windows 7>tracert 119.81.28.242
Tracing route to 119.81.28.242-static.reverse.softlayer.com [119.81.28.242]
over a maximum of 30 hops:
1 <1 ms 1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 16 ms 14 ms 15 ms static-mum-59.185.211.205.mtnl.net.in [59.185.21
1.205]
4 17 ms 19 ms 19 ms static-mum-59.185.211.206.mtnl.net.in [59.185.21
1.206]
5 158 ms 160 ms 157 ms 221-135-253-248.sify.net [221.135.253.248]
6 158 ms 156 ms 152 ms 221-134-232-154.sify.net [221.134.232.154]
7 306 ms 306 ms 309 ms bbr01.xn01.fra01.networklayer.com [80.81.194.167
]
8 213 ms 177 ms 173 ms ae1.bbr01.tg01.lon01.networklayer.com [50.97.18.
208]
9 296 ms 296 ms 293 ms ae1.bbr02.tl01.nyc01.networklayer.com [50.97.18.
204]
10 296 ms 295 ms * ae1.bbr01.eq01.chi01.networklayer.com [173.192.1
8.132]
11 331 ms 296 ms 296 ms ae7.bbr02.eq01.chi01.networklayer.com [173.192.1
8.171]
12 307 ms 309 ms 309 ms ae1.bbr02.cs01.den01.networklayer.com [173.192.1
8.131]
13 302 ms 304 ms 305 ms ae1.bbr01.eq01.sjc02.networklayer.com [173.192.1
8.148]
14 309 ms 310 ms 315 ms ae7.bbr02.eq01.sjc02.networklayer.com [173.192.1
8.165]
15 465 ms 465 ms 464 ms ae0.bbr01.eq01.tok01.networklayer.com [50.97.18.
161]
16 498 ms 496 ms 499 ms ae1.bbr01.eq01.sng02.networklayer.com [50.97.18.
165]
17 511 ms 551 ms 512 ms ae5.dar02.sr03.sng01.networklayer.com [50.97.18.
199]
18 545 ms 498 ms 558 ms po2.fcr01.sr03.sng01.networklayer.com [174.133.1
18.133]
19 503 ms 502 ms 503 ms 119.81.28.242-static.reverse.softlayer.com [119.
81.28.242]
Trace complete.

His Ip- 120.61.34.188
#46
Lol Manky, it's high. It's your ISP having problem, just contact them already!
Just Go With IT. √

 Why are you even looking here? scroll down if you can.
#47
Can everyone with high ping traceroute these ips: 180.92.185.162 and 119.81.28.241?
Steam Wrote: 4:02 PM - George, of the jungle: was out
4:02 PM - George, of the jungle: bison, dude
4:02 PM - Brawl Bashin’ Bison: ???
4:02 PM - George, of the jungle: you're very rude towards alina
4:02 PM - George, of the jungle: how about unbanning her friend?
4:02 PM - George, of the jungle: I mean
4:02 PM - George, of the jungle: it's only gamebanana skins
4:02 PM - Brawl Bashin’ Bison: LOL
4:02 PM - George, of the jungle: ^^
4:02 PM - Brawl Bashin’ Bison: LOLOL
4:02 PM - George, of the jungle: lol
#48
Manky™, post: 92531, member: 15413 Wrote:Matt take a look at this, a tracert from my friend who is in Mumbai using MTNL.



His Ip- 120.61.34.188

I've passed this onto our datacenter, we shall see what they say.

Sibrox, post: 92542, member: 14065 Wrote:Lol Manky, it's high. It's your ISP having problem, just contact them already!

What you don't seem to understand that this is all a blame game, Softlayer (Our datacenter) blames the ISP while the ISP blames the datacenter. This makes it quite frustrating and time consuming for us in the middle trying to make it better for you guys. You need to remember that we don't get paid for this, it is all done in our free time.

In BSNL's case it is their fault, they generally have bad routes, congestion to everywhere and run a crap network.
#49
Sibrox, post: 92542, member: 14065 Wrote:Lol Manky, it's high. It's your ISP having problem, just contact them already!
It's not mine, as i mentioned this tracert is of my friend.
And if you can see the ping goes high after reaching network layer right?

M. Bison, post: 92545, member: 359 Wrote:Can everyone with high ping traceroute these ips: 180.92.185.162 and 119.81.28.241?
This is mine
Quote:C:\Users\Manky>tracert 119.81.28.241

Tracing route to 119.81.28.241-static.reverse.softlayer.com [119.81.28.241]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 * 14 ms 13 ms triband-del-59.180.210.210.bol.net.in [59.180.21
0.210]
4 * 13 ms 14 ms triband-del-59.180.210.209.bol.net.in [59.180.21
0.209]
5 * * 16 ms segment-119-226.sify.net [119.226.16.33]
6 * 209 ms 222 ms 221-134-189-190.sify.net [221.134.189.190]
7 209 ms 207 ms 209 ms 221-134-139-54.sify.net [221.134.139.54]
8 * 195 ms 193 ms 221-135-68-181.sify.net [221.135.68.181]
9 210 ms 208 ms 207 ms 221-134-232-154.sify.net [221.134.232.154]
10 * * * Request timed out.
11 * 224 ms 225 ms ae1.bbr01.tg01.lon01.networklayer.com [50.97.18.
208]
12 * 282 ms 296 ms ae1.bbr02.tl01.nyc01.networklayer.com [50.97.18.
204]
13 346 ms * 304 ms ae1.bbr01.eq01.chi01.networklayer.com [173.192.1
8.132]
14 * 304 ms 305 ms ae7.bbr02.eq01.chi01.networklayer.com [173.192.1
8.171]
15 * 329 ms 329 ms ae1.bbr02.cs01.den01.networklayer.com [173.192.1
8.131]
16 356 ms 356 ms 356 ms ae1.bbr01.eq01.sjc02.networklayer.com [173.192.1
8.148]
17 * 370 ms 357 ms ae7.bbr02.eq01.sjc02.networklayer.com [173.192.1
8.165]
18 455 ms 454 ms 454 ms ae0.bbr01.eq01.tok01.networklayer.com [50.97.18.
161]
19 * 489 ms 490 ms ae1.bbr01.eq01.sng02.networklayer.com [50.97.18.
165]
20 * 474 ms 473 ms ae5.dar01.sr03.sng01.networklayer.com [50.97.18.
197]
21 488 ms * * po1.fcr01.sr03.sng01.networklayer.com [174.133.1
18.131]
22 473 ms 475 ms 473 ms 119.81.28.241-static.reverse.softlayer.com [119.
81.28.241]

Trace complete.

C:\Users\Manky>

And i dun know what next one is Tongue LOL


Quote:C:\Users\Manky>tracert 180.92.185.162

Tracing route to 180.92.185.162 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 * 14 ms 14 ms triband-del-59.180.210.193.bol.net.in [59.180.21
0.193]
4 * 14 ms 13 ms triband-del-59.180.210.194.bol.net.in [59.180.21
0.194]
5 17 ms 18 ms 16 ms segment-119-226.sify.net [119.226.16.33]
6 208 ms 206 ms 206 ms 221-134-189-190.sify.net [221.134.189.190]
7 207 ms 212 ms 208 ms 221-134-139-54.sify.net [221.134.139.54]
8 207 ms 193 ms 193 ms 221-135-68-181.sify.net [221.135.68.181]
9 178 ms 179 ms 193 ms 221-134-211-141.sify.net [221.134.211.141]
10 * * * Request timed out.
11 * 601 ms 614 ms te0-1-0-7-gw1.lax3.asianetcom.net [202.147.58.14
4]
12 * 656 ms 644 ms te0-3-0-1.wr1.sin0.asianetcom.net [61.14.158.49]

13 * 660 ms 663 ms te0-0-4-0.wr2.sin0.asianetcom.net [61.14.157.38]

14 * 652 ms 660 ms gi6-0-0.gw2.sin1.asianetcom.net [61.14.157.114]

15 644 ms 652 ms 648 ms gi14-0-0.gw5.sin1.asianetcom.net [202.147.48.122
]
16 635 ms 637 ms 643 ms gi3-0-0.gw2.sin1.asianetcom.net [202.147.48.121]

17 619 ms 641 ms 621 ms ip-static-202-147-38-210.asianetcom.net [202.147
.38.210]
18 * 614 ms 593 ms 0.te2-1.tsr1.sin1.sg.voxel.net [107.6.120.10]
19 * 598 ms 608 ms 20.te1-1.csr1.sin1.sg.voxel.net [72.26.220.10]
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.

its all the same till 30 hops.
#50
t
M. Bison, post: 92545, member: 359 Wrote:Can everyone with high ping traceroute these ips: 180.92.185.162 and 119.81.28.241?
traceroute to the first one
Microsoft Windows [Version 6.1.7601]
Copyright © 2009 Microsoft Corporation. All rights reserved.
C:\Users\gskjain>tracert 180.92.185.162
Tracing route to 180.92.185.162 over a maximum of 30 hops
1 1 ms 1 ms 2 ms 192.168.1.1
2 26 ms 26 ms 37 ms 117.201.16.1
3 * 27 ms 27 ms 218.248.174.234
4 66 ms 64 ms 64 ms 59.163.206.177.static.chennai.vsnl.net.in [59.16
3.206.177]
5 66 ms 65 ms 65 ms 180.87.37.1
6 109 ms 125 ms * 180.87.37.14
7 107 ms 107 ms 109 ms 180.87.12.1
8 * 98 ms 100 ms 180.87.36.21
9 102 ms 107 ms 106 ms 120.29.214.2
10 97 ms * 96 ms Vlan572.icore1.SVQ-Singapore.as6453.net [120.29.
215.46]
11 98 ms 98 ms 99 ms mpr2.ge6-1.bbnet2.sin001.pnap.net [202.58.8.66]
12 241 ms 241 ms 248 ms 202.58.10.38
13 290 ms 279 ms 272 ms 21.te1-5.csr1.sin1.sg.voxel.net [72.26.220.18]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
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 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

guys see it reached singa pore in 96ms,

Double post

Rockstar, post: 92556, member: 10627 Wrote:t
traceroute to the first one
Microsoft Windows [Version 6.1.7601]
Copyright © 2009 Microsoft Corporation. All rights reserved.
C:\Users\gskjain>tracert 180.92.185.162
Tracing route to 180.92.185.162 over a maximum of 30 hops
1 1 ms 1 ms 2 ms 192.168.1.1
2 26 ms 26 ms 37 ms 117.201.16.1
3 * 27 ms 27 ms 218.248.174.234
4 66 ms 64 ms 64 ms 59.163.206.177.static.chennai.vsnl.net.in [59.16
3.206.177]
5 66 ms 65 ms 65 ms 180.87.37.1
6 109 ms 125 ms * 180.87.37.14
7 107 ms 107 ms 109 ms 180.87.12.1
8 * 98 ms 100 ms 180.87.36.21
9 102 ms 107 ms 106 ms 120.29.214.2
10 97 ms * 96 ms Vlan572.icore1.SVQ-Singapore.as6453.net [120.29.
215.46]
11 98 ms 98 ms 99 ms mpr2.ge6-1.bbnet2.sin001.pnap.net [202.58.8.66]
12 241 ms 241 ms 248 ms 202.58.10.38
13 290 ms 279 ms 272 ms 21.te1-5.csr1.sin1.sg.voxel.net [72.26.220.18]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
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 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

guys see it reached singa pore in 96ms,



guys the other one is horrible routing

Double post

this may sound stupid pls tell how to screenshot traceroutes

Users browsing this thread: 2 Guest(s)