lag issue identified, I believe

[GalenKnighthawke]

Galen, the issue has been brought to their attention with all the details. It has also been discussed at length in this thread. Nothing hidden.

Weird that those servers are named fert.....Fert is some ferret owners' slang term for ferrets, and of course the name lent itself to one of our now-former team members, Fertbert.

100% packet loss....Please forgive my ignorance, but doesn't that typically mean that a server doesn't accept pings? Otherwise, isn't 100% packet loss basically "page not found?"

Could someone launching denial of service attacks on a server cause that?

Again please forgive my amateurish ignorance....This is all quite fascinating and my knowledge of this stuff is touch-and-go at best.

-Galen's player

 

[Beastmaster]

The 100% packet loss seen in several traces from AT&T routers just means those routers do not respond to pings. If you have a home router, like a Linksys, Dlink, etc., you can usually configure them not to respond to pings as well (and its a good idea to do so if you understand your home network)

 

[Beastmaster]

On XP tracert defaults to 30 hops so you should be good. If all you are seeing is timeouts your firewall may be blocking tracert.

 

[GalenKnighthawke]

The 100% packet loss seen in several traces from AT&T routers just means those routers do not respond to pings. If you have a home router, like a Linksys, Dlink, etc., you can usually configure them not to respond to pings as well (and its a good idea to do so if you understand your home network)

Thank you.

-Galen's player

 

[Sytherea]

I thought this morning that the lag was gone, but alas, it's Sunday night and it's back in full force. Great job, EA. If Christmas is going to be anything like this, let me know now, so I can find something else to do. This, aside from the launch of AOS, has been the single worse week I can remember in UO. It's a shame because it had so much potential of being one of the best.

Someone really should rename this thread so people that ARE experiencing lag don't get their hopes up that a fix is just around the corner.

 

[HD2300]

It is a bandwidth issue

1. No problem at 1-4am
2. No problem with West coast servers

 

[Xenobia]

Why not just post in generic terms what you think the issue is? If someone contacts you personally there'll be accusations of favoritism.

Also they can't tell a real network guy from some noob who says he is something he is not.

So why not just post, in generic terms, what you think the issue is? And if they like it then maybe they'll contact you>?

Either way remember that Mythic does have network people.....They may have already thought of whatever it is you thought of?

-Galen's player

I beleive EA posted that they were "looking for the problem" when Beastmaster saw it plain as day. When I started REALLY looking at it, so did I. If they contact Beastmaster personally and resolve this issue then I would be happy if they gave him a year worth of free gameplay and personally delivered chocolates and roses to his door. It's already been presented that there is an issue with DNS whether it be on the software or hardware side. AND if they had already found the issue then the problem is that they are letting it slide while we lag. That is altogether another problem. It's ok if someone other then you or me or the other MANY people complaining of lag get's the credit in this. It is not about a pat on the back, it's about being able to play a game we are paying for. Oh one more thing...If they have network guys as you say they do (and yes they do), then trust me when I tell you they will know if Beastmaster knows his stuff or not. Period. End of story. I mean hell, I could tell the minute he said something and I started really looking at the traceroutes that he had picked up the issue. Now I'm done fussing.

 

[Lady Kiara]

It is a bandwidth issue

1. No problem at 1-4am
2. No problem with West coast servers

I have noticed this my self as there is hardly anylag at 3am compared to peek time.

 

[Cherokee UOA]

I feel that if EA cant fix the lag problems that we are all having they should at least offer us free game play or something...I'm paying for time I cant even use. This blows really bad does not matter what time of day or night I log onto game I cant play...walk two steps freeze. I really love playing UO and I dont get the chance as often as I use to in the past. So now when I'm able to log into game now I cant do anything but SIT at the bank.
EA needs to step up and do something for us. They make alot of cash off alot of people and for them to do nothing while we sit here paying for something we cant even enjoy is just wrong!!!!! 9 years is long time to stay with a game but I'm about to give this game a toss out the window if EA does not do something soon. Not worth paying for something anymore if you cant enjoy it.

 

[Xenobia]

