Imagine Broadband Breeze Review

Kev.

Imagine Broadband Breeze Review

Okay I thought I would give some people some info on this product as when I was looking for some info or reviews there wasnt many around.....

After months of getting an absolute rubbish connection/Service from Eircom,the only other solution for me was Imagine/Irish Broadband fixed sattelite service offering 4mb down and up.
The problem stemmed from my local exchange (Clonee) being overloaded at peak times and contension left my internet unusabl....more like a dial up connection,
This is where I found it tricky,as most companies basically resell Eircoms broadband,
Where my house is in Clonsilla the lines are crap and the exchange is overloaded so I could be waiting years for a good Broadband service,
As I use broadband for work,gaming and downloading stuff I needed it resolve quickly so I decided to look for alternatives.
So after some research I decided to get Breeze 4mb,

When I rang up to order I was asked for 100 euro deposit,which if I didnt want the package after a weeks trial I would get back.
So the order was placed and I was told that Ill have to wait 10 days for installation,
About 8 days later 2 chaps rang me and told me the time they would arrive,Happy days !

When the lads came out they first of all told me that the connection was dependent on the line of sight to the High site,which in my case was beside Clonsilla railway station.
They done the tests and everything passed,and it was then installed.
The satellite is a small white triangle which was placed beside my chimney,a cat5 cable was ran from the triangle in through my wall which would then eventually lead into my router.

The router itself is not supplied and needs to be purchased seperately.
I had a netopia router from Eircom which I tought would be sufficiant but because its a DSL router it wasnt any use.I needed a CABLE router...
Imagine broadband recommend that a netgear is used,most of the lads in support know how to use these so I ended up purchasing a Netgear WNR 2000 for about 60 euro.

On setting this up I had no problems,I have been in touch with the lads in support a few times and they have been usefull and seem nice people who are down to earth and will lend a hand to anybody looking for help.

Okay now to the product itself.....

First of all speedtests....for the best part of the day I am getting 3.8 down and 3.7 upload
Contension does have a say in it though,at peak times it drops to about 1-2.5 mb down and up,
This isnt too bad with me as with Eircom my connection would drop to 0.35 and made it unbareable to use,with Breeze I can still browse the net and play games at peak times

Gaming: Ping 20-23 ms all the time,absolutely perfect,Nearly every game Ive played/hosted have been lag free

Torrents:Slow to start off with ,sometimes stays at 50 kbs but after a few minutes it seems to average out at around 200 kbs,this morning I got up early and had a look it was downloading at 450kbs!

Rapidshare/Mediafire/megaupload:I had 5 files running last night at once and the total speed came in at 500 kbs.

All in all Im happy with the package-the 55 euro package might put some people off but what can you do.

I hope this quick review helps some people out.

From most of the threads about Eircom speeds lately my advice would be get rid of them and find other solutions,
If your exchange is overloaded and you have crap lines,Imagine Breeze is a good alternative

tech_guy

Hi Kev,

I am looking for an alternate to Imaginge DSL 7.6Mb download business package for my colleague in Loughlinstown -Co Dublin. Ping results are as below

192.168.254.180 with 32 bytes of data:

Reply from 192.168.254.180: bytes=32 time=72ms TTL=128
Reply from 192.168.254.180: bytes=32 time=71ms TTL=128
Reply from 192.168.254.180: bytes=32 time=70ms TTL=128
Reply from 192.168.254.180: bytes=32 time=70ms TTL=128
Reply from 192.168.254.180: bytes=32 time=72ms TTL=128
Reply from 192.168.254.180: bytes=32 time=71ms TTL=128
Reply from 192.168.254.180: bytes=32 time=70ms TTL=128
Reply from 192.168.254.180: bytes=32 time=73ms TTL=128
Reply from 192.168.254.180: bytes=32 time=71ms TTL=128
Reply from 192.168.254.180: bytes=32 time=70ms TTL=128
Reply from 192.168.254.180: bytes=32 time=71ms TTL=128
Reply from 192.168.254.180: bytes=32 time=70ms TTL=128
Reply from 192.168.254.180: bytes=32 time=72ms TTL=128
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.254.180: bytes=32 time=71ms TTL=128
Reply from 192.168.254.180: bytes=32 time=71ms TTL=128
Reply from 192.168.254.180: bytes=32 time=71ms TTL=128
Reply from 192.168.254.180: bytes=32 time=70ms TTL=128
Reply from 192.168.254.180: bytes=32 time=69ms TTL=128
Reply from 192.168.254.180: bytes=32 time=71ms TTL=128
Reply from 192.168.254.180: bytes=32 time=71ms TTL=128
Reply from 192.168.254.180: bytes=32 time=70ms TTL=128
Reply from 192.168.254.180: bytes=32 time=73ms TTL=128
Reply from 192.168.254.180: bytes=32 time=72ms TTL=128
Reply from 192.168.254.180: bytes=32 time=71ms TTL=128
Reply from 192.168.254.180: bytes=32 time=72ms TTL=128
Reply from 192.168.254.180: bytes=32 time=69ms TTL=128
Reply from 192.168.254.180: bytes=32 time=71ms TTL=128
Reply from 192.168.254.180: bytes=32 time=69ms TTL=128
Reply from 192.168.254.180: bytes=32 time=69ms TTL=128
Reply from 192.168.254.180: bytes=32 time=73ms TTL=128
Reply from 192.168.254.180: bytes=32 time=71ms TTL=128
Reply from 192.168.254.180: bytes=32 time=71ms TTL=128
Reply from 192.168.254.180: bytes=32 time=71ms TTL=128
Reply from 192.168.254.180: bytes=32 time=71ms TTL=128
Reply from 192.168.254.180: bytes=32 time=72ms TTL=128
Reply from 192.168.254.180: bytes=32 time=72ms TTL=128
Reply from 192.168.254.180: bytes=32 time=72ms TTL=128
Reply from 192.168.254.180: bytes=32 time=72ms TTL=128
Reply from 192.168.254.180: bytes=32 time=71ms TTL=128
Reply from 192.168.254.180: bytes=32 time=71ms TTL=128
Reply from 192.168.254.180: bytes=32 time=71ms TTL=128
Reply from 192.168.254.180: bytes=32 time=70ms TTL=128
Reply from 192.168.254.180: bytes=32 time=72ms TTL=128
Reply from 192.168.254.180: bytes=32 time=71ms TTL=128
Reply from 192.168.254.180: bytes=32 time=70ms TTL=128

