Page 1 of 2 12 LastLast
Results 1 to 40 of 78
  1. #1
    Join Date
    Jun 2002
    Posts
    233

    WebReseller Pings Up Again - Customers Furious

    I've posted before about this, and then it seems as though they have fixed the problem. Now once again the pings are spiking, even above 300. I simply cannot take this anymore - Unless webreseller prooves to provide reliable pings, I'm afraid I may have to cancel my server. I'll have to see how things go. Is anyone else experiencing this?

    Tracing route to synhost.com [66.227.25.201]
    over a maximum of 30 hops:

    1 26 ms 10 ms 22 ms 10.250.8.1
    2 10 ms 11 ms 10 ms ssr1.wprt1.suscom.net [64.78.83.238]
    3 14 ms 9 ms 52 ms att-ssr1.wprt1.suscom.net [64.78.83.253]
    4 36 ms 26 ms 20 ms 12.119.191.241
    5 19 ms 17 ms 19 ms gbr1-p57.phlpa.ip.att.net [12.123.205.98]
    6 21 ms 22 ms 21 ms gbr4-p20.n54ny.ip.att.net [12.122.2.17]
    7 27 ms 20 ms 22 ms ggr1-p370.n54ny.ip.att.net [12.123.1.125]
    8 287 ms 298 ms 302 ms pos6-1.core2.NewYork1.Level3.net [63.211.54.97]

    9 314 ms 303 ms 293 ms ae0-51.mp1.NewYork1.Level3.net [64.159.17.1]
    10 292 ms 309 ms 301 ms so-0-2-0.mp2.Philadelphia1.Level3.net [64.159.0.
    133]
    11 257 ms 273 ms 261 ms gig4-1.hsa1.Philadelphia1.level3.net [64.159.3.3
    0]
    12 255 ms 251 ms 250 ms unknown.Level3.net [63.209.178.162]
    13 262 ms 266 ms 260 ms 66.54.175.194
    14 314 ms 322 ms 345 ms o1-4bd1.phl053s101.yipes.com [66.54.144.109]
    15 289 ms 248 ms 249 ms o1-53s11.phl054si01.yipes.com [66.54.144.190]
    16 313 ms 328 ms 339 ms 66.7.139.82
    17 277 ms 314 ms 310 ms 66.227.25.201

    Thanks,
    Ben

  2. #2
    Join Date
    Apr 2001
    Location
    St. Louis, MO
    Posts
    2,508
    I don't think there is much they can do to fix. Looks like they use Yipes and the problem is the ATT and Level3 peer. Because they use Yipes, they really have not ability to correct the problem except to complain to Yipes.
    Mike @ Xiolink.com
    http://www.xiolink.com 1-877-4-XIOLINK
    Advanced Managed Microsoft Hosting
    "Your data... always within reach"

  3. #3
    Join Date
    Nov 2001
    Posts
    852
    I usually defend webreseller about this stuff but this time it is affecting me, it seems anything that goes over an At&t connection gets slow as hell.

    Also, if anyone can tell me why I have to type the whole path to get commands to work in windows XP, please let me know because it is annoying, it just started doing this and i dont known why:

    c:\windows\system32\tracert atlnetworks.com

    Tracing route to atlnetworks.com [66.227.36.243]
    over a maximum of 30 hops:

    1 24 ms 28 ms 207 ms 10.150.112.1
    2 * * * Request timed out.
    3 * * * Request timed out.
    4 45 ms 52 ms 60 ms 68.47.160.62
    5 115 ms 107 ms 130 ms 12.118.184.9
    6 114 ms 95 ms 35 ms gbr1-p70.attga.ip.att.net [12.123.21.2]
    7 39 ms 61 ms 35 ms tbr2-p013502.attga.ip.att.net [12.122.12.33]
    8 124 ms 123 ms 37 ms tbr2-p013801.wswdc.ip.att.net [12.122.10.69]
    9 148 ms 32 ms 91 ms ggr1-p3100.wswdc.ip.att.net [12.122.11.238]
    10 260 ms 268 ms 351 ms pos6-3.core1.Washington1.Level3.net [209.244.219
    .157]
    11 325 ms 341 ms 469 ms ae0-55.mp1.Washington1.Level3.net [64.159.18.129
    ]
    12 279 ms 305 ms 266 ms so-0-0-0.mp1.Philadelphia1.Level3.net [64.159.0.
    110]
    13 349 ms 364 ms 450 ms gige9-0.hsipaccess1.Philadelphia1.Level3.net [64
    .159.0.146]
    14 260 ms 321 ms 357 ms unknown.Level3.net [63.209.178.162]
    15 272 ms 318 ms 291 ms 66.54.175.194
    16 356 ms 383 ms 304 ms o1-4bd1.phl053s101.yipes.com [66.54.144.109]
    17 317 ms 278 ms 283 ms o1-53s11.phl054si01.yipes.com [66.54.144.190]
    18 280 ms 344 ms 290 ms 66.7.139.82
    19 279 ms 300 ms 340 ms 66.227.36.243

    Trace complete.

  4. #4
    Join Date
    Jun 2001
    Location
    Denver, CO
    Posts
    3,301
    Not much webreseller can do about this problem. The issue is with peering between AT&T and Level(3) in Washington. You'll see from my traceroute, which avoids that hop, that the webreseller "network" itself is actually working just fine:


    Target Name: webreseller.net
    IP: 66.54.216.242
    Date/Time: 10/16/2002 10:15:04 PM

    1 0 ms 0 ms 0 ms [192.168.123.254]
    2 10 ms 10 ms 10 ms router-209-54-72-1.ct.dsl.ntplx.com [209.54.72.1]
    3 10 ms 10 ms 10 ms broadband-router.ether.ntplx.net [204.213.183.29]
    4 30 ms 30 ms 30 ms sl-gw27-nyc-2-0-TS10.sprintlink.net [144.223.36.245]
    5 10 ms 10 ms 10 ms sl-bb23-nyc-15-1.sprintlink.net [144.232.7.21]
    6 30 ms 30 ms 10 ms sl-bb20-nyc-8-0.sprintlink.net [144.232.7.13]
    7 40 ms 30 ms 30 ms pos6-2.core1.newyork1.level3.net [209.244.160.153]
    8 30 ms 50 ms 30 ms ae0-55.mp1.newyork1.level3.net [64.159.17.129]
    9 40 ms 30 ms 30 ms so-0-1-0.mp1.Philadelphia1.Level3.net [64.159.0.141]
    10 30 ms 50 ms 50 ms gige9-0.hsipaccess1.philadelphia1.level3.net [64.159.0.146]
    11 40 ms 30 ms 30 ms unknown.Level3.net [63.209.178.162]
    12 40 ms 30 ms 50 ms [66.54.175.194]
    13 41 ms 30 ms 30 ms o1-4bd1.phl053s101.yipes.com [66.54.144.109]
    14 30 ms 50 ms 50 ms o1-53s11.phl054si01.yipes.com [66.54.144.190]
    15 40 ms 30 ms 60 ms [66.7.139.82]
    16 30 ms 30 ms 50 ms webreseller.net [66.54.216.242]
    Jay Sudowski // Handy Networks LLC // Co-Founder & CTO
    AS30475 - Level(3), HE, Telia, XO and Cogent. Noction optimized network.
    Offering Dedicated Server and Colocation Hosting from our SSAE 16 SOC 2, Type 2 Certified Data Center.
    Current specials here. Check them out.

  5. #5
    Join Date
    Apr 2001
    Location
    St. Louis, MO
    Posts
    2,508
    Also, if anyone can tell me why I have to type the whole path to get commands to work in windows XP, please let me know because it is annoying, it just started doing this and i dont known why
    Probably becuase you have something wrong in your Enviroment Variables. Right click My Computer and open Properties. Then select the Advanced tab and click Enviroment Variables. What do you have under "Path"?
    Mike @ Xiolink.com
    http://www.xiolink.com 1-877-4-XIOLINK
    Advanced Managed Microsoft Hosting
    "Your data... always within reach"

  6. #6
    Join Date
    Apr 2002
    Location
    North Kansas City, MO
    Posts
    2,565
    Check your path statement and make sure the directory is there.

    Aaron

    Originally posted by goodness0001
    I usually defend webreseller about this stuff but this time it is affecting me, it seems anything that goes over an At&t connection gets slow as hell.

    Also, if anyone can tell me why I have to type the whole path to get commands to work in windows XP, please let me know because it is annoying, it just started doing this and i dont known why:

    c:\windows\system32\tracert atlnetworks.com

    Tracing route to atlnetworks.com [66.227.36.243]
    over a maximum of 30 hops:

    1 24 ms 28 ms 207 ms 10.150.112.1
    2 * * * Request timed out.
    3 * * * Request timed out.
    4 45 ms 52 ms 60 ms 68.47.160.62
    5 115 ms 107 ms 130 ms 12.118.184.9
    6 114 ms 95 ms 35 ms gbr1-p70.attga.ip.att.net [12.123.21.2]
    7 39 ms 61 ms 35 ms tbr2-p013502.attga.ip.att.net [12.122.12.33]
    8 124 ms 123 ms 37 ms tbr2-p013801.wswdc.ip.att.net [12.122.10.69]
    9 148 ms 32 ms 91 ms ggr1-p3100.wswdc.ip.att.net [12.122.11.238]
    10 260 ms 268 ms 351 ms pos6-3.core1.Washington1.Level3.net [209.244.219
    .157]
    11 325 ms 341 ms 469 ms ae0-55.mp1.Washington1.Level3.net [64.159.18.129
    ]
    12 279 ms 305 ms 266 ms so-0-0-0.mp1.Philadelphia1.Level3.net [64.159.0.
    110]
    13 349 ms 364 ms 450 ms gige9-0.hsipaccess1.Philadelphia1.Level3.net [64
    .159.0.146]
    14 260 ms 321 ms 357 ms unknown.Level3.net [63.209.178.162]
    15 272 ms 318 ms 291 ms 66.54.175.194
    16 356 ms 383 ms 304 ms o1-4bd1.phl053s101.yipes.com [66.54.144.109]
    17 317 ms 278 ms 283 ms o1-53s11.phl054si01.yipes.com [66.54.144.190]
    18 280 ms 344 ms 290 ms 66.7.139.82
    19 279 ms 300 ms 340 ms 66.227.36.243

    Trace complete.
    Aaron Wendel
    Wholesale Internet, Inc. - http://www.wholesaleinternet.net
    Kansas City Internet eXchange - http://www.kcix.net

  7. #7
    Join Date
    Aug 2001
    Posts
    1,210
    This is a problem between Level3 and AT&T, and has nothing to do with webreseller. In both of your traceroutes, the problems start well before you get anywhere near webreseller's network.


    -Bob

  8. #8
    Yes this is out of webreseller's control but if they are only using yipes they may want to add another provider.
    Multiple Image Corporation - http://www.multipleimage.com
    Diverse Solutions for Diverse Companies.
    Virtual, Dedicated & Colocated Hosting.

  9. #9
    Join Date
    Jun 2001
    Location
    Denver, CO
    Posts
    3,301
    Even if they did have another provider BGP'd, it would be hard to route around this because the link is still up, it's just very congested.
    Jay Sudowski // Handy Networks LLC // Co-Founder & CTO
    AS30475 - Level(3), HE, Telia, XO and Cogent. Noction optimized network.
    Offering Dedicated Server and Colocation Hosting from our SSAE 16 SOC 2, Type 2 Certified Data Center.
    Current specials here. Check them out.

  10. #10
    Join Date
    Apr 2001
    Location
    St. Louis, MO
    Posts
    2,508
    Even if they did have another provider BGP'd, it would be hard to route around this because the link is still up, it's just very congested.
    Right, but they could always stop routing on Yipes or prepend, etc.
    Mike @ Xiolink.com
    http://www.xiolink.com 1-877-4-XIOLINK
    Advanced Managed Microsoft Hosting
    "Your data... always within reach"

  11. #11
    Join Date
    Jun 2002
    Posts
    233
    Sorry,

    I should have clarified in my original post. I know very well this is out of WebReseller's hands and completely a peering issue between Level3 and AT&T, but still there has to be something that can be done. Basically webreseller isn't getting the level of service they are paying for.. They are paying for Yipes connections with horrible pings - doesn't that affect them and shouldn't that be in their service agreement?

    Reguardless of who it is, unfortunately I may have to cancel with webreseller, as they are my provider, and they are my provider that uses as of right now, seemingly unreliable ping-wise connections.

  12. #12
    Join Date
    Nov 2001
    Posts
    852
    Yes i agree with the last post, we are paying webreseller so as far was we are concerned it is their problem. At&t has been having these problems for weeks now, i would be really really really pissed off if i were webreseller.

  13. #13
    Join Date
    Oct 2002
    Posts
    30
    How do you know its and AT&T problem?

    Could be Level3 issue and their peering link with AT&T and them not buying enough transfer to handle the peak times of the day.

  14. #14
    Join Date
    May 2002
    Posts
    190
    synhost post the traceroute from your server to yourself .. you have yet to do so i would like to see the otherside of this story
    C Code. C code run. Run, code, run...
    Segmentation fault (core dumped).. aww sh!t

  15. #15
    Join Date
    Jun 2002
    Posts
    233
    Here you go faggle, although from the traceroute that I showed to begin with, it would naturally go the same way in reverse as you can see the slowdown is the hop between Level3 and AT&T:

    [[email protected] root]# traceroute x
    traceroute to x (x), 30 hops max, 38 byte packets
    1 66.54.168.1 (66.54.168.1) 0.796 ms 0.314 ms 0.261 ms
    2 66.7.139.81 (66.7.139.81) 0.748 ms 1.376 ms 1.041 ms
    3 o1-10s11.phl053s101.yipes.com (66.54.144.189) 2.254 ms 1.840 ms 2.065 ms
    4 o1-53s11.phl004bd01.yipes.com (66.54.144.110) 2.343 ms 3.987 ms 2.870 ms
    5 66.54.175.193 (66.54.175.193) 2.367 ms 2.870 ms 2.305 ms
    6 gigabitethernet8-0-515.hsipaccess1.Philadelphia1.Level3.net (63.209.178.161) 2.539 ms 2.218 ms 2.020 ms
    7 ge-6-0-0.mp2.Philadelphia1.Level3.net (64.159.0.153) 2.997 ms 3.346 ms 2.871 ms
    8 so-0-0-0.mp1.NewYork1.level3.net (64.159.1.65) 4.692 ms 7.594 ms 7.005 ms
    9 gigabitethernet2-1.core2.NewYork1.Level3.net (64.159.17.70) 5.682 ms 5.572 ms 5.131 ms
    10 ggr1-p370.n54ny.ip.att.net (63.211.54.66) 116.091 ms 113.970 ms 114.674 ms
    11 gbr4-p50.n54ny.ip.att.net (12.123.1.126) 116.527 ms 114.698 ms 115.447 ms
    12 gbr1-p20.phlpa.ip.att.net (12.122.2.18) 114.226 ms 116.805 ms 114.992 ms
    13 ar1-p310.cmdnj.ip.att.net (12.123.205.97) 116.139 ms 115.369 ms 119.252 ms
    14 12.119.191.242 (12.119.191.242) 132.582 ms 131.886 ms 135.338 ms
    15 ssr1-att.wprt1.suscom.net (64.78.83.254) 136.697 ms 137.866 ms 133.658 ms
    16 ubr1.wprt1.suscom.net (64.78.83.235) 155.533 ms 134.831 ms 138.796 ms

    Other people are having problems as well, and I've had these in the past. What other side of the story could there be?

  16. #16
    Join Date
    Nov 2001
    Posts
    852
    --- 66.227.XX.XX ping statistics ---
    103 packets transmitted, 76 packets received, 26% packet loss
    round-trip min/avg/max/mdev = 60.273/72.092/105.587/9.103 ms

    26% loss from dialtone internet

  17. #17
    Join Date
    May 2002
    Posts
    190
    Originally posted by SynHost
    Here you go faggle, although from the traceroute that I showed to begin with, it would naturally go the same way in reverse as you can see the slowdown is the hop between Level3 and AT&T:

    [[email protected] root]# traceroute x
    traceroute to x (x), 30 hops max, 38 byte packets
    1 66.54.168.1 (66.54.168.1) 0.796 ms 0.314 ms 0.261 ms
    2 66.7.139.81 (66.7.139.81) 0.748 ms 1.376 ms 1.041 ms
    3 o1-10s11.phl053s101.yipes.com (66.54.144.189) 2.254 ms 1.840 ms 2.065 ms
    4 o1-53s11.phl004bd01.yipes.com (66.54.144.110) 2.343 ms 3.987 ms 2.870 ms
    5 66.54.175.193 (66.54.175.193) 2.367 ms 2.870 ms 2.305 ms
    6 gigabitethernet8-0-515.hsipaccess1.Philadelphia1.Level3.net (63.209.178.161) 2.539 ms 2.218 ms 2.020 ms
    7 ge-6-0-0.mp2.Philadelphia1.Level3.net (64.159.0.153) 2.997 ms 3.346 ms 2.871 ms
    8 so-0-0-0.mp1.NewYork1.level3.net (64.159.1.65) 4.692 ms 7.594 ms 7.005 ms
    9 gigabitethernet2-1.core2.NewYork1.Level3.net (64.159.17.70) 5.682 ms 5.572 ms 5.131 ms
    10 ggr1-p370.n54ny.ip.att.net (63.211.54.66) 116.091 ms 113.970 ms 114.674 ms
    11 gbr4-p50.n54ny.ip.att.net (12.123.1.126) 116.527 ms 114.698 ms 115.447 ms
    12 gbr1-p20.phlpa.ip.att.net (12.122.2.18) 114.226 ms 116.805 ms 114.992 ms
    13 ar1-p310.cmdnj.ip.att.net (12.123.205.97) 116.139 ms 115.369 ms 119.252 ms
    14 12.119.191.242 (12.119.191.242) 132.582 ms 131.886 ms 135.338 ms
    15 ssr1-att.wprt1.suscom.net (64.78.83.254) 136.697 ms 137.866 ms 133.658 ms
    16 ubr1.wprt1.suscom.net (64.78.83.235) 155.533 ms 134.831 ms 138.796 ms

    Other people are having problems as well, and I've had these in the past. What other side of the story could there be?

    well i had a problem just like that with one of my servers it would jump like right at the same spot level3 -> att in ny but on the reverse route it didnt go near ny and the problem was in chicago with atdn to no surprise. ;p
    C Code. C code run. Run, code, run...
    Segmentation fault (core dumped).. aww sh!t

  18. #18
    Join Date
    Nov 2001
    Posts
    852
    Now they are completely offline

  19. #19
    Join Date
    Apr 2002
    Location
    Philadelphia
    Posts
    2,277
    25% Packet Loss
    Ping Average: 1488

    However, I do wish them best of luck getting these issues resolved. I know how it feels to have problems that are sometimes out of your control

  20. #20
    Join Date
    May 2002
    Posts
    190
    --- webreseller.net ping statistics ---
    131 packets transmitted, 126 packets received, 3% packet loss
    round-trip min/avg/max/mdev = 40.958/41.516/44.870/0.562 ms

    --- webreseller.net ping statistics ---
    131 packets transmitted, 126 packets received, 3% packet loss
    round-trip min/avg/max/stddev = 11.016/12.430/44.639/3.768 ms

    hostmania/servint
    C Code. C code run. Run, code, run...
    Segmentation fault (core dumped).. aww sh!t

  21. #21
    Join Date
    Nov 2001
    Posts
    852
    It is going on and off like a yo yo. I wonder if they are doing their router and switch maintenance and i think yipes had some maintenance coming up as well.

    Usually their network is awsome, but looks like there are some issues out of their hands.

  22. #22
    Join Date
    Nov 2000
    Location
    Tasmania, Australia.
    Posts
    3,587
    According to last night's email, we're 1 hour into a 4 hour Yipes maintenance window right now.

    Cheers

    Gary

  23. #23
    Join Date
    Sep 2001
    Location
    Pennsylvania
    Posts
    248
    There was a maintenance notice sent out the other day that network upgrades and such were going to be done last night...

  24. #24
    Join Date
    Nov 2001
    Posts
    852
    I dont much care about the network upgrades, those are fine, because i found the notice in my inbox after the fact, but the only thing that concerns me is the latency that occurs on some routes to your network...and also the amount of dropped packets...

    What is webreseller doing to prevent this latency every night? It got so bad at some points that my ssh client would drop the connection right in the middle of doing something...

  25. #25
    Join Date
    Sep 2001
    Location
    Pennsylvania
    Posts
    248
    We are working with Level 3 and ATT with this issue...

  26. #26
    Join Date
    Nov 2001
    Posts
    852
    We will all be excited when this issue is resolved, hopefully your check book can do some talking with them.

  27. #27
    Join Date
    Jun 2001
    Posts
    960
    webreseller, any ETA about the new lines?

  28. #28
    Join Date
    Sep 2001
    Location
    Pennsylvania
    Posts
    248
    New Lines ? We had no idea we were getting new lines....

    Level3 stated that they have already increase bandwidth with ATT in NYC. This past week L3 has been having more capacity issues, I.E. last night they had a 3 hour period of heavy usage between ATT and L3. Level 3 has plans to add more capacity

  29. #29
    Join Date
    Jun 2001
    Posts
    960
    What? If I remember correctly, you mentioned in another threads about the plan to add one or two new lines Hmmm...

  30. #30
    Join Date
    Aug 2001
    Posts
    1,210
    Originally posted by webreseller
    New Lines ? We had no idea we were getting new lines....
    ????

    Back in April, you stated that the new datacenter would have a second line, a new carrier, and BGP.

    <me digs furiously through old bookmarks....>

    http://webhostingtalk.com/showthread...93&#post316393


    -Bob

  31. #31
    Join Date
    Jun 2001
    Posts
    960
    TMX, thanks for backing me up

    I also found the thread where you mentioned about a new provider coming soon:
    http://www.webhostingtalk.com/showth...5&pagenumber=3

    And JBIZ718 said you're waiting for Verizon in this thread:
    http://www.webhostingtalk.com/showth...n&pagenumber=3

  32. #32
    Join Date
    Nov 2001
    Posts
    1,262
    Microsoft Windows XP [Version 5.1.2600]
    (C) Copyright 1985-2001 Microsoft Corp.

    C:\Documents and Settings\cowman>ping 66.227.25.201

    Pinging 66.227.25.201 with 32 bytes of data:

    Reply from 66.227.25.201: bytes=32 time=75ms TTL=238
    Reply from 66.227.25.201: bytes=32 time=125ms TTL=238
    Reply from 66.227.25.201: bytes=32 time=79ms TTL=238
    Reply from 66.227.25.201: bytes=32 time=78ms TTL=238

    Ping statistics for 66.227.25.201:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 75ms, Maximum = 125ms, Average = 89ms

    C:\Documents and Settings\cowman>tracert 66.227.25.201

    Tracing route to 66.227.25.201 over a maximum of 30 hops

    1 11 ms 44 ms 35 ms 10.1.0.1
    2 16 ms 23 ms 56 ms 65.70.113.149
    3 22 ms 22 ms 18 ms bb1-g1-0.okcyok.swbell.net [151.164.23.225]
    4 33 ms 31 ms 29 ms bb2-p2-1.ksc2mo.sbcglobal.net [151.164.240.33]
    5 31 ms 31 ms 31 ms bb1-p14-0.ksc2mo.sbcglobal.net [151.164.242.157]

    6 31 ms 34 ms 32 ms sl-gw16-kc-8-0.sprintlink.net [144.232.128.241]

    7 49 ms 38 ms 38 ms sl-bb21-kc-8-0.sprintlink.net [144.232.23.69]
    8 37 ms 34 ms 35 ms sl-bb21-fw-10-2.sprintlink.net [144.232.18.117]

    9 33 ms 33 ms 38 ms pos2-1.core1.Dallas1.Level3.net [209.245.240.165
    ]
    10 38 ms 42 ms 82 ms so-4-0-0.mp2.Dallas1.Level3.net [209.247.10.105]

    11 70 ms 82 ms 73 ms so-0-1-0.mp2.Philadelphia1.Level3.net [64.159.0.
    142]
    12 73 ms 72 ms 136 ms gig4-1.hsa1.Philadelphia1.level3.net [64.159.3.3
    0]
    13 75 ms 77 ms 71 ms unknown.Level3.net [63.209.178.162]
    14 72 ms 73 ms 70 ms 66.54.175.194
    15 72 ms 71 ms 72 ms o1-4bd1.phl053s101.yipes.com [66.54.144.109]
    16 72 ms 77 ms 75 ms o1-53s11.phl054si01.yipes.com [66.54.144.190]
    17 140 ms 72 ms 72 ms 66.7.139.82
    18 99 ms 98 ms 92 ms 66.227.25.201

    Trace complete.

    C:\Documents and Settings\cowman>

  33. #33
    Join Date
    Sep 2001
    Location
    Pennsylvania
    Posts
    248
    Dual entry and new providers are 2 different things, the BGP is already in place.

  34. #34
    Join Date
    Nov 2001
    Posts
    1,262
    Originally posted by webreseller
    Dual entry and new providers are 2 different things, the BGP is already in place.
    what providers will you be adding if any ?

    n/m looked at page 2

  35. #35
    Join Date
    Aug 2001
    Posts
    1,210
    .
    Last edited by TMX; 10-18-2002 at 03:22 AM.

  36. #36
    Join Date
    Nov 2001
    Posts
    852
    Its mighty slow again tonight

  37. #37
    Join Date
    Jun 2002
    Posts
    233
    Yeah -

    I'm actually getting above-300 now. I simply can't bank my business on this kind of reliability.. no matter who's fault it is.
    Webreseller, any time frame when this might be resolved? I know it was resolved completely before (pings were back down to normal, and normal is very good for webreseller usually) - what was the problem? How could the same thing spring up again. Once again I know its not your direct problem, but I'm just curious as to what is going on

    Thanks,
    Ben

  38. #38
    Join Date
    Nov 2001
    Posts
    852
    You know it is getting rough when connections to an ssh client are getting dropped.

  39. #39
    Join Date
    Sep 2001
    Location
    Pennsylvania
    Posts
    248
    Level3 stated that they have already increase bandwidth with ATT in NYC. This past week L3 has been having more capacity issues, I.E. last night they had a 3 hour period of heavy usage between ATT and L3. Level 3 has plans to add more capacity.

    An emergency ticket is open on both end and we are resolving this. Please send any network issues to [email protected] as our support team does not use WHT....

  40. #40
    Join Date
    Jun 2002
    Posts
    233
    K - thanks for the explination. However what I don't get is, if they are having bandwidth/capacity issues, then why for the past 2 weeks have pings and transfer been perfect, and now just the past 2 days pings been 3 times worse - if there wasn't any change wouldn't it be the same?

Page 1 of 2 12 LastLast

Posting Permissions

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