Author Message

Qlander

Rank 1
Joined
24 Mar 2008
Posts
349
Location
Australia
PostedApr 26, 2012 10:08 pm

DC Issues 26 April'12

More of the same thing, mass server DC (many players just got disconnected in game). Shaiya sits on IP 174.142.118.118
-------------------
>ping 174.142.118.118 -t

Pinging 174.142.118.118 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 174.142.118.118: bytes=32 time=282ms TTL=103
Reply from 174.142.118.118: bytes=32 time=282ms TTL=103
Reply from 174.142.118.118: bytes=32 time=282ms TTL=103

Ping statistics for 174.142.118.118:
Packets: Sent = 23, Received = 3, Lost = 20 (86% loss),
Approximate round trip times in milli-seconds:
Minimum = 282ms, Maximum = 282ms, Average = 282ms
-------------------
Again, local is fine:
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64

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


Display posts from previous:   Sort by: