Here's my ping result for slashdot, don't seem to be getting such problems

Tracing route to slashdot.org [66.35.250.150]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 62 ms 11 ms 38 ms bb219-74-193-1.singnet.com.sg [219.74.193.1]
3 168 ms 55 ms 58 ms bb78-41.singnet.com.sg [165.21.78.41]
4 62 ms 20 ms 51 ms ge-0-0-4-0.guinness.singnet.com.sg [202.166.126.26]
5 54 ms 9 ms 9 ms 202.166.126.101
6 19 ms 52 ms 10 ms 203.208.182.77
7 11 ms 9 ms 10 ms p1-2.sngtp-cr3.ix.singtel.com [203.208.182.126]
8 221 ms 236 ms 250 ms so-2-1-0.plapx-cr3.ix.singtel.com [203.208.182.114]
9 217 ms 257 ms 284 ms ge-0-0-0.plapx-ar1.ix.singtel.com [203.208.168.130]
10 267 ms 222 ms 233 ms 206.24.241.13
11 211 ms 202 ms 250 ms bpr2-ge-6-3-0.PaloAltoPaix.savvis.net [206.24.221.241]
12 220 ms 220 ms 247 ms dcr2-so-3-3-0.SanFranciscosfo.savvis.net [208.172.147.93]
13 205 ms 204 ms 220 ms bhr1-pos-0-0.SantaClarasc8.savvis.net [208.172.156.198]
14 603 ms 256 ms 209 ms csr1-ve243.SantaClarasc8.savvis.net [66.35.194.50]
15 240 ms 210 ms 210 ms 66.35.212.174
16 236 ms 209 ms 208 ms slashdot.org [66.35.250.150]

Trace complete.