tracert ALTER.NET is back
I ran this on AUgust 14, at 7:53 AM EST
Tracing route to 74.201.102.13 over a maximum of 30 hops
6 14 ms 15 ms 15 ms cr2.cgcil.ip.att.net [12.122.132.250]
7 13 ms 13 ms 16 ms cgcil04jt.ip.att.net [12.122.81.97]
8 12 ms 21 ms 21 ms 0.ae10.BR3.CHI13.ALTER.NET [204.255.168.165]
9 * * * Request timed out.
10 34 ms 35 ms 37 ms 0.xe-8-2-0.GW15.BOS4.ALTER.NET [152.63.24.34]
11 38 ms 36 ms 36 ms internap-gw.customer.alter.net [152.179.134.214]
12 37 ms 35 ms 35 ms border1.te7-1-bbnet1.bsn003.pnap.net [63.251.128.43]
13 37 ms 35 ms 37 ms turbine-7.border1.bsn003.pnap.net [64.95.76.202]
14 36 ms 35 ms 35 ms 74.201.102.154
15 37 ms 37 ms 35 ms 74.201.102.13
Trace complete.
This will cause server is full messages.
This will cause the "The connection to the server has been lost!" message. Usually during a zone change.
This will cause you to not be able to log into your most played characters on the most played servers for some unknown reason. Probably to do with cache though.
server hop 9 could be this server, this is the line that is timing out.
0.ge-7-2-0.XL3.BOS4.ALTER.NET [152.63.5.182]
This is the same as I had last night.
So what you're really saying is, you have NO FRIGGING CLUE HOW TO RUN A GAME.
Soooooooooo, after getting off the phone with Customer Support:
Turbine's official response to the "Server Full" is that it's my provider that's preventing me from connecting/staying connected to the server. I'm a time warner cable ISP customer..
For those of you who are not familiar with what this means, it means that apparently they can't even communicate with their own bloody ISP servers.
How is it MY fault that your VERY OWN ISP and game cant communicate with each other?
Hernando Cordez is in Brazil
Quote:
Originally Posted by
Fedora1
Moomoo, I hope things work out. I don't think you are in the minority, it affected several of my characters last week. Here is the thread I mentioned:
https://www.ddo.com/forums/showthrea...Routing-Issues
HC - wow those are long reply times. I was in-game this morning for about 30 minutes (5AM-5:30AM EST) with no issues. Won't be able to try again unitl about 6PM tonight.
Or somewhere down south of the equator I think.