1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
  2. Greetings Guest!!

    In order to combat SPAM on the forums, all users are required to have a minimum of 2 posts before they can submit links in any post or thread.

    Dismiss Notice

Lag? Send your trace route!

Discussion in 'UO Resources' started by RL'S pker, Sep 1, 2009.

  1. RL'S pker

    RL'S pker Sage
    Stratics Veteran

    Joined:
    May 24, 2008
    Messages:
    715
    Likes Received:
    19
    Anyone else having extreme lag with UO?

    I've recently been in contact with EA customer support.

    They're asking for the following;


    You can also send them feed back using the uo.com site http://www.uoherald.com/feedback/index.php


    Please, everyone send trace routes in, so we can get this fixed!!!!
     
  2. Coffin

    Coffin Guest

    I have been lagging for 3 weeks.

    The thing is, I connect to Great Lakes from the west coast, and have been for 11+ years. Usually, I ping at about 95ms, which is playable. But now, during the day and some of the night I am up to about 150ms - 190ms. Can't pvp with that.

    Anyone else on the west coast or mountain area having lag to the east coast servers?
     
  3. RL'S pker

    RL'S pker Sage
    Stratics Veteran

    Joined:
    May 24, 2008
    Messages:
    715
    Likes Received:
    19
    I think it's anyone with Cable to any east coast shards.

    I live in FL, and I ping anywhere from 100-150+ to all east coast shards. It's horrible.:thumbdown:
     
  4. Coffin

    Coffin Guest

    This is what I'm getting, look familiar to anyone else? It improves at about midnight or so, eastern time. I wonder what's going on. This happened last year also, it took a few weeks to go away. Feeling really helpless. Ahhh well, it will go away eventually I suppose.

    [​IMG]
     
  5. Kellgory

    Kellgory Certifiable
    Stratics Veteran

    Joined:
    May 14, 2008
    Messages:
    1,639
    Likes Received:
    1
    I used the UO Traceroute utility because of lag problems to Sonoma and while I was pinging on average 60ms, I was suffering between 26%-50% packet loss at Central-aw4.owo.com. Pretty hard to do anything when you take a couple steps and lock-up for 10 seconds. It seems to come and go.
     
  6. NewYears1978

    NewYears1978 Guest


    This looks just like mine..Im okay until I hit all those Level3.net's and I get some bad pings in there..then when I hit EA servers it doubles or triples..
     
  7. MrBooDangIt

    MrBooDangIt Visitor
    Stratics Veteran

    Joined:
    Sep 19, 2009
    Messages:
    5
    Likes Received:
    0
    I cannot use the SA client I don't know why. Soon as I log into my character I loose the internet icon on my network connection system tray icon. I can use the 2d client fine with lots of lag.


    Host Name IP Address Hop Ping Time Ping Avg % Loss Pkts r/s Ping best/worst
    * Unknown Host * 192.168.0.1 1 0ms
    * Unknown Host * 192.168.29.1 2 1ms
    * Unknown Host * 10.0.0.1 3 10ms
    bluebird.gtwy.switchnap.com 209.66.45.64 4 36ms
    gig2-7.las-esw04.switchnap.com 209.66.45.221 5 13ms
    te1-1.las-core2-1.switchnap.com 209.66.45.113 6 13ms
    lv-ten1-4-cust.wvfiber.net 66.186.192.45 7 12ms
    sjc-ten1-3-lv-ten1-2.wvfiber.net 66.186.192.198 8 29ms
    Eth1-7.edge03.abn-sjc.ea.com 206.223.116.55 9 28ms
    edge01.eqx-sjc.ea.com 159.153.192.1 10 29ms
    * Unknown Host * 159.153.192.238 11 29ms
    central-aw5.owo.com 159.153.209.54 12 27ms

    This is my traceroute however when I poll the servers i get this


    Eth1-7.edge03.abn-sjc.ea.com 206.223.116.55 9 28ms 100% 0 / 17

    i get 100% packet loss on this server when I do the polling function however it does ping when i just do the initial traceroute.

    If anyone has any ideas on how to get this SA client running perhaps the route is not my problem
     
  8. mastodon

    mastodon Guest

    nah i aint just east coast, im getting it bad to


    Host Name IP Address Hop Ping Time Ping Avg % Loss Pkts r/s Ping best/worst
    wl.Belkin 1 1 0ms 0ms 0% 101 / 101 0ms / 4m
    ip70-173-6-1.lv.lv.cox.net 70.173.6.1 2 8ms 11ms 0% 101 / 101 6ms / 54ms
    24-234-8-185.ptp.lvcm.net 24.234.8.185 3 10ms 11ms 0% 101 / 101 7ms / 58ms
    24-234-6-53.ptp.lvcm.net 24.234.6.53 4 11ms 12ms 0% 101 / 101 7ms / 123ms
    ashbbbrj01-ae0.0.r2.as.cox.net 68.1.0.220 5 88ms 91ms 0% 101 / 101 87ms / 118ms
    * Unknown Host * 159.153.224.222 6 86ms 87ms 0% 101 / 101 85ms / 143ms
    fert07-eqx-iad.ea.com 159.153.224.230 7 86ms 87ms 1% 99 / 100 85ms / 148ms
    meav5-pub.pt.iad.ea.com 159.153.226.105 8 88ms 87ms 0% 100 / 100 86ms / 101ms
     
  9. uoBuoY

    uoBuoY Guest

    I'm in Vancouver, CA. I play on Baja an my ping is great (30-32). For the last week I also am "suffering between 26%-50% packet loss at Central-aw4.owo.com" as well as on edge01.eqx-sjc.ea.com. I've had lags as long as 20 seconds. Seriously impacts how you play!

    I submitted a support request with print screens. Received the canned message "Your question has been received. You should expect a response from us within 24 hours". That was last Tuesday and I'm still waiting for my "response from us within 24 hours".
     
  10. KTULU_ATL

    KTULU_ATL Guest

    East Coast Shards 3:30 PM - 10:30 PM bad ping every day for last month

    Host Name IP Address Hop Ping Time Ping Avg % Loss Pkts r/s Ping best/worst
    * Unknown Host * 2 0ms
    * Unknown Host * 3 8ms 14ms 0% 115 / 115 7ms / 446ms
    so-4-0-1.edge4.Dallas1.Level3.net 67.96.56.85 4 35ms 58ms 0% 115 / 115 21ms / 120ms
    ae-83-80.ebr3.Dallas1.Level3.net 4.69.145.180 5 40ms 62ms 0% 115 / 115 22ms / 119ms
    ae-7.ebr3.Atlanta2.Level3.net 4.69.134.22 6 66ms 81ms 0% 115 / 115 44ms / 141ms
    ae-2.ebr1.Washington1.Level3.net 4.69.132.86 7 70ms 94ms 0% 115 / 115 56ms / 145ms
    ae-91-91.csw4.Washington1.Level3.net 4.69.134.142 8 75ms 95ms 0% 115 / 115 56ms / 153ms
    ae-43-99.car3.Washington1.Level3.net 4.68.17.197 9 55ms 100% 0 / 115
    ELECTRONIC.car3.Washington1.Level3.net 4.79.169.74 10 103ms 92ms 0% 115 / 115 55ms / 151ms
    fert08-eqx-iad.ea.com 159.153.224.238 11 391ms 193ms 0% 115 / 115 138ms / 408ms
    * Unknown Host * 159.153.233.23 12 195ms 181ms 0% 115 / 115 128ms / 238ms
     
  11. Malador

    Malador Guest

    I am really curious when something is going to be done about this. I mean for some it has been going on for a couple of months

    [​IMG]
     
  12. Coffin

    Coffin Guest

    I'm still getting this lag between about 12pm EST and 9-10pm EST. God, I miss pvping :[

    C:\Documents and Settings\>tracert greatlakes.owo.com

    Tracing route to central-ae6.owo.com [159.153.233.71]
    over a maximum of 30 hops:

    1 13 ms 8 ms 15 ms 73.98.104.1
    2 18 ms 8 ms 9 ms 68.87.207.145
    3 14 ms 13 ms 14 ms te-5-3-ur02.ferndale.wa.seattle.comcast.net [68.
    86.96.110]
    4 16 ms 15 ms 11 ms te-0-9-0-7-ar01.seattle.wa.seattle.comcast.net [
    68.86.96.105]
    5 18 ms 17 ms 13 ms pos-0-5-0-0-cr01.seattle.wa.ibone.comcast.net [6
    8.86.90.213]
    6 14 ms 15 ms 11 ms te-3-2.car1.Seattle1.Level3.net [4.79.104.105]
    7 21 ms 18 ms 18 ms ae-31-51.ebr1.Seattle1.Level3.net [4.68.105.30]

    8 16 ms 15 ms 18 ms ae-1-100.ebr2.Seattle1.Level3.net [4.69.132.18]

    9 44 ms 42 ms 66 ms ae-2.ebr2.Denver1.Level3.net [4.69.132.54]
    10 80 ms 72 ms 66 ms ae-3.ebr1.Chicago2.Level3.net [4.69.132.62]
    11 66 ms 69 ms 63 ms ae-1-100.ebr2.Chicago2.Level3.net [4.69.132.114]

    12 105 ms 95 ms 99 ms ae-2-2.ebr2.Washington1.Level3.net [4.69.132.70]

    13 94 ms 103 ms 94 ms ae-62-62.csw1.Washington1.Level3.net [4.69.134.1
    46]
    14 97 ms 98 ms 95 ms ae-13-69.car3.Washington1.Level3.net [4.68.17.5]

    15 94 ms 96 ms 104 ms ELECTRONIC.car3.Washington1.Level3.net [4.79.169
    .74]
    16 238 ms 221 ms 361 ms fert08-eqx-iad.ea.com [159.153.224.238]
    17 183 ms 178 ms 175 ms 159.153.233.71
     
  13. chad

    chad Sage
    Stratics Veteran

    Joined:
    Jun 11, 2008
    Messages:
    586
    Likes Received:
    40
    It looks as though we are all pinging poorly when we reach
    fert07-eqx-iad.ea.com or fert08-eqx-iad.ea.com



    [​IMG]

    [​IMG]
     
  14. Speaking the Truth

    Speaking the Truth Lore Keeper
    Stratics Veteran

    Joined:
    Mar 9, 2009
    Messages:
    791
    Likes Received:
    146
    I've been pinging the same as everyone that's posted. Normally about 45 to the east coast, right now from 4pm till 12am est I ping about 150 avg. It's only to the east coast shards.

    This goes for most of my guild as well.
     
  15. sdk

    sdk Guest

    fert08 is killing me as well.. has been for about ~3 weeks. i'm going to cancel my account until they fix this crap. going from 17-25ms pings to 100+ is unacceptable. I remember something similar happening a while back, but it seemed to resolve itself pretty quickly.


    Pinging central-ae6.owo.com [159.153.233.71] with 32 bytes of data:
    Reply from 159.153.233.71: bytes=32 time=111ms TTL=55
    Reply from 159.153.233.71: bytes=32 time=102ms TTL=55
    Reply from 159.153.233.71: bytes=32 time=95ms TTL=55
    Reply from 159.153.233.71: bytes=32 time=114ms TTL=55
    Reply from 159.153.233.71: bytes=32 time=100ms TTL=55
    Reply from 159.153.233.71: bytes=32 time=112ms TTL=55
    Reply from 159.153.233.71: bytes=32 time=99ms TTL=55
    Reply from 159.153.233.71: bytes=32 time=108ms TTL=55
    Reply from 159.153.233.71: bytes=32 time=105ms TTL=55
    Reply from 159.153.233.71: bytes=32 time=90ms TTL=55

    Ping statistics for 159.153.233.71:
    Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 90ms, Maximum = 114ms, Average = 103ms



    Tracing route to central-ae6.owo.com [159.153.233.71]
    over a maximum of 30 hops:

    1 2 ms <1 ms <1 ms 192.168.1.1
    2 * * * Request timed out.
    3 7 ms 12 ms 9 ms 68.85.77.181
    4 9 ms 8 ms 9 ms te-7-4-ur01.wayneave.pa.panjde.comcast.net [68.8
    6.211.177]
    5 14 ms 11 ms 13 ms pos-1-5-0-0-cr01.mclean.va.ibone.comcast.net [68
    .86.91.233]
    6 13 ms 15 ms 13 ms ge-4-0-142.ipcolo2.Washington1.Level3.net [63.21
    0.62.33]
    7 13 ms 17 ms 21 ms ae-43-99.car3.Washington1.Level3.net [4.68.17.19
    7]
    8 15 ms 12 ms 14 ms ELECTRONIC.car3.Washington1.Level3.net [4.79.169
    .74]
    9 100 ms 98 ms 102 ms fert08-eqx-iad.ea.com [159.153.224.238]
    10 101 ms 103 ms 104 ms 159.153.233.71

    Trace complete.
     
  16. Coffin

    Coffin Guest

    C:\Documents and Settings\>ping greatlakes.owo.com -t

    Pinging central-ae6.owo.com [159.153.233.71] with 32 bytes of data:

    Reply from 159.153.233.71: bytes=32 time=165ms TTL=50
    Reply from 159.153.233.71: bytes=32 time=168ms TTL=50
    Reply from 159.153.233.71: bytes=32 time=163ms TTL=50
    Reply from 159.153.233.71: bytes=32 time=162ms TTL=50
    Reply from 159.153.233.71: bytes=32 time=162ms TTL=50
    Reply from 159.153.233.71: bytes=32 time=163ms TTL=50
    Reply from 159.153.233.71: bytes=32 time=160ms TTL=50
    Reply from 159.153.233.71: bytes=32 time=171ms TTL=50
    Reply from 159.153.233.71: bytes=32 time=159ms TTL=50
    Reply from 159.153.233.71: bytes=32 time=152ms TTL=50
    Reply from 159.153.233.71: bytes=32 time=153ms TTL=50
    Reply from 159.153.233.71: bytes=32 time=152ms TTL=50
    Reply from 159.153.233.71: bytes=32 time=146ms TTL=50
    Reply from 159.153.233.71: bytes=32 time=147ms TTL=50

    Ping statistics for 159.153.233.71:
    Packets: Sent = 14, Received = 14, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 146ms, Maximum = 171ms, Average = 158ms
    Control-C
    ^C
    C:\Documents and Settings\>



    C:\Documents and Settings\>tracert greatlakes.owo.com

    Tracing route to central-ae6.owo.com [159.153.233.71]
    over a maximum of 30 hops:

    1 10 ms 7 ms 7 ms 73.98.104.1
    2 14 ms 7 ms 9 ms 68.87.207.145
    3 8 ms 10 ms 24 ms te-5-3-ur02.ferndale.wa.seattle.comcast.net [68.
    86.96.110]
    4 10 ms 13 ms 10 ms te-0-9-0-7-ar01.seattle.wa.seattle.comcast.net [
    68.86.96.105]
    5 24 ms 12 ms 12 ms pos-0-5-0-0-cr01.seattle.wa.ibone.comcast.net [6
    8.86.90.213]
    6 14 ms 39 ms 11 ms te-3-2.car1.Seattle1.Level3.net [4.79.104.105]
    7 41 ms 18 ms 35 ms ae-31-51.ebr1.Seattle1.Level3.net [4.68.105.30]

    8 12 ms 16 ms 17 ms ae-1-100.ebr2.Seattle1.Level3.net [4.69.132.18]

    9 52 ms 53 ms 56 ms ae-2.ebr2.Denver1.Level3.net [4.69.132.54]
    10 63 ms 90 ms 65 ms ae-3.ebr1.Chicago2.Level3.net [4.69.132.62]
    11 67 ms 65 ms 63 ms ae-1-100.ebr2.Chicago2.Level3.net [4.69.132.114]

    12 107 ms 107 ms 107 ms ae-2-2.ebr2.Washington1.Level3.net [4.69.132.70]

    13 103 ms 109 ms 108 ms ae-62-62.csw1.Washington1.Level3.net [4.69.134.1
    46]
    14 94 ms 96 ms 99 ms ae-13-69.car3.Washington1.Level3.net [4.68.17.5]

    15 99 ms 95 ms 97 ms ELECTRONIC.car3.Washington1.Level3.net [4.79.169
    .74]
    16 151 ms 155 ms 174 ms fert08-eqx-iad.ea.com [159.153.224.238]
    17 170 ms 168 ms 170 ms 159.153.233.71
     
  17. Mr X

    Mr X Guest

    I have been having the same problems for months. Some days are good some days are bad. But I do know this, they do not give a ****.
     
  18. Weakling

    Weakling Guest

    Im the same as all you guys.
    I am in California (West Coast).
    I usually ping 70-100 but now 180-220
    [​IMG]
     
  19. Shamus Turlough

    Shamus Turlough Lore Master
    Stratics Veteran Alumni

    Joined:
    May 19, 2008
    Messages:
    1,066
    Likes Received:
    207
    This is at 6:41am my time, will trace again at 6:41pm my time (Central) and see if there is any difference.

    C:\Users\*****>tracert siege.owo.com
    Tracing route to central-ae4.owo.com [159.153.233.47]
    over a maximum of 30 hops:
    1 <1 ms <1 ms <1 ms 192.168.0.1
    2 * * * Request timed out.
    3 30 ms 41 ms 16 ms 8.9.**.**
    4 14 ms 6 ms 6 ms 8.9.**.**
    5 95 ms 20 ms 15 ms so-10-1.hsa1.Dallas1.Level3.net [209.246.148.205]
    6 15 ms 15 ms 14 ms ae-63-60.ebr3.Dallas1.Level3.net [4.69.145.52]
    7 136 ms 44 ms 112 ms ae-7.ebr3.Atlanta2.Level3.net [4.69.134.22]
    8 58 ms * 137 ms ae-2.ebr1.Washington1.Level3.net [4.69.132.86]
    9 63 ms 51 ms 54 ms ae-91-91.csw4.Washington1.Level3.net [4.69.134.142]
    10 51 ms 48 ms 43 ms ae-43-99.car3.Washington1.Level3.net [4.68.17.197]
    11 50 ms 45 ms 52 ms ELECTRONIC.car3.Washington1.Level3.net[4.79.169.74]
    12 61 ms 51 ms 89 ms fert07-eqx-iad.ea.com [159.153.224.230]
    13 56 ms 46 ms 92 ms 159.153.233.47
    Trace complete.
     
  20. Wulf2k

    Wulf2k Stratics Legend
    Stratics Veteran Stratics Legend Crusader of Chaos

    Joined:
    Feb 27, 2004
    Messages:
    7,565
    Likes Received:
    314
    Wow Shammy, your crappy is better than most people's good. You should play Siege =]

    I like how the very first response from the very first Level3 server is already spiking.
     
  21. Basara

    Basara UO Forum Moderator
    Moderator Professional Wiki Moderator Stratics Veteran Stratics Legend Campaign Supporter

    Joined:
    Jul 16, 2003
    Messages:
    8,461
    Likes Received:
    583
    For those of you using UOTrace, please do the following...

    When you do a trace to do a screencap for posting here, do it as a POLL (next button over to the right), and let it run through 100 or more cycles.

    Remember that simple ping time doesn't always show where the problem is occurring. If the problem is packet loss (and some of other issues) occurring a small percentage of the time, you will probably hit the problem router during a simple ping trace when it is behaving, but since there are multiple machines being pinged after the troublesome one, and the pings have to go through it, you're more likely to see the problem hit in the later machines.

    While, if you do a poll, for a significant number of iterations, you'll hit the problem one several times in its bad state, PLUS that bad state will also affect all the pings after it equally.

    Say you had a 12 hop trace. The problem is at hop 8.

    A typical tracert might look like (for hops 7-12)

    40 ms
    45 ms
    70 ms
    115 ms
    300 ms
    100 ms

    Which makes it look like the trouble is in hops 10-12, when those are actually being caused by the pings for those hops going through #8.


    Now, a poll, 100 times, will be more likely to show the issue

    Hop / Average ping / packet loss / minimum / maximum
    7 / 42 / 0% / 36 /47
    8 / 156 / 8% / 41 / 869
    9 / 170 / 7% / 64 / 760
    10 / 173 / 9% / 70 / 883
    11 / 172 / 7% / 82 / 773
    12 / 176 / 10% / 90 / 688

    That's not saying there can't be issues on other machines after the first, but until you clear the first issue in the chain, any others will be masked by it (and if you're doing just a tracert without polling, you're more likely to see the wrong machine pinging bad because of the bad one in the route to it).
     
  22. sdk

    sdk Guest

    Host Name IP Address Hop Ping Time Ping Avg % Loss Pkts r/s Ping best/worst
    * Unknown Host * 0.0.0.0 2 0ms
    * Unknown Host * 68.85.77.181 3 8ms 9ms 0% 149 / 149 7ms / 66ms
    te-7-4-ur01.wayneave.pa.panjde.comcast.net 68.86.211.177 4 9ms 9ms 0% 149 / 149 8ms / 25ms
    pos-1-5-0-0-cr01.mclean.va.ibone.comcast.net 68.86.91.233 5 14ms 13ms 0% 149 / 149 11ms / 42ms
    ge-4-0-142.ipcolo2.Washington1.Level3.net 63.210.62.33 6 12ms 15ms 0% 149 / 149 11ms / 50ms
    ae-43-99.car3.Washington1.Level3.net 4.68.17.197 7 13ms 26ms 0% 149 / 149 12ms / 190ms
    ELECTRONIC.car3.Washington1.Level3.net 4.79.169.74 8 12ms 13ms 0% 149 / 149 11ms / 32ms
    fert08-eqx-iad.ea.com 159.153.224.238 9 103ms 113ms 0% 149 / 149 79ms / 239ms
    * Unknown Host * 159.153.233.71 10 101ms 104ms 0% 149 / 149 84ms / 123ms
     
  23. Coffin

    Coffin Guest

    Damn you, fert08-eqx-iad.ea.com.......
    .......................................damn youuuuuuuuuuu!!!!!!!!!

    [​IMG]
    [​IMG]
     
  24. Mr X

    Mr X Guest

    It is level3.net washington. Everyone who is having a problem has them on their trace route. They have crappy service and they will not fix it unless somebody big like EA or YOUR isp gets on their ass. Otherwise we are all SOL.
     
  25. Malador

    Malador Guest

    nothings changed

    10 PM EST

    [​IMG]
     
  26. Malador

    Malador Guest

    still no change

    [​IMG]
     
  27. KidJoe

    KidJoe Guest

    wcsdca1-gsr1-ge14-0-0.san.rr.com 24.25.193.41 2 158ms 140ms 0% 313 / 313 93ms / 201ms
    gig5-0-0.wcsdca1-gsr3.san.rr.com 24.25.192.14 3 154ms 140ms 0% 313 / 313 92ms / 201ms
    so-0-1-0.gar1.SanDiego1.Level3.net 4.79.36.13 4 158ms 142ms 0% 313 / 313 93ms / 203ms
    ae-14-14.car1.SanDiego1.Level3.net 4.69.142.74 5 151ms 152ms 0% 311 / 313 96ms / 332ms
    ae-5-5.ebr1.LosAngeles1.Level3.net 4.69.133.206 6 161ms 148ms 0% 313 / 313 102ms / 212ms
    ae-1-60.edge1.LosAngeles1.Level3.net 4.69.144.7 7 164ms 144ms 0% 313 / 313 93ms / 205ms
    level3-gw.la2ca.ip.att.net 192.205.33.229 8 165ms 143ms 0% 313 / 313 94ms / 197ms
    cr1.la2ca.ip.att.net 12.122.128.14 9 117ms 100% 0 / 313
    cr1.sffca.ip.att.net 12.122.3.121 10 119ms 100% 0 / 312
    * Unknown Host * 12.122.137.65 11 122ms 100% 0 / 312
    * Unknown Host * 12.119.139.10 12 184ms 154ms 0% 312 / 312 102ms / 211ms
    * Unknown Host * 159.153.192.230 13 172ms 161ms 0% 312 / 312 109ms / 331ms
    central-aw2.owo.com 159.153.209.18 14 170ms 154ms 0% 312 / 312 112ms / 205ms

    Anyone understand any of this anyway...
    Has lag been fixed for anyone?

    Wonder when I will hear back from EA

    Sorry to everyone else with painful issues
     
  28. SUPRsalad

    SUPRsalad Guest

    Yeah, i was pinging from Colorado to pac with about 30-35.
    As of the last couple days, I'm around 150 and much worse. Here's my screen..
    Looks like my uo days are over for now. If it doesn't get better in a month, I'm shutting down permanently. (I pvp, therefore, I would rather not play than play crappily)

    Heres the screen: Doesn't look good on several levels..
    Can anyone tell me what we're looking at here??
    [​IMG]
     
  29. SUPRsalad

    SUPRsalad Guest

    SO I check again in the AM, and the ping time is way better, at around 30-35 again, but still getting around 25% packet loss to the same server.. I am currently on hold with with my ISP corporate headquarters in NY to see if I can have the problem rectified. . . Something tells me 'no', is going to be the result here.. Something tells me I'll be switching to DSL today..
     
  30. SUPRsalad

    SUPRsalad Guest

    aaaand, its almost 10 now, and I am back to where it was last night again..
    Thing is, I have to work all day when the ping is good, so this is my only time i can sit down and play... :(
    The phone call to corporate headquarters went well, I suppose. . She put me in contact with the 'general technician' who SEEMED very interested in my problem, and agreed that it was a problem, and that something SHOULD be done.. He said he would have a look into it, and if it is something they can resolve, they will. . .
    Somehow, im betting its not something they can resolve.. Im guessing a call to the attourney general is my only real bet.. Frankly, I'd rather bet on a horse with a broken leg..
    I am sad..