It is a bandwidth issue

1. No problem at 1-4am
2. No problem with West coast servers

West coast are not routed through fert07 or fert08...try a trace route on all the west coast shards and you will see what I am talking about

 

[sapphirediablo11]

If it is a bandwith issue does that mean

A:UO is now over flown wiht people and cna't stop the massive amount of poeple playing...
or
B: They bought a cheaper bandwith system... thing *inserts alot of specail technological terms here*

 

[HD2300]

West coast are not routed through fert07 or fert08...try a trace route on all the west coast shards and you will see what I am talking about

Yes. It is a bandwidth issue into the East coast.

DNS is only used to initially resolve a domain name (atlantic.owo.com) to an ip address (x.x.x.x). Thereafter only ip addresses are used.

If the connection(s) into the East coast servers are flooded, that would cause lag.

 

[Xenobia]

Yes. It is a bandwidth issue into the East coast.

DNS is only used to initially resolve a domain name (atlantic.owo.com) to an ip address (x.x.x.x). Thereafter only ip addresses are used.

If the connection(s) into the East coast servers are flooded, that would cause lag.

If you say so Did you happen to take a gander at the trace routes? I did and I can tell you there is a problem ...and btw I know what DNS does but I thank you for the tutorial. Now let's get on to what is soooo flooding the East coast servers????? hmm? There is a problem with DNS. Oh wait! People have been talking about a retro shard...maybe 100000000 new subscribers happened on to the servers over the past few weeks eh?

 

[Pink Dragoness]

I would like to say that at 11:30 pm est time, Sunday, that I was pining low numbers to the sever and had no packet loss. I hope this continues.

 

[Violence]

I feel I should pay Beastmaster 14 Euro just for looking into this and being communicative.

And I'm not being sarcastic.. I mean really, what did EA do before he sent them the info and got this going? If it can be argued that they had pinpointed the problem and knew all along, it would only indicate they are twice as lazy.

Are we supposed to do EVERYTHING for them, from player-organised events to junk repairs and policing the game?

EA, just let people bid on buying Ultima Online so someone competent can run it. Hey I know.. XMass is near. Give Blizzard a present? There won't be much difference anyway, what's left from Ultima..?

 

[Tina Small]

Ever since I read someone's comment yesterday (I think it was Dermott) that the fert07 and/or fert08 IPs might also be routing some of EA's web traffic, I can't help thinking that could be a big reason for the lag.

I know folks have been complaining about the lag sporadically for a while (there was quite a discussion going here around August 15th). However, it seems to have picked up again early this month, only a few days after EA laid off 700-800 people. Could we be seeing the results of a denial-of-service attack initiated by disgruntled employees? If yes, it might explain why we're hearing very little from EA regarding the issue.

 

[Littleblue]

I did a tracert to pogo.com, and fert07 was the first EA node that I hit.

 

[Beastmaster]

Yes, I have friends that Pogo and they have been reporting the same issues.

 

[Littleblue]

I wondered about that when I saw that they share similar paths. I really hope this issue gets resolved, for all of those that enjoy Pogo as well as UO.

 

[phantus]

Yes. It is a bandwidth issue into the East coast.

DNS is only used to initially resolve a domain name (atlantic.owo.com) to an ip address (x.x.x.x). Thereafter only ip addresses are used.

If the connection(s) into the East coast servers are flooded, that would cause lag.

If you say so Did you happen to take a gander at the trace routes? I did and I can tell you there is a problem ...and btw I know what DNS does but I thank you for the tutorial. Now let's get on to what is soooo flooding the East coast servers????? hmm? There is a problem with DNS. Oh wait! People have been talking about a retro shard...maybe 100000000 new subscribers happened on to the servers over the past few weeks eh?

It's not a DNS issue. At best it's a routing issue and there is no way in hell anyway can find the problem without logging into the router and looking at the actual counters or other information. Traceroute can only take you so far. I have no lag. Not before the publish. Not after. All my pings are are as I expect them to be. Therein lies the problem. It's not everyone that is lagging. Certain parts of the country to certain servers. That rules out DNS and points the finger at routing.

 

