I suppose this is not the biggest hickup of all time, but since the BT seems to work again, latency have noticably increased from mid 60ms to 200+ms during the day.
Pinging saix.net [196.25.1.200] with 32 bytes of data:
Reply from 196.25.1.200: bytes=32 time=216ms TTL=246
Reply from 196.25.1.200: bytes=32 time=198ms TTL=246
Reply from 196.25.1.200: bytes=32 time=217ms TTL=246
Reply from 196.25.1.200: bytes=32 time=232ms TTL=246
Ping statistics for 196.25.1.200:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 198ms, Maximum = 232ms, Average = 215ms
Its better in regards to the 700ms of pre-torrent shutdown, but maybe only few users know BT is working, so that would explain only the marginal ping increase?
Damn, uunet plz work on a final solution and no more temp solutions.
I trust you can do it tho, I love doing business with uunet even with the hickups.
Pinging saix.net [196.25.1.200] with 32 bytes of data:
Reply from 196.25.1.200: bytes=32 time=216ms TTL=246
Reply from 196.25.1.200: bytes=32 time=198ms TTL=246
Reply from 196.25.1.200: bytes=32 time=217ms TTL=246
Reply from 196.25.1.200: bytes=32 time=232ms TTL=246
Ping statistics for 196.25.1.200:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 198ms, Maximum = 232ms, Average = 215ms
Its better in regards to the 700ms of pre-torrent shutdown, but maybe only few users know BT is working, so that would explain only the marginal ping increase?
Damn, uunet plz work on a final solution and no more temp solutions.
I trust you can do it tho, I love doing business with uunet even with the hickups.