U.TV Internet pings - spiking / timeouts

Xcellor

Just wondering if anyone else on UTV is experiencing up and down pings the last few days...

C:\Users\xxx>ping www.boards.ie -t

Pinging loadbalancer.boards.ie [89.234.66.107] with 32 bytes of data:
Reply from 89.234.66.107: bytes=32 time=37ms TTL=55
Reply from 89.234.66.107: bytes=32 time=79ms TTL=55
Reply from 89.234.66.107: bytes=32 time=33ms TTL=55
Reply from 89.234.66.107: bytes=32 time=46ms TTL=55
Reply from 89.234.66.107: bytes=32 time=74ms TTL=55
Request timed out.
Reply from 89.234.66.107: bytes=32 time=65ms TTL=55
Reply from 89.234.66.107: bytes=32 time=84ms TTL=55
Reply from 89.234.66.107: bytes=32 time=96ms TTL=55



This is a sample of what is it like presently.... usually I get 30ms consistently. Now the jitter is all over the place and packet loss aswell. Can't play Halo

zoom_cool

me getting the same mate I have rang them and they went through a whole lot of test I even changed my router and same problem I am getting approx 30% packet loss I have to contact them again tomorrow I will let u know outcome its good to know not my line :mad:

zoom_cool

If you could ring them tommorrow as well that would be great the more people that complain the better

zoom_cool

Pinging loadbalancer.boards.ie [89.234.66.107] with 32 bytes of data:
Reply from 89.234.66.107: bytes=32 time=27ms TTL=55
Request timed out.
Reply from 89.234.66.107: bytes=32 time=26ms TTL=55
Reply from 89.234.66.107: bytes=32 time=22ms TTL=55
Reply from 89.234.66.107: bytes=32 time=19ms TTL=55
Request timed out.
Request timed out.
Reply from 89.234.66.107: bytes=32 time=28ms TTL=55
Reply from 89.234.66.107: bytes=32 time=30ms TTL=55
Request timed out.
Reply from 89.234.66.107: bytes=32 time=29ms TTL=55
Reply from 89.234.66.107: bytes=32 time=30ms TTL=55
Reply from 89.234.66.107: bytes=32 time=29ms TTL=55
Reply from 89.234.66.107: bytes=32 time=30ms TTL=55
Reply from 89.234.66.107: bytes=32 time=30ms TTL=55
Reply from 89.234.66.107: bytes=32 time=31ms TTL=55
Request timed out.
Reply from 89.234.66.107: bytes=32 time=32ms TTL=55

Ping statistics for 89.234.66.107:
Packets: Sent = 18, Received = 13, Lost = 5 (27% loss),
Approximate round trip times in milli-seconds:
Minimum = 19ms, Maximum = 32ms, Average = 27ms

Now that is Bad

Xcellor

zoom_cool wrote: »

Pinging loadbalancer.boards.ie [89.234.66.107] with 32 bytes of data:
Reply from 89.234.66.107: bytes=32 time=27ms TTL=55
Request timed out.
Reply from 89.234.66.107: bytes=32 time=26ms TTL=55
Reply from 89.234.66.107: bytes=32 time=22ms TTL=55
Reply from 89.234.66.107: bytes=32 time=19ms TTL=55
Request timed out.
Request timed out.
Reply from 89.234.66.107: bytes=32 time=28ms TTL=55
Reply from 89.234.66.107: bytes=32 time=30ms TTL=55
Request timed out.
Reply from 89.234.66.107: bytes=32 time=29ms TTL=55
Reply from 89.234.66.107: bytes=32 time=30ms TTL=55
Reply from 89.234.66.107: bytes=32 time=29ms TTL=55
Reply from 89.234.66.107: bytes=32 time=30ms TTL=55
Reply from 89.234.66.107: bytes=32 time=30ms TTL=55
Reply from 89.234.66.107: bytes=32 time=31ms TTL=55
Request timed out.
Reply from 89.234.66.107: bytes=32 time=32ms TTL=55

Ping statistics for 89.234.66.107:
Packets: Sent = 18, Received = 13, Lost = 5 (27% loss),
Approximate round trip times in milli-seconds:
Minimum = 19ms, Maximum = 32ms, Average = 27ms

