![]() ![]() ![]() |
|
Ragic: Managed to raid tonight for the first time in 2 weeks :) I'm happy
PC: 3.3ghz Core i5-2500, 8gb DDR3, ATI Radeon 5850, 27" QHD IPS Monitor
Mobile Phone: iPhone 5 32gb Graphite.
System: For the first night in a while i have had bad pings:
Pinging telecom.co.nz [146.171.18.242] with 32 bytes of data:
Reply from 146.171.18.242: bytes=32 time=863ms TTL=121
Reply from 146.171.18.242: bytes=32 time=525ms TTL=121
Reply from 146.171.18.242: bytes=32 time=454ms TTL=121
Reply from 146.171.18.242: bytes=32 time=542ms TTL=121
Ping statistics for 146.171.18.242:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 454ms, Maximum = 863ms, Average = 596ms
So if anything the solution to fix it has only made the problem bigger
Sheagae:System: For the first night in a while i have had bad pings:
Pinging telecom.co.nz [146.171.18.242] with 32 bytes of data:
Reply from 146.171.18.242: bytes=32 time=863ms TTL=121
Reply from 146.171.18.242: bytes=32 time=525ms TTL=121
Reply from 146.171.18.242: bytes=32 time=454ms TTL=121
Reply from 146.171.18.242: bytes=32 time=542ms TTL=121
Ping statistics for 146.171.18.242:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 454ms, Maximum = 863ms, Average = 596ms
So if anything the solution to fix it has only made the problem bigger
You sound suprised? Why would you be suprised??
PC: 3.3ghz Core i5-2500, 8gb DDR3, ATI Radeon 5850, 27" QHD IPS Monitor
Mobile Phone: iPhone 5 32gb Graphite.
System: For the first night in a while i have had bad pings:
Pinging telecom.co.nz [146.171.18.242] with 32 bytes of data:
Reply from 146.171.18.242: bytes=32 time=863ms TTL=121
Reply from 146.171.18.242: bytes=32 time=525ms TTL=121
Reply from 146.171.18.242: bytes=32 time=454ms TTL=121
Reply from 146.171.18.242: bytes=32 time=542ms TTL=121
Ping statistics for 146.171.18.242:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 454ms, Maximum = 863ms, Average = 596ms
So if anything the solution to fix it has only made the problem bigger
WallySimmonds: Still pretty bad tonight. Got a constant ping going to bbc.com
Reply from 212.58.224.138: bytes=32 time=345ms TTL=110
Reply from 212.58.224.138: bytes=32 time=348ms TTL=110
Request timed out.
Reply from 212.58.224.138: bytes=32 time=344ms TTL=110
Request timed out.
Reply from 212.58.224.138: bytes=32 time=345ms TTL=110
Request timed out.
Reply from 212.58.224.138: bytes=32 time=344ms TTL=110
Reply from 212.58.224.138: bytes=32 time=349ms TTL=110
Request timed out.
Reply from 212.58.224.138: bytes=32 time=344ms TTL=110
Request timed out.
Reply from 212.58.224.138: bytes=32 time=344ms TTL=110
Reply from 212.58.224.138: bytes=32 time=345ms TTL=110
Reply from 212.58.224.138: bytes=32 time=345ms TTL=110
Request timed out.
Reply from 212.58.224.138: bytes=32 time=345ms TTL=110
And anywhere international is very similar.
I'm a geek, a gamer, a dad and an IT Professional. I have a full rack home lab, size 15 feet, an epic beard and Asperger's. I'm a bit of a Cypherpunk, who believes information wants to be free and the Net interprets censorship as damage and routes around it.
|
![]() ![]() ![]() |