Clicksilver Users Gather Here Please

kin9pin

ai ing wrote:

Every time Im losing packets as well as such slow ping.

UTV apologises for your inconvenience, but that's all it is. Please refer to section 88.c of your t&c's which states that "We have you by the balls and there's nothing you can do"

davewcelbridge

My connection speeds seem to have improved in the last two days. I am getting uploads of 85-90Kbps and downloads at 400-420Kbps.

Big improvement from the 220 Down 40 Up i was getting three days ago. Anyone else experiencing this or am i a fluke??

Also i pinged my local Uni. Maynooth NUI and got these pings...
Pinging walnut.may.ie [149.157.1.115] with 32 bytes of data:

Reply from 149.157.1.115: bytes=32 time=65ms TTL=241
Reply from 149.157.1.115: bytes=32 time=80ms TTL=241
Reply from 149.157.1.115: bytes=32 time=63ms TTL=241
Reply from 149.157.1.115: bytes=32 time=88ms TTL=241

Ping statistics for 149.157.1.115:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 63ms, Maximum = 88ms, Average = 74ms

mike65

My own go -

Pinging walnut.may.ie [149.157.1.115] with 32 bytes of data:

Reply from 149.157.1.115: bytes=32 time=58ms TTL=241
Reply from 149.157.1.115: bytes=32 time=74ms TTL=241
Reply from 149.157.1.115: bytes=32 time=62ms TTL=241
Reply from 149.157.1.115: bytes=32 time=68ms TTL=241

Ping statistics for 149.157.1.115:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 58ms, Maximum = 74ms, Average = 65ms

---

Tracing route to www.boards.ie [82.195.131.128]
over a maximum of 30 hops:

1 <10 ms <10 ms 1 ms 192.168.1.1
2 38 ms 34 ms 37 ms 195.218.116.25
3 36 ms 38 ms 36 ms UTV-DUB-fastethernet0-0.116.218.195.in-addr.arpa
[195.218.116.1]
4 38 ms 37 ms 38 ms 195.218.126.178
5 43 ms 37 ms 35 ms 195.218.112.195
6 49 ms 47 ms 49 ms 195.92.55.134
7 48 ms 48 ms 46 ms pos1-0.ber-1.r18.telh.as5388.net [195.92.55.160]

8 46 ms 52 ms 50 ms 195.50.91.65
9 47 ms 50 ms 50 ms ge-9-0.ipcolo1.London1.Level3.net [212.187.131.1
47]
10 57 ms 60 ms 59 ms 80.253.124.21
11 60 ms 61 ms 58 ms sneezy.hosting365.ie [82.195.128.8]
12 66 ms 59 ms 72 ms www.boards.ie [82.195.131.128]

Mike.

kin9pin

What times are you checking this? Speeds & pings are generally fine during the (week) day. It's only when UTV turn the lights out each night that they get bad.

mike65

Did those just now (last 30 mins) I think part of the reason it goes tits up
in evening is becuase its when the US west coast traffic is at its busiest.


Mike.

Gonzo

mike65 wrote:

Did those just now (last 30 mins) I think part of the reason it goes tits up
in evening is becuase its when the US west coast traffic is at its busiest.


Mike.

if that was the case wouldnt if effect everyone on eircom, iol, netsource and digiweb also? I think all of utv problems are purely down to their own network providers who are based in London, routing an Irish service through london seems daft to begin with, pinging anything Irish shows that you have to make your way to london first then back to Ireland, this adds nearly 30ms with many extra hops to a utv ping on a normal day on top of what everyone else gets on eircom, iol etc. This doesnt explain the disconnections or 56k style download speeds but I think if UTV are serious about operating as a broadband provider to the republic of Ireland that they need to change their network totally over to an Irish one thats reliable and gives their Irish customers the fastest pings and improved bandwidth that they deserve. AFAIK UTV Clicksilver performs grand in Northern Ireland itself as its on BT lines and the london based network suits that fine but it sure aint the case down here in the south. I really think the only proper resolve is for UTV to operate Clicksilver totally from Dublin rather than Belfast/London for their customers here using Irish based network providers.

Moriarty

mike65 wrote:

Did those just now (last 30 mins) I think part of the reason it goes tits up
in evening is becuase its when the US west coast traffic is at its busiest.

Whatever the reason(s) turn out to be, you can be certain this has nothing to do with it.

mike65

Whatever the reason(s) turn out to be, you can be certain this has nothing to do with it.

Still love to know why its at its worst in the evening, I'd imagine most net traffic locally is during business hours (if this place is anything to go by!).