Now that is Bad

I rang them earlier and they said "I was the only one" and they suggested increasing my interleaving!!! (because everyone knows this makes the ping much better,,,:rolleyes: ).

At the moment I am 7-10% packet loss which is hopeless. I sent them an email to complain as well. If anyone else from UTV is suffering the same problem please report...

Cheers,
X

zoom_cool

The f**ckers they told me the same I was the only one to have issue it looks like a bigger issue the guys on vodafone have same issue something really screwed :mad:

stuff.hunter

no problems at all here:

C:\Users\Kris>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=50ms TTL=55
Reply from 89.234.66.107: bytes=32 time=49ms TTL=55
Reply from 89.234.66.107: bytes=32 time=49ms TTL=55
Reply from 89.234.66.107: bytes=32 time=53ms TTL=55
Reply from 89.234.66.107: bytes=32 time=52ms TTL=55
Reply from 89.234.66.107: bytes=32 time=53ms TTL=55
Reply from 89.234.66.107: bytes=32 time=54ms TTL=55
Reply from 89.234.66.107: bytes=32 time=51ms TTL=55
Reply from 89.234.66.107: bytes=32 time=53ms TTL=55
Reply from 89.234.66.107: bytes=32 time=47ms TTL=55
Reply from 89.234.66.107: bytes=32 time=47ms TTL=55
Reply from 89.234.66.107: bytes=32 time=53ms TTL=55
Reply from 89.234.66.107: bytes=32 time=55ms TTL=55
Reply from 89.234.66.107: bytes=32 time=53ms TTL=55
Reply from 89.234.66.107: bytes=32 time=50ms TTL=55
Reply from 89.234.66.107: bytes=32 time=50ms TTL=55
Reply from 89.234.66.107: bytes=32 time=53ms TTL=55
Reply from 89.234.66.107: bytes=32 time=53ms TTL=55
Reply from 89.234.66.107: bytes=32 time=52ms TTL=55
Reply from 89.234.66.107: bytes=32 time=52ms TTL=55
Reply from 89.234.66.107: bytes=32 time=52ms TTL=55
Reply from 89.234.66.107: bytes=32 time=53ms TTL=55
Reply from 89.234.66.107: bytes=32 time=52ms TTL=55
Reply from 89.234.66.107: bytes=32 time=53ms TTL=55
Reply from 89.234.66.107: bytes=32 time=53ms TTL=55
Reply from 89.234.66.107: bytes=32 time=49ms TTL=55
Reply from 89.234.66.107: bytes=32 time=55ms TTL=55
Ping statistics for 89.234.66.107:
Packets: Sent = 27, Received = 27, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 47ms, Maximum = 55ms, Average = 51ms
Control-C
^C
C:\Users\Kris>

...so may be an Eircom line fault

Xcellor

Perhaps it would be helpful to mention our locations in case its a regional thing.

Longford, Newtownforbes exchange.

stuff.hunter

Dublin 7, Phibsborough exchange here

zoom_cool

Kells Co. Meath Exchange

Xcellor

Things improved for me from around 2am now the following:

PING 89.234.66.107 (89.234.66.107): 56 data bytes
64 bytes from 89.234.66.107: icmp_seq=0 ttl=56 time=29.5 ms
64 bytes from 89.234.66.107: icmp_seq=1 ttl=56 time=29.6 ms
64 bytes from 89.234.66.107: icmp_seq=2 ttl=56 time=30.1 ms
64 bytes from 89.234.66.107: icmp_seq=3 ttl=56 time=29.9 ms

--- 89.234.66.107 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 29.5/29.7/30.1 ms


Hopefully it will stay that way............

X

zoom_cool

Thing back up for me as well I still rang them to ask what went wrong and they dont know they said keep monitoring and if it happens again ring them so they can raise issue with eircom.

Xcellor

Seems bad again this evening.....

Ping statistics for 89.234.66.107:
Packets: Sent = 179, Received = 174, Lost = 5 (2% loss),
Approximate round trip times in milli-seconds:
Minimum = 29ms, Maximum = 155ms, Average = 53ms

