Not signed in (Sign In)

Check This Out: Slicehost unreachable sometimes

Bottom of Page

1 to 20 of 22

  1. <
  2. 1
  3. 2
  4. >
    • CommentAuthorkahwee
    • CommentTimeAug 6th 2008 edited
     permalink
    This is a ping from Singapore. The ping isn't that good here somehow, my slice is also affected. Anybody with similar issues? Other US websites appear fine.

    C:\Users\KahWee>ping slicehost.com /t

    Pinging slicehost.com [67.207.128.80] with 32 bytes of data:
    Request timed out.
    Reply from 67.207.128.80: bytes=32 time=249ms TTL=47
    Reply from 67.207.128.80: bytes=32 time=249ms TTL=47
    Reply from 67.207.128.80: bytes=32 time=250ms TTL=47
    Reply from 67.207.128.80: bytes=32 time=249ms TTL=47
    Reply from 67.207.128.80: bytes=32 time=249ms TTL=47
    Request timed out.
    Reply from 67.207.128.80: bytes=32 time=249ms TTL=47
    Reply from 67.207.128.80: bytes=32 time=249ms TTL=47
    Request timed out.
    Reply from 67.207.128.80: bytes=32 time=249ms TTL=47
    Request timed out.
    Reply from 67.207.128.80: bytes=32 time=249ms TTL=47
    Reply from 67.207.128.80: bytes=32 time=249ms TTL=47
    Reply from 67.207.128.80: bytes=32 time=249ms TTL=47
    Reply from 67.207.128.80: bytes=32 time=250ms TTL=47
    Reply from 67.207.128.80: bytes=32 time=249ms TTL=47
    Reply from 67.207.128.80: bytes=32 time=249ms TTL=47
    Reply from 67.207.128.80: bytes=32 time=249ms TTL=47
    Reply from 67.207.128.80: bytes=32 time=249ms TTL=47
    Reply from 67.207.128.80: bytes=32 time=250ms TTL=47
    Request timed out.
    Reply from 67.207.128.80: bytes=32 time=249ms TTL=47
    Request timed out.
    Reply from 67.207.128.80: bytes=32 time=252ms TTL=47
    Reply from 67.207.128.80: bytes=32 time=256ms TTL=47
    Reply from 67.207.128.80: bytes=32 time=259ms TTL=47
    Reply from 67.207.128.80: bytes=32 time=297ms TTL=47
    Reply from 67.207.128.80: bytes=32 time=250ms TTL=47

    Ping statistics for 67.207.128.80:
    Packets: Sent = 29, Received = 23, Lost = 6 (20% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 249ms, Maximum = 297ms, Average = 252ms



    Here is the tracert

    C:\Users\KahWee>tracert slicehost.com

    Tracing route to slicehost.com [67.207.128.80]
    over a maximum of 30 hops:

    1 1 ms 1 ms 1 ms 192.168.1.1
    2 8 ms 8 ms 8 ms bb121-7-197-1.singnet.com.sg [121.7.197.1]
    3 7 ms 8 ms 7 ms 202.166.121.209
    4 7 ms 8 ms 8 ms ge-0-2-0-13.asahi.singnet.com.sg [202.166.124.14
    9]
    5 7 ms 8 ms 7 ms xe-10-0-0.budwesier.singnet.com.sg [202.166.126.
    1]
    6 7 ms 8 ms 8 ms ae1-0.beck.singnet.com.sg [202.166.124.234]
    7 8 ms 8 ms 8 ms 203.208.190.57
    8 8 ms 8 ms 8 ms xe-1-0-0-0.sngtp-cr2.ix.singtel.com [203.208.183
    .65]
    9 206 ms 206 ms 206 ms so-2-0-0-0.plapx-cr3.ix.singtel.com [203.208.151
    .74]
    10 194 ms 195 ms 195 ms ge-7-0-0-0.plapx-dr2.ix.singtel.com [203.208.183
    .182]
    11 310 ms 186 ms * gi1-2.mpd01.sjc04.atlas.cogentco.com [154.54.11.
    81]
    12 * * 193 ms te9-1.mpd01.sfo01.atlas.cogentco.com [154.54.0.1
    69]
    13 222 ms 222 ms * te7-4.mpd01.mci01.atlas.cogentco.com [154.54.24.
    106]
    14 228 ms 227 ms 227 ms gi11-0-0.core01.mci01.atlas.cogentco.com [154.54
    .2.217]
    15 * 250 ms 250 ms po15-0.core01.stl03.atlas.cogentco.com [154.54.7
    .90]
    16 227 ms 228 ms * vl3502.na21.b016110-1.stl03.atlas.cogentco.com [
    66.28.5.58]
    17 227 ms 227 ms 227 ms 38.104.162.22
    18 238 ms 238 ms * 209.20.79.227
    19 * 250 ms 250 ms www.slicehost.com [67.207.128.80]

    Trace complete.

    C:\Users\KahWee>


    Problem is likely with cogentco.com side. Anyone encounter similar issues?
    •  
      CommentAuthorjason
    • CommentTimeAug 6th 2008 edited
     permalink
    Here is a mtr test from us to you. The fact that it is showing Level(3) from us means that this is the shortest AS path to your IP. If singtel is preferring cogent that is based on a configuration on their end I believe. I don't see any losses until we get to the international IX, so I'm not sure there is a ton we can do about it on our end.



    Host                                                                        Loss%   Snt   Last   Avg  Best  Wrst StDev
     1. 209-20-72-2.slicehost.net                                                 0.0%    51    0.1   0.2   0.1   1.0   0.1
     2. 209.20.79.225                                                             0.0%    51    0.3   0.3   0.1   1.0   0.1
     3. ge-6-13-115.car1.StLouis1.Level3.net                                      0.0%    51    0.5  11.3   0.4 131.0  31.2
     4. ae-4-4.ebr1.Denver1.Level3.net                                            0.0%    50   18.8  23.1  18.8  30.8   3.9
     5. ae-3.ebr2.SanJose1.Level3.net                                             0.0%    50   45.5  49.3  44.4  57.6   4.7
     6. ae-82-82.csw3.SanJose1.Level3.net                                         0.0%    50   47.8  49.7  44.5  57.7   4.2
     7. ae-32-89.car2.SanJose1.Level3.net                                         0.0%    50   44.8  52.9  44.6 236.8  33.8
     8. SINGAPORE-T.car2.SanJose1.Level3.net                                     32.0%    50   43.6  44.2  43.4  49.6   1.7
     9. ge-5-0-0-0.plapx-cr2.ix.singtel.com                                       0.0%    50   43.8  43.6  43.4  44.0   0.1
        ge-5-0-0-0.plapx-cr3.ix.singtel.com
    10. ge-4-0-0-0.plapx-cr3.ix.singtel.com                                      34.7%    50   43.9  43.8  43.5  44.1   0.1
    11. so-3-0-1-0.sngtp-cr2.ix.singtel.com                                       0.0%    50  230.3 238.0 226.5 254.4   9.3
        so-2-0-0-0.sngtp-cr1.ix.singtel.com
    12. 203.208.190.142                                                           0.0%    50  225.0 229.5 224.8 273.0   9.6
    13. xe-2-0-0.budweiser.singnet.com.sg                                         0.0%    50  231.5 235.9 231.4 278.2   8.5
    14. xe-0-0-0.sapporo.singnet.com.sg                                           0.0%    50  228.3 226.4 224.7 246.2   3.2
    15. 202.166.124.150                                                           0.0%    50  271.7 259.2 251.7 317.5  16.3
    16. bb121-7-197-1.singnet.com.sg                                             26.0%    50  256.1 254.6 252.6 265.1   2.8
    Thankful People: kahwee
    • CommentAuthorkahwee
    • CommentTimeAug 6th 2008
     permalink
    Is there anything that can be done then? This is mtr from my slice to my ISP:

    Resolver: Received error response 2. (server failure)er of fields quit
    Packets Pings
    Host Loss% Snt Last Avg Best Wrst StDev
    1. 209-20-64-2.slicehost.net 0.0% 637 0.1 0.1 0.1 6.0 0.4
    2. 209.20.79.225 0.2% 637 0.5 0.2 0.2 13.4 0.8
    3. ge-6-13-115.car1.StLouis1.Level3.net 0.2% 637 0.7 9.1 0.4 210.9 30.3
    4. ae-4-4.ebr1.Denver1.Level3.net 0.6% 637 24.1 23.8 18.7 40.2 4.5
    5. ae-3.ebr2.SanJose1.Level3.net 0.2% 637 48.1 49.6 44.3 67.0 4.4
    6. ae-92-92.csw4.SanJose1.Level3.net 0.0% 636 44.8 49.6 43.0 87.5 4.8
    7. ae-42-99.car2.SanJose1.Level3.net 0.5% 636 45.0 52.6 43.2 247.6 29.7
    8. SINGAPORE-T.car2.SanJose1.Level3.net 2.8% 636 43.8 44.3 41.7 82.1 2.5
    9. ge-5-0-0-0.plapx-cr2.ix.singtel.com 0.0% 636 44.0 43.6 42.7 75.9 2.3
    ge-5-0-0-0.plapx-cr3.ix.singtel.com
    10. ge-1-0-8-0.plapx-dr2.ix.singtel.com 0.0% 636 240.6 237.0 231.1 274.4 4.3
    so-2-0-0-0.sngtp-cr1.ix.singtel.com
    11. ge-2-1-0-0.sngtp-dr1.ix.singtel.com 0.0% 636 224.8 236.5 223.1 291.0 11.6
    ge-3-0-0-0.sngtp-dr1.ix.singtel.com
    12. 203.208.190.58 0.0% 636 261.8 257.2 245.0 312.2 11.5
    13. ae1-0.budweiser.singnet.com.sg 0.0% 636 247.3 243.0 232.0 335.3 13.8
    14. xe-1-0-0.stella.singnet.com.sg 0.0% 636 226.5 234.1 226.4 273.9 7.6
    15. bb219-74-64-1.singnet.com.sg 19.7% 636 243.4 236.3 226.4 396.4 11.0
    • CommentAuthorpkchukiss
    • CommentTimeAug 6th 2008
     permalink
    Hi kahwee,

    I'm also using Singnet, and have the same problem with my slice. Have you contacted Singnet on the issue yet?

                                                              Packets               Pings
     Host                                                   Loss%   Snt   Last   Avg  Best  Wrst StDev
     1. 67-207-128-2.slicehost.net                           0.0%   355    0.2   0.1   0.1   0.6   0.1
     2. 209.20.79.225                                        0.3%   355    0.3   0.3   0.2  16.0   0.8
     3. ge-6-13-115.car1.StLouis1.Level3.net                 0.3%   355    0.7  11.7   0.4 196.2  36.8
     4. ae-4-4.ebr1.Denver1.Level3.net                       1.1%   355   22.2  23.8  18.7  39.6   4.8
     5. ae-3.ebr2.SanJose1.Level3.net                        0.3%   355   56.6  49.5  44.2  59.8   4.4
     6. ae-72-72.csw2.SanJose1.Level3.net                    0.0%   355   49.4  49.9  41.2  58.1   4.4
     7. ae-22-79.car2.SanJose1.Level3.net                    0.0%   355   45.0  54.0  41.2 261.9  35.2
     8. ???
     9. ge-5-0-0-0.plapx-cr3.ix.singtel.com                  0.0%   355   43.1  43.0  42.7  43.7   0.2
        ge-5-0-0-0.plapx-cr2.ix.singtel.com
    10. ???
    11. so-2-0-1-0.sngtp-cr2.ix.singtel.com                  0.3%   354  227.2 230.6 215.7 293.1   9.4
        ge-3-0-0-0.sngtp-dr1.ix.singtel.com
    12. ???
    13. ae1-0.budweiser.singnet.com.sg                       0.3%   354  228.5 231.2 226.6 320.5  12.8
    14. xe-0-0-0.sapporo.singnet.com.sg                      0.3%   354  228.6 227.7 223.3 238.4   1.1
    15. 202.166.124.154                                      0.0%   354  240.4 245.4 240.2 346.2  14.6
    16. 202.166.120.58                                       0.0%   354  247.6 247.4 245.8 275.7   2.6
    17. bb219-74-222-145.singnet.com.sg                     17.8%   354  228.2 228.0 225.9 239.8   1.5

    • CommentAuthorkahwee
    • CommentTimeAug 6th 2008
     permalink
    Hi pkchukiss, great to know that someone using Singnet on Slicehost too. No, I haven't contacted SingNet. I'm not sure if Singnet could do much on it.

    Any suggestions on how to get around this issue? I don't mind contacting Singnet.
    •  
      CommentAuthorechoz
    • CommentTimeAug 9th 2008
     permalink

    Am also on SingNet and seeing the same problems as you guys.

    Its weird that about a week ago this problem did not exist. Things were fine.

    I’ve emailed SingNet tech support and hope to hear from them at the start of next week.

    • CommentAuthorkahwee
    • CommentTimeAug 9th 2008 edited
     permalink
    Thanks echoz, I was planning to give them a ring. I discovered a few things, the ping always shows 20% loss over a long period of time. Likely SingNet's side problem. Probably one of their 5 servers aren't working or something. Starhub works fine and there's likely nothing wrong with SingTel or Cogent.

    You can find me at Twitter, my username is kahwee.
    •  
      CommentAuthorechoz
    • CommentTimeAug 9th 2008
     permalink

    Agreed. I have no problems from school as well. Its blazing fast as it used to be. Just that it sucks at home.

    • CommentAuthorkahwee
    • CommentTimeAug 9th 2008
     permalink
    I tried the network at my company, things are great there too. You reply fast, hahaa.. Happy national day to you. You have Twitter?
    •  
      CommentAuthorechoz
    • CommentTimeAug 9th 2008
     permalink

    Happy National Day to you too man. Haha.

    Yeah. www.twitter.com/echoz

    We should start a community of Singapore slicehost users man…

    • CommentAuthorkahwee
    • CommentTimeAug 9th 2008
     permalink
    LOL, we should start a support group. I actually thought I was the only person in SG using their services. Most Singaporeans are on Dreamhost I think.
    •  
      CommentAuthorechoz
    • CommentTimeAug 9th 2008
     permalink

    Yeah we should. SIngaporeans love oversold services. Its a kiasu thing I guess.

    • CommentAuthorkahwee
    • CommentTimeAug 9th 2008
     permalink
    Yeah, I almost wanted to get Dreamhost too until I did some research online and I see tons of complaints.
    •  
      CommentAuthorechoz
    • CommentTimeAug 9th 2008
     permalink

    I made the choice of getting Site5. Thank god their money back was prompt. That was a contrast to their support.

    • CommentAuthorkahwee
    • CommentTimeAug 9th 2008
     permalink
    I am with Media Temple and Slicehost. Media Temple is rather slow these days, they had some issues with storage. I hope SingNet replies you and Slicehost be normal again. :)
    •  
      CommentAuthorechoz
    • CommentTimeAug 9th 2008
     permalink

    Packets Pings Host Loss% Snt Last Avg Best Wrst StDev 1. 209-20-78-2.slicehost.net 0.0% 13 0.2 0.2 0.2 0.3 0.0 2. 209.20.79.225 0.0% 13 0.3 0.3 0.3 0.4 0.0 3. ge-6-13-115.car1.StLouis1.Level3.net 0.0% 13 0.8 0.8 0.5 2.6 0.5 4. ae-4-4.ebr1.Denver1.Level3.net 0.0% 13 25.8 24.4 19.0 31.1 3.7 5. ae-3.ebr2.SanJose1.Level3.net 0.0% 13 47.2 49.3 44.6 55.3 3.8 6. ae-92-92.csw4.SanJose1.Level3.net 0.0% 13 50.8 49.6 44.8 56.4 4.1 7. ae-42-99.car2.SanJose1.Level3.net 0.0% 13 45.0 48.1 44.8 85.3 11.2 8. SINGAPORE-T.car2.SanJose1.Level3.net 50.0% 13 43.1 43.6 43.1 45.6 1.0 9. ge-5-0-0-0.plapx-cr2.ix.singtel.com 0.0% 13 43.2 43.3 43.0 43.6 0.2 ge-5-0-0-0.plapx-cr3.ix.singtel.com 10. ge-4-0-0-0.plapx-cr2.ix.singtel.com 0.0% 13 43.4 43.6 43.1 47.4 1.1 ge-4-0-0-0.plapx-cr3.ix.singtel.com 11. so-3-0-1-0.sngtp-cr2.ix.singtel.com 0.0% 13 252.7 242.3 226.4 254.9 11.1 so-2-0-0-0.sngtp-cr1.ix.singtel.com 12. ??? 13. xe-2-0-0.budweiser.singnet.com.sg 0.0% 13 255.0 255.1 251.6 276.5 6.6 14. xe-0-0-0.stella.singnet.com.sg 0.0% 13 235.2 233.9 231.8 235.6 1.7 15. 202.166.124.106 0.0% 13 252.2 252.5 249.0 274.1 7.0 16. ??? 17. bb121-7-62-74.singnet.com.sg 8.3% 13 269.6 256.2 248.4 273.7 10.3

    This is mine btw.

    • CommentAuthorohkus
    • CommentTimeAug 9th 2008
     permalink
    Couldn't slicehost select not to announce cogent to singnet? That way things would travel over l3....
    • CommentAuthorpkchukiss
    • CommentTimeAug 9th 2008
     permalink
    Hello echoz, that makes 3 of us so far! Happy 43rd National Day!

    I tried to access with my Broadband On Mobile device, and there isn't any such packet loss. The BBOM infrastructure appears to merge with the SingNet network somewhere in the middle. The BBOM service is notoriously slow though! Here's a sample:



                                           Packets               Pings
     Host                                Loss%   Snt   Last   Avg  Best  Wrst StDev
     1. 67-207-128-2.slicehost.net        0.0%   109    0.2   0.2   0.1   0.5   0.1
     2. 209.20.79.225                     0.0%   109    0.2   0.3   0.2   0.7   0.1
     3. ge-6-13-115.car1.StLouis1.Level3  0.0%   109    0.6  12.1   0.4 201.9  38.3
     4. ae-4-4.ebr1.Denver1.Level3.net    0.0%   108   18.9  23.2  18.8  31.8   4.1
     5. ae-3.ebr2.SanJose1.Level3.net     0.0%   108   44.6  49.2  44.3  57.6   5.0
     6. ae-62-62.csw1.SanJose1.Level3.ne  0.0%   108   48.9  48.8  44.5  57.3   3.3
     7. ae-21-69.car1.SanJose2.Level3.ne  0.0%   108  233.1  49.9  44.8 233.1  26.4
     8. SINGAPORE-T.car1.SanJose2.Level3  0.0%   108   45.8  44.3  43.5  69.1   2.7
     9. xe-0-0-0-0.plapx-cr3.ix.singtel.  0.0%   108   43.8  43.8  43.5  48.9   0.5
    10. so-2-0-1-0.sngtp-cr2.ix.singtel.  0.0%   108  236.0 219.4 215.3 242.9   3.3
    11. ???
    12. 203.208.151.162                   0.0%   108  227.1 227.2 223.5 236.4   1.0
    13. 203.208.192.134                   0.0%   108  228.0 227.8 227.5 230.7   0.3
    14. ???


    Destination is not reachable since my machine is behind NAT on the mobile broadband network. It does appear to be a misconfigured node that is causing the problem.

    I've written in to complain about the problem too, so now we'll just have to sit and twiddle our thumbs :)
    •  
      CommentAuthorechoz
    • CommentTimeAug 9th 2008
     permalink

    Yeah. Its quite weird from our machines to slicehost as well. I’m seeing these types of packet losses.

    Packets Pings Host Loss% Snt Last Avg Best Wrst StDev 1. WRT54GL 0.0% 41 8.1 1.7 0.8 8.1 1.5 2. bb121-7-62-73.singnet.com.sg 2.4% 41 7.7 6.8 1.9 30.0 5.3 3. bb116-14-180-1.singnet.com.sg 0.0% 41 38.9 42.5 17.5 128.3 23.0 4. 202.166.121.41 0.0% 41 20.6 41.9 18.3 88.5 16.6 5. 202.166.124.105 14.6% 41 36.0 44.8 16.4 155.9 26.3 6. xe-0-3-0.budweiser.singnet.com.sg 0.0% 41 67.6 52.1 18.9 157.8 29.0 7. ae1-0.beck.singnet.com.sg 0.0% 41 33.2 46.0 17.9 137.0 24.5 8. 203.208.190.57 12.5% 41 81.8 43.0 17.3 105.4 20.4 9. xe-1-0-0-0.sngtp-cr1.ix.singtel.com 0.0% 41 89.8 40.6 17.5 89.8 18.5 10. so-2-0-0-0.plapx-cr2.ix.singtel.com 0.0% 41 225.3 230.2 209.1 259.3 14.4 11. ge-6-0-0-0.plapx-dr2.ix.singtel.com 0.0% 41 208.1 225.1 199.8 275.5 18.9 12. gi1-2.mpd01.sjc04.atlas.cogentco.com 35.9% 40 238.2 233.0 205.7 260.0 15.3 203.208.169.14 gi1-1.mpd01.sjc04.atlas.cogentco.com 13. te9-1.mpd01.sfo01.atlas.cogentco.com 17.9% 40 204.3 230.6 201.5 441.4 42.6 14. te4-1.mpd01.mci01.atlas.cogentco.com 15.0% 40 326.0 268.1 244.8 326.0 18.8 15. gi11-0-0.core01.mci01.atlas.cogentco.com 20.0% 40 309.2 280.8 257.2 309.2 14.7 16. po15-0.core01.stl03.atlas.cogentco.com 17.5% 40 294.1 267.1 241.0 309.3 17.4 17. vl3802.na21.b016110-1.stl03.atlas.cogentco.com 20.0% 40 255.0 264.5 246.1 313.3 17.6 18. 38.104.162.22 23.1% 40 253.7 270.8 246.7 299.5 14.1 19. 209.20.79.227 17.5% 40 289.8 278.1 248.2 340.6 20.6 20. www.slicehost.com 25.0% 40 283.3 273.7 243.6 304.1 15.8

    •  
      CommentAuthorjason
    • CommentTimeAug 9th 2008
     permalink
    Rossh,

    Unfortunately thats not the way it works. We have no control over Cogent's network. We can either announce our prefixes to them or not, but the peering between them and other carriers is completely out our control. Note again that the shortest AS path visible to our network for reaching singtel is over level(3) and that is how our traffic leaves.

1 to 20 of 22

  1. <
  2. 1
  3. 2
  4. >