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

East Coast Lag

Discussion in 'UO Resources' started by KTULU_ATL, Sep 24, 2009.

  1. KTULU_ATL

    KTULU_ATL Guest

    I am one of the players experiencing bad latency to ATL, GL, LS, and all other east coast shards. I am still connecting well to the west shards. I have read the previous post which started in August.

    My situation:
    I ping bad during peak hours from 3:30 PM CST - 10:30 CST. Between these hours, I ping 100 - 220, usually around 150ms. All other times i ping 40's, 50's and 60's. The problem starts around 3:30 PM and progressively gets worse.

    I am performing an hour by hour trace route and will post. Someone please help. This is making it impossible to play the game.
     
  2. KTULU_ATL

    KTULU_ATL Guest

    This is the start of the lag I will post more times and traceroutes. Also, why is ae-43-99.car3.Washington1.Level3.net losing 100% of packets in my traceroutes?

    PING SUMMARY - atlantic.owo.com
    Date Time Host Name IP Address Hop Ping Time Ping Avg % Loss Pkts r/s Ping best/worst
    9/24/2009 3:30 PM * Unknown Host * 159.153.233.23 69ms 62ms 0% 103 / 103 55ms / 78ms

    Date Time Host Name IP Address Hop Ping Time Ping Avg % Loss Pkts r/s Ping best/worst
    9/24/2009 3:30 PM * Unknown Host * 2 0ms
    9/24/2009 3:30 PM * Unknown Host * 3 13ms
    9/24/2009 3:30 PM so-4-0-1.edge4.Dallas1.Level3.net 67.96.56.85 4 21ms
    9/24/2009 3:30 PM ae-83-80.ebr3.Dallas1.Level3.net 4.69.145.180 5 33ms
    9/24/2009 3:30 PM ae-7.ebr3.Atlanta2.Level3.net 4.69.134.22 6 56ms
    9/24/2009 3:30 PM ae-2.ebr1.Washington1.Level3.net 4.69.132.86 7 61ms
    9/24/2009 3:30 PM ae-91-91.csw4.Washington1.Level3.net 4.69.134.142 8 55ms
    9/24/2009 3:30 PM ae-43-99.car3.Washington1.Level3.net 4.68.17.197 9 56ms
    9/24/2009 3:30 PM ELECTRONIC.car3.Washington1.Level3.net 4.79.169.74 10 57ms
    9/24/2009 3:30 PM fert08-eqx-iad.ea.com 159.153.224.238 11 70ms
    9/24/2009 3:30 PM * Unknown Host * 159.153.233.23 12 70ms

    Date Time Host Name IP Address Hop Ping Time Ping Avg % Loss Pkt s r/s Ping best/worst
    9/24/2009 3:30 PM * Unknown Host * 2 0ms
    9/24/2009 3:30 PM * Unknown Host * 3 8ms 10ms 0% 101 / 101 7ms / 34ms
    9/24/2009 3:30 PM so-4-0-1.edge4.Dallas1.Level3.net 67.96.56.85 4 21ms 23ms 0% 101 / 101 20ms / 44ms
    9/24/2009 3:30 PM ae-83-80.ebr3.Dallas1.Level3.net 4.69.145.180 5 23ms 28ms 0% 101 / 101 21ms / 42ms
    9/24/2009 3:30 PM ae-7.ebr3.Atlanta2.Level3.net 4.69.134.22 6 44ms 49ms 0% 101 / 101 42ms / 66ms
    9/24/2009 3:30 PM ae-2.ebr1.Washington1.Level3.net 4.69.132.86 7 61ms 64ms 0% 101 / 101 54ms / 89ms
    9/24/2009 3:30 PM ae-91-91.csw4.Washington1.Level3.net 4.69.134.142 8 59ms 62ms 0% 100 / 100 55ms / 77ms
    9/24/2009 3:30 PM ae-43-99.car3.Washington1.Level3.net 4.68.17.197 9 56ms 100% 0 / 100
    9/24/2009 3:30 PM ELECTRONIC.car3.Washington1.Level3.net 4.79.169.74 10 59ms 58ms 0% 100 / 100 54ms / 72ms
    9/24/2009 3:30 PM fert08-eqx-iad.ea.com 159.153.224.238 11 75ms 95ms 0% 100 / 100 63ms / 263ms
    9/24/2009 3:30 PM * Unknown Host * 159.153.233.23 12 74ms 81ms 0% 100 / 100 61ms / 122ms

    Date Time Host Name IP Address Hop Ping Time Ping Avg % Loss Pkts r/s Ping best/worst
    9/24/2009 4:00 PM * Unknown Host * 159.153.233.23 94ms 93ms 0% 100 / 100 81ms / 111ms

    Date Time Host Name IP Address Hop Ping Time Ping Avg % Loss Pkts r/s Ping best/worst
    9/24/2009 4:00 PM * Unknown Host * 2 0ms
    9/24/2009 4:00 PM * Unknown Host * 3 8ms
    9/24/2009 4:00 PM so-4-0-1.edge4.Dallas1.Level3.net 67.96.56.85 4 20ms
    9/24/2009 4:00 PM ae-83-80.ebr3.Dallas1.Level3.net 4.69.145.180 5 30ms
    9/24/2009 4:00 PM ae-7.ebr3.Atlanta2.Level3.net 4.69.134.22 6 44ms
    9/24/2009 4:00 PM ae-2.ebr1.Washington1.Level3.net 4.69.132.86 7 69ms
    9/24/2009 4:00 PM ae-91-91.csw4.Washington1.Level3.net 4.69.134.142 8 59ms
    9/24/2009 4:00 PM ae-43-99.car3.Washington1.Level3.net 4.68.17.197 9 58ms
    9/24/2009 4:00 PM ELECTRONIC.car3.Washington1.Level3.net 4.79.169.74 10 70ms
    9/24/2009 4:00 PM fert08-eqx-iad.ea.com 159.153.224.238 11 114ms
    9/24/2009 4:00 PM * Unknown Host * 159.153.233.23 12 86ms

    Date Time Host Name IP Address Hop Ping Time Ping Avg % Loss Pkts r/s Ping best/worst
    9/24/2009 4:00 PM * Unknown Host * 2 0ms
    9/24/2009 4:00 PM * Unknown Host * 3 9ms 14ms 0% 101 / 101 7ms / 139ms
    9/24/2009 4:00 PM so-4-0-1.edge4.Dallas1.Level3.net 67.96.56.85 4 23ms 24ms 0% 101 / 101 20ms / 46ms
    9/24/2009 4:00 PM ae-93-90.ebr3.Dallas1.Level3.net 4.69.145.244 5 29ms 28ms 0% 101 / 101 21ms / 52ms
    9/24/2009 4:00 PM ae-7.ebr3.Atlanta2.Level3.net 4.69.134.22 6 55ms 48ms 0% 101 / 101 40ms / 77ms
    9/24/2009 4:00 PM ae-2.ebr1.Washington1.Level3.net 4.69.132.86 7 56ms 63ms 0% 101 / 101 54ms / 82ms
    9/24/2009 4:00 PM ae-91-91.csw4.Washington1.Level3.net 4.69.134.142 8 62ms 64ms 0% 101 / 101 55ms / 91ms
    9/24/2009 4:00 PM ae-43-99.car3.Washington1.Level3.net 4.68.17.197 9 54ms 100% 0 / 99
    9/24/2009 4:00 PM ELECTRONIC.car3.Washington1.Level3.net 4.79.169.74 10 58ms 58ms 0% 99 / 99 55ms / 71ms
    9/24/2009 4:00 PM fert08-eqx-iad.ea.com 159.153.224.238 11 78ms 106ms 0% 99 / 99 78ms / 314ms
    9/24/2009 4:00 PM * Unknown Host * 159.153.233.23 12 86ms 100ms 0% 99 / 99 78ms / 147ms

    Date Time Host IP Address Hop Ping Time Ping Avg % Loss Pkts r/s Ping best/worst
    9/24/2009 4:30 PM * Host * 159.153.233.23 89ms 91ms 0% 116 / 116 80ms / 104ms

    Date Time Host Name IP Address Hop Ping Time Ping Avg % Loss Pkts r/s Ping best/worst
    9/24/2009 4:30 PM * Unknown Host * 2 0ms
    9/24/2009 4:30 PM * Unknown Host * 3 11ms
    9/24/2009 4:30 PM so-4-0-1.edge4.Dallas1.Level3.net 67.96.56.85 4 24ms
    9/24/2009 4:30 PM ae-73-70.ebr3.Dallas1.Level3.net 4.69.145.116 5 22ms
    9/24/2009 4:30 PM ae-7.ebr3.Atlanta2.Level3.net 4.69.134.22 6 46ms
    9/24/2009 4:30 PM ae-2.ebr1.Washington1.Level3.net 4.69.132.86 7 55ms
    9/24/2009 4:30 PM ae-91-91.csw4.Washington1.Level3.net 4.69.134.142 8 62ms
    9/24/2009 4:30 PM ae-43-99.car3.Washington1.Level3.net 4.68.17.197 9 56ms
    9/24/2009 4:30 PM ELECTRONIC.car3.Washington1.Level3.net 4.79.169.74 10 58ms
    9/24/2009 4:30 PM fert08-eqx-iad.ea.com 159.153.224.238 11 172ms
    9/24/2009 4:30 PM * Unknown Host * 159.153.233.23 12 91ms

    Date Time Host Name IP Address Hop Ping Time Ping Avg % Loss Pkt s r/s Ping best/worst
    9/24/2009 4:30 PM * Unknown Host * 2 0ms
    9/24/2009 4:30 PM * Unknown Host * 3 8ms 13ms 0% 101 / 101 7ms / 310ms
    9/24/2009 4:30 PM so-4-0-1.edge4.Dallas1.Level3.net 67.96.56.85 4 23ms 24ms 0% 101 / 101 20ms / 50ms
    9/24/2009 4:30 PM ae-63-60.ebr3.Dallas1.Level3.net 4.69.145.52 5 26ms 29ms 0% 101 / 101 21ms / 51ms
    9/24/2009 4:30 PM ae-7.ebr3.Atlanta2.Level3.net 4.69.134.22 6 44ms 47ms 0% 101 / 101 41ms / 73ms
    9/24/2009 4:30 PM ae-2.ebr1.Washington1.Level3.net 4.69.132.86 7 57ms 63ms 0% 101 / 101 53ms / 84ms
    9/24/2009 4:30 PM ae-91-91.csw4.Washington1.Level3.net 4.69.134.142 8 62ms 63ms 0% 101 / 101 55ms / 87ms
    9/24/2009 4:30 PM ae-43-99.car3.Washington1.Level3.net 4.68.17.197 9 56ms 100% 0 / 100
    9/24/2009 4:30 PM ELECTRONIC.car3.Washington1.Level3.net 4.79.169.74 10 58ms 58ms 0% 100 / 100 55ms / 71ms
    9/24/2009 4:30 PM fert08-eqx-iad.ea.com 159.153.224.238 11 103ms 117ms 0% 100 / 100 82ms / 314ms
    9/24/2009 4:30 PM * Unknown Host * 159.153.233.23 12 105ms 105ms 0% 100 / 100 80ms / 153ms
     
  3. KTULU_ATL

    KTULU_ATL Guest

    5:00 PM and 7:00 PM CST - Now it is getting very bad. 150+ ms.

    Date Time Host Address Hop Ping Time Ping Avg % Loss Pkts r/s Ping best/worst
    9/24/2009 5:00 PM * * 159.153.233.23 103ms 110ms 0% 102 / 102 99ms / 134ms

    Date Time Host Name IP Address Hop Ping Time Ping Avg % Loss Pkts r/s Ping best/worst
    9/24/2009 5:00 PM * Unknown Host * 2 0ms
    9/24/2009 5:00 PM * Unknown Host * 3 7ms
    9/24/2009 5:00 PM so-4-0-1.edge4.Dallas1.Level3.net 67.96.56.85 4 28ms
    9/24/2009 5:00 PM ae-63-60.ebr3.Dallas1.Level3.net 4.69.145.52 5 32ms
    9/24/2009 5:00 PM ae-7.ebr3.Atlanta2.Level3.net 4.69.134.22 6 46ms
    9/24/2009 5:00 PM ae-2.ebr1.Washington1.Level3.net 4.69.132.86 7 63ms
    9/24/2009 5:00 PM ae-91-91.csw4.Washington1.Level3.net 4.69.134.142 8 61ms
    9/24/2009 5:00 PM ae-43-99.car3.Washington1.Level3.net 4.68.17.197 9 55ms
    9/24/2009 5:00 PM ELECTRONIC.car3.Washington1.Level3.net 4.79.169.74 10 67ms
    9/24/2009 5:00 PM fert08-eqx-iad.ea.com 159.153.224.238 11 104ms
    9/24/2009 5:00 PM * Unknown Host * 159.153.233.23 12 113ms

    Date Time Host Name IP Address Hop Ping Time Ping Avg % Loss Pkt s r/s Ping best/worst
    9/24/2009 5:00 PM * Unknown Host * 2 0ms
    9/24/2009 5:00 PM * Unknown Host * 3 7ms 11ms 0% 101 / 101 7ms / 96ms
    9/24/2009 5:00 PM so-4-0-1.edge4.Dallas1.Level3.net 67.96.56.85 4 22ms 24ms 0% 101 / 101 20ms / 44ms
    9/24/2009 5:00 PM ae-63-60.ebr3.Dallas1.Level3.net 4.69.145.52 5 32ms 30ms 0% 101 / 101 21ms / 56ms
    9/24/2009 5:00 PM ae-7.ebr3.Atlanta2.Level3.net 4.69.134.22 6 43ms 51ms 0% 101 / 101 41ms / 85ms
    9/24/2009 5:00 PM ae-2.ebr1.Washington1.Level3.net 4.69.132.86 7 66ms 63ms 0% 101 / 101 54ms / 94ms
    9/24/2009 5:00 PM ae-91-91.csw4.Washington1.Level3.net 4.69.134.142 8 59ms 63ms 0% 101 / 101 55ms / 86ms
    9/24/2009 5:00 PM ae-43-99.car3.Washington1.Level3.net 4.68.17.197 9 55ms 100% 0 / 100
    9/24/2009 5:00 PM ELECTRONIC.car3.Washington1.Level3.net 4.79.169.74 10 61ms 60ms 0% 100 / 100 55ms / 83ms
    9/24/2009 5:00 PM fert08-eqx-iad.ea.com 159.153.224.238 11 300ms 121ms 0% 100 / 100 75ms / 300ms
    9/24/2009 5:00 PM * Unknown Host * 159.153.233.23 12 105ms 112ms 0% 100 / 100 80ms / 144ms


    Date Time Host Name IP Address Hop Ping Time Ping Avg % Loss Pkts r/s Ping best/worst
    9/24/2009 7:00 PM * Unknown Host * 159.153.233.23 159ms 161ms 0% 221 / 221 128ms / 228ms

    Date Time Host Name IP Address Hop Ping Time Ping Avg % Loss Pkts r/s Ping best/worst
    9/24/2009 7:00 PM * Unknown Host * 2 0ms
    9/24/2009 7:00 PM * Unknown Host * 3 8ms
    9/24/2009 7:00 PM so-4-0-1.edge4.Dallas1.Level3.net 67.96.56.85 4 65ms
    9/24/2009 7:00 PM ae-73-70.ebr3.Dallas1.Level3.net 4.69.145.116 5 53ms
    9/24/2009 7:00 PM ae-7.ebr3.Atlanta2.Level3.net 4.69.134.22 6 75ms
    9/24/2009 7:00 PM ae-2.ebr1.Washington1.Level3.net 4.69.132.86 7 90ms
    9/24/2009 7:00 PM ae-91-91.csw4.Washington1.Level3.net 4.69.134.142 8 104ms
    9/24/2009 7:00 PM ae-43-99.car3.Washington1.Level3.net 4.68.17.197 9 59ms
    9/24/2009 7:00 PM ELECTRONIC.car3.Washington1.Level3.net 4.79.169.74 10 62ms
    9/24/2009 7:00 PM fert08-eqx-iad.ea.com 159.153.224.238 11 151ms
    9/24/2009 7:00 PM * Unknown Host * 159.153.233.23 12 212ms

    Date Time Host Name IP Address Hop Ping Time Ping Avg % Loss Pkts r/s Ping best/worst
    9/24/2009 7:00 PM * Unknown Host * 2 0ms
    9/24/2009 7:00 PM * Unknown Host * 3 9ms 9ms 0% 100 / 100 6ms / 16ms
    9/24/2009 7:00 PM so-4-0-1.edge4.Dallas1.Level3.net 67.96.56.85 4 77ms 47ms 0% 100 / 100 20ms / 101ms
    9/24/2009 7:00 PM ae-73-70.ebr3.Dallas1.Level3.net 4.69.145.116 5 72ms 53ms 0% 100 / 100 21ms / 119ms
    9/24/2009 7:00 PM ae-7.ebr3.Atlanta2.Level3.net 4.69.134.22 6 88ms 72ms 0% 100 / 100 42ms / 129ms
    9/24/2009 7:00 PM ae-2.ebr1.Washington1.Level3.net 4.69.132.86 7 100ms 86ms 0% 100 / 100 57ms / 145ms
    9/24/2009 7:00 PM ae-91-91.csw4.Washington1.Level3.net 4.69.134.142 8 114ms 86ms 0% 100 / 100 56ms / 142ms
    9/24/2009 7:00 PM ae-43-99.car3.Washington1.Level3.net 4.68.17.197 9 59ms 100% 0 / 100
    9/24/2009 7:00 PM ELECTRONIC.car3.Washington1.Level3.net 4.79.169.74 10 120ms 86ms 0% 100 / 100 56ms / 154ms
    9/24/2009 7:00 PM fert08-eqx-iad.ea.com 159.153.224.238 11 197ms 181ms 0% 100 / 100 133ms / 359ms
    9/24/2009 7:00 PM * Unknown Host * 159.153.233.23 12 213ms 169ms 2% 97 / 99 132ms / 231ms
     
  4. KTULU_ATL

    KTULU_ATL Guest

    9:00 PM Lag - Really bad. 175 - 225 ms. Almost unplayable. Definitely no pvp going on here on prime time which is a shame because I used to pvp during these times every day. Will someone please help me diagnose the problem?

    Date Time Host Name IP Address Hop Ping Time Ping Avg % Loss Pkts r/s Ping best/worst
    9/24/2009 9:00 PM * Unknown Host * 159.153.233.23 191ms 172ms 0% 100 / 100 98ms / 219ms

    Date Time Host Name IP Address Hop Ping Time Ping Avg % Loss Pkts r/s Ping best/worst
    9/24/2009 9:00 PM * Unknown Host * 2 0ms
    9/24/2009 9:00 PM * Unknown Host * 3 9ms
    9/24/2009 9:00 PM so-4-0-1.edge4.Dallas1.Level3.net 67.96.56.85 4 83ms
    9/24/2009 9:00 PM ae-73-70.ebr3.Dallas1.Level3.net 4.69.145.116 5 105ms
    9/24/2009 9:00 PM ae-7.ebr3.Atlanta2.Level3.net 4.69.134.22 6 137ms
    9/24/2009 9:00 PM ae-2.ebr1.Washington1.Level3.net 4.69.132.86 7 135ms
    9/24/2009 9:00 PM ae-91-91.csw4.Washington1.Level3.net 4.69.134.142 8 126ms
    9/24/2009 9:00 PM ae-43-99.car3.Washington1.Level3.net 4.68.17.197 9 57ms
    9/24/2009 9:00 PM ELECTRONIC.car3.Washington1.Level3.net 4.79.169.74 10 58ms
    9/24/2009 9:00 PM fert08-eqx-iad.ea.com 159.153.224.238 11 142ms
    9/24/2009 9:00 PM * Unknown Host * 159.153.233.23 12 242ms

    Date Time Host Name IP Address Hop Ping Time Ping Avg % Loss Pkt s r/s Ping best/worst
    9/24/2009 9:00 PM * Unknown Host * 2 0ms
    9/24/2009 9:00 PM * Unknown Host * 3 13ms 13ms 0% 101 / 101 6ms / 252ms
    9/24/2009 9:00 PM so-4-0-1.edge4.Dallas1.Level3.net 67.96.56.85 4 105ms 92ms 0% 100 / 101 54ms / 110ms
    9/24/2009 9:00 PM ae-73-70.ebr3.Dallas1.Level3.net 4.69.145.116 5 110ms 98ms 0% 101 / 101 59ms / 125ms
    9/24/2009 9:00 PM ae-7.ebr3.Atlanta2.Level3.net 4.69.134.22 6 127ms 117ms 0% 101 / 101 67ms / 168ms
    9/24/2009 9:00 PM ae-2.ebr1.Washington1.Level3.net 4.69.132.86 7 133ms 129ms 0% 101 / 101 85ms / 158ms
    9/24/2009 9:00 PM ae-91-91.csw4.Washington1.Level3.net 4.69.134.142 8 131ms 131ms 0% 101 / 101 82ms / 161ms
    9/24/2009 9:00 PM ae-43-99.car3.Washington1.Level3.net 4.68.17.197 9 57ms 100% 0 / 101
    9/24/2009 9:00 PM ELECTRONIC.car3.Washington1.Level3.net 4.79.169.74 10 123ms 128ms 0% 101 / 101 79ms / 152ms
    9/24/2009 9:00 PM fert08-eqx-iad.ea.com 159.153.224.238 11 211ms 225ms 0% 101 / 101 166ms / 393ms
    9/24/2009 9:00 PM * Unknown Host * 159.153.233.23 12 229ms 216ms 0% 100 / 100 160ms / 251ms
     
  5. KTULU_ATL

    KTULU_ATL Guest

    10:15 PM CST Ping rates - Seems to be getting better. Like I said in the beginning post, it gets progressively worse. Is there anything my ISP can do? I would like to get this resolved ASARP. Can somone provide me with some advice with what I should do? What should be my next steps? Should I upgrade to the fastest cable connection available at my ISP? Should I dump my ISP for another? What will help? Please help me out.

    Date Time Host Name IP Address Hop Ping Time Ping Avg % Loss Pkts r/s Ping best/worst
    9/24/2009 10:15 PM * Unknown Host * 159.153.233.23 146ms 136ms 0% 108 / 108 104ms / 175ms

    Date Time Host Name IP Address Hop Ping Time Ping Avg % Loss Pkts r/s Ping best/worst
    9/24/2009 10:15 PM * Unknown Host * 0.0.0.0 2 0ms
    9/24/2009 10:15 PM * Unknown Host * 10.0.1.5 3 12ms
    9/24/2009 10:15 PM so-4-0-1.edge4.Dallas1.Level3.net 67.96.56.85 4 68ms
    9/24/2009 10:15 PM ae-93-90.ebr3.Dallas1.Level3.net 4.69.145.244 5 80ms
    9/24/2009 10:15 PM ae-7.ebr3.Atlanta2.Level3.net 4.69.134.22 6 83ms
    9/24/2009 10:15 PM ae-2.ebr1.Washington1.Level3.net 4.69.132.86 7 83ms
    9/24/2009 10:15 PM ae-91-91.csw4.Washington1.Level3.net 4.69.134.142 8 74ms
    9/24/2009 10:15 PM ae-43-99.car3.Washington1.Level3.net 4.68.17.197 9 55ms
    9/24/2009 10:15 PM ELECTRONIC.car3.Washington1.Level3.net 4.79.169.74 10 56ms
    9/24/2009 10:15 PM fert08-eqx-iad.ea.com 159.153.224.238 11 123ms
    9/24/2009 10:15 PM * Unknown Host * 159.153.233.23 12 114ms

    Date Time Host Name IP Address Hop Ping Time Ping Avg % Loss Pkt s r/s Ping best/worst
    9/24/2009 10:15 PM * Unknown Host * 0.0.0.0 2 0ms
    9/24/2009 10:15 PM * Unknown Host * 10.0.1.5 3 8ms 11ms 0% 101 / 101 7ms / 202ms
    9/24/2009 10:15 PM so-4-0-1.edge4.Dallas1.Level3.net 67.96.56.85 4 20ms 33ms 0% 101 / 101 20ms / 100ms
    9/24/2009 10:15 PM ae-93-90.ebr3.Dallas1.Level3.net 4.69.145.244 5 26ms 39ms 0% 101 / 101 22ms / 113ms
    9/24/2009 10:15 PM ae-7.ebr3.Atlanta2.Level3.net 4.69.134.22 6 48ms 59ms 0% 101 / 101 43ms / 122ms
    9/24/2009 10:15 PM ae-2.ebr1.Washington1.Level3.net 4.69.132.86 7 55ms 73ms 0% 101 / 101 55ms / 132ms
    9/24/2009 10:15 PM ae-91-91.csw4.Washington1.Level3.net 4.69.134.142 8 58ms 72ms 0% 101 / 101 55ms / 125ms
    9/24/2009 10:15 PM ae-43-99.car3.Washington1.Level3.net 4.68.17.197 9 57ms 100% 0 / 100
    9/24/2009 10:15 PM ELECTRONIC.car3.Washington1.Level3.net 4.79.169.74 10 56ms 70ms 0% 100 / 100 55ms / 126ms
    9/24/2009 10:15 PM fert08-eqx-iad.ea.com 159.153.224.238 11 85ms 104ms 0% 100 / 100 72ms / 213ms
    9/24/2009 10:15 PM * Unknown Host * 159.153.233.23 12 82ms 99ms 0% 100 / 100 74ms / 163ms
     
  6. Harlequin

    Harlequin Babbling Loonie
    Stratics Veteran

    Joined:
    Jun 11, 2008
    Messages:
    2,716
    Likes Received:
    32
    Ah, good, I was waiting for someone to post something like this besides just posting a couple of traces and then blindly insist someone (the officials) help.

    And you are a direct client of Level3 to boot! Perhaps you can get somewhere that others can't.

    First off, the 100% packet loss from ae-43-99.car3.Washington1.Level3.net is because it's configured to drop ICMP packets.



    I initially thought the lag was due to them updating the route tables during those laggy times and switching to a slower/faulty router. But the only hop that has changed in your tracerts is the 4th hop.

    Looks like normal load-balancing and doesn't seem to be a problem.

    The problem for you seems to start at fert08-eqx-iad.ea.com (but note that this could still be caused by the hop prior to it).

    Why I say that is because I'm hitting fert08-eqx-iad.ea.com via alter.net (verizon) and do not have similar issues. Any of your friends in the neighbourhood use Verizon or other isp besides Level 3?

    Ask them help for a favor and do a tracert during these times. Compare it to yours. Then post/send to EA and Level3.

    I think EA needs to work with Level 3 to isolate the issue. Once they have isolated whose eqm is causing the issue, then they can get it resolved. Right now, it a case of everyone denying it's their issue and nothing is getting done.
     
  7. KTULU_ATL

    KTULU_ATL Guest

    Any of your friends in the neighborhood use Verizon or other isp besides Level 3?

    -No. I do not know anyone locally whom uses Verizon. I got moved here for work and do not know many people here. (Atleast who I want to share I play UO with!)

    Besides from that, what should be my next steps? I would like to get EA involved. How should I do this? Should I send them my latency reports? Where should I send them?

    I have called my ISP and they said they would have a Tech get back to me. They never did. But I still have faith in that.


    :wall:
     
  8. Harlequin

    Harlequin Babbling Loonie
    Stratics Veteran

    Joined:
    Jun 11, 2008
    Messages:
    2,716
    Likes Received:
    32

    Don't have to be Verizon, any isp besides Level3 will do. Or you can pop over to an internet cafe, or use your company's internet connection (unless your company blocks direct internet traffic), or anywhere with free wireless internet if you have a laptop. Etc.


    To raise an case with EA, go to http://support.ea.com. Send them your hour by hour tracert results.

    Also see http://vboards.stratics.com/showthread.php?t=154840

    At the same time, call your ISP again and ask for an update of your case. 1st thing to do, ask for the name of the person that answered your call and write down his name.

    Call him/her by that name to make sure the person understands you know his/her name. Also, ask for your case number. Do not put down the phone until you have that.

    If they can't find your old case number and says they have no records you called, turn deadly calm and very politely (you know the kind of sudden politeless that unnerves people?) ask to speak to the manager.

    You - "Can I speak to your manager please?"
    Engineer - "blah blah"
    You - "Yes I understand it's not your fault. Can I speak to your manager please?"
    Engineer - "blah blah"
    You - "John, please undertand that this is the 3rd time I am asking to speak to your manager. Can I speak to your manager please?"
    Engineer - "blah blah"
    You - "John, please undertand that this is the 4th time I am asking to speak to your manager. Can I speak to your manager please?"

    Etc etc.



    When you get emails from both parties, reply to the latest one (remove any personal info first, like your UO Account name!) and copy both of them in the same email. Include the case numbers from both parties for their easy reference. But phrase it politely and let them talk to each other and sort it out.

    eg

    "My ISP/game provider says it's it problem on your end. But I'm not a techinical person. I have copied them in this email in hopes that with your combined expertise, you can help me resolve this issue. Thank you very much in advance."

    Sign it using "Your loyal customer, <your name>".
     
  9. KTULU_ATL

    KTULU_ATL Guest

    UPDATE:

    I sent feedback to EA through the website like you said to do. They have still yet to send a response.

    I spoke with my ISP and he told me there was some good news and bad news. He said the bad news was since it was outside of their servers, there was little they could do to help resolve the latency issue. The good news was that my piticular ISP runs Level3.net in half the city and Qwest in half the city. He told me to change my MAC ID adress and it would release a Qwest IP to me. I did this and am still experiencing the high latency between 3:30 PM and 10:30 PM CST. I still connect to the Level3.net servers on the way to the East Coast UO Servers, so this must be the problem.

    What should we do now?
     
  10. KTULU_ATL

    KTULU_ATL Guest

    LOL. Trash.

    How should I reply to this?

    --------------------------

    Hi Mike,

    Thank you for contacting Electronic Arts.

    If you experience lag during game play, clean up and delete any unnecessary files.

    Make sure that your disk drives have been defragmented. Windows has a default disk de fragmenting tool that you can use by following the steps below:

    Click the Start button on the Windows Taskbar.
    Select All Programs or Programs.
    Select Accessories.
    Select System Tools.
    Select Disk Defragmenter.

    This will run the Disk Defragmenter on your hard drive to make sure that all of your files are efficiently organized.

    Game settings can contribute to connection issues and lag.

    In-game details and options can impact packet size and speed. The more details you are using in your settings, the more information the game has to process. If you have any filters for text, these can also slow down the game. Try lowering options to speed up game play. Here is a small example list of things that could slow down online games.

    Translation filters for incoming text.
    Error logging
    Obscenity filters
    High end lighting effects
    High graphic details

    If you have any further questions or concerns please reply to this email or visit our extensive knowledge base online at http://support.ea.com.

    Thank you,

    Rafael
    EA Online Support.
     
  11. Coffin

    Coffin Guest

    I feel you on this problem KTULU. I almost wish more people were affected by the fert08-eqx-iad.ea.com lag so that something could be done. But what do I know? Maybe nothing can be done!
     
  12. Snakeman

    Snakeman UO Forum Moderator
    Moderator Professional Premium Wiki Moderator Stratics Veteran Stratics Legend

    Joined:
    Jun 13, 2002
    Messages:
    4,961
    Likes Received:
    165
    Good luck, I had bad lag in January from one of their servers for over, heck 3 mos, & nothing was done by them for me & a few others that experienced this. I sent in & posted many Trace Routes for over 3 weeks. It finally cleared itself up about late March to early April. I don't know if EA fixed it or it cleared itself up..

    [​IMG]

    [​IMG]
     
  13. Coffin

    Coffin Guest

    Serves some of us right though, like me. I connect to great lakes from Washington. Really, I should be on the west coast servers. But still, over the last 12 years I've connected to the east coast servers at around 95ms, which has always been playable. Can't mage duel very well with the under 40ms guys, but it's not bad. Pacific, Baja, and Sonoma seem kinda dull. I like being around a large player base, and more importantly, around friends.

    Aww well, I have a feeling this winter some hardware will get replaced or something ruther, and some of us can get back to playing as normal. But in the meantime, bawwwww! =P
     
  14. sdk

    sdk Guest

    I seem to have the same issue.. it just popped up in the last 2-3 weeks or so. I've been pinging 15-25ms to GL for years and now its constantly over 100. I know it's not Comcast. Fix your **** EA!!!

    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 9 ms 11 ms 9 ms 68.85.77.181
    4 8 ms 12 ms 9 ms te-7-4-ur01.wayneave.pa.panjde.comcast.net [68.8
    6.211.177]
    5 15 ms 13 ms 15 ms pos-1-5-0-0-cr01.mclean.va.ibone.comcast.net [68
    .86.91.233]
    6 20 ms 12 ms 11 ms ge-4-0-142.ipcolo2.Washington1.Level3.net [63.21
    0.62.33]
    7 15 ms 12 ms 14 ms ae-43-99.car3.Washington1.Level3.net [4.68.17.19
    7]
    8 25 ms 12 ms 30 ms ELECTRONIC.car3.Washington1.Level3.net [4.79.169
    .74]
    9 111 ms 116 ms 111 ms fert08-eqx-iad.ea.com [159.153.224.238]
    10 113 ms 106 ms 118 ms 159.153.233.71

    =================================================================

    Pinging central-ae6.owo.com [159.153.233.71] with 32 bytes of dat
    Reply from 159.153.233.71: bytes=32 time=101ms TTL=55
    Reply from 159.153.233.71: bytes=32 time=84ms TTL=55
    Reply from 159.153.233.71: bytes=32 time=107ms TTL=55
    Reply from 159.153.233.71: bytes=32 time=101ms TTL=55
    Reply from 159.153.233.71: bytes=32 time=94ms TTL=55
    Reply from 159.153.233.71: bytes=32 time=110ms TTL=55
    Reply from 159.153.233.71: bytes=32 time=100ms TTL=55
    Reply from 159.153.233.71: bytes=32 time=95ms TTL=55
    Reply from 159.153.233.71: bytes=32 time=103ms TTL=55
    Reply from 159.153.233.71: bytes=32 time=103ms TTL=55
    Reply from 159.153.233.71: bytes=32 time=109ms TTL=55
    Reply from 159.153.233.71: bytes=32 time=107ms TTL=55
    Reply from 159.153.233.71: bytes=32 time=96ms TTL=55
    Reply from 159.153.233.71: bytes=32 time=109ms TTL=55
    Reply from 159.153.233.71: bytes=32 time=109ms TTL=55
    Reply from 159.153.233.71: bytes=32 time=104ms TTL=55
    Reply from 159.153.233.71: bytes=32 time=100ms TTL=55
    Reply from 159.153.233.71: bytes=32 time=100ms TTL=55
    Reply from 159.153.233.71: bytes=32 time=116ms TTL=55
    Reply from 159.153.233.71: bytes=32 time=99ms TTL=55
    Reply from 159.153.233.71: bytes=32 time=112ms TTL=55
    Reply from 159.153.233.71: bytes=32 time=110ms TTL=55
    Reply from 159.153.233.71: bytes=32 time=114ms TTL=55
    Reply from 159.153.233.71: bytes=32 time=118ms TTL=55
    Reply from 159.153.233.71: bytes=32 time=108ms TTL=55
    Reply from 159.153.233.71: bytes=32 time=111ms TTL=55
    Reply from 159.153.233.71: bytes=32 time=109ms TTL=55
    Reply from 159.153.233.71: bytes=32 time=102ms TTL=55
    Reply from 159.153.233.71: bytes=32 time=111ms TTL=55
    Reply from 159.153.233.71: bytes=32 time=113ms TTL=55
    Reply from 159.153.233.71: bytes=32 time=104ms TTL=55
    Reply from 159.153.233.71: bytes=32 time=114ms TTL=55
    Reply from 159.153.233.71: bytes=32 time=113ms TTL=55
    Reply from 159.153.233.71: bytes=32 time=98ms TTL=55

    Ping statistics for 159.153.233.71:
    Packets: Sent = 34, Received = 34, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 84ms, Maximum = 118ms, Average = 105ms
     
  15. Malador

    Malador Guest

    10 PM EST

    [​IMG]
     
  16. Malador

    Malador Guest

    11 pm EST

    [​IMG]
     
  17. Coffin

    Coffin Guest

    Can we get an official acknowledgment about this lag problem? It's either a Level3.net server or it's fert08-eqx-iad.ea.com. But something is seriously up. It's been like 3 months for some people.
     
  18. Diggity

    Diggity Guest

    I recently moved and switched from DSL (worked fine at old location) to Cable. Cable works fine except the UO lag. Seems to start sometime in the morning Pacific time and end around 9 PM Pacific time. This is from the West coast to the East coast servers.

    Decided to switch back to DSL at the new place. I have both cable and DSL at the moment but will cancel cable tomorrow. Anyway, here are comparison trace routes from west coast to east coast. Approx 5:30 PM Pacific time. I expect the cable lag to clear up around 9PM Pacific.

    Code:
    ATT DSL trace
    
    Host Name                                         IP Address              Hop    Ping Time   Ping Avg   % Loss    Pkts r/s        Ping best/worst
    
    vlan69.csw1.SanJose1.Level3.net                   4.68.18.62              7      11ms
    ae-64-64.ebr4.SanJose1.Level3.net                 4.69.134.241            8      22ms
    ae-2.ebr4.NewYork1.Level3.net                     4.69.135.186            9      90ms
    ae-74-74.csw2.NewYork1.Level3.net                 4.69.134.118            10     84ms
    ae-71-71.ebr1.NewYork1.Level3.net                 4.69.134.69             11     81ms
    ae-3-3.ebr4.Washington1.Level3.net                4.69.132.93             12     96ms
    ae-64-64.csw1.Washington1.Level3.net              4.69.134.178            13     83ms
    ae-13-69.car3.Washington1.Level3.net              4.68.17.5               14     84ms
    ELECTRONIC.car3.Washington1.Level3.net            4.79.169.74             15     84ms
    fert08-eqx-iad.ea.com                             159.153.224.238         16     84ms
    * Unknown Host *                                  159.153.233.23          17     84ms
    
    
    Comcast cable trace
    
    Host Name                                         IP Address              Hop    Ping Time   Ping Avg   % Loss    Pkts r/s        Ping best/worst
    
    xe-10-3-0.edge1.SanJose1.Level3.net               4.71.118.5              6      16ms
    vlan79.csw2.SanJose1.Level3.net                   4.68.18.126             7      25ms
    ae-74-74.ebr4.SanJose1.Level3.net                 4.69.134.245            8      24ms
    ae-2.ebr4.NewYork1.Level3.net                     4.69.135.186            9      94ms
    ae-74-74.csw2.NewYork1.Level3.net                 4.69.134.118            10     92ms
    ae-71-71.ebr1.NewYork1.Level3.net                 4.69.134.69             11     93ms
    ae-3-3.ebr4.Washington1.Level3.net                4.69.132.93             12     96ms
    ae-64-64.csw1.Washington1.Level3.net              4.69.134.178            13     97ms
    ae-13-69.car3.Washington1.Level3.net              4.68.17.5               14     112ms
    ELECTRONIC.car3.Washington1.Level3.net            4.79.169.74             15     93ms
    fert07-eqx-iad.ea.com                             159.153.224.230         16     190ms
    * Unknown Host *                                  159.153.233.23          17     191ms
    
    
    East coast servers play fine thru DSL and laggy thru cable at times like this for me. Hope they can clear it up for those who can't switch ISP's. I don't blame Comcast, but I believe the problem is beyond their control so the most expedient thing for me to do was to get DSL again.
     
  19. Deprave

    Deprave Sage
    Stratics Veteran

    Joined:
    Dec 16, 2008
    Messages:
    542
    Likes Received:
    90
    C:\Documents and Settings\superheros>tracert greatlakes.owo.com

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

    1 <1 ms <1 ms <1 ms Carlos [192.168.2.1]
    2 * * * Request timed out.
    3 14 ms 7 ms 8 ms 68.85.140.73
    4 10 ms 9 ms 14 ms po-53-ar01.foxboro.ma.boston.comcast.net [68.85.
    162.161]
    5 14 ms 11 ms 11 ms be-56-ar01.needham.ma.boston.comcast.net [68.85.
    162.181]
    6 12 ms 17 ms 19 ms po-10-ar01.springfield.ma.boston.comcast.net [68
    .87.146.22]
    7 14 ms 19 ms 14 ms be-11-ar01.chartford.ct.hartford.comcast.net [68
    .87.146.26]
    8 19 ms 17 ms 18 ms pos-2-3-0-0-cr01.newyork.ny.ibone.comcast.net [6
    8.86.90.57]
    9 18 ms 18 ms 19 ms xe-8-2-0.edge1.NewYork2.Level3.net [4.71.186.21]

    10 16 ms 21 ms 19 ms vlan51.ebr1.NewYork2.Level3.net [4.69.138.222]
    11 22 ms 27 ms 28 ms ae-3-3.ebr2.Washington1.Level3.net [4.69.132.89]

    12 25 ms 31 ms 34 ms ae-82-82.csw3.Washington1.Level3.net [4.69.134.1
    54]
    13 25 ms 211 ms 217 ms ae-33-89.car3.Washington1.Level3.net [4.68.17.13
    3]
    14 25 ms 23 ms 24 ms ELECTRONIC.car3.Washington1.Level3.net [4.79.169
    .74]
    15 122 ms 123 ms 123 ms fert08-eqx-iad.ea.com [159.153.224.238]
    16 122 ms * * 159.153.233.71
    17 123 ms 124 ms 122 ms 159.153.233.71

    Trace complete.

    C:\Documents and Settings\superheros>^A
     
  20. Malador

    Malador Guest

     
  21. sdk

    sdk Guest

    I don't want to jinx myself but the last portion of my routing appears to be going through ATT now instead of Level3, and my connection is back to normal. It's been stable for about 24 hours now..

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

    1 <1 ms <1 ms <1 ms 192.168.1.1
    2 * * * Request timed out.
    3 9 ms 8 ms 8 ms 68.85.77.181
    4 10 ms 9 ms 10 ms te-7-4-ur01.wayneave.pa.panjde.comcast.net [68.8
    6.211.177]
    5 12 ms 18 ms 12 ms pos-1-5-0-0-cr01.mclean.va.ibone.comcast.net [68
    .86.91.233]
    6 14 ms 13 ms 14 ms pos-0-2-0-0-pe01.ashburn.va.ibone.comcast.net [6
    8.86.86.70]
    7 15 ms 13 ms 14 ms 192.205.37.45
    8 15 ms 16 ms 15 ms cr2.wswdc.ip.att.net [12.122.84.82]
    9 15 ms 15 ms 13 ms gar2.ascva.ip.att.net [12.122.134.121]
    10 15 ms 13 ms 13 ms 12.116.77.34
    11 14 ms 14 ms 13 ms fert08-eqx-iad.ea.com [159.153.224.234]
    12 14 ms 14 ms 13 ms 159.153.233.71
     
  22. Malador

    Malador Guest

    Interesting at 5:45 PM EST on Wed I am not over 100 ms ping. maybe they are doing something

    [​IMG]
     
  23. RL'S pker

    RL'S pker Sage
    Stratics Veteran

    Joined:
    May 24, 2008
    Messages:
    715
    Likes Received:
    19
    Is it just me, or is the Lag completely gone now? I'm logged in right now, no lag, and pinging at 47 to Atlantic. Shoot, i might be able to actually make a come back to the game now!!!
     
  24. Coffin

    Coffin Guest

    I was pinging normal today also, the first day in months!
     
  25. KTULU_ATL

    KTULU_ATL Guest

    Bad ping is back as of today 10/31/2009. Was good for over a week but now it's bad again.