Ping statistics for 192.168.254.180:
Packets: Sent = 50, Received = 45, Lost = 5 (10% loss),
Approximate round trip times in milli-seconds:
Minimum = 69ms, Maximum = 73ms, Average = 70ms

Pinging 192.168.254.180 with 32 bytes of data:

Reply from 192.168.254.180: bytes=32 time=71ms TTL=128
Reply from 192.168.254.180: bytes=32 time=68ms TTL=128
Reply from 192.168.254.180: bytes=32 time=84ms TTL=128
Reply from 192.168.254.180: bytes=32 time=70ms TTL=128
Reply from 192.168.254.180: bytes=32 time=87ms TTL=128
Reply from 192.168.254.180: bytes=32 time=71ms TTL=128
Reply from 192.168.254.180: bytes=32 time=72ms TTL=128
Reply from 192.168.254.180: bytes=32 time=81ms TTL=128
Reply from 192.168.254.180: bytes=32 time=80ms TTL=128
Reply from 192.168.254.180: bytes=32 time=82ms TTL=128
Reply from 192.168.254.180: bytes=32 time=69ms TTL=128
Reply from 192.168.254.180: bytes=32 time=462ms TTL=128
Reply from 192.168.254.180: bytes=32 time=611ms TTL=128
Reply from 192.168.254.180: bytes=32 time=285ms TTL=128
Reply from 192.168.254.180: bytes=32 time=427ms TTL=128
Request timed out.
Reply from 192.168.254.180: bytes=32 time=70ms TTL=128
Reply from 192.168.254.180: bytes=32 time=71ms TTL=128
Reply from 192.168.254.180: bytes=32 time=70ms TTL=128
Reply from 192.168.254.180: bytes=32 time=71ms TTL=128
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.254.180: bytes=32 time=71ms TTL=128
Reply from 192.168.254.180: bytes=32 time=72ms TTL=128

Ping statistics for 192.168.254.180:
Packets: Sent = 50, Received = 21, Lost = 29 (58% loss),
Approximate round trip times in milli-seconds:
Minimum = 68ms, Maximum = 611ms, Average = 145ms

Unfortunately he had 3mb download business package with 48:1 contention ratio and now locked with 12 months contract with 12:1. I thought that would improve broadband connection drastically but see the results above. VOIP and even outlook is giving big trouble and looking for an upgrade to breeze 4mb package.

Do you mind to give me some ping results to www.google.co.uk and post it from morning and afternoon result.

ping -n 50 www.google.co.uk
tracert www.google.co.uk

Your help is highly appreciated here.

Thanks and regards,

Tech_guy

pizzahead77

By the way, its not Satellite, its Fixed Wireless

tech_guy

pizzahead77 wrote: »

By the way, its not Satellite, its Fixed Wireless

No it's DSL line 7.6mb dowload /600kb upload business broadband with 12:1 contention ration.

johnciall

tech_guy wrote: »

No it's DSL line 7.6mb dowload /600kb upload business broadband with 12:1 contention ration.

I think he was commenting on the OP

Kev.

Sorry only seen the replys now,I have fixed wireless and can do some pings for you later this evening if you still want

tech_guy

Yes please... Much appreciated. Eager to see ping result. thanks

BigMoose

Since I'm "working from home" (bored) I thought I'd post the results from IBB Breeze 4Mb from Wicklow:

ping -n 50 www.google.co.uk

Pinging www.l.google.com [74.125.43.104] with 32 bytes of data:

