Duno what those nuts doing la... started beginning this week.
Symptoms same as you guys - stable from 12am - late mornings...
Ping to DNS server intermittent time out lost packet!
IP Range: 218.111.*.*
Location: Farlim, Penang
Package: 4MB Combo
C:\Users\-removed->ping 202.188.0.133 -n 30
Pinging 202.188.0.133 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 202.188.0.133: bytes=32 time=14ms TTL=248
Reply from 202.188.0.133: bytes=32 time=13ms TTL=248
Reply from 202.188.0.133: bytes=32 time=13ms TTL=248
Reply from 202.188.0.133: bytes=32 time=14ms TTL=248
Reply from 202.188.0.133: bytes=32 time=14ms TTL=248
Reply from 202.188.0.133: bytes=32 time=31ms TTL=248
Reply from 202.188.0.133: bytes=32 time=24ms TTL=248
Reply from 202.188.0.133: bytes=32 time=14ms TTL=248
Reply from 202.188.0.133: bytes=32 time=13ms TTL=248
Reply from 202.188.0.133: bytes=32 time=13ms TTL=248
Reply from 202.188.0.133: bytes=32 time=14ms TTL=248
Reply from 202.188.0.133: bytes=32 time=13ms TTL=248
Reply from 202.188.0.133: bytes=32 time=34ms TTL=248
Reply from 202.188.0.133: bytes=32 time=27ms TTL=248
Reply from 202.188.0.133: bytes=32 time=15ms TTL=248
Reply from 202.188.0.133: bytes=32 time=13ms TTL=248
Reply from 202.188.0.133: bytes=32 time=14ms TTL=248
Reply from 202.188.0.133: bytes=32 time=13ms TTL=248
Reply from 202.188.0.133: bytes=32 time=14ms TTL=248
Reply from 202.188.0.133: bytes=32 time=27ms TTL=248
Reply from 202.188.0.133: bytes=32 time=13ms TTL=248
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 202.188.0.133:
Packets: Sent = 30, Received = 21, Lost = 9 (30% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 34ms, Average = 17ms
The "extreme Screamyx Slowdowns" V4, Edisi :Extreme International Slowdowns
May 24 2009, 02:27 PM
Quote
0.0381sec
0.51
7 queries
GZIP Disabled