[Lynk]

It's not a DNS issue. At best it's a routing issue and there is no way in hell anyway can find the problem without logging into the router and looking at the actual counters or other information. Traceroute can only take you so far. I have no lag. Not before the publish. Not after. All my pings are are as I expect them to be. Therein lies the problem. It's not everyone that is lagging. Certain parts of the country to certain servers. That rules out DNS and points the finger at routing.

Xenobia just likes to look like she knows what she's talking about, when she really doesn't.

 

[soze]

Ever since I read someone's comment yesterday (I think it was Dermott) that the fert07 and/or fert08 IPs might also be routing some of EA's web traffic, I can't help thinking that could be a big reason for the lag.

I know folks have been complaining about the lag sporadically for a while (there was quite a discussion going here around August 15th). However, it seems to have picked up again early this month, only a few days after EA laid off 700-800 people. Could we be seeing the results of a denial-of-service attack initiated by disgruntled employees? If yes, it might explain why we're hearing very little from EA regarding the issue.

Rather...It may be a case that they are seriously understaffed to handle all the day to day issues. I think some things are falling in between the cracks and they cant keep up

 

[Harlequin]

It's not a DNS issue. At best it's a routing issue and there is no way in hell anyway can find the problem without logging into the router and looking at the actual counters or other information. Traceroute can only take you so far. I have no lag. Not before the publish. Not after. All my pings are are as I expect them to be. Therein lies the problem. It's not everyone that is lagging. Certain parts of the country to certain servers. That rules out DNS and points the finger at routing.

Agreed, although ping and tracert are useful troubleshooting tools, and can even identify certain misconfiguration issues (eg max packet size), they only go so far.

In this case, it's useful because with enough sampling like what they have been asking people to provide, they can isolate which routers are the potential culprit. Their network guys would have to login to the router to check the logs to find out what the problem is. Having said that, most folks do not turn on logging on the routers since it takes up resources. It's only turned on when there's a problem. Once turned on, they have to log the activities for some time, possibly a day or 2 to get enough info into the logs. Even with the logs, it might not be an easily identified problem.

Could be a misconfiguration in the IOS, could be a problem with the routing tables, could be a hardware issue, could even be other routers on the next hop failing over every 30 mins and continuously sending route table updates to the router that seems to be giving the problem.

If it's a hardware issue, you next need to identify which is the faulty module. If there's no clear indication in the logs, you swap out modules 1 by 1, let it run for a day to identify which is the faulty one. Unless they have a solid maintenance contract with their vendor and can swap out the entire chassis including all modules.

So I can understand the delay in resolution. However, at least continue to update customers on the progress, even if there's no progress.

 

[Maplestone]

So I can understand the delay in resolution. However, at least continue to update customers on the progress, even if there's no progress.

*nods*

I keep going to check the the hourly status report from the resolution team ... only to remember there is no status page.

 

[Pink Dragoness]

Last night and early today I was pining fine to server, but at 5:30pm est time im already getting packet loss:

Host Name IP Address Hop Ping Time Ping Avg % Loss Pkts r/s Ping best/worst
h1.96.18.98.dynamic.ip.windstream98.18.96.1 2 31ms 31ms 0% 101 / 101 31ms / 39ms
h114.123.213.151.static.ip.windst151.213.123.114 3 31ms 32ms 0% 101 / 101 31ms / 65ms
h86.122.90.75.static.ip.windstrea75.90.122.86 4 40ms 37ms 0% 101 / 101 36ms / 45ms
h98.254.213.151.static.ip.windstr151.213.254.98 5 39ms 37ms 0% 101 / 101 36ms / 43ms
te-3-2.car2.Atlanta2.Level3.net 4.71.254.13 6 37ms 49ms 0% 101 / 101 36ms / 233ms
ae-63-51.ebr3.Atlanta2.Level3.net4.68.103.30 7 44ms 44ms 0% 101 / 101 39ms / 53ms
ae-2.ebr1.Washington1.Level3.net 4.69.132.86 8 54ms 60ms 0% 101 / 101 53ms / 67ms
ae-81-81.csw3.Washington1.Level3.4.69.134.138 9 59ms 58ms 0% 101 / 101 53ms / 68ms
ae-33-89.car3.Washington1.Level3.4.68.17.133 10 51ms 55ms 0% 100 / 100 51ms / 197ms
ELECTRONIC.car3.Washington1.Level4.79.169.74 11 52ms 52ms 0% 100 / 100 51ms / 57ms
fert07-eqx-iad.ea.com 159.153.224.230 12 150ms 157ms 5% 95 / 100 148ms / 306ms
* Unknown Host * 159.153.233.23 13 150ms 149ms 2% 98 / 100 139ms / 155ms

 

[phantus]

Is there anyone that is experiencing lag that isn't going through level3?

 

[Maplestone]

Is there anyone that is experiencing lag that isn't going through level3?

Yes, my route goes through sprintlink.net (but for me it's a box with IP 144.223.246.6 right before fert08 instead of fert08 itself where the lag hits)

 

[Pink Dragoness]

Is there anyone that is experiencing lag that isn't going through level3?

Yes, my route goes through sprintlink.net (but for me it's a box with IP 144.223.246.6 right before fert08 instead of fert08 itself where the lag hits)

Why is yours fert08 and mine is fert07? I am not understanding that one

 

[Maplestone]

Why is yours fert08 and mine is fert07? I am not understanding that one

All roads lead to Britain - but we don't all take the same road and the city has more than one entrance

*gets lost in the metaphor and tries to recall to the server*

 

[Beastmaster]

Update(sorta):

I asked Joanne when she thought someone would look into this last night. Since it was still just Sunday I anticipated an answer of today (Monday) when folks got back in the office. I also asked whether maybe they had already looked into it and had ruled out the configuration issues I pointed out.

She expressed her concern over so many people being so adversely affected (and I believe her to be sincere). She said she had been monitoring the threads all weekend (true, I saw that) and would continue sending info up the ladder. She did not however answer my questions at all.

This leads me to believe the router issues are so far out of the hands of our Dev team that they are as much at the mercy of the corporate giant as we are. This is obviously something they cannot comment on. With the economic crunch and heads rolling regularly I'm sure its all they can do to try and hold onto their jobs to protect their families.

Today's inaction on the issues I brought up are the final straw for me. UO's subscription numbers are estimated to be somewhere around 100k, Pogo's are in the millions. We're sharing the same pipelines and we're all suffering. Someone brought up the era when most east coast connections were made through Abovenet. I was around then and it wasn't pleasant. BUT! Someone from EA worked with Abovenet to resolve those issues. It was not an issue caused by EA equipment but they recognized their customers were suffering and went the extra mile to contact Abovenet and work it out.

It is extremely difficult to diagnose these issues from the client end. Thanks to the abundance of trace routes posted though, it is easy to say the issue is directly connected to Fert07 and Fert08. These 2 devices are accessed through several carriers dependent upon your region, but the result is always the same, lag and packet loss. It has been shown these 2 devices have configuration issues. Over 24 hours later nothing has changed.

I cannot accept the inaction.

I won't say goodbye yet, but rather à bientôt.

 

[Pink Dragoness]

Thanks Beastmaster for the info

where a Speedman when you need one :[

 

[Maplestone]

Thank you for all your input Beastmaster.

I will say that today my lag is not as severe - only about 2% packet loss - there are noticable hickups, but I was able to take down my first skeletal dragon, so I can't claim to be incapacitated.

The confirmation that it's not just us affected is good to know - it lends a lot of credibility to the conclusions we've been drawing over the last few days. I have to admit that I'm surprised the packet loss is not setting off in the network monitoring center at EA (unless it is and for corporate reasons, they aren't allowed to admit to it).

(*wonders who the manufacturer of that fert07/08 router is*)

 

[Pink Dragoness]

Dont you remember when they put that router in, I beleive it was back around 2003 and im sure by now it probably needs some upgrading. Well it was around the time that EA Calli was combinging the accounts all in one after the move from Austin Tx.
I think Mythic has no control of this and that EA in Ca. is where emails should be directed about this situation.

 

[HD2300]

The confirmation that it's not just us affected is good to know - it lends a lot of credibility to the conclusions we've been drawing over the last few days. I have to admit that I'm surprised the packet loss is not setting off in the network monitoring center at EA (unless it is and for corporate reasons, they aren't allowed to admit to it).

I suspect it is a bean counter decision to cut the bandwidth.

 

[Spree]

Fix the lag

 

[phantus]

(*wonders who the manufacturer of that fert07/08 router is*)

Cisco

Anyone still see fert08? I see edge01 and fert07..

 

[Maplestone]

Cisco

Ah, that explains it. ( oops, I might be biased )

(although at least for the moment, I'm back in superfast ping and no packet loss)

 

[Basara]

BTW, what ports does uotrace use for its trace routes ? Ever since I installed my new firewall, uotrace hasn't allowed traces (though I can link test through the firewall with the program)

 

[Tina Small]

Cisco

Anyone still see fert08? I see edge01 and fert07..

I'm seeing fert08 for Atlantic and GL (polling from Colorado). (Didn't check any other shards.) At the moment it's looking pretty darn good too, pinging about 74 on average and no packet loss. Will have to check again in the morning.

Edited to add: Checked Chesapeake and it is using fert07. The ping's pretty good too (mid-70s) but showing some very sporadic minor packet loss on the router one hop before it (ELECTRONIC.car.Washington1.Level3.net).

 

[Harlequin]

BTW, what ports does uotrace use for its trace routes ? Ever since I installed my new firewall, uotrace hasn't allowed traces (though I can link test through the firewall with the program)

Haven't used UOTrace for a very long time, but I suspect it uses ICMP like tracert plus maybe dns/reverse lookup and another to check the login server for the server list?

I can't remember, but in this case, if you are sure that your UOTrace.exe is not compromised, you might want to add an "any to any" (any network traffic TCP/UDP/ICMP to any destination) rule for uotrace just to keep your firewall rules simple.

If your want to play it safe, turn on learning mode in Kaspersky (I remember you mentioned your ISP uses that) and delete any prior entries for UOTrace, then fire it up and select the "create a rule" option when Kaspersky prompts.

Btw, did my suggestion on the other thread re toggling the compatibility mode in Kaspesky work for you?

 

[Basara]

I managed to get it to work by changing the ICMP setting - which is stange cause I tried changing those very same settings once before with no effect.

As for changing the compatibility settings to try to get UO Assist to run, I didn't have to - all it took was changing from loading method 1 to loading method 2.

I just wish I could get a faster average ping time from Kentucky to Lake Austin than about 100 ms, but part of that is from my being at the effective terminus of my cable line - even when I got the service, the installers could only get me to connect at about half the advertised speed, due to distance and line conditions (Charter ran this system into the ground before selling it to Newwave - I've seen a 20% improvement as Newwave rehabilitated it over the last 2 years).

 

[Harlequin]

I managed to get it to work by changing the ICMP setting - which is stange cause I tried changing those very same settings once before with no effect.

As for changing the compatibility settings to try to get UO Assist to run, I didn't have to - all it took was changing from loading method 1 to loading method 2.

I just wish I could get a faster average ping time from Kentucky to Lake Austin than about 100 ms, but part of that is from my being at the effective terminus of my cable line - even when I got the service, the installers could only get me to connect at about half the advertised speed, due to distance and line conditions (Charter ran this system into the ground before selling it to Newwave - I've seen a 20% improvement as Newwave rehabilitated it over the last 2 years).

That's wonderful, I remember that there were 3 ways to start UOA - new, old and one more. But just thought it's for memory and performance, never realized that it works for this case too. You learn something new everyday!

 

[Tina Small]

It's morning now and the high ping to fert07 and fert08 and the last hop is back, as well as some (2%) packet loss.

 

[laurlo]

thanks for doing what you can

 

[gjohnson5]

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Timothy>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  164.111.207.254
  2     1 ms    <1 ms    <1 ms  138.26.220.193
  3     4 ms    <1 ms     1 ms  nucleon.dpo.uab.edu [138.26.1.211]
  4     4 ms     4 ms     4 ms  atx-edge-02.inet.qwest.net [65.101.202.41]
  5     4 ms     5 ms     4 ms  atl-core-01.inet.qwest.net [205.171.21.5]
  6     4 ms     4 ms     4 ms  atl-brdr-03.inet.qwest.net [205.171.21.98]
  7     4 ms     4 ms     5 ms  63.146.26.234
  8    25 ms    26 ms    24 ms  tbr1.attga.ip.att.net [12.123.20.202]
  9    24 ms    25 ms    24 ms  cr1.attga.ip.att.net [12.122.17.9]
 10    24 ms    24 ms    24 ms  cr2.wswdc.ip.att.net [12.122.1.174]
 11    24 ms    24 ms    24 ms  tbr2.wswdc.ip.att.net [12.122.16.94]
 12    23 ms    23 ms    23 ms  gar2.ascva.ip.att.net [12.122.113.73]
 13   121 ms   121 ms   121 ms  12.116.77.34
 14   122 ms   121 ms   122 ms  fert07-eqx-iad.ea.com [159.153.224.226]
 15   121 ms   121 ms   121 ms  159.153.233.71

Trace complete.

I'm seeing the exact same thing.
Professionally I am a unix administrator and an Oracle DBA and this is what my traceroutes look like

C:\Documents and Settings\gjohnson>tracert 159.153.233.71

Tracing route to 159.153.233.71 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 5 ms 5 ms 5 ms 73.25.50.1
3 6 ms 7 ms 6 ms ge-2-2-ur01.ebroadst.ga.savannah.comcast.net [68
.86.251.37]
4 7 ms 5 ms 5 ms te-9-4-ar01.savannah.ga.savannah.comcast.net [68
.86.250.33]
5 8 ms 9 ms 9 ms te-7-4-ar02.augusta.ga.augusta.comcast.net [68.8
6.164.21]
6 33 ms 34 ms 31 ms 68.86.90.189
7 33 ms 33 ms 33 ms pos-0-12-0-0-cr01.atlanta.ga.ibone.comcast.net [
68.86.85.213]
8 32 ms 33 ms 31 ms te-3-3.car1.Atlanta2.Level3.net [4.71.252.1]
9 35 ms 36 ms 36 ms ae-62-51.ebr2.Atlanta2.Level3.net [4.68.103.29]

10 43 ms 35 ms 35 ms ae-63-60.ebr3.Atlanta2.Level3.net [4.69.138.4]
11 46 ms 51 ms 53 ms ae-2.ebr1.Washington1.Level3.net [4.69.132.86]
12 52 ms 54 ms 55 ms ae-61-61.csw1.Washington1.Level3.net [4.69.134.1
30]
13 53 ms 59 ms 55 ms ae-13-69.car3.Washington1.Level3.net [4.68.17.5]

14 48 ms 47 ms 47 ms ELECTRONIC.car3.Washington1.Level3.net [4.79.169
.74]
15 146 ms 147 ms 147 ms fert07-eqx-iad.ea.com [159.153.224.230]
16 146 ms 147 ms 146 ms 159.153.233.71

Trace complete.

C:\Documents and Settings\gjohnson>

The fact that EA has 2 internet connections, one to att.net and another to level3 seems to indicate that it is their routers that are having issues.
Whether this is some multihoming misconfiguration or some Cisco IOS upgrade causing the problems, that would need to be addressed

 

[Kage]

How do I copy my trace? I was not able to copy it so just screen shot it.

 

[gjohnson5]

How do I copy my trace? I was not able to copy it so just screen shot it.

in a command prompt , you right click the title bar of the cmd.exe and mouse over to "edit". There will be "mark" as an option. highlight the text you wish to mark (as you would normally)
right click the cmd.exe title bar again and select "copy"

Then the text will be in your clipboard can be "ctrl-v" or pasted as normal

 

[Kage]

Thank you gjohnson5.

 

[Kage]

C:\Documents and Settings\Randy Johnston>tracert siegeperilous.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.1.1
2 7 ms 7 ms 7 ms 10.247.15.1
3 8 ms 7 ms 8 ms 208.52.160.181
4 22 ms 18 ms 26 ms 216.24.172.229
5 32 ms 19 ms 18 ms Cat65-1-Vlan8.broadriver.com [216.24.161.244]
6 26 ms 17 ms 19 ms 208.52.177.194
7 17 ms 18 ms 18 ms 208.52.178.174
8 25 ms 18 ms 19 ms so-5-0-1.edge1.Atlanta2.Level3.net [4.71.192.29]

9 29 ms 36 ms 37 ms ae-63-51.ebr3.Atlanta2.Level3.net [4.68.103.30]

10 50 ms 35 ms 28 ms ae-73-70.ebr3.Atlanta2.Level3.net [4.69.138.20]

11 48 ms 38 ms 38 ms ae-2.ebr1.Washington1.Level3.net [4.69.132.86]
12 34 ms 43 ms 35 ms ae-13-69.car3.Washington1.Level3.net [4.68.17.5]

13 31 ms 30 ms 31 ms ae-13-69.car3.Washington1.Level3.net [4.68.17.5]

14 32 ms 35 ms 32 ms ELECTRONIC.car3.Washington1.Level3.net [4.79.169
.74]
15 133 ms 129 ms * fert08-eqx-iad.ea.com [159.153.224.238]
16 145 ms 140 ms 147 ms 159.153.233.47

Trace complete.

C:\Documents and Settings\Randy Johnston>

 

[Kage]

C:\Documents and Settings\Randy Johnston>tracert siegeperilous.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.1.1
2 7 ms 7 ms 7 ms 10.247.15.1
3 8 ms 7 ms 8 ms 208.52.160.181
4 22 ms 18 ms 26 ms 216.24.172.229
5 32 ms 19 ms 18 ms Cat65-1-Vlan8.broadriver.com [216.24.161.244]
6 26 ms 17 ms 19 ms 208.52.177.194
7 17 ms 18 ms 18 ms 208.52.178.174
8 25 ms 18 ms 19 ms so-5-0-1.edge1.Atlanta2.Level3.net [4.71.192.29]

9 29 ms 36 ms 37 ms ae-63-51.ebr3.Atlanta2.Level3.net [4.68.103.30]

10 50 ms 35 ms 28 ms ae-73-70.ebr3.Atlanta2.Level3.net [4.69.138.20]

11 48 ms 38 ms 38 ms ae-2.ebr1.Washington1.Level3.net [4.69.132.86]
12 34 ms 43 ms 35 ms ae-13-69.car3.Washington1.Level3.net [4.68.17.5]

13 31 ms 30 ms 31 ms ae-13-69.car3.Washington1.Level3.net [4.68.17.5]

14 32 ms 35 ms 32 ms ELECTRONIC.car3.Washington1.Level3.net [4.79.169
.74]
15 133 ms 129 ms * fert08-eqx-iad.ea.com [159.153.224.238]
16 145 ms 140 ms 147 ms 159.153.233.47

Trace complete.

C:\Documents and Settings\Randy Johnston>

Usually when fert08 is acting up and the one under it not sure what that even is because I know nothing about this stuff.

I can't play UO at all and I get this when I check my ping...

This is what I get a lot of times making it where I can not play UO at all. notice the time out and packet loss.

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Randy Johnston>Ping Siege.owo.com

Pinging central-ae4.owo.com [159.153.233.47] with 32 bytes of data:

Reply from 159.153.233.47: bytes=32 time=141ms TTL=50
Reply from 159.153.233.47: bytes=32 time=130ms TTL=50
Request timed out.
Reply from 159.153.233.47: bytes=32 time=130ms TTL=50

Ping statistics for 159.153.233.47:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 130ms, Maximum = 141ms, Average = 133ms

C:\Documents and Settings\Randy Johnston>