zoom_cool

Xcellor wrote: »

Seems bad again this evening.....

Ping statistics for 89.234.66.107:
Packets: Sent = 179, Received = 174, Lost = 5 (2% loss),
Approximate round trip times in milli-seconds:
Minimum = 29ms, Maximum = 155ms, Average = 53ms

Mine ok this evening so far

Reply from 89.234.66.107: bytes=32 time=26ms TTL=55
Reply from 89.234.66.107: bytes=32 time=21ms TTL=55
Reply from 89.234.66.107: bytes=32 time=27ms TTL=55
Reply from 89.234.66.107: bytes=32 time=26ms TTL=55
Reply from 89.234.66.107: bytes=32 time=18ms TTL=55
Reply from 89.234.66.107: bytes=32 time=22ms TTL=55
Reply from 89.234.66.107: bytes=32 time=21ms TTL=55
Reply from 89.234.66.107: bytes=32 time=24ms TTL=55
Reply from 89.234.66.107: bytes=32 time=25ms TTL=55
Reply from 89.234.66.107: bytes=32 time=23ms TTL=55
Reply from 89.234.66.107: bytes=32 time=22ms TTL=55
Reply from 89.234.66.107: bytes=32 time=22ms TTL=55
Reply from 89.234.66.107: bytes=32 time=33ms TTL=55
Reply from 89.234.66.107: bytes=32 time=31ms TTL=55
Reply from 89.234.66.107: bytes=32 time=33ms TTL=55
Reply from 89.234.66.107: bytes=32 time=36ms TTL=55
Reply from 89.234.66.107: bytes=32 time=37ms TTL=55
Reply from 89.234.66.107: bytes=32 time=36ms TTL=55
Reply from 89.234.66.107: bytes=32 time=37ms TTL=55
Reply from 89.234.66.107: bytes=32 time=35ms TTL=55
Reply from 89.234.66.107: bytes=32 time=85ms TTL=55
Reply from 89.234.66.107: bytes=32 time=68ms TTL=55
Reply from 89.234.66.107: bytes=32 time=29ms TTL=55
Reply from 89.234.66.107: bytes=32 time=29ms TTL=55
Reply from 89.234.66.107: bytes=32 time=30ms TTL=55
Reply from 89.234.66.107: bytes=32 time=29ms TTL=55
Reply from 89.234.66.107: bytes=32 time=29ms TTL=55
Reply from 89.234.66.107: bytes=32 time=29ms TTL=55
Reply from 89.234.66.107: bytes=32 time=31ms TTL=55
Reply from 89.234.66.107: bytes=32 time=34ms TTL=55
Reply from 89.234.66.107: bytes=32 time=28ms TTL=55

Ping statistics for 89.234.66.107:
Packets: Sent = 77, Received = 77, Lost = 0 (0% los
Approximate round trip times in milli-seconds:
Minimum = 17ms, Maximum = 98ms, Average = 29ms

Xcellor

zoom_cool wrote: »

Mine ok this evening so far

Reply from 89.234.66.107: bytes=32 time=26ms TTL=55
Reply from 89.234.66.107: bytes=32 time=21ms TTL=55
Reply from 89.234.66.107: bytes=32 time=27ms TTL=55
Reply from 89.234.66.107: bytes=32 time=26ms TTL=55
Reply from 89.234.66.107: bytes=32 time=18ms TTL=55
Reply from 89.234.66.107: bytes=32 time=22ms TTL=55
Reply from 89.234.66.107: bytes=32 time=21ms TTL=55
Reply from 89.234.66.107: bytes=32 time=24ms TTL=55
Reply from 89.234.66.107: bytes=32 time=25ms TTL=55
Reply from 89.234.66.107: bytes=32 time=23ms TTL=55
Reply from 89.234.66.107: bytes=32 time=22ms TTL=55
Reply from 89.234.66.107: bytes=32 time=22ms TTL=55
Reply from 89.234.66.107: bytes=32 time=33ms TTL=55
Reply from 89.234.66.107: bytes=32 time=31ms TTL=55
Reply from 89.234.66.107: bytes=32 time=33ms TTL=55
Reply from 89.234.66.107: bytes=32 time=36ms TTL=55
Reply from 89.234.66.107: bytes=32 time=37ms TTL=55
Reply from 89.234.66.107: bytes=32 time=36ms TTL=55
Reply from 89.234.66.107: bytes=32 time=37ms TTL=55
Reply from 89.234.66.107: bytes=32 time=35ms TTL=55
Reply from 89.234.66.107: bytes=32 time=85ms TTL=55
Reply from 89.234.66.107: bytes=32 time=68ms TTL=55
Reply from 89.234.66.107: bytes=32 time=29ms TTL=55
Reply from 89.234.66.107: bytes=32 time=29ms TTL=55
Reply from 89.234.66.107: bytes=32 time=30ms TTL=55
Reply from 89.234.66.107: bytes=32 time=29ms TTL=55
Reply from 89.234.66.107: bytes=32 time=29ms TTL=55
Reply from 89.234.66.107: bytes=32 time=29ms TTL=55
Reply from 89.234.66.107: bytes=32 time=31ms TTL=55
Reply from 89.234.66.107: bytes=32 time=34ms TTL=55
Reply from 89.234.66.107: bytes=32 time=28ms TTL=55

Ping statistics for 89.234.66.107:
Packets: Sent = 77, Received = 77, Lost = 0 (0% los
Approximate round trip times in milli-seconds:
Minimum = 17ms, Maximum = 98ms, Average = 29ms

The jitter on that ping is not great. Try www.pingtest.net and let me know what you get.

stuff.hunter

just got:
Pinging boards.ie [89.234.66.107] with 32 bytes of data:
Reply from 89.234.66.107: bytes=32 time=52ms TTL=55
Reply from 89.234.66.107: bytes=32 time=51ms TTL=55
Reply from 89.234.66.107: bytes=32 time=46ms TTL=55
Reply from 89.234.66.107: bytes=32 time=44ms TTL=55
Reply from 89.234.66.107: bytes=32 time=44ms TTL=55
Reply from 89.234.66.107: bytes=32 time=49ms TTL=55
Reply from 89.234.66.107: bytes=32 time=50ms TTL=55
Reply from 89.234.66.107: bytes=32 time=59ms TTL=55
Reply from 89.234.66.107: bytes=32 time=54ms TTL=55
Reply from 89.234.66.107: bytes=32 time=47ms TTL=55
Reply from 89.234.66.107: bytes=32 time=54ms TTL=55
Reply from 89.234.66.107: bytes=32 time=56ms TTL=55
Reply from 89.234.66.107: bytes=32 time=46ms TTL=55
Reply from 89.234.66.107: bytes=32 time=44ms TTL=55
Reply from 89.234.66.107: bytes=32 time=54ms TTL=55
Reply from 89.234.66.107: bytes=32 time=48ms TTL=55
Reply from 89.234.66.107: bytes=32 time=46ms TTL=55
Reply from 89.234.66.107: bytes=32 time=52ms TTL=55
Reply from 89.234.66.107: bytes=32 time=45ms TTL=55
Reply from 89.234.66.107: bytes=32 time=51ms TTL=55
Reply from 89.234.66.107: bytes=32 time=53ms TTL=55
Reply from 89.234.66.107: bytes=32 time=47ms TTL=55
Reply from 89.234.66.107: bytes=32 time=54ms TTL=55
Reply from 89.234.66.107: bytes=32 time=46ms TTL=55
Reply from 89.234.66.107: bytes=32 time=51ms TTL=55
Reply from 89.234.66.107: bytes=32 time=60ms TTL=55
Reply from 89.234.66.107: bytes=32 time=58ms TTL=55
Reply from 89.234.66.107: bytes=32 time=60ms TTL=55
Reply from 89.234.66.107: bytes=32 time=56ms TTL=55
Reply from 89.234.66.107: bytes=32 time=57ms TTL=55
Reply from 89.234.66.107: bytes=32 time=59ms TTL=55
Ping statistics for 89.234.66.107:
Packets: Sent = 31, Received = 31, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 44ms, Maximum = 60ms, Average = 51ms
Control-C

...no problems with pocket loss whatsoever but ping a bit up...weather or what

Xcellor

Unfortunately problem persists.

Can UTV customers please post their ping results here and give their locations? Even if you don't think you have a problem.

As well as bad pings you maybe experiencing pages not loading, or parts not loading and having to refresh multiple times. Steaming video content will be breaking up, especially if its in higher definition.

Any help that can be given would be great.

Goto 'cmd'
and type

ping www.boards.ie -n 20

and post the results (20 pings gives a better idea of jitter)

Thanks,
X

zoom_cool

Today not that good


:mad:

Shyboy

C:\Users\Jason>ping www.boards.ie -n 20

Pinging loadbalancer.boards.ie [89.234.66.107] with 32 bytes of data:
Reply from 89.234.66.107: bytes=32 time=55ms TTL=55
Reply from 89.234.66.107: bytes=32 time=53ms TTL=55
Reply from 89.234.66.107: bytes=32 time=55ms TTL=55
Reply from 89.234.66.107: bytes=32 time=54ms TTL=55
Reply from 89.234.66.107: bytes=32 time=55ms TTL=55
Reply from 89.234.66.107: bytes=32 time=53ms TTL=55
Reply from 89.234.66.107: bytes=32 time=55ms TTL=55
Reply from 89.234.66.107: bytes=32 time=55ms TTL=55
Reply from 89.234.66.107: bytes=32 time=55ms TTL=55
Reply from 89.234.66.107: bytes=32 time=54ms TTL=55
Reply from 89.234.66.107: bytes=32 time=55ms TTL=55
Reply from 89.234.66.107: bytes=32 time=54ms TTL=55
Reply from 89.234.66.107: bytes=32 time=56ms TTL=55
Reply from 89.234.66.107: bytes=32 time=54ms TTL=55
Reply from 89.234.66.107: bytes=32 time=55ms TTL=55
Reply from 89.234.66.107: bytes=32 time=64ms TTL=55
Reply from 89.234.66.107: bytes=32 time=55ms TTL=55
Reply from 89.234.66.107: bytes=32 time=54ms TTL=55
Reply from 89.234.66.107: bytes=32 time=56ms TTL=55
Reply from 89.234.66.107: bytes=32 time=54ms TTL=55

Ping statistics for 89.234.66.107:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 53ms, Maximum = 64ms, Average = 55ms

I am Turloughmore, County Galway.

I have noticed that I have had to reload pages so many times lately and Youtube etc, has been so slow. :mad:

Best Regards
Jason

Xcellor

Can anyone with poor performance please report it... The more reports the bigger the case.

One guy in the middle of Longford wont fix much

byte

ping www.boards.ie -n 20

Pinging loadbalancer.boards.ie [89.234.66.107] with 32 bytes of data:
Reply from 89.234.66.107: bytes=32 time=37ms TTL=55
Reply from 89.234.66.107: bytes=32 time=46ms TTL=55
Reply from 89.234.66.107: bytes=32 time=37ms TTL=55
Reply from 89.234.66.107: bytes=32 time=36ms TTL=55
Reply from 89.234.66.107: bytes=32 time=43ms TTL=55
Reply from 89.234.66.107: bytes=32 time=37ms TTL=55
Reply from 89.234.66.107: bytes=32 time=37ms TTL=55
Reply from 89.234.66.107: bytes=32 time=37ms TTL=55
Reply from 89.234.66.107: bytes=32 time=37ms TTL=55
Reply from 89.234.66.107: bytes=32 time=38ms TTL=55
Reply from 89.234.66.107: bytes=32 time=36ms TTL=55
Reply from 89.234.66.107: bytes=32 time=37ms TTL=55
Reply from 89.234.66.107: bytes=32 time=37ms TTL=55
Reply from 89.234.66.107: bytes=32 time=37ms TTL=55
Reply from 89.234.66.107: bytes=32 time=44ms TTL=55
Reply from 89.234.66.107: bytes=32 time=94ms TTL=55
Reply from 89.234.66.107: bytes=32 time=74ms TTL=55
Reply from 89.234.66.107: bytes=32 time=58ms TTL=55
Reply from 89.234.66.107: bytes=32 time=49ms TTL=55
Reply from 89.234.66.107: bytes=32 time=49ms TTL=55

Ping statistics for 89.234.66.107:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 36ms, Maximum = 94ms, Average = 45ms




Location: Donegal town.

EDIT: Just retried Pingtest, now have an A.. how reliable is Pingtest really?

Xcellor

byte wrote: »

ping www.boards.ie -n 20

Pinging loadbalancer.boards.ie [89.234.66.107] with 32 bytes of data:
Reply from 89.234.66.107: bytes=32 time=37ms TTL=55
Reply from 89.234.66.107: bytes=32 time=46ms TTL=55
Reply from 89.234.66.107: bytes=32 time=37ms TTL=55
Reply from 89.234.66.107: bytes=32 time=36ms TTL=55
Reply from 89.234.66.107: bytes=32 time=43ms TTL=55
Reply from 89.234.66.107: bytes=32 time=37ms TTL=55
Reply from 89.234.66.107: bytes=32 time=37ms TTL=55
Reply from 89.234.66.107: bytes=32 time=37ms TTL=55
Reply from 89.234.66.107: bytes=32 time=37ms TTL=55
Reply from 89.234.66.107: bytes=32 time=38ms TTL=55
Reply from 89.234.66.107: bytes=32 time=36ms TTL=55
Reply from 89.234.66.107: bytes=32 time=37ms TTL=55
Reply from 89.234.66.107: bytes=32 time=37ms TTL=55
Reply from 89.234.66.107: bytes=32 time=37ms TTL=55
Reply from 89.234.66.107: bytes=32 time=44ms TTL=55
Reply from 89.234.66.107: bytes=32 time=94ms TTL=55
Reply from 89.234.66.107: bytes=32 time=74ms TTL=55
Reply from 89.234.66.107: bytes=32 time=58ms TTL=55
Reply from 89.234.66.107: bytes=32 time=49ms TTL=55
Reply from 89.234.66.107: bytes=32 time=49ms TTL=55

Ping statistics for 89.234.66.107:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 36ms, Maximum = 94ms, Average = 45ms




Location: Donegal town.

EDIT: Just retried Pingtest, now have an A.. how reliable is Pingtest really?

I would suggest you have a problem. Look at the jitter on your ping. You should be getting around 30 mark consistently but you are rarely hitting the same number twice.

The question is not how reliable pingtest is, its how reliable is UTV internet. You are getting different results because your connection is up and down. I would suggest running the command ping www.boards.ie -n 1000 >> c:\yourfolder\results.txt

Let it finish and have a look at the spread. Regardless of the average if the number jumps up and down that indicates ther is a problem. If you get time outs or lost that is even worse.

crownhill

Bit better than last 2 nights but still unstable.Difficulty in loading some web pages. South Co. Sligo

Bytes Source Seq Time Units
64 89.234.66.107 1 70.6 ms
64 89.234.66.107 2 68.9 ms
64 89.234.66.107 3 62.2 ms
64 89.234.66.107 4 60.2 ms
64 89.234.66.107 6 60.2 ms
64 89.234.66.107 7 68.3 ms
64 89.234.66.107 8 66.2 ms
64 89.234.66.107 9 61.3 ms
64 89.234.66.107 11 57.7 ms
64 89.234.66.107 12 59.8 ms
64 89.234.66.107 13 62.9 ms
64 89.234.66.107 14 60.4 ms
64 89.234.66.107 15 72.9 ms
64 89.234.66.107 16 59.6 ms
64 89.234.66.107 17 59.9 ms
64 89.234.66.107 18 57.9 ms
64 89.234.66.107 19 58.4 ms
64 89.234.66.107 20 60.8 ms
64 89.234.66.107 21 62.0 ms
64 89.234.66.107 22 65.7 ms
64 89.234.66.107 23 68.9 ms
64 89.234.66.107 24 61.7 ms
64 89.234.66.107 25 61.9 ms
64 89.234.66.107 26 62.9 ms
64 89.234.66.107 27 59.9 ms
64 89.234.66.107 29 61.0 ms
64 89.234.66.107 30 66.1 ms
64 89.234.66.107 31 65.8 ms
64 89.234.66.107 32 63.9 ms
64 89.234.66.107 33 65.9 ms
64 89.234.66.107 34 57.9 ms
64 89.234.66.107 35 61.4 ms
64 89.234.66.107 36 61.9 ms
64 89.234.66.107 37 56.5 ms
64 89.234.66.107 38 63.0 ms
64 89.234.66.107 39 56.7 ms
64 89.234.66.107 40 62.8 ms
64 89.234.66.107 41 63.3 ms
64 89.234.66.107 42 61.0 ms
64 89.234.66.107 43 64.8 ms
64 89.234.66.107 44 68.4 ms
64 89.234.66.107 45 63.4 ms
64 89.234.66.107 46 69.8 ms
64 89.234.66.107 47 65.9 ms
64 89.234.66.107 48 67.4 ms
64 89.234.66.107 49 61.5 ms
64 89.234.66.107 50 61.2 ms
Time minimum: 56.50 ms
Time average: 63.27 ms
Time maximum: 72.90 ms
Packets transmitted: 50
Packets received: 47
Successful packets: 94%

On tracert
Hop Hostname IP Time 1 Time 2
1 WORKGROUP.local 192.168.1.1 0.143ms \
192.168.1.254 192.168.1.254 1.926ms
192.168.1.254 192.168.1.254 0.751ms
194.46.193.49 194.46.193.49 109.193ms vlan81.rt701.cwt.esat-x.com 193.95.145.34 99.000ms vlan71.rt001.cwt.esat.net 193.95.130.201 95.039ms ge1-0.core002.cwt.esat.net 193.95.129.2 100.965ms
deg-gw-1.rte.ie 193.242.111.42 103.429ms
www.rte.ie 89.207.56.140 97.113ms

deaglan169

been having similar problems past 3 weeks or so here are my results but they seem ok, my exchange is monaghan town im 1 mile from exchange

Pinging loadbalancer.boards.ie [89.234.66.107] with 32 bytes of data:
Reply from 89.234.66.107: bytes=32 time=22ms TTL=55
Reply from 89.234.66.107: bytes=32 time=19ms TTL=55
Reply from 89.234.66.107: bytes=32 time=17ms TTL=55
Reply from 89.234.66.107: bytes=32 time=25ms TTL=55
Reply from 89.234.66.107: bytes=32 time=22ms TTL=55
Reply from 89.234.66.107: bytes=32 time=20ms TTL=55
Reply from 89.234.66.107: bytes=32 time=28ms TTL=55
Reply from 89.234.66.107: bytes=32 time=26ms TTL=55
Reply from 89.234.66.107: bytes=32 time=25ms TTL=55
Reply from 89.234.66.107: bytes=32 time=23ms TTL=55
Reply from 89.234.66.107: bytes=32 time=21ms TTL=55
Reply from 89.234.66.107: bytes=32 time=19ms TTL=55
Reply from 89.234.66.107: bytes=32 time=28ms TTL=55
Reply from 89.234.66.107: bytes=32 time=24ms TTL=55
Reply from 89.234.66.107: bytes=32 time=23ms TTL=55
Reply from 89.234.66.107: bytes=32 time=22ms TTL=55
Reply from 89.234.66.107: bytes=32 time=21ms TTL=55
Reply from 89.234.66.107: bytes=32 time=20ms TTL=55
Reply from 89.234.66.107: bytes=32 time=29ms TTL=55
Reply from 89.234.66.107: bytes=32 time=18ms TTL=55

Ping statistics for 89.234.66.107:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 17ms, Maximum = 29ms, Average = 22ms









im signed up to a 8mb connection before it started acting up i had a constant 7mb connection

Xcellor

So it seems this issue is not at the exchange level but something beyond...

I have yet to see someone post ping results that are consistent and low jitter... 1-5 ms is acceptable but if you can't get this every time on pingtest there is something wrong (providing you are not using up your bandwidth downloading).

Can anyone who is experiencing this issue please log it with UTV. At the moment they are seeing this as isolated and I bet many people are just taking the typical "can't be arsed" and "sure its good enough"

byte

Could it be down to contention if it appears fine in the middle of the night?

deaglan169

i have logged fault with utv, they promised to ring back never did usual story eircom fault, ring eircom utv fault:rolleyes:

zoom_cool

Bad again tonight :mad:

Ringing them again in the morning

Pinging loadbalancer.boards.ie [89.234.66.107] with 32 bytes of data:
Reply from 89.234.66.107: bytes=32 time=43ms TTL=55
Reply from 89.234.66.107: bytes=32 time=45ms TTL=55
Reply from 89.234.66.107: bytes=32 time=39ms TTL=55
Reply from 89.234.66.107: bytes=32 time=35ms TTL=55
Reply from 89.234.66.107: bytes=32 time=43ms TTL=55
Reply from 89.234.66.107: bytes=32 time=51ms TTL=55
Reply from 89.234.66.107: bytes=32 time=40ms TTL=55
Reply from 89.234.66.107: bytes=32 time=44ms TTL=55
Reply from 89.234.66.107: bytes=32 time=39ms TTL=55
Reply from 89.234.66.107: bytes=32 time=41ms TTL=55
Reply from 89.234.66.107: bytes=32 time=45ms TTL=55
Reply from 89.234.66.107: bytes=32 time=55ms TTL=55
Reply from 89.234.66.107: bytes=32 time=44ms TTL=55
Reply from 89.234.66.107: bytes=32 time=42ms TTL=55
Reply from 89.234.66.107: bytes=32 time=108ms TTL=55
Reply from 89.234.66.107: bytes=32 time=75ms TTL=55
Reply from 89.234.66.107: bytes=32 time=38ms TTL=55
Reply from 89.234.66.107: bytes=32 time=44ms TTL=55
Reply from 89.234.66.107: bytes=32 time=39ms TTL=55
Reply from 89.234.66.107: bytes=32 time=38ms TTL=55
Reply from 89.234.66.107: bytes=32 time=43ms TTL=55
Reply from 89.234.66.107: bytes=32 time=44ms TTL=55
Reply from 89.234.66.107: bytes=32 time=52ms TTL=55
Reply from 89.234.66.107: bytes=32 time=49ms TTL=55
Reply from 89.234.66.107: bytes=32 time=58ms TTL=55
Reply from 89.234.66.107: bytes=32 time=51ms TTL=55
Reply from 89.234.66.107: bytes=32 time=54ms TTL=55
Reply from 89.234.66.107: bytes=32 time=50ms TTL=55
Request timed out.
Reply from 89.234.66.107: bytes=32 time=47ms TTL=55
Reply from 89.234.66.107: bytes=32 time=47ms TTL=55
Reply from 89.234.66.107: bytes=32 time=48ms TTL=55
Reply from 89.234.66.107: bytes=32 time=50ms TTL=55
Reply from 89.234.66.107: bytes=32 time=54ms TTL=55
Reply from 89.234.66.107: bytes=32 time=48ms TTL=55
Reply from 89.234.66.107: bytes=32 time=47ms TTL=55
Reply from 89.234.66.107: bytes=32 time=51ms TTL=55
Reply from 89.234.66.107: bytes=32 time=45ms TTL=55
Reply from 89.234.66.107: bytes=32 time=48ms TTL=55
Request timed out.
Reply from 89.234.66.107: bytes=32 time=42ms TTL=55
Reply from 89.234.66.107: bytes=32 time=37ms TTL=55
Reply from 89.234.66.107: bytes=32 time=42ms TTL=55
Reply from 89.234.66.107: bytes=32 time=42ms TTL=55

Ping statistics for 89.234.66.107:
Packets: Sent = 44, Received = 42, Lost = 2 (4% loss),
Approximate round trip times in milli-seconds:
Minimum = 35ms, Maximum = 108ms, Average = 47ms

Xcellor

My understanding is contention is at exchange level... for this to be affecting people on different exchanges suggests something else. Please continue to pester them. Hopefully enough complaints will escalate it further in Eircom.

zoom_cool

Bad ping times again how is the rest of you getting on

jay93

Hmmm odd it just starting doing this tonight





supposed to be 3mb connection whats going on with utv??