Форум сервера Counter-Strike компании IPTelecom
- Вы не зашли.
Объявление
#1 05.07.2011 20:34:56
Ping Problem...
guys i dont know what has happened but in the afternoon i got redirected due to high ping from high latency server.....previously my ping remained between the range 230-260......but now when i connect to it the ping goes to 450 to 500....and the funny thing is that the server to which i am redirected there my ping is 250-260.......so what is the problem????any idea....
Отсутствует
#2 05.07.2011 20:44:30
Re: Ping Problem...
Start - Run - cmd.exe
tracert cs.iptcom.net
right mouse click - Select - select all command output, press Enter and paste on forum
Пых безусловно во всем прав. Почему, спросите Вы? Да просто потому, что Пых ВСЕГДА и БЕЗУСЛОВНО во всем прав© Pepper
----------------------------------------------------------------------
Не комментирую, умные не нуждаются, тупые не поймут©
Отсутствует
#3 05.07.2011 20:51:01
Re: Ping Problem...
looks bad...but how come just in a day my ping now goes from 250+ to 500+...?
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\LuL>tracert cs.iptcom.net
Tracing route to cs.iptcom.net [212.9.224.163]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 87 ms 62 ms 54 ms 10.130.0.3
4 71 ms 58 ms 54 ms 58-27-175-148.wateen.net [58.27.175.148]
5 66 ms 58 ms 59 ms 58-27-175-148.wateen.net [58.27.175.148]
6 67 ms 59 ms 58 ms 58-27-175-130.wateen.net [58.27.175.130]
7 81 ms 69 ms 58 ms 58-27-209-54.wateen.net [58.27.209.54]
8 75 ms 74 ms 103 ms 58-27-183-230.wateen.net [58.27.183.230]
9 80 ms 64 ms 59 ms 58-27-183-75.wateen.net [58.27.183.75]
10 186 ms 184 ms 168 ms tw31-static109.tw1.com [117.20.31.109]
11 186 ms 178 ms 169 ms tw112-static205.tw1.com [221.132.112.205]
12 197 ms 184 ms 193 ms atm9-0-0.1877.gw2.par4.alter.net [194.98.61.173]
13 195 ms 189 ms 229 ms so-3-0-0.XT1.PAR2.ALTER.NET [146.188.9.25]
14 196 ms 193 ms 179 ms POS2-0.BR1.PAR2.ALTER.NET [146.188.8.118]
15 556 ms 639 ms 714 ms PAR.glbx.net [146.188.112.118]
16 491 ms 499 ms 499 ms ae0-20G.scr1.CDG2.gblx.net [67.16.129.194]
17 515 ms 539 ms 518 ms ae4.scr4.FRA4.gblx.net [67.16.146.14]
18 511 ms 508 ms 510 ms lag2.ar4.fra4.gblx.net [67.16.145.242]
19 562 ms 559 ms 554 ms UCOMLINE-JSC.Te7-3.ar3.FRA4.gblx.net [64.215.181.146]
20 516 ms 519 ms 519 ms core-0-wsx670410ge-3-2-212dot1q.kiev.ucomline.net [213.130.30.169]
21 561 ms 544 ms 554 ms metro-gw1.kiev.ucomline.net [93.178.204.206]
22 731 ms 548 ms 549 ms catagi01-ext.optima.ua [62.221.50.4]
23 557 ms 543 ms 548 ms gigamot-ext.iptelecom.net.ua [212.9.224.114]
24 560 ms 579 ms 559 ms counterl9.iptelecom.net.ua [212.9.244.130]
25 561 ms 548 ms 549 ms cs.iptcom.net [212.9.224.163]
Trace complete.
C:\Users\LuL>tracert cs.iptcom.net
Tracing route to cs.iptcom.net [212.9.224.163]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 73 ms 69 ms 64 ms 10.130.0.3
4 73 ms 69 ms 73 ms 58-27-175-148.wateen.net [58.27.175.148]
5 72 ms 69 ms 64 ms 58-27-175-148.wateen.net [58.27.175.148]
6 73 ms 74 ms 69 ms 58-27-175-130.wateen.net [58.27.175.130]
7 73 ms 74 ms 69 ms 58-27-209-54.wateen.net [58.27.209.54]
8 74 ms 73 ms 69 ms 58-27-183-230.wateen.net [58.27.183.230]
9 73 ms 73 ms 69 ms 58-27-183-75.wateen.net [58.27.183.75]
10 192 ms 183 ms 178 ms tw31-static109.tw1.com [117.20.31.109]
11 193 ms 183 ms 178 ms tw112-static205.tw1.com [221.132.112.205]
12 197 ms 188 ms 189 ms atm9-0-0.1877.gw2.par4.alter.net [194.98.61.173]
13 197 ms 189 ms 188 ms so-3-0-0.XT1.PAR2.ALTER.NET [146.188.9.25]
14 196 ms 185 ms 193 ms POS2-0.BR1.PAR2.ALTER.NET [146.188.8.118]
15 511 ms 499 ms 489 ms PAR.glbx.net [146.188.112.118]
16 483 ms 488 ms 499 ms ae0-20G.scr1.CDG2.gblx.net [67.16.129.194]
17 522 ms 509 ms 504 ms ae1.scr4.FRA4.gblx.net [67.16.145.234]
18 506 ms 499 ms 509 ms lag2.ar4.fra4.gblx.net [67.16.145.242]
19 553 ms 554 ms 544 ms UCOMLINE-JSC.Te7-3.ar3.FRA4.gblx.net [64.215.181.146]
20 557 ms 544 ms 553 ms core-0-wsx670410ge-3-2-212dot1q.kiev.ucomline.net [213.130.30.169]
21 542 ms 539 ms 544 ms metro-gw1.kiev.ucomline.net [93.178.204.206]
22 558 ms 538 ms 534 ms catagi01-ext.optima.ua [62.221.50.4]
23 558 ms 559 ms 549 ms gigamot-ext.iptelecom.net.ua [212.9.224.114]
24 557 ms 554 ms 549 ms counterl9.iptelecom.net.ua [212.9.244.130]
25 558 ms 564 ms 554 ms cs.iptcom.net [212.9.224.163]
Trace complete.
C:\Users\LuL>
Отсутствует
#4 05.07.2011 21:09:45
Re: Ping Problem...
EnCoRe написал:
14 196 ms 193 ms 179 ms POS2-0.BR1.PAR2.ALTER.NET [146.188.8.118]
15 556 ms 639 ms 714 ms PAR.glbx.net [146.188.112.118]
Looks like overloaded router somewhere on ALTER.NET and glbx.net networks border in Europe, there nothing to help here. Also, backtrace to your IP shows different route with same problems, so...
Пых безусловно во всем прав. Почему, спросите Вы? Да просто потому, что Пых ВСЕГДА и БЕЗУСЛОВНО во всем прав© Pepper
----------------------------------------------------------------------
Не комментирую, умные не нуждаются, тупые не поймут©
Отсутствует
#7 13.07.2012 20:19:18
Re: Ping Problem...
C:\Documents and Settings\abc>tracert cs.iptcom.net
Tracing route to cs.iptcom.net [212.9.224.163]
over a maximum of 30 hops:
1 80 ms 9 ms 22 ms 10.30.0.1
2 8 ms 10 ms 11 ms 125.99.127.165
3 11 ms 71 ms 13 ms 203.212.193.34
4 20 ms 10 ms 8 ms 203.212.193.249
5 63 ms 21 ms 13 ms 121.241.1.194.mumbai-static.vsnl.net.in [121.241
.1.194]
6 60 ms * 84 ms ix-0-100.tcore1.MLV-Mumbai.as6453.net [180.87.38
.5]
7 263 ms 264 ms 310 ms if-9-5.tcore1.WYN-Marseille.as6453.net [80.231.2
17.17]
8 297 ms 273 ms 295 ms if-8-1600.tcore1.PYE-Paris.as6453.net [80.231.21
7.6]
9 263 ms 268 ms 261 ms if-2-2.tcore1.PVU-Paris.as6453.net [80.231.154.1
7]
10 268 ms 263 ms 256 ms po1-120-10G.ar3.CDG2.gblx.net [64.208.27.41]
11 274 ms 275 ms 285 ms ae4.scr3.CDG2.gblx.net [67.16.130.222]
12 275 ms 276 ms 277 ms ae13-scr3.FRA4.gblx.net [67.16.165.138]
13 278 ms 279 ms 279 ms lag1.ar4.fra4.gblx.net [67.16.145.238]
14 * 316 ms 315 ms UCOMLINE-JSC.Te7-3.ar3.FRA4.gblx.net [64.215.181
.146]
15 309 ms 315 ms 321 ms core-0-wsx670410ge-3-2-220dot1q.kiev.ucomline.ne
t [93.178.204.205]
16 302 ms 308 ms 306 ms metro-gw1.kiev.ucomline.net [93.178.204.206]
17 304 ms 307 ms 316 ms catagi01-ext.optima.ua [62.221.50.4]
18 331 ms 312 ms 311 ms gigamot-ext.iptelecom.net.ua [212.9.224.114]
19 362 ms 319 ms 321 ms counterl9.iptelecom.net.ua [212.9.244.130]
20 333 ms 332 ms 332 ms cs.iptcom.net [212.9.224.163]
Trace complete. Here it is
Отсутствует
#11 13.07.2012 20:26:17
Re: Ping Problem...
Tracing route to cs.iptcom.net [212.9.224.163]
over a maximum of 30 hops:
1 12 ms 10 ms 15 ms 10.30.0.1
2 16 ms 17 ms 11 ms 125.99.127.165
3 9 ms 28 ms 20 ms 203.212.193.34
4 14 ms 12 ms 10 ms 203.212.193.249
5 10 ms 11 ms 9 ms 121.241.1.194.mumbai-static.vsnl.net.in [121.241
.1.194]
6 42 ms 41 ms 55 ms ix-0-100.tcore1.MLV-Mumbai.as6453.net [180.87.38
.5]
7 261 ms 264 ms 268 ms if-9-5.tcore1.WYN-Marseille.as6453.net [80.231.2
17.17]
8 264 ms 267 ms 270 ms if-8-1600.tcore1.PYE-Paris.as6453.net [80.231.21
7.6]
9 264 ms 258 ms 259 ms if-2-2.tcore1.PVU-Paris.as6453.net [80.231.154.1
7]
10 257 ms 258 ms 259 ms po1-120-10G.ar3.CDG2.gblx.net [64.208.27.41]
11 274 ms 281 ms 277 ms ae4.scr3.CDG2.gblx.net [67.16.130.222]
12 275 ms 275 ms 277 ms ae13-scr3.FRA4.gblx.net [67.16.165.138]
13 281 ms 287 ms 282 ms lag1.ar4.fra4.gblx.net [67.16.145.238]
14 311 ms 314 ms 316 ms UCOMLINE-JSC.Te7-3.ar3.FRA4.gblx.net [64.215.181
.146]
15 309 ms 319 ms 328 ms core-0-wsx670410ge-3-2-220dot1q.kiev.ucomline.ne
t [93.178.204.205]
16 307 ms 309 ms 304 ms metro-gw1.kiev.ucomline.net [93.178.204.206]
17 311 ms 306 ms 304 ms catagi01-ext.optima.ua [62.221.50.4]
18 313 ms 314 ms 323 ms gigamot-ext.iptelecom.net.ua [212.9.224.114]
19 316 ms 313 ms 320 ms counterl9.iptelecom.net.ua [212.9.244.130]
20 342 ms 332 ms 331 ms cs.iptcom.net [212.9.224.163]
Trace complete.
i hope these one is enough 
Отсутствует
#12 13.07.2012 20:33:35
Re: Ping Problem...
vaity96 написал:
6 42 ms 41 ms 55 ms ix-0-100.tcore1.MLV-Mumbai.as6453.net [180.87.38.5]
7 261 ms 264 ms 268 ms if-9-5.tcore1.WYN-Marseille.as6453.net [80.231.217.17]
That's looks like overload inside TATA network on the way from India to France, there is nothing not you, nor we can do
Also, I make back trace, things there even worse
Код:
1: 1 counter-colocation.iptelecom.net.ua (212.9.224.181) 0.472 ms 0.349 ms 0.330 ms 2: 2 concord-ext.iptelecom.net.ua (212.9.244.29) 0.686 ms 0.397 ms 0.345 ms 3: 3 IPT-AT-ext.iptelecom.net.ua (212.9.224.113) 6.492 ms 7.160 ms 6.018 ms 4: 4 62-221-50-5.static.kiev.farlep.net (62.221.50.5) 5.979 ms 6.958 ms 6.954 ms 5: 5 core-0-po1-271dot1q.kiev.ucomline.net (93.178.232.225) 6.957 ms 6.208 ms 5.981 ms 6: 6 ltd-ucomline-gw.ip4.tinet.net (77.67.90.54) 14.914 ms 15.110 ms 15.049 ms 7: 7 xe-8-3-0.fra60.ip4.tinet.net (77.67.90.53) 44.992 ms 44.365 ms 43.852 ms 8: 8 xe-11-2-1.fra23.ip4.tinet.net (89.149.182.77) 47.968 ms 44.246 ms 45.871 ms 9: 9 ix-22-0.tcore1.FR0-Frankfurt.as6453.net (195.219.50.137) 41.961 ms 41.215 ms 41.818 ms 10: 10 if-7-2.tcore1.FNM-Frankfurt.as6453.net (195.219.50.2) 303.045 ms 302.885 ms 303.925 ms 11: 11 if-5-2.tcore1.AV2-Amsterdam.as6453.net (195.219.194.13) 306.868 ms 307.123 ms 307.854 ms 12: 12 if-2-2.tcore2.AV2-Amsterdam.as6453.net (195.219.194.6) 305.998 ms 305.244 ms 304.940 ms 13: 13 if-5-2.tcore2.L78-London.as6453.net (80.231.131.13) 307.728 ms 307.174 ms 308.888 ms 14: 14 if-20-2.tcore2.NYY-NewYork.as6453.net (216.6.99.13) 303.933 ms 305.200 ms 304.909 ms 15: 15 if-11-2.tcore1.NYY-NewYork.as6453.net (216.6.99.2) 308.892 ms 309.237 ms 308.857 ms 16: 16 if-1-2.tcore1.PDI-PaloAlto.as6453.net (66.198.127.5) 305.933 ms 306.153 ms 305.789 ms 17: 17 if-2-2.tcore2.PDI-PaloAlto.as6453.net (66.198.127.2) 321.956 ms 304.184 ms 304.924 ms 18: 18 if-9-2.tcore1.TV2-Tokyo.as6453.net (180.87.180.18) 307.960 ms 307.950 ms 308.078 ms 19: 19 if-2-2.tcore2.TV2-Tokyo.as6453.net (180.87.180.2) 316.752 ms 311.535 ms 311.068 ms 20: 20 if-6-2.tcore1.SVW-Singapore.as6453.net (180.87.12.109) 318.831 ms 318.127 ms 324.880 ms 21: 21 if-5-2.tcore1.CXR-Chennai.as6453.net (180.87.12.54) 317.921 ms 318.055 ms 318.953 ms 22: 22 180.87.36.58 (180.87.36.58) 314.895 ms 314.963 ms 320.986 ms 23: 23 * * * 24: 24 * * *
It's looks like circuit because of misconfiguration inside same network, so traffic to you bouncing back and forth all over the world. You can forget about normal ping till they fix that
Нам 10 лет, ня!
Отсутствует
#14 14.07.2012 13:36:44
- NorthNikko
- Участник
- Откуда: France
- Зарегистрирован: 23.10.2011
- Сообщений: 151
19.0- Рейтинг : [+ 5/ -0 ]
- Профиль
Re: Ping Problem...
Funny, your last line are 300 or 500 and mine is 78
Отсутствует
#16 14.07.2012 21:35:20
Re: Ping Problem...
vaity96 написал:
px can u tll me when they will fix d problem
No, nobody can
vaity96 написал:
or where i can find myself
Just ping server, when numbers drops to normal => problem fixed
Нам 10 лет, ня!
Отсутствует
#18 15.07.2012 17:48:43
- :.:War Lords:.: | MaF!a
- Участник
- Откуда: Pakistan
- Зарегистрирован: 15.05.2012
- Сообщений: 22
12.00- Профиль Вебсайт
Re: Ping Problem...
vaity96 написал:
fix d problem
if u still have a problem with ping try restarting your router!!
or shift your internet connection! 
Sometimes expect the unexpected
Отсутствует
#19 15.07.2012 20:10:25
Re: Ping Problem...
hey px can u chek this stats
Pinging cs.iptcom.net [212.9.224.163] with 32 bytes of data:
Reply from 212.9.224.163: bytes=32 time=318ms TTL=35
Reply from 212.9.224.163: bytes=32 time=311ms TTL=35
Reply from 212.9.224.163: bytes=32 time=313ms TTL=35
Reply from 212.9.224.163: bytes=32 time=312ms TTL=35
Ping statistics for 212.9.224.163:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 311ms, Maximum = 318ms, Average = 313ms
Отсутствует
#23 16.07.2012 15:25:06
Re: Ping Problem...
can u pls chek this again man 
i can't stop myself frm playing man pls
Tracing route to cs.iptcom.net [212.9.224.163]
over a maximum of 30 hops:
1 7 ms 7 ms 7 ms 10.30.0.1
2 9 ms 33 ms 11 ms 125.99.127.165
3 9 ms 12 ms 18 ms 203.212.193.34
4 9 ms 11 ms 9 ms 203.212.193.249
5 10 ms 18 ms 8 ms 121.241.1.194.mumbai-static.vsnl.net.in [121.24
.1.194]
6 10 ms 8 ms 7 ms ix-0-100.tcore1.MLV-Mumbai.as6453.net [180.87.3
.5]
7 275 ms 271 ms 273 ms if-9-5.tcore1.WYN-Marseille.as6453.net [80.231.
17.17]
8 270 ms 271 ms 281 ms if-8-1600.tcore1.PYE-Paris.as6453.net [80.231.2
7.6]
9 256 ms 256 ms 261 ms if-2-2.tcore1.PVU-Paris.as6453.net [80.231.154.
7]
10 256 ms 254 ms 253 ms 208.178.58.109
11 270 ms 270 ms 269 ms xe0-2-2-10G.scr3.CDG2.gblx.net [67.16.148.106]
12 268 ms 267 ms 267 ms ae13-scr3.FRA4.gblx.net [67.16.165.138]
13 266 ms 275 ms 272 ms lag1.ar4.fra4.gblx.net [67.16.145.238]
14 306 ms 308 ms 307 ms UCOMLINE-JSC.Te7-3.ar3.FRA4.gblx.net [64.215.18
.146]
15 319 ms 321 ms 318 ms core-0-wsx670410ge-3-2-220dot1q.kiev.ucomline.n
t [93.178.204.205]
16 298 ms 310 ms 300 ms metro-gw1.kiev.ucomline.net [93.178.204.206]
17 304 ms 304 ms 307 ms catagi01-ext.optima.ua [62.221.50.4]
18 321 ms 321 ms 326 ms gigamot-ext.iptelecom.net.ua [212.9.224.114]
19 316 ms 316 ms 324 ms counterl9.iptelecom.net.ua [212.9.244.130]
20 309 ms 307 ms 309 ms cs.iptcom.net [212.9.224.163]
Trace complete
Отсутствует
srry man 2 disturbe you