fair played to IBB

jesus_thats_gre

Seeing as I complained about their Customer Service before, I thought I would congratulate them on solving my problem in about 4 working days.

Late Wednesday evening, my latency timings shot through the roof. Previously I had pings of 8ms to www.boards.ie and <40ms to the Counter Strike server.

For the last few days, my pings averaged about 120ms to boards.ie and in or around 190 to the CS server I play on.

I reported the problem to them on Thursday, followed up Friday evening and followed the call up yesterday evening again. Around lunch time today, I started to see improvements and now they are perfect again.

Example:

Reply from 82.138.226.130: bytes=32 time=19ms TTL=120
Reply from 82.138.226.130: bytes=32 time=23ms TTL=120
Reply from 82.138.226.130: bytes=32 time=28ms TTL=120
Reply from 82.138.226.130: bytes=32 time=18ms TTL=120
Reply from 82.138.226.130: bytes=32 time=21ms TTL=120
Reply from 82.138.226.130: bytes=32 time=20ms TTL=120
Reply from 82.138.226.130: bytes=32 time=22ms TTL=120
Reply from 82.138.226.130: bytes=32 time=27ms TTL=120
Reply from 82.138.226.130: bytes=32 time=35ms TTL=120
Reply from 82.138.226.130: bytes=32 time=26ms TTL=120
Reply from 82.138.226.130: bytes=32 time=19ms TTL=120

Ping statistics for 82.138.226.130:
Packets: Sent = 98, Received = 98, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 95ms, Average = 29ms





C:\Documents and Settings>ping www.boards.ie

Pinging www.boards.ie [82.195.136.250] with 32 bytes of dat

Reply from 82.195.136.250: bytes=32 time=8ms TTL=57
Reply from 82.195.136.250: bytes=32 time=9ms TTL=57
Reply from 82.195.136.250: bytes=32 time=12ms TTL=57
Reply from 82.195.136.250: bytes=32 time=7ms TTL=57

Ping statistics for 82.195.136.250:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 12ms, Average = 9ms


So fair played IBB.

PowerHouseDan

I give ya 23 Hours

Drapper

PowerHouseDan wrote:

I give ya 23 Hours

must be one of the perks of the job!

jesus_thats_gre

PowerHouseDan wrote:

I give ya 23 Hours

Well it was perfect for 6 months pretty much.. Bad for 4 days.. Will give em the benefit of the doubt for now.

Mutant_Fruit

perfect for 3 months, bad for 3 months, perfect for 11 months, bad for just over 3 months... seems to be very unreliable from a long-term point of view.

Adey2002

??

You're congratulating a Company for providing the Service that you're paying for? I want you as one of my customers.

Nevyn

We are right beside the shopping ventre in blanch and we can't get ntl
and apprently smart didnt get enough intrest out here and arent bothered.

jesus_thats_gre What mast are you on ?
Why is it that they could fix your connection and not anyone elses ?

philologos

fair play to them for sorting out their problem anyway

spooky donkey

4 days is still to long but its better than 2 months.
3 months good then 2 months bad then 3 months bad followed by 3 months good and am now comming to the end of another bad 2 months and my year is almost up with them now.

Cuddlesworth

I give you a week at best.

[V3]

My ping have been crazy last week. Was reaching 200ms on UK servers but it seems fine now too. Problem is now the speed is slower than before. Oh well, with IBB, you cant have them all

jesus_thats_gre

Adey2002 wrote:

??

You're congratulating a Company for providing the Service that you're paying for? I want you as one of my customers.

Well we are all too quick to criticise someone for a job badly done. I feel its time to congratulate for a job well done.. The service is still perfect for the doubters..

Jolt:

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

Pinging www.jolt.co.uk [82.133.85.65] with 32 bytes of dat

Reply from 82.133.85.65: bytes=32 time=16ms TTL=53
Reply from 82.133.85.65: bytes=32 time=17ms TTL=53
Reply from 82.133.85.65: bytes=32 time=23ms TTL=53
Reply from 82.133.85.65: bytes=32 time=16ms TTL=53

Ping statistics for 82.133.85.65:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 16ms, Maximum = 23ms, Average = 18ms


Boards:


C:\Documents and Settings\Luke>ping www.boards.ie

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

Reply from 82.195.136.250: bytes=32 time=8ms TTL=57
Reply from 82.195.136.250: bytes=32 time=7ms TTL=57
Reply from 82.195.136.250: bytes=32 time=6ms TTL=57
Reply from 82.195.136.250: bytes=32 time=7ms TTL=57

Ping statistics for 82.195.136.250:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 6ms, Maximum = 8ms, Average = 7ms

Thaedydal wrote:

jesus_thats_gre What mast are you on ?
Why is it that they could fix your connection and not anyone elses ?

Am off ThreeRock and am based in Leopardstown..

I explained the problem to them on Thursday and they said there was a problem with the high site. I took their word for it but done a few ping tests on each hop on the way to the net. It turned out that the problem was on one of their gateway routers to the internet.

I called them back on Friday and told them what I discovered. The lad on the phone thanked me for for information and said he would escalate it to second line and that it would not be dealt with until the next working day. So I called on Monday to say that there was a slight improvement on my line and that I want it fixed ASAP. Come Tuesday evening, it was fine. What can I say.