UTV Broadband ping times very Bad

zoom_cool

Hi Guys

Any body experience problems with UTV broadband ping times very bad and about 15% drop out rate

Pinging boards.ie [89.234.66.108] with 32 bytes of data:
Reply from 89.234.66.108: bytes=32 time=1278ms TTL=54
Reply from 89.234.66.108: bytes=32 time=1314ms TTL=54
Reply from 89.234.66.108: bytes=32 time=1326ms TTL=54
Reply from 89.234.66.108: bytes=32 time=1384ms TTL=54
Reply from 89.234.66.108: bytes=32 time=1429ms TTL=54
Reply from 89.234.66.108: bytes=32 time=1395ms TTL=54
Reply from 89.234.66.108: bytes=32 time=1439ms TTL=54

Ping statistics for 89.234.66.108:
Packets: Sent = 7, Received = 7, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1278ms, Maximum = 1439ms, Average = 1366ms

to this in the space of a minute


Pinging boards.ie [89.234.66.108] with 32 bytes of data:
Reply from 89.234.66.108: bytes=32 time=23ms TTL=54
Reply from 89.234.66.108: bytes=32 time=19ms TTL=54
Reply from 89.234.66.108: bytes=32 time=30ms TTL=54

Ping statistics for 89.234.66.108:
Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 19ms, Maximum = 30ms, Average = 24ms

zoom_cool

Just to show you how bad the packet drops are

Pinging boards.ie [89.234.66.108] with 32 bytes of data:
Reply from 89.234.66.108: bytes=32 time=32ms TTL=54
Reply from 89.234.66.108: bytes=32 time=20ms TTL=54

Ping statistics for 89.234.66.108:
Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 20ms, Maximum = 32ms, Average = 26ms
Control-C
^C
C:\WINDOWS\System32>ping boards.ie -t

Pinging boards.ie [89.234.66.107] with 32 bytes of data:
Reply from 89.234.66.107: bytes=32 time=1040ms TTL=54
Reply from 89.234.66.107: bytes=32 time=1206ms TTL=54
Reply from 89.234.66.107: bytes=32 time=1288ms TTL=54
Reply from 89.234.66.107: bytes=32 time=1084ms TTL=54
Request timed out.
Reply from 89.234.66.107: bytes=32 time=1211ms TTL=54
Reply from 89.234.66.107: bytes=32 time=1305ms TTL=54
Reply from 89.234.66.107: bytes=32 time=1401ms TTL=54
Reply from 89.234.66.107: bytes=32 time=1410ms TTL=54
Request timed out.
Reply from 89.234.66.107: bytes=32 time=1159ms TTL=54
Reply from 89.234.66.107: bytes=32 time=1320ms TTL=54
Reply from 89.234.66.107: bytes=32 time=1281ms TTL=54
Reply from 89.234.66.107: bytes=32 time=1360ms TTL=54
Reply from 89.234.66.107: bytes=32 time=1265ms TTL=54
Reply from 89.234.66.107: bytes=32 time=1329ms TTL=54
Reply from 89.234.66.107: bytes=32 time=1197ms TTL=54
Request timed out.
Reply from 89.234.66.107: bytes=32 time=1362ms TTL=54
Reply from 89.234.66.107: bytes=32 time=1263ms TTL=54
Request timed out.
Reply from 89.234.66.107: bytes=32 time=1292ms TTL=54
Reply from 89.234.66.107: bytes=32 time=1222ms TTL=54
Reply from 89.234.66.107: bytes=32 time=1267ms TTL=54
Request timed out.
Request timed out.
Request timed out.
Reply from 89.234.66.107: bytes=32 time=1169ms TTL=54
Request timed out.
Request timed out.
Reply from 89.234.66.107: bytes=32 time=1297ms TTL=54
Reply from 89.234.66.107: bytes=32 time=1393ms TTL=54
Reply from 89.234.66.107: bytes=32 time=1294ms TTL=54
Reply from 89.234.66.107: bytes=32 time=1242ms TTL=54
Reply from 89.234.66.107: bytes=32 time=1324ms TTL=54
Reply from 89.234.66.107: bytes=32 time=1269ms TTL=54
Request timed out.
Reply from 89.234.66.107: bytes=32 time=1340ms TTL=54
Reply from 89.234.66.107: bytes=32 time=1245ms TTL=54
Reply from 89.234.66.107: bytes=32 time=1262ms TTL=54
Reply from 89.234.66.107: bytes=32 time=1250ms TTL=54
Reply from 89.234.66.107: bytes=32 time=1241ms TTL=54
Reply from 89.234.66.107: bytes=32 time=1069ms TTL=54
Reply from 89.234.66.107: bytes=32 time=1182ms TTL=54
Request timed out.
Reply from 89.234.66.107: bytes=32 time=1363ms TTL=54
Reply from 89.234.66.107: bytes=32 time=1235ms TTL=54
Reply from 89.234.66.107: bytes=32 time=1384ms TTL=54
Reply from 89.234.66.107: bytes=32 time=1251ms TTL=54
Request timed out.
Request timed out.
Reply from 89.234.66.107: bytes=32 time=1412ms TTL=54
Request timed out.
Reply from 89.234.66.107: bytes=32 time=1091ms TTL=54
Reply from 89.234.66.107: bytes=32 time=1223ms TTL=54
Reply from 89.234.66.107: bytes=32 time=1199ms TTL=54
Reply from 89.234.66.107: bytes=32 time=811ms TTL=54
Reply from 89.234.66.107: bytes=32 time=827ms TTL=54
Reply from 89.234.66.107: bytes=32 time=814ms TTL=54
Reply from 89.234.66.107: bytes=32 time=710ms TTL=54
Reply from 89.234.66.107: bytes=32 time=438ms TTL=54
Reply from 89.234.66.107: bytes=32 time=591ms TTL=54
Reply from 89.234.66.107: bytes=32 time=682ms TTL=54
Reply from 89.234.66.107: bytes=32 time=366ms TTL=54
Reply from 89.234.66.107: bytes=32 time=15ms TTL=54

Ping statistics for 89.234.66.107:
Packets: Sent = 65, Received = 51, Lost = 14 (21% loss),
Approximate round trip times in milli-seconds:
Minimum = 15ms, Maximum = 1412ms, Average = 1142ms

Xcellor

Plug directly into the router with cable. Check if same result. Better still if you can run a ping command from the router itself try that. Could be interference over wireless.

If that gives same result get on the phone to U.TV. Most likely they won't be able to help you I struggled with really bad packet loss for about 6 months, then one day it just fixed itself.

zoom_cool

I did test from Router still the same if they dont resolve I will be moving.