Mike.

jonski

i am fairly sure its something to do with flicking the light switch when they are on the way out the door on the way home . having said that , fair play to the guy that comes in at 2 in the morning to start work .

mike65

C:\WINDOWS> tracert www.boards.ie

Tracing route to www.boards.ie [82.195.131.128]
over a maximum of 30 hops:

1 1 ms 1 ms <10 ms 192.168.1.1
2 190 ms 205 ms 188 ms 195.218.116.25
3 183 ms 173 ms 168 ms UTV-DUB-fastethernet0-0.116.21 [195.218.116.1]
4 * * 205 ms 195.218.126.178
5 192 ms 191 ms 189 ms 195.218.112.195
6 198 ms 208 ms * 195.92.55.134
7 * 200 ms 218 ms pos1-0.ber-1.r18.telh.as5388.n
8 212 ms * * 195.50.91.65
9 211 ms 196 ms 210 ms ge-9-0.ipcolo1.London1.Level3.
47]
10 236 ms 235 ms 219 ms 80.253.124.21
11 207 ms 201 ms 196 ms sneezy.hosting365.ie [82.195.1
12 236 ms 235 ms * www.boards.ie [82.195.131.128]
13 216 ms 234 ms 243 ms www.boards.ie [82.195.131.128]

---

Pinging www.boards.ie [82.195.131.128] with 32 bytes of data:

Reply from 82.195.131.128: bytes=32 time=239ms TTL=52
Reply from 82.195.131.128: bytes=32 time=240ms TTL=52
Reply from 82.195.131.128: bytes=32 time=233ms TTL=52
Reply from 82.195.131.128: bytes=32 time=201ms TTL=52

Ping statistics for 82.195.131.128:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 201ms, Maximum = 240ms, Average = 228ms

Mike.

CapBean

Just a suggestion for those people on the trial bb accounts.

Have you read fully the contract agreement you signed.

I seem to recall ( please put me right if i'm wrong ) that in order to get out of the 3 months free trial you MUST submit in writing your request to be disconnected BEFORE the 3 months are finished.

Failure to do so will AUTOMATICALLY means you have accepted the service for the next 1 YEAR contract obligations.

Read your contract agreements or you might be stuffed for another year,
afterall nothing is ever free, theres always a price to pay somewhere along the line!

daveyjoe

mike65 wrote:

Still love to know why its at its worst in the evening, I'd imagine most net traffic locally is during business hours (if this place is anything to go by!).

Mike.

While most local net traffic would be during business hours. The people who do heavy downloading (i.e.. Movies, Music, Wares) would probably use the internet in the evening, The heavy downloaders would put a lot more strain on the network than the business users and casual surfers in the afternoon.

It's 4.20 AM and I'm just back from the pub and the pings are pretty decent, it's a pity that I'm too tired for gaming though.

C:\Documents and Settings\Dave>ping www.jolt.co.uk

Pinging clarity.jolt.co.uk [195.149.21.11] with 32 bytes of data:

Reply from 195.149.21.11: bytes=32 time=51ms TTL=55
Reply from 195.149.21.11: bytes=32 time=49ms TTL=55
Reply from 195.149.21.11: bytes=32 time=48ms TTL=55
Reply from 195.149.21.11: bytes=32 time=47ms TTL=55

Ping statistics for 195.149.21.11:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 47ms, Maximum = 51ms, Average = 48ms

LoBo

anyone got a program that will periodically ping a list of servers you give it, and keep track of results over any time period? Basically I want to put in u.tv, utvinternet.com, boards.ie, google.ie and say bbc.co.uk and have it ping them once an hour for a few weeks...

If no one knows one, I might just hack one out..

Stephen

Charles on utv.support wrote:

Dear Customer,

This is to advise you that, as part of an ongoing engineering works, we
have been notified of planned maintenance which will affect all RoI
ClickSilver customers.

Schedule As follows:

Planned start: Friday 13/08/2004 16:00
Planned finish: Friday 13/08/2004 18:00

During this timeframe you may notice a loss of connection or be unable to
connect to the service. The outage should be for approximately 30 minutes
within the allocated timeframe and we anticipate this to be much less.

*wonders if this has any chance of fixing UTV in general*

Moriarty

I wonder if anyone from UTV could give us more details here of the planned work..?

Stephen

This is all I've got so far:

"Stephen" <no.spam@ever> wrote in message
news:411b9f07$1@ni-news.utvinternet.com...

>> Charles (UTV Internet) wrote:
>
>>> > Dear Customer,
>
>> <snip>
>>
>> Charles... is this related to the bandwidth upgrade/fixing the current
>> chronic problems?


Yes it is.

Charles
-- Technical Support Supervisor UTV Internet http://u.tv/support/

kin9pin

LoBo wrote:

anyone got a program that will periodically ping a list of servers you give it, and keep track of results over any time period? Basically I want to put in u.tv, utvinternet.com, boards.ie, google.ie and say bbc.co.uk and have it ping them once an hour for a few weeks...

If no one knows one, I might just hack one out..

Paste this into notepad and save as ****.bat
The schedule it to run every 15 mins using Scheduled Tasks in your System Tools Menu.

It will write the date, time and ping to the txt file. For me, I'm pinging utv, jolt, boards and heanet.

date /t >> c:\Webstats\UTVPing.txt
time /t >> c:\Webstats\UTVPing.txt
ping www.utvinternet.com >> c:\Webstats\UTVPing.txt
date /t >> c:\Webstats\JoltPing.txt
time /t >> c:\Webstats\JoltPing.txt
ping www.jolt.co.uk >> c:\Webstats\JoltPing.txt
date /t >> c:\Webstats\boardsPing.txt
time /t >> c:\Webstats\boardsPing.txt
ping www.boards.ie >> c:\Webstats\boardsPing.txt
date /t >> c:\Webstats\heanetPing.txt
time /t >> c:\Webstats\heanetPing.txt
ping www.heanet.ie >> c:\Webstats\heanetPing.txt

I also have a program download files from certain sites and writing the speed results to txt files. pm me if you want it.

Couch Potato

C:\>ping -n 40 www.boards.ie

Pinging www.boards.ie [82.195.131.128] with 32 bytes of data:

Reply from 82.195.131.128: bytes=32 time=230ms TTL=52
Reply from 82.195.131.128: bytes=32 time=211ms TTL=52
Reply from 82.195.131.128: bytes=32 time=200ms TTL=52
Reply from 82.195.131.128: bytes=32 time=200ms TTL=52
Reply from 82.195.131.128: bytes=32 time=210ms TTL=52
Reply from 82.195.131.128: bytes=32 time=180ms TTL=52
Reply from 82.195.131.128: bytes=32 time=210ms TTL=52
Reply from 82.195.131.128: bytes=32 time=170ms TTL=52
Request timed out.
Reply from 82.195.131.128: bytes=32 time=190ms TTL=52
Reply from 82.195.131.128: bytes=32 time=211ms TTL=52
Reply from 82.195.131.128: bytes=32 time=210ms TTL=52
Reply from 82.195.131.128: bytes=32 time=200ms TTL=52
Reply from 82.195.131.128: bytes=32 time=210ms TTL=52
Reply from 82.195.131.128: bytes=32 time=200ms TTL=52
Reply from 82.195.131.128: bytes=32 time=201ms TTL=52
Reply from 82.195.131.128: bytes=32 time=200ms TTL=52
Reply from 82.195.131.128: bytes=32 time=211ms TTL=52
Reply from 82.195.131.128: bytes=32 time=200ms TTL=52
Reply from 82.195.131.128: bytes=32 time=201ms TTL=52
Reply from 82.195.131.128: bytes=32 time=220ms TTL=52
Reply from 82.195.131.128: bytes=32 time=170ms TTL=52
Request timed out.
Reply from 82.195.131.128: bytes=32 time=200ms TTL=52
Reply from 82.195.131.128: bytes=32 time=210ms TTL=52
Reply from 82.195.131.128: bytes=32 time=190ms TTL=52
Reply from 82.195.131.128: bytes=32 time=210ms TTL=52
Reply from 82.195.131.128: bytes=32 time=201ms TTL=52
Reply from 82.195.131.128: bytes=32 time=190ms TTL=52
Reply from 82.195.131.128: bytes=32 time=201ms TTL=52
Reply from 82.195.131.128: bytes=32 time=210ms TTL=52
Reply from 82.195.131.128: bytes=32 time=211ms TTL=52
Reply from 82.195.131.128: bytes=32 time=200ms TTL=52
Reply from 82.195.131.128: bytes=32 time=220ms TTL=52
Reply from 82.195.131.128: bytes=32 time=210ms TTL=52
Reply from 82.195.131.128: bytes=32 time=230ms TTL=52
Reply from 82.195.131.128: bytes=32 time=260ms TTL=52
Reply from 82.195.131.128: bytes=32 time=190ms TTL=52
Reply from 82.195.131.128: bytes=32 time=181ms TTL=52
Reply from 82.195.131.128: bytes=32 time=220ms TTL=52

Ping statistics for 82.195.131.128:
Packets: Sent = 40, Received = 38, Lost = 2 (5% loss),
Approximate round trip times in milli-seconds:
Minimum = 170ms, Maximum = 260ms, Average = 194ms

C:\> :rolleyes: :rolleyes: :rolleyes: :rolleyes: :rolleyes: :rolleyes: :rolleyes: :rolleyes: :rolleyes: :rolleyes: :rolleyes:

Psygnosis

Mines pretty woefull as well when are they going to do something this is unacceptable


Pinging www.boards.ie [82.195.131.128] with 32 bytes of

Reply from 82.195.131.128: bytes=32 time=227ms TTL=52
Reply from 82.195.131.128: bytes=32 time=203ms TTL=53
Reply from 82.195.131.128: bytes=32 time=203ms TTL=53
Reply from 82.195.131.128: bytes=32 time=218ms TTL=53
Reply from 82.195.131.128: bytes=32 time=218ms TTL=53
Reply from 82.195.131.128: bytes=32 time=227ms TTL=53
Reply from 82.195.131.128: bytes=32 time=203ms TTL=52
Request timed out.
Reply from 82.195.131.128: bytes=32 time=249ms TTL=53
Request timed out.
Reply from 82.195.131.128: bytes=32 time=217ms TTL=53
Reply from 82.195.131.128: bytes=32 time=217ms TTL=52
Reply from 82.195.131.128: bytes=32 time=244ms TTL=53
Reply from 82.195.131.128: bytes=32 time=221ms TTL=53
Reply from 82.195.131.128: bytes=32 time=202ms TTL=53
Reply from 82.195.131.128: bytes=32 time=208ms TTL=53
Reply from 82.195.131.128: bytes=32 time=202ms TTL=53
Reply from 82.195.131.128: bytes=32 time=206ms TTL=52
Reply from 82.195.131.128: bytes=32 time=206ms TTL=53
Reply from 82.195.131.128: bytes=32 time=209ms TTL=53
Reply from 82.195.131.128: bytes=32 time=207ms TTL=52
Request timed out.
Reply from 82.195.131.128: bytes=32 time=212ms TTL=53
Reply from 82.195.131.128: bytes=32 time=202ms TTL=53
Reply from 82.195.131.128: bytes=32 time=193ms TTL=52
Reply from 82.195.131.128: bytes=32 time=208ms TTL=52
Reply from 82.195.131.128: bytes=32 time=175ms TTL=53
Reply from 82.195.131.128: bytes=32 time=266ms TTL=53
Reply from 82.195.131.128: bytes=32 time=177ms TTL=53
Reply from 82.195.131.128: bytes=32 time=255ms TTL=53
Reply from 82.195.131.128: bytes=32 time=231ms TTL=52
Reply from 82.195.131.128: bytes=32 time=201ms TTL=53
Reply from 82.195.131.128: bytes=32 time=249ms TTL=53
Reply from 82.195.131.128: bytes=32 time=198ms TTL=53
Reply from 82.195.131.128: bytes=32 time=201ms TTL=53
Reply from 82.195.131.128: bytes=32 time=265ms TTL=53
Reply from 82.195.131.128: bytes=32 time=304ms TTL=52
Reply from 82.195.131.128: bytes=32 time=423ms TTL=53
Reply from 82.195.131.128: bytes=32 time=415ms TTL=53
Reply from 82.195.131.128: bytes=32 time=428ms TTL=53

Ping statistics for 82.195.131.128:
Packets: Sent = 40, Received = 37, Lost = 3 (7% los
Approximate round trip times in milli-seconds:
Minimum = 175ms, Maximum = 428ms, Average = 234ms

dub45

Psygnosis wrote:

Mines pretty woefull as well when are they going to do something this is unacceptable


Pinging www.boards.ie [82.195.131.128] with 32 bytes of

Reply from 82.195.131.128: bytes=32 time=227ms TTL=52
Reply from 82.195.131.128: bytes=32 time=203ms TTL=53
..............

Not getting much more that 120 kbps tonight myself.

I was prepared to be relatively patient about this until Scott posted on boards and apologised for the 'inconvenience' ohh how I hate that smooth PR blather from MDs who think they can patronise their customers.

And now UTV are saying in the newsgroup that they apparently dont know how effective the work tomorrow will be!!!!

> Charles - is this finally going to fix the issue or are there other future
> works involved aswell?
>
>
> tks

This is a big part of it but other works may be needed depending on the
outcome tomorrow.

jonski

That was more than a little annoying

Páid

Is Clicksilver down for anyone else at the moment?

I'm in Rathmines and cannot connect for the last hour and a half.

jonski

Not down here , having said that it may aswell be .

Páid

Its back now @ 214 kbit after 2 hours of trying to connect.

Stephen

Anyone have any updates from the utv.support newsgroup today? Wish I could read it from work

dub45

Stephen wrote:

Anyone have any updates from the utv.support newsgroup today? Wish I could read it from work

You are hardly missing anything I would guess. The upgrading is not due to take place until late this afternoon and we probably wont know how effective it is until the evening time anyways as its usually then that the speeds and pings take a hit.

Stephen

Still, i like to keep up with the latest flaming on UTV

They were getting a thorough roasting last time I checked.

radiospan

CS down for anyone?

I'm on 56K now, I haven't been able to connect with my modem or router for the past hour or so.

Stephen

This falls into the time period that they scheduled downtime for. (see email/newsgroup posts pasted earlier in this thread).

Planned start: Friday 13/08/2004 16:00
Planned finish: Friday 13/08/2004 18:00

During this timeframe you may notice a loss of connection or be unable to
connect to the service. The outage should be for approximately 30 minutes
within the allocated timeframe and we anticipate this to be much less.

Moriarty

Pings seem fine on this clicksilver line at the moment..

traceroute www.boards.ie

traceroute to www.boards.ie (82.195.131.128), 30 hops max, 40 byte packets
1 192.168.1.1 (192.168.1.1) 3.245 ms 1.17 ms 0.953 ms
2 195.218.x.x (195.218.x.x) 25.085 ms 23.444 ms 26.057 ms
3 UTV-DUB-fastethernet0-0.116.218.195.in-addr.arpa (195.218.116.1) 26.738 ms 22.588 ms 23.32 ms
4 195.218.126.178 (195.218.126.178) 25.734 ms 24.789 ms 25.101 ms
5 195.218.112.2 (195.218.112.2) 23.367 ms 24.998 ms 23.334 ms
6 195.92.55.134 (195.92.55.134) 37.946 ms 39.995 ms 39.864 ms
7 pos1-0.ber-1.r18.telh.as5388.net (195.92.55.160) 39.64 ms 39.124 ms 40.618 ms
8 195.50.91.65 (195.50.91.65) 40.314 ms 35.882 ms 37.383 ms
9 ge-9-0.ipcolo1.London1.Level3.net (212.187.131.147) 39.898 ms 41.314 ms 37.057 ms
10 80.253.124.21 (80.253.124.21) 51.293 ms 50.281 ms 48.678 ms
11 sneezy.hosting365.ie (82.195.128.8) 55.446 ms 48.567 ms 48.494 ms

--- www.boards.ie ping statistics ---
30 packets transmitted, 30 packets received, 0% packet loss
round-trip min/avg/max = 52.1/55.8/68.8 ms

---

traceroute www.jolt.co.uk
traceroute to clarity.jolt.co.uk (195.149.21.11), 30 hops max, 40 byte packets
1 192.168.1.1 (192.168.1.1) 18.432 ms 1.076 ms 0.93 ms
2 195.218.x.x (195.218.x.x) 25.32 ms 22.56 ms 24.02 ms
3 UTV-DUB-fastethernet0-0.116.218.195.in-addr.arpa (195.218.116.1) 105.177 ms 291.202 ms 387.324 ms
4 195.218.126.178 (195.218.126.178) 25.627 ms 25.199 ms 24.096 ms
5 195.218.112.2 (195.218.112.2) 23.745 ms 24.253 ms 24.07 ms
6 195.92.55.134 (195.92.55.134) 38.869 ms 37.631 ms 38.841 ms
7 ber-1.r18.telc.as5388.net (195.92.55.156) 39.918 ms 39.156 ms 40.277 ms
8 lon1-9.nildram.net (195.66.224.59) 40.666 ms 38.184 ms 41.332 ms
9 jolt-gw.nildram.net (195.149.20.126) 38.182 ms 38.452 ms 40.265 ms
10 clarity.jolt.co.uk (195.149.21.11) 39.932 ms 38.658 ms 38.817 ms

--- clarity.jolt.co.uk ping statistics ---
30 packets transmitted, 30 packets received, 0% packet loss
round-trip min/avg/max = 40.8/44.5/60.3 ms