Results 1 to 29 of 29
  1. #1
    Join Date
    Jun 2002
    Posts
    233

    Once Again WebReseller Pings Failing

    I regret ever going with webreseller for my dedicated service - I am very disturbed at how unreliable they are for pings. I realize it isn't their direct fault, but they are my provider, and they are who I answer to. I've gathered a couple traceroutes and sent them to the e-mail address @webreseller that I was encouraged to write to about network problems. After submitting the traceroutes, the CTO claimed there were no problems when he did traceroutes from many providers. Clearly there is a problem with bbnplanet's "gigabitethernet" router as it shows in the traceroutes to jump exactly at that router. Instead I was encouraged to use a more sophisticaed tracerouting tool as it provides a "more accurate measure of latency on a single device".

    Does anyone have any kind of feedback about this? Does anyone else agree with me that these kind of pings are unacceptible? What have you heard about WebReseller doing to solve this problem. For those of you that say e-mail webreseller yourself, if you read the first portion of this, you'll know I have.

  2. #2
    Join Date
    Jun 2002
    Location
    New York City
    Posts
    330
    HOST LOSS RCVD SENT BEST AVG WORST
    nycmny2wcx1-atm.wcg.net 0% 100 100 3.52 5.59 23.67
    pos4-6.core1.Dallas.Level3.net 0% 100 100 3.73 6.29 32.95
    ae0-54.mp2.NewYork1.Level3.net 0% 100 100 4.39 6.52 20.51
    so-0-1-0.mp1.Philadelphia1.Level3.net 0% 100 100 6.67 8.36 15.01
    gig10-0.hsa1.Philadelphia1.level3.net 0% 100 100 6.83 8.72 16.44
    unknown.Level3.net 0% 100 100 6.81 8.61 13.82
    o0-4jp1.phl004bd01.yipes.com 0% 100 100 7.26 8.91 13.60
    o1-4bd1.phl053s101.yipes.com 0% 100 100 8.12 10.07 22.78
    o1-53s11.phl054si01.yipes.com 0% 100 100 8.64 11.17 37.62
    66.7.139.82 0% 100 100 9.15 15.68 50.78
    webreseller.net 1% 99 100 9.75 14.43 40.08


    Doesn't look that bad to me.

  3. #3
    Join Date
    Jun 2002
    Posts
    233
    Your traceroute doesn't go through the "gigabitethernet" router I was talking about - It seems to be for most people in the East Coast.

  4. #4
    Join Date
    Oct 2002
    Location
    Port Chester, NY
    Posts
    15

    Re: Once Again WebReseller Pings Failing

    Originally posted by SynHost
    Does anyone else agree with me that these kind of pings are unacceptible?
    I dunno - post a traceroute and let's get a look.

    =mazz=

  5. #5
    Join Date
    Aug 2002
    Location
    DC
    Posts
    3,635
    Traceroute webreseller.net

    # IP address Host name Round trip time
    1 192.168.0.1 Unavailable 1 ms
    **********local***********
    6 68.39.224.162 Unavailable 18 ms
    7 12.125.176.121 Unavailable 18 ms
    8 12.123.137.22 gbr1-p70.phlpa.ip.att.net 42 ms
    9 12.122.2.17 gbr4-p20.n54ny.ip.att.net 35 ms
    10 12.123.1.125 ggr1-p370.n54ny.ip.att.net 31 ms
    11 192.205.32.18 att-gw.ny.genuity.net 45 ms
    12 4.24.11.138 p6-0.nycmny1-nbr2.bbnplanet.net 41 ms
    13 4.24.10.177 p9-0.phlapa1-br1.bbnplanet.net 27 ms
    14 4.24.11.81 p1-0.phlapa1-cr1.bbnplanet.net 30 ms
    15 4.25.93.54 gigabitethernet0-0.yipes2.bbnplanet.net28 ms
    16 66.54.175.202 o0-4jp2.phl004bd02.yipes.com 26 ms
    17 66.54.175.125 o1-4bd2.phl004bd01.yipes.com 27 ms
    18 66.54.144.109 o1-4bd1.phl053s101.yipes.com 37 ms
    19 66.54.144.190 o1-53s11.phl054si01.yipes.com 37 ms
    20 66.7.139.82 Unavailable 38 ms
    21 66.54.216.242 webreseller.net 39 ms


    No problems here.

  6. #6
    Join Date
    Oct 2002
    Location
    Georgia, USA
    Posts
    109
    Looks good to me @ #12. This is from NYC BTW.

    Tracing route to webreseller.net [66.54.216.242]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms fe0-0.router.X*********** [10.0.0.254]
    2 1 ms <1 ms <1 ms fe0-0.router.205.X*********** [10.0.0.254]
    3 1 ms 1 ms 1 ms 500.serial2-6.gw7.nyc1.alter.net [65.194.72.169]
    4 1 ms 1 ms 1 ms 553.at-5-0-0.XR1.NYC1.ALTER.NET [152.63.25.82]
    5 2 ms 1 ms 2 ms 0.so-1-1-0.xl1.nyc1.alter.net [152.63.19.86]
    6 2 ms 1 ms 1 ms 0.so-2-0-0.xl1.nyc9.alter.net [152.63.27.30]
    7 1 ms 1 ms 1 ms POS6-0.BR1.NYC9.ALTER.NET [152.63.18.225]
    8 2 ms 2 ms 1 ms p7-2.nycmny1-cr10.bbnplanet.net [4.0.6.141]
    9 2 ms 2 ms 2 ms p1-0.nycmny1-nbr2.bbnplanet.net [4.24.8.169]
    10 4 ms 3 ms 3 ms p9-0.phlapa1-br1.bbnplanet.net [4.24.10.177]
    11 3 ms 3 ms 3 ms p1-0.phlapa1-cr1.bbnplanet.net [4.24.11.81]
    12 39 ms 39 ms 39 ms gigabitethernet0-0.yipes2.bbnplanet.net [4.25.93.54]
    13 40 ms 40 ms 40 ms o0-4jp2.phl004bd02.yipes.com [66.54.175.202]
    14 40 ms 40 ms 40 ms o1-4bd2.phl004bd01.yipes.com [66.54.175.125]
    15 41 ms 40 ms 41 ms o1-4bd1.phl053s101.yipes.com [66.54.144.109]
    16 41 ms 41 ms 42 ms o1-53s11.phl054si01.yipes.com [66.54.144.190]
    17 44 ms 45 ms 107 ms 66.7.139.82
    18 43 ms 43 ms 42 ms webreseller.net [66.54.216.242]

    Trace complete.
    --
    Speckz

  7. #7
    Join Date
    Aug 2002
    Location
    DC
    Posts
    3,635
    From Network-Tools.com:

    TraceRoute to 66.54.216.242 [webreseller.net]

    Hop (ms) (ms) (ms) IP Address Host name
    1 0 0 0 66.46.176.3 -
    2 0 0 0 216.191.97.45 pos5-2.core2-mtl.bb.attcanada.ca
    3 0 0 0 216.191.65.217 srp2-0.core1-mtl.bb.attcanada.ca
    4 0 0 16 216.191.65.173 pos8-1.core2-tor.bb.attcanada.ca
    5 0 16 0 216.191.65.243 srp2-0.gwy1-tor.bb.attcanada.ca
    6 15 16 15 12.125.142.5 -
    7 16 15 16 12.123.5.222 gbr6-p80.cgcil.ip.att.net
    8 15 31 16 12.122.5.10 gbr3-p90.cgcil.ip.att.net
    9 31 16 16 12.123.5.145 ggr1-p360.cgcil.ip.att.net
    10 16 15 32 4.24.224.53 p6-0.chcgil2-cr8.bbnplanet.net
    11 15 32 15 4.24.9.45 so-3-3-0.chcgil2-br2.bbnplanet.net
    12 15 16 16 4.24.5.217 so-7-0-0.chcgil2-br1.bbnplanet.net
    13 32 15 31 4.24.9.58 p13-0.iplvin1-br1.bbnplanet.net
    14 16 31 16 4.24.10.154 p15-0.iplvin1-br2.bbnplanet.net
    15 47 31 62 4.24.10.181 p13-0.phlapa1-br1.bbnplanet.net
    16 31 47 47 4.24.11.81 p1-0.phlapa1-cr1.bbnplanet.net
    17 172 187 188 4.25.93.54 gigabitethernet0-0.yipes2.bbnplanet.net
    18 187 188 187 66.54.175.202 o0-4jp2.phl004bd02.yipes.com
    19 187 203 188 66.54.175.125 o1-4bd2.phl004bd01.yipes.com
    20 188 187 204 66.54.144.109 o1-4bd1.phl053s101.yipes.com
    21 203 188 187 66.54.144.190 o1-53s11.phl054si01.yipes.com
    22 203 188 187 66.7.139.82 -
    23 188 203 187 66.54.216.242 webreseller.net


    Now I see that...

  8. #8
    Join Date
    Nov 2001
    Posts
    1,262
    yea a server in new york is'nt taking that gigabitethernet

    newyork
    ---
    bash-2.05a$ /usr/sbin/traceroute webreseller.net
    traceroute to webreseller.net (66.54.216.242), 64 hops max, 40 byte packets
    1 66.181.174.1 (66.181.174.1) 0.570 ms 0.446 ms 0.436 ms
    2 ge-0-0-0-215.nyc002jp01.yipes.com (66.7.129.253) 1.071 ms 1.082 ms 1.040 ms
    3 nycmny2wcx1-pos4-2.wcg.net (64.200.86.209) 1.095 ms 1.052 ms 0.755 ms
    4 nycmny1wce1-pos5-0.wcg.net (65.77.98.29) 0.880 ms 1.221 ms 0.862 ms
    5 pos4-3.core1.NewYork1.Level3.net (209.244.160.137) 1.269 ms 1.724 ms 1.471 ms
    6 ae0-54.mp2.NewYork1.Level3.net (64.159.17.98) 2.065 ms 1.839 ms 1.848 ms
    7 so-0-1-0.mp1.Philadelphia1.Level3.net (64.159.0.141) 4.242 ms 4.765 ms 4.644 ms
    8 gig10-0.hsa1.Philadelphia1.level3.net (64.159.3.22) 5.017 ms 4.192 ms 4.328 ms
    9 unknown.Level3.net (63.209.178.162) 4.466 ms 4.521 ms 4.346 ms
    10 o0-4jp1.phl004bd01.yipes.com (66.54.175.194) 5.241 ms * 4.856 ms
    11 o1-4bd1.phl053s101.yipes.com (66.54.144.109) 5.667 ms 5.854 ms 5.868 ms
    12 o1-53s11.phl054si01.yipes.com (66.54.144.190) 7.540 ms 5.877 ms 6.142 ms
    13 66.7.139.82 (66.7.139.82) 7.428 ms 6.505 ms 6.789 ms
    14 webreseller.net (66.54.216.242) 6.105 ms 6.867 ms 6.445 ms
    bash-2.05a$

  9. #9
    Join Date
    Jul 2002
    Posts
    924
    # traceroute webreseller.net
    traceroute to webreseller.net (66.54.216.242), 30 hops max, 38 byte packets
    3 border6.s5-9.digitalwire-3.sfo.pnap.net (63.251.61.229) 2.893 ms 2.490 ms 2.498 ms
    4 core2.ge2-0-bbnet2.sfo.pnap.net (63.251.63.66) 3.124 ms 3.818 ms 2.944 ms
    5 POS2-3.GW4.SFO4.ALTER.NET (157.130.205.201) 4.733 ms 4.732 ms 8.023 ms
    6 162.ATM2-0.XR1.SFO4.ALTER.NET (152.63.48.194) 7.422 ms 4.643 ms 5.217 ms
    7 0.so-0-0-0.XL1.SFO4.ALTER.NET (152.63.55.57) 5.138 ms 5.303 ms 4.710 ms
    8 0.so-6-0-0.XL1.SAC1.ALTER.NET (152.63.145.242) 5.740 ms 4.971 ms 4.823 ms
    9 POS6-0.BR5.SAC1.ALTER.NET (152.63.52.225) 5.101 ms 6.249 ms 7.878 ms
    10 204.255.168.170 (204.255.168.170) 8.808 ms 6.490 ms 8.857 ms
    11 p1-0.paix-bi3.bbnplanet.net (4.0.3.173) 8.002 ms 6.259 ms 5.949 ms
    12 p13-0.snjpca1-br2.bbnplanet.net (4.24.7.37) 7.129 ms 7.039 ms 7.210 ms
    13 p3-0.dnvtco1-br2.bbnplanet.net (4.0.6.226) 29.881 ms 31.326 ms 31.450 ms
    14 so-0-0-0.chcgil2-br2.bbnplanet.net (4.24.9.61) 56.908 ms 57.759 ms 60.458 ms
    15 so-7-0-0.chcgil2-br1.bbnplanet.net (4.24.5.217) 57.314 ms 57.642 ms 58.227 ms
    16 p13-0.iplvin1-br1.bbnplanet.net (4.24.9.58) 61.392 ms 60.038 ms 60.877 ms
    17 p15-0.iplvin1-br2.bbnplanet.net (4.24.10.154) 206.550 ms 82.461 ms 205.627 ms
    18 p13-0.phlapa1-br1.bbnplanet.net (4.24.10.181) 116.538 ms 115.443 ms 227.563 ms

    19 p1-0.phlapa1-cr1.bbnplanet.net (4.24.11.81) 76.132 ms 78.517 ms 76.993 ms
    20 gigabitethernet0-0.yipes2.bbnplanet.net (4.25.93.54) 80.035 ms 79.860 ms 80.324 ms
    21 o0-4jp2.phl004bd02.yipes.com (66.54.175.202) 81.699 ms 80.169 ms 80.206 ms
    22 o1-4bd2.phl004bd01.yipes.com (66.54.175.125) 81.364 ms 79.875 ms 80.643 ms
    23 o1-4bd1.phl053s101.yipes.com (66.54.144.109) 80.427 ms 82.846 ms 80.711 ms
    24 o1-53s11.phl054si01.yipes.com (66.54.144.190) 81.621 ms 81.365 ms 81.411 ms
    25 66.7.139.82 (66.7.139.82) 82.004 ms 82.369 ms 81.426 ms
    26 webreseller.net (66.54.216.242) 82.161 ms 82.238 ms 81.966 ms
    From a unitedcolo dedicated server
    Unlimited Space & Bandwidth
    http://localhost/
    Providing hosting since 17/99/3003

  10. #10
    Join Date
    Sep 2001
    Location
    Pennsylvania
    Posts
    248

  11. #11
    Join Date
    Sep 2001
    Location
    Pennsylvania
    Posts
    248
    .
    Last edited by webreseller; 11-04-2002 at 10:38 PM.

  12. #12
    Join Date
    Apr 2002
    Location
    Philadelphia, PA
    Posts
    19
    As it stands right now I, nor anyone of my customer's that I keep in close contact with are having any problems. There is one issue that should be addressed and that is you should always perform at least three traceroutes to any host over a small period of time. There are hundreds of factors that can cause a momentary increase in response times. There is also the fact that upstream traffic can effect any traceroute to a host, and add latency. I have had many discussions with other stating that if you perform a traceroute and then increase your local (on your desktop or home LAN) traffic throughput that this can adversely effect the remainder of your traceroute. I would highly suggest to any and all that you get a program such as PingPlotter (even the free copy) to perform multiple and repeated traceroutes to a host and watch the changes in the trace as time progresses.


    There are also a number of outside sources (lookingglass) that you can use as reference, such as http://lg.level3.net.


    -Paul Rice
    CTO - WebReseller.Net

  13. #13
    Join Date
    Jun 2002
    Posts
    233
    Paul Rice - You act like we are all having "momentary" ping increases and that it is only occuring through very few people. You encourage us to use pingplotter, I have done so and even sent you a traceroute from it. Your company encourages us to e-mail [email protected] for network issues and not to post on this forum. I've e-mailed there and nothing has been done except recommending these alternatives that show no difference. I was treated like the problems I am experiencing are "not real" or "do not apply". Your complete unprofessionalism is so disturbing - I've gotten better responses using the old HelpDesk system for network issues.
    Stop giving excuses - I've done what you've said and you don't even assure us anything is being done to resolve this. It's been resolved before, but unfortunately once again it has gone down, and how do we know how long this will go on? I'm not going to put my business plan on promises that the issue will be resolved - Resolving it for two weeks doesn't count then having it go back down doesn't count.

    Lets take a look at some traceroutes if you are so determined this problem is miniscule. Anyone else is encouraged to post traceroutes - granted some will be fine it looks, and some will be bad, but I'm not going to profit over 70% of my customers having good pings and the rest not.

    Traceroute from ssr1.wprt1.suscom.net on AT&T:

    Tracing route to www.webreseller.net [66.54.216.242]
    over a maximum of 30 hops:

    1 11 ms 12 ms 10 ms 10.250.8.1
    2 8 ms 14 ms 10 ms ssr1.wprt1.suscom.net [64.78.83.238]
    3 16 ms 11 ms 20 ms att-ssr1.wprt1.suscom.net [64.78.83.253]
    4 56 ms 49 ms 33 ms 12.119.191.241
    5 17 ms 20 ms 17 ms gbr1-p57.phlpa.ip.att.net [12.123.205.98]
    6 24 ms 45 ms 20 ms gbr4-p20.n54ny.ip.att.net [12.122.2.17]
    7 35 ms 26 ms 48 ms ggr1-p370.n54ny.ip.att.net [12.123.1.125]
    8 23 ms 23 ms 21 ms att-gw.ny.genuity.net [192.205.32.18]
    9 23 ms 25 ms 22 ms p6-0.nycmny1-nbr2.bbnplanet.net [4.24.11.138]
    10 25 ms 24 ms 22 ms p9-0.phlapa1-br1.bbnplanet.net [4.24.10.177]
    11 25 ms 23 ms 71 ms p1-0.phlapa1-cr1.bbnplanet.net [4.24.11.81]
    12 207 ms 212 ms 209 ms gigabitethernet0-0.yipes2.bbnplanet.net [4.25.93
    .54]
    13 207 ms 233 ms 210 ms o0-4jp2.phl004bd02.yipes.com [66.54.175.202]
    14 214 ms 213 ms 201 ms o1-4bd2.phl004bd01.yipes.com [66.54.175.125]
    15 235 ms 191 ms 191 ms o1-4bd1.phl053s101.yipes.com [66.54.144.109]
    16 197 ms 215 ms 203 ms o1-53s11.phl054si01.yipes.com [66.54.144.190]
    17 215 ms 223 ms 220 ms 66.7.139.82
    18 190 ms 240 ms 192 ms webreseller.net [66.54.216.242]

    Trace complete.


    Trace from Atlanta:

    4 42 ms 27 ms 28 ms 12.124.58.77
    5 28 ms 55 ms 27 ms gbr6-p80.attga.ip.att.net [12.123.21.78]
    6 41 ms 42 ms 13 ms tbr1-p013601.attga.ip.att.net [12.122.12.25]
    7 1744 ms 426 ms 27 ms tbr2-p013801.wswdc.ip.att.net [12.122.10.69]
    8 41 ms 55 ms 96 ms ggr1-p3100.wswdc.ip.att.net [12.122.11.238]
    9 27 ms 82 ms 55 ms att-gw.dc.genuity.net [192.205.32.114]
    10 41 ms 41 ms 96 ms so-3-1-0.washdc3-nbr2.bbnplanet.net [4.24.8.121]

    11 41 ms 28 ms 41 ms p9-0.phlapa1-br2.bbnplanet.net [4.24.10.186]
    12 82 ms 69 ms 55 ms p15-0.phlapa1-br1.bbnplanet.net [4.24.10.89]
    13 55 ms 42 ms 41 ms p1-0.phlapa1-cr1.bbnplanet.net [4.24.11.81]
    14 206 ms 151 ms 220 ms gigabitethernet0-0.yipes2.bbnplanet.net [4.25.93
    .54]
    15 151 ms 206 ms 193 ms ge-1-3-0.phl004jp01.yipes.com [66.54.175.134]
    16 151 ms 151 ms 165 ms o0-4jp1.phl004bd01.yipes.com [66.54.175.194]
    17 193 ms 178 ms 220 ms o1-4bd1.phl053s101.yipes.com [66.54.144.109]
    18 178 ms 165 ms 233 ms o1-53s11.phl054si01.yipes.com [66.54.144.190]
    19 220 ms 164 ms 206 ms 66.7.139.82
    20 165 ms 234 ms 178 ms www.kmclan.com [66.227.25.201]

    Trace complete.


    Again, others encouraged to post. Webreseller would rather have us e-mail them, but I'd much rather see if other customers are having the same problems and how we feel about they are handling it. This board is a place for discussion - rest assured WebReseller we do e-mail you too..

  14. #14
    Join Date
    Jan 2002
    Location
    Boston
    Posts
    5,010
    NeoTrace Trace Version 3.25 Results
    Target: webreseller.net
    Date: 11/4/02 (Monday), 10:43:31 PM
    Nodes: 23


    Node Data
    Node Net Reg IP Address Location Node Name
    1 - - xx.xx.xx.xx 42.265N, 72.269W e1r9t2
    2 1 - 10.216.232.1 Unknown
    3 2 1 24.128.8.105 Unknown bar01-p2-0-0.spfdhe1.ma.attbb.net
    4 2 1 24.128.0.201 Unknown bar01-p1-0.wsfdhe1.ma.attbb.net
    5 2 1 24.128.0.101 Unknown bar02-p6-0.ndhmhe1.ma.attbb.net
    6 3 - 12.125.39.45 Unknown
    7 3 2 12.123.40.102 Unknown gbr2-p70.cb1ma.ip.att.net
    8 3 2 12.122.11.241 Unknown tbr2-p013601.cb1ma.ip.att.net
    9 - - 0.0.0.0 Unknown No Response
    10 3 2 12.122.11.210 Chicago ggr1-p3100.cgcil.ip.att.net
    11 4 3 4.24.224.53 Chicago p6-0.chcgil2-cr8.bbnplanet.net
    12 4 3 4.24.9.45 Chicago so-3-3-0.chcgil2-br2.bbnplanet.net
    13 4 3 4.24.4.18 New York p13-0.nycmny1-nbr1.bbnplanet.net
    14 4 3 4.24.10.210 New York p15-0.nycmny1-nbr2.bbnplanet.net
    15 4 3 4.24.10.177 Unknown p9-0.phlapa1-br1.bbnplanet.net
    16 4 3 4.24.11.81 Unknown p1-0.phlapa1-cr1.bbnplanet.net
    17 4 3 4.25.93.54 Unknown gigabitethernet0-0.yipes2.bbnplanet.net
    18 5 4 66.54.175.134 Unknown ge-1-3-0.phl004jp01.yipes.com
    19 5 4 66.54.175.194 Unknown o0-4jp1.phl004bd01.yipes.com
    20 5 4 66.54.144.109 Unknown o1-4bd1.phl053s101.yipes.com
    21 5 4 66.54.144.190 Unknown o1-53s11.phl054si01.yipes.com
    22 6 - 66.7.139.82 Unknown
    23 7 5 66.54.216.242 Unknown webreseller.net


    Packet Data
    Node High Low Avg Tot Lost
    1 0 0 0 1 0
    2 36 12 26 5 0
    3 21 10 17 5 0
    4 31 13 20 5 0
    5 36 17 25 5 0
    6 52 15 28 5 0
    7 30 17 24 5 0
    8 41 20 28 5 0
    9 ---- ---- ---- 10 10
    10 46 40 43 5 0
    11 59 40 44 5 0
    12 48 39 41 5 0
    13 72 40 52 5 0
    14 60 45 58 5 0
    15 61 46 56 5 0
    16 58 46 49 5 0
    17 183 152 154 5 0
    18 214 180 185 5 0
    19 171 142 152 5 0
    20 227 170 196 5 0
    21 164 148 154 4 0
    22 212 163 191 4 0
    23 152 108 148 4 0


    Network Data
    Network id#: 1

    OrgName: Internet Assigned Numbers Authority
    OrgID: IANA

    Network id#: 2

    OrgName: AT&T Broadband Northeast
    OrgID: ATBN

    Network id#: 3

    OrgName: AT&T WorldNet Services
    OrgID: ATTW

    Network id#: 4

    OrgName: Genuity
    OrgID: GNTY

    Network id#: 5

    OrgName: Yipes Communications, Inc.
    OrgID: YIPS

    Network id#: 6

    OrgName: Yipes Communications, Inc.
    OrgID: YIPS

    Network id#: 7
    Yipes Communications, Inc. YIPES-BLK3 (NET-66-54-128-0-1)
    66.54.128.0 - 66.54.255.255
    Advanced Web Hosting and Design, Inc AWHD-BLK3 (NET-66-54-216-0-1)
    66.54.216.0 - 66.54.219.255
    WebReseller.Net WEBRESELLER-BLK1 (NET-66-54-216-0-2)
    66.54.216.0 - 66.54.216.255



    Registrant Data
    Registrant id#: 1
    Registrant:
    AT&T Broadband (ATTBB-DOM)
    188 INVERNESS DR W
    ENGLEWOOD, CO 80112-5202
    US

    Registrant id#: 2
    Registrant:
    AT&T Corp. (ATT2-DOM)
    55 Corporate Drive
    Bridgewater, NJ 08807
    US

    Registrant id#: 3
    Registrant:
    BBN PLANET CORP. (BBNPLANET2-DOM)
    3801 East Bayshore Road
    Palo Alto, CA 94303
    US

    Registrant id#: 4
    Registrant:
    Yipes Enterprise Services, Inc. (YIPES2-DOM)
    114 Sansome St., 11th Floor
    San Francisco, CA 94104
    US

    Registrant id#: 5
    Registrant:
    Advanced Web Hosting & Design, Inc. (WN-D-93795822)
    422 Exton Commons
    Exton
    PA,19341

    _____
    NeoTrace Copyright 1997-2001 NeoWorx Inc

  15. #15
    Join Date
    Jun 2002
    Posts
    233
    This makes no sense - how can data going through the same router have completely different response times from different places even if hops before that show similar pings? Clearly there is still a problem.. Any other traceroutes appreciated.

  16. #16
    Join Date
    Nov 2001
    Posts
    1,262
    SynHost: can I please have a file on your server like 50 megs to test? i just tested download from my server and the fastest i could pull from my webreseller box is 10mbit but from rackshack i got 65mbit so i'm thinking webreseller caps us @ 10mbit i dont believe they did that before did they ?

  17. #17
    Join Date
    Apr 2002
    Location
    Philadelphia, PA
    Posts
    19
    I am not denying that there may be an issue, but I am stating that we have not been able to reproduce this (from the same path). I have been monitoring the traceroutes through my Comcast cable modem and it too is go through the same hop (4.25.93.54), but I have not once seen any problems. This is where the question is coming into play.

    I have submitted another ticket with Yipes! to have them look into the issue once again. Perhaps you could supply me with more information, such as the time/date of the traceroute, your internet service provider, and even your IP address.

  18. #18
    Join Date
    Apr 2002
    Location
    Philadelphia, PA
    Posts
    19
    Originally posted by zdwebhosting
    webreseller box is 10mbit but from rackshack i got 65mbit so i'm thinking webreseller caps us @ 10mbit
    We do not cap the network speeds for anyone, unless they specifically ask us to do so.


    -Paul Rice
    CTO - WebReseller.Net

  19. #19
    Join Date
    Nov 2001
    Posts
    1,262
    Originally posted by paulrice420


    We do not cap the network speeds for anyone, unless they specifically ask us to do so.


    -Paul Rice
    CTO - WebReseller.Net
    wierd how much bandwidth do youguys have available to burst too? thats not being used that is

  20. #20
    Join Date
    Apr 2002
    Location
    Philadelphia, PA
    Posts
    19
    Just an FYI for some that don't know...

    http://webreseller.net/NOC/Packet%20...%20Latency.htm

  21. #21
    Join Date
    Nov 2001
    Posts
    852
    yipes goes to 1 gbps

  22. #22
    Join Date
    Jun 2002
    Posts
    233
    Problem stop occuring - I've lost many clients already because of this - It seems most of the problems are occuring with the BBNPLanet router that routes packets to AT&T

  23. #23
    Join Date
    Jun 2002
    Posts
    233
    I absolutely cannot understand how barely anybody seems to be experiencing any of these problems with the yipes router.. Am I the only broadband customer with packets routing through AT&T? I've had 3 days of straght 150+ pings - I cannot stand this!

  24. #24
    Join Date
    Sep 2001
    Location
    Pennsylvania
    Posts
    248
    Honestly Syn, we have received zero complaints about this tonight... They will be moving things back to Level 3 very shortly. It appears as though the AT&T and Level 3 issue has been resolved, however, things will be tested prior..

  25. #25
    Join Date
    Nov 2002
    Location
    Chicago IL
    Posts
    885
    Originally posted by SynHost
    Problem stop occuring - I've lost many clients already because of this - It seems most of the problems are occuring with the BBNPLanet router that routes packets to AT&T

    Then i think you should complain to ATT cause last time it was an issue with ATT->L3 Now you had ATT->BBN, i understand your frustation but no need to take it out on webreseller when it is out of there hands..

  26. #26
    Join Date
    Jun 2002
    Posts
    233
    Thanks webreseller - I feel much better when I'm updated to the status. I think i would feel better about the Level3 to AT&T peer so I hope they switch that soon and I hope pings are once again stable. I'm sorry for taking it out on webreseller, but more of my frustration was that the CTO seemd to think my problem was nonexistant - he seemed to think traceroutes lie

    Thanks for the update and hopefully things will be back to normal soon.

  27. #27
    Join Date
    Sep 2001
    Location
    Pennsylvania
    Posts
    248
    I do not think he thought there was no problem, but when we try to duplicate the problem from different sources and are unable to do so it can make it very difficult....

  28. #28
    Join Date
    Jun 2001
    Posts
    960
    I'm glad that it'd be back to Level3

    I hope this would resolve your problem, SynHost. I know the latency problem affected you most cause you're running game servers where ping times are very sensitive. Anyway, I hope you'd still stay with Webreseller. They're doing their best to keep the network top-notch

  29. #29
    Join Date
    Sep 2002
    Location
    Los Angeles
    Posts
    37
    Originally posted by SynHost
    This makes no sense - how can data going through the same router have completely different response times from different places even if hops before that show similar pings? Clearly there is still a problem.. Any other traceroutes appreciated.
    Because at that hop, you're entering a different AS, with a different return path/outbound routing policy. Doesn't mean there's a problem per se, just that the routing happens to be highly assymetric.

    Grant

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •