Verio sucks!

[nyankoframe]

Together with cogentco and other backbone providers.

I mean, really, a ping time of 1200 ms on a border router is just atrocious.

Trace to rakuen.de.eu.zirc.org:

  8    43 ms    43 ms    46 ms  ge-0-0-0.r00.sngpsi01.sg.bb.verio.net [61.8.234.61]
  9  1173 ms  1174 ms     *     p1-0-1-2.r81.mlpsca01.us.bb.verio.net [129.250.4.149]
 10  1149 ms  1145 ms  1152 ms  p16-1-1-0.r20.mlpsca01.us.bb.verio.net [129.250.2.247]
 11  1158 ms     *        *     p64-0-3-0.r21.snjsca04.us.bb.verio.net [129.250.5.3]
 12  1160 ms  1163 ms  1155 ms  p15-0.core01.sjc03.atlas.cogentco.com [154.54.11.245]
 13  1167 ms  1156 ms  1156 ms  p5-0.core02.sfo01.atlas.cogentco.com [66.28.4.134]
 14     *     1155 ms  1156 ms  p15-0.core01.sfo01.atlas.cogentco.com [66.28.4.69]
 15     *     1198 ms     *     p14-0.core01.ord01.atlas.cogentco.com [66.28.4.186]
 16  1224 ms  1221 ms  1221 ms  p14-0.core01.bos01.atlas.cogentco.com [66.28.4.109]
 17     *     1237 ms     *     p3-0.core01.lon02.atlas.cogentco.com [130.117.0.45]
 18  1242 ms  1244 ms  1238 ms  p15-0.core01.ams03.atlas.cogentco.com [130.117.1.226]
 19     *     1242 ms  1249 ms  p6-0.core01.fra03.atlas.cogentco.com [130.117.0.85]
 20     *        *     1249 ms  130.117.152.139
 21  1250 ms  1247 ms  1238 ms  194.106.206.74

Trace to slashdot.org:

  7    13 ms    10 ms    11 ms  61.8.233.29
  8    45 ms    41 ms    43 ms  ge-0-0-0.r00.sngpsi01.sg.bb.verio.net [61.8.234.61]
  9    45 ms    43 ms    42 ms  p1-1-2-3.r01.sngpsi01.sg.bb.verio.net [129.250.2.154]
 10     *        *     1217 ms  p1-1-0-0.r81.sttlwa01.us.bb.verio.net [129.250.3.93]
 11  1215 ms     *     1209 ms  p16-1-1-1.r20.sttlwa01.us.bb.verio.net [129.250.2.218]
 12     *        *        *     Request timed out.
 13     *     1179 ms  1175 ms  bpr4-so-5-2-0.SeattleSwitchDesign.savvis.net [208.173.50.65]
 14  1168 ms  1181 ms     *     acr2-so-0-0-0.Seattle.savvis.net [208.172.83.66]
 15     *     1181 ms     *     dcr2-so-5-0-0.SanFranciscosfo.savvis.net [204.70.192.150]
 16  1177 ms  1176 ms     *     bhr1-pos-0-0.SantaClarasc8.savvis.net [208.172.156.198]
 17     *     1177 ms     *     csr1-ve240.SantaClarasc8.savvis.net [66.35.194.34]
 18  1177 ms  1177 ms     *     66.35.212.174
 19     *     1179 ms  1175 ms  slashdot.org [66.35.250.150]

Trace to livejournal.com:

  7    12 ms    10 ms    13 ms  203.116.6.57
  8    12 ms    11 ms    10 ms  pc2-an-uts-int01.starhub.net.sg [203.118.3.209]
  9   194 ms   199 ms   198 ms  sl-gw23-ana-3-1.sprintlink.net [144.228.114.53]
 10   195 ms   196 ms   200 ms  sl-bb23-ana-12-1.sprintlink.net [144.232.1.153]
 11   208 ms   198 ms   195 ms  sl-bb25-sj-9-0.sprintlink.net [144.232.20.159]
 12     *      195 ms     *     sl-bb22-sj-12-0.sprintlink.net [144.232.3.209]
 13   217 ms   216 ms   215 ms  sl-bb23-tac-14-0.sprintlink.net [144.232.20.9]
 14     *        *        *     Request timed out.
 15   217 ms   216 ms   218 ms  sl-bb20-sea-0-0.sprintlink.net [144.232.9.150]
 16   219 ms     *      218 ms  sl-gw12-sea-0-0.sprintlink.net [144.232.6.120]
 17   217 ms   218 ms   220 ms  sl-internap-127-0.sprintlink.net [144.228.93.66]
 18   221 ms   216 ms     *     border9.ge1-1-bbnet1.sef.pnap.net [63.251.160.19]
 19   218 ms   218 ms   220 ms  livejournal.com [66.150.15.150]

Comments

[antineo.livejournal.com]

eeek.

[nyankoframe.livejournal.com]

Fortunately, I think Verio (or someone) kicked the routers, so that now they have ping times of around 240 ms which is about normal for us poor Asian users. *shrug*

Ping!

[edible-llama.livejournal.com]

*llama pings*

Re: Ping!

[nyankoframe.livejournal.com]

* basket dies from ping timeouts.
--- basket has quit IRC (Connection reset by llama)

Oh no! @_@

Re: Ping!

[edible-llama.livejournal.com]

Nooo! Come back basket! *cries*

Re: Ping!

[nyankoframe.livejournal.com]

At least it wasn't TCP/IP over carrier pigeon. If one of the pigeons was shot or somehow fell from the sky, it would be pretty hard for me to reconnect. :P

[(Anonymous)]

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.

[nyankoframe.livejournal.com]

You're using SingTel, which presumably has a different route to the US (notice how there are no verio hops in the route).

Also, the problem was fixed some time yesterday (see my earlier comment)