Overnight changes to connection?

[Nopedont]

Hello,

Sorry to pester, yesterday 4/20. I ran around all day with the massive fights and holds with zero connection issues. Today 4/21 , I cant get into a fight period with even small man to 8 man. Without the center dot of the 3 going full red and getting 30seconds+ worth of delay. I haven't changed anything.

My ping is fine:
Pinging game.eden-daoc.net [142.132.144.167] with 32 bytes of data:
Reply from 142.132.144.167: bytes=32 time=202ms TTL=46
Reply from 142.132.144.167: bytes=32 time=196ms TTL=46
Reply from 142.132.144.167: bytes=32 time=195ms TTL=46
Reply from 142.132.144.167: bytes=32 time=202ms TTL=46

Ping statistics for 142.132.144.167:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 195ms, Maximum = 202ms, Average = 198ms

So I have no idea what is going on and would like some ideas to try and remedy the situation.

[Weck]

Pinging 142.132.144.167 with 32 bytes of data:
Reply from 142.132.144.167: bytes=32 time=167ms TTL=48
Reply from 142.132.144.167: bytes=32 time=167ms TTL=48
Reply from 142.132.144.167: bytes=32 time=167ms TTL=48
Reply from 142.132.144.167: bytes=32 time=167ms TTL=48

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

C:\Users\>ping 142.132.144.167

Pinging 142.132.144.167 with 32 bytes of data:
Reply from 142.132.144.167: bytes=32 time=167ms TTL=48
Reply from 142.132.144.167: bytes=32 time=169ms TTL=48
Reply from 142.132.144.167: bytes=32 time=167ms TTL=48
Reply from 142.132.144.167: bytes=32 time=168ms TTL=48

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

C:\Users\>ping 142.132.144.167

Pinging 142.132.144.167 with 32 bytes of data:
Request timed out.
Reply from 142.132.144.167: bytes=32 time=167ms TTL=48
Request timed out.
Reply from 142.132.144.167: bytes=32 time=167ms TTL=48

Ping statistics for 142.132.144.167:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 167ms, Maximum = 167ms, Average = 167ms

C:\Users\>ping 142.132.144.167

Pinging 142.132.144.167 with 32 bytes of data:
Reply from 142.132.144.167: bytes=32 time=167ms TTL=48
Reply from 142.132.144.167: bytes=32 time=167ms TTL=48
Reply from 142.132.144.167: bytes=32 time=169ms TTL=48
Reply from 142.132.144.167: bytes=32 time=172ms TTL=48

Ping statistics for 142.132.144.167:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 167ms, Maximum = 172ms, Average = 168ms

C:\Users\>ping 142.132.144.167

Pinging 142.132.144.167 with 32 bytes of data:
Reply from 142.132.144.167: bytes=32 time=167ms TTL=48
Reply from 142.132.144.167: bytes=32 time=167ms TTL=48
Reply from 142.132.144.167: bytes=32 time=169ms TTL=48
Reply from 142.132.144.167: bytes=32 time=167ms TTL=48

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

C:\Users\>ping 142.132.144.167

Pinging 142.132.144.167 with 32 bytes of data:
Reply from 142.132.144.167: bytes=32 time=168ms TTL=48
Reply from 142.132.144.167: bytes=32 time=168ms TTL=48
Reply from 142.132.144.167: bytes=32 time=167ms TTL=48
Reply from 142.132.144.167: bytes=32 time=167ms TTL=48

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

C:\Users\>ping 142.132.144.167

Pinging 142.132.144.167 with 32 bytes of data:
Request timed out.
Reply from 142.132.144.167: bytes=32 time=167ms TTL=48
Request timed out.
Reply from 142.132.144.167: bytes=32 time=168ms TTL=48

Ping statistics for 142.132.144.167:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 167ms, Maximum = 168ms, Average = 167ms

I have some loss but not all the time. but sounds like same problem.

[themountaindewd]

I'm also having trouble connecting tonight -- even though it's been working flawlessly all of Season 3.

If you don't mind me asking, who's your ISP (I'm with AT&T)?

[midlyfe]

Hi trying to help a friend and guildie who may have ran into the same problem. When you perform a "tracert" what are your results. Do you get quite a few time outs? Also if you dont mind me asking who is your ISP provider? Are you in North America?

[Weck]

I'm also having trouble connecting tonight -- even though it's been working flawlessly all of Season 3.

If you don't mind me asking, who's your ISP (I'm with AT&T)?

AT&T NA

[themountaindewd]

I'm also having trouble connecting tonight -- even though it's been working flawlessly all of Season 3.

If you don't mind me asking, who's your ISP (I'm with AT&T)?

AT&T NA

Are you in the Midwest? Like possibly Missouri (lol)? Maybe it's a localized issue.

[Nopedont]

I'm also having trouble connecting tonight -- even though it's been working flawlessly all of Season 3.

If you don't mind me asking, who's your ISP (I'm with AT&T)?

AT&T NA

Are you in the Midwest? Like possibly Missouri (lol)? Maybe it's a localized issue.

Tex/Ok boarder... Vexus Fiber. On Tracert there was only a couple of non reponses the last couple of days. Yet it still made it there eventualy. haha