Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
High on from 2 days :/
#1
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 7 ms 7 ms 9 ms adsl.loop6.dhivehinet.net.mv [202.1.193.46]
3 11 ms 7 ms 8 ms 202.1.205.221
4 13 ms 12 ms 11 ms ac-124-1-9.dhivehinet.net.mv [202.1.205.9]
5 9 ms 9 ms 8 ms ac-rb-1-1.dhivehinet.net.mv [202.1.205.1]
6 19 ms 28 ms 18 ms 222.165.143.249
7 23 ms 21 ms 20 ms 222.165.175.81
8 21 ms 20 ms 23 ms 222.165.175.18
9 133 ms 131 ms 134 ms pos4-3.palermo1.pal.seabone.net [195.22.198.16]

10 * 154 ms 150 ms te1-2.milano52.mil.seabone.net [195.22.196.175]

11 238 ms 235 ms 235 ms ntt-verio.milano52.mil.seabone.net [93.186.128.2
5]
12 302 ms 303 ms 301 ms xe-0-0-0-3.r03.amstnl02.nl.bb.gin.ntt.net [129.2
50.4.14]
13 289 ms 236 ms 286 ms ae-4.r22.amstnl02.nl.bb.gin.ntt.net [129.250.2.2
10]
14 289 ms 301 ms 291 ms ae-5.r23.londen03.uk.bb.gin.ntt.net [129.250.5.1
97]
15 288 ms 285 ms 289 ms as-0.r22.osakjp01.jp.bb.gin.ntt.net [129.250.5.3
5]
16 313 ms 302 ms 300 ms ae-7.r24.tokyjp05.jp.bb.gin.ntt.net [129.250.3.2
21]
17 292 ms 289 ms 290 ms ae-1.r25.tokyjp05.jp.bb.gin.ntt.net [129.250.6.1
85]
18 309 ms 296 ms 298 ms ae-2.r00.tokyjp03.jp.bb.gin.ntt.net [129.250.2.5
]
19 323 ms 332 ms 328 ms xe-0-1-0-8.r00.tokyjp03.jp.ce.gin.ntt.net [61.21
3.145.38]
20 318 ms 310 ms 309 ms ae1.bbr01.eq01.sng02.networklayer.com [50.97.18.
165]
21 313 ms 313 ms 312 ms ae5.dar02.sr03.sng01.networklayer.com [50.97.18.
199]
22 339 ms 319 ms 311 ms po2.fcr01.sr03.sng01.networklayer.com [174.133.1
18.133]
23 313 ms 311 ms 311 ms 119.81.28.241-static.reverse.softlayer.com [119.
81.28.241]

Trace complete.
[Image: 21103919493_c13c1c093d_o.png]
#2
This is a traceroute from our server to your IP.

traceroute to your IP (Your IP), 30 hops max, 60 byte packets
1 119.81.33.41-static.reverse.softlayer.com (119.81.33.41) 0.309 ms 0.298 ms 0.351 ms
2 ae11.dar02.sr03.sng01.networklayer.com (174.133.118.132) 0.173 ms 0.215 ms 0.210 ms
3 ae9.bbr01.eq01.sng02.networklayer.com (50.97.18.198) 0.805 ms 0.802 ms 54.909 ms
4 p9498.sgw.equinix.com (202.79.197.40) 1.705 ms 1.646 ms 1.739 ms
5 203.101.100.221 (203.101.100.221) 33.227 ms 33.230 ms 33.225 ms
6 125.17.16.98 (125.17.16.98) 58.109 ms 58.014 ms 58.020 ms
7 222.165.175.9 (222.165.175.9) 290.642 ms 290.479 ms 290.401 ms
8 222.165.175.86 (222.165.175.86) 293.564 ms 293.444 ms 222.165.175.82 (222.165.175.82) 293.193 ms
9 222.165.143.238 (222.165.143.238) 302.910 ms 302.912 ms 302.948 ms
10 ac-124-2-4.dhivehinet.net.mv (202.1.205.4) 305.913 ms 306.941 ms 305.266 ms
11 202.1.205.12 (202.1.205.12) 302.075 ms 301.533 ms 301.574 ms
12 202.1.205.214 (202.1.205.214) 310.956 ms 311.550 ms 311.526 ms

I'm not sure this is a problem with our datacenter. Softlayer is handing off to peering in Equinix which is where their network ends and I assume the peer is either your ISP or a transit provider for your ISP (203.101.100.221 Bharti Airtel in Delhi, India).
#3
yeah complained to the isp and they fixed it Big Grin
[Image: 21103919493_c13c1c093d_o.png]

Users browsing this thread: 2 Guest(s)