Reply from 74.125.43.104: bytes=32 time=53ms TTL=53
Reply from 74.125.43.104: bytes=32 time=47ms TTL=53
Reply from 74.125.43.104: bytes=32 time=49ms TTL=53
Reply from 74.125.43.104: bytes=32 time=48ms TTL=53
Reply from 74.125.43.104: bytes=32 time=48ms TTL=53
Reply from 74.125.43.104: bytes=32 time=48ms TTL=53
Reply from 74.125.43.104: bytes=32 time=48ms TTL=53
Reply from 74.125.43.104: bytes=32 time=66ms TTL=53
Reply from 74.125.43.104: bytes=32 time=49ms TTL=53
Reply from 74.125.43.104: bytes=32 time=77ms TTL=53
Reply from 74.125.43.104: bytes=32 time=82ms TTL=53
Reply from 74.125.43.104: bytes=32 time=48ms TTL=53
Reply from 74.125.43.104: bytes=32 time=102ms TTL=53
Reply from 74.125.43.104: bytes=32 time=48ms TTL=53
Reply from 74.125.43.104: bytes=32 time=48ms TTL=53
Reply from 74.125.43.104: bytes=32 time=47ms TTL=53
Reply from 74.125.43.104: bytes=32 time=49ms TTL=53
Reply from 74.125.43.104: bytes=32 time=50ms TTL=53
Reply from 74.125.43.104: bytes=32 time=49ms TTL=53
Reply from 74.125.43.104: bytes=32 time=47ms TTL=53
Reply from 74.125.43.104: bytes=32 time=52ms TTL=53
Reply from 74.125.43.104: bytes=32 time=48ms TTL=53
Reply from 74.125.43.104: bytes=32 time=64ms TTL=53
Reply from 74.125.43.104: bytes=32 time=49ms TTL=53
Reply from 74.125.43.104: bytes=32 time=52ms TTL=53
Reply from 74.125.43.104: bytes=32 time=52ms TTL=53
Reply from 74.125.43.104: bytes=32 time=48ms TTL=53
Reply from 74.125.43.104: bytes=32 time=48ms TTL=53
Reply from 74.125.43.104: bytes=32 time=48ms TTL=53
Reply from 74.125.43.104: bytes=32 time=53ms TTL=53
Reply from 74.125.43.104: bytes=32 time=49ms TTL=53
Reply from 74.125.43.104: bytes=32 time=48ms TTL=53
Reply from 74.125.43.104: bytes=32 time=48ms TTL=53
Reply from 74.125.43.104: bytes=32 time=62ms TTL=53
Reply from 74.125.43.104: bytes=32 time=48ms TTL=53
Reply from 74.125.43.104: bytes=32 time=58ms TTL=53
Reply from 74.125.43.104: bytes=32 time=48ms TTL=53
Reply from 74.125.43.104: bytes=32 time=66ms TTL=53
Reply from 74.125.43.104: bytes=32 time=76ms TTL=53
Reply from 74.125.43.104: bytes=32 time=48ms TTL=53
Reply from 74.125.43.104: bytes=32 time=85ms TTL=53
Reply from 74.125.43.104: bytes=32 time=90ms TTL=53
Reply from 74.125.43.104: bytes=32 time=97ms TTL=53
Reply from 74.125.43.104: bytes=32 time=48ms TTL=53
Reply from 74.125.43.104: bytes=32 time=48ms TTL=53
Reply from 74.125.43.104: bytes=32 time=49ms TTL=53
Reply from 74.125.43.104: bytes=32 time=49ms TTL=53
Reply from 74.125.43.104: bytes=32 time=49ms TTL=53
Reply from 74.125.43.104: bytes=32 time=47ms TTL=53
Reply from 74.125.43.104: bytes=32 time=48ms TTL=53

Ping statistics for 74.125.43.104:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 47ms, Maximum = 102ms, Average = 55ms

tech_guy

Thanks a lot. Now I have to find out if it is available in Loughlinstown South Dublin.

BigMoose

Tracing route to www.l.google.com [209.85.129.103]
over a maximum of 30 hops:

1 3 ms 1 ms 1 ms
2 5 ms 10 ms 10 ms WW04-fe-0-0-1-160-kilpoolehill.irishbroadband.ie
[87.192.124.1]
3 97 ms 4 ms 4 ms 89.127.192.61
4 7 ms 6 ms 6 ms 89.127.197.161
5 167 ms 80 ms 22 ms inex.google.com [193.242.111.57]
6 18 ms 22 ms 19 ms 72.14.239.132
7 54 ms 26 ms 73 ms 209.85.251.189
8 32 ms 32 ms 32 ms 209.85.250.141
9 32 ms 34 ms 33 ms 72.14.232.203
10 35 ms 32 ms 32 ms 72.14.233.206
11 33 ms 32 ms 32 ms 209.85.129.103

Trace complete.

I'm not the only one using the connection, although I dont think anything else is going mad at the mo.

tech_guy

Thanks for tracert. Any review 4mb breeze for someone in Loughlinstown South Dublin.