Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie
Help Keep Boards Alive. Support us by going ad free today. See here: https://subscriptions.boards.ie/

Any issues with IBB Breeze Access please post here. Help is always at hand

124

Comments

  • #92
    Drapper
    Registered Users, Registered Users 2 Posts: 3,814 ✭✭✭Drapper


    gline wrote:
    thats crazy, those pings are unacceptable, your right, they must think all people are dumb :(

    Mine are back down to 20 -30 again fingers crossed ! ofcourse it was not thier fault just some "external" router issue!!


  • #93
    spooky donkey
    Registered Users, Registered Users 2 Posts: 5,042 ✭✭✭spooky donkey


    I never got to check my pings after the call last night as I went out to see Star wars but giving me the whole they dont gurentee good pings all the time but bad pings for 5 days in a row is not acceptable. i`ll check it out tonight and see how it is and if its bad it will be monday before I can get on to them again. I dont have a home phone line and it cose mt 6 quid to ring them on my mobile after 6pm just to get my pings improved.


  • #94
    Velcrow
    Registered Users, Registered Users 2 Posts: 577 ✭✭✭Velcrow


    spooky donkey wrote:
    but bad pings for 5 days in a row is not acceptable

    I had the same problem / and still do - my pings can go from 50 to 450 to 900 - which makes it impossible to play games - they sent out the "man" and they moved me to another reciever in phibsborough... things improved but not greatly...one reason they gave me was if a building crane swings into the line of sight ..... :(


  • #95
    jesus_thats_gre
    Registered Users, Registered Users 2 Posts: 17,442 ✭✭✭✭jesus_thats_gre


    Hi Lads

    I emailed this to IBB support but thought I would throw it up here anyway:



    I connect to a CS:Source server, 82.138.226.130, regularly. While the ping times are generally very good, I keep getting severe instances of lag every 2 or 3 minutes.. It seems that there is quite a bit of packet loss.




    I done a ping test to the server and got the following results:


    First test:


    Pinging 82.138.226.130 with 32 bytes of data:

    Reply from 82.138.226.130: bytes=32 time=24ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=23ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=21ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=22ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=20ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=23ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=24ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=26ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=22ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=24ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=18ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=35ms 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=17ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=25ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=29ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=132ms TTL=120
    Request timed out.
    Reply from 82.138.226.130: bytes=32 time=26ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=19ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=22ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=18ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=22ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=25ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=20ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=20ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=21ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=26ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=17ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=26ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=25ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=19ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=25ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=33ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=16ms TTL=120
    Request timed out.
    Request timed out.
    Reply from 82.138.226.130: bytes=32 time=18ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=19ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=16ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=16ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=18ms 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=18ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=31ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=19ms TTL=120
    Request timed out.
    Reply from 82.138.226.130: bytes=32 time=25ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=20ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=766ms TTL=98
    Request timed out.
    Request timed out.
    Reply from 82.138.226.130: bytes=32 time=17ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=20ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=20ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=20ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=40ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=21ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=18ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=18ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=20ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=18ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=20ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=20ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=19ms 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=18ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=16ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=15ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=20ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=17ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=42ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=78ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=18ms TTL=120
    Request timed out.
    Reply from 82.138.226.130: bytes=32 time=17ms 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=26ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=25ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=19ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=19ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=24ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=21ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=18ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=18ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=18ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=19ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=19ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=39ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=20ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=21ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=21ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=24ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=21ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=18ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=23ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=20ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=23ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=18ms TTL=120
    Request timed out.
    Request timed out.
    Reply from 82.138.226.130: bytes=32 time=18ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=17ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=21ms TTL=120

    Ping statistics for 82.138.226.130:
    Packets: Sent = 109, Received = 100, Lost = 9 (8% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 15ms, Maximum = 766ms, Average = 30ms


    Out of curiosity I decided to ping another server as I thought it may have been something to do with one particular hop to the above:

    So I test it with www.boards.ie out of curiosity. Once again ping were very good but itere was a bit of packet loss and the odd spike:



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

    Request timed out.
    Reply from 82.195.136.36: bytes=32 time=7ms TTL=57
    Reply from 82.195.136.36: bytes=32 time=9ms TTL=57
    Reply from 82.195.136.36: bytes=32 time=9ms TTL=57

    Ping statistics for 82.195.136.36:
    Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 7ms, Maximum = 9ms, Average = 8ms






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

    Reply from 82.195.136.36: bytes=32 time=6ms TTL=57
    Request timed out.
    Reply from 82.195.136.36: bytes=32 time=8ms TTL=57
    Reply from 82.195.136.36: bytes=32 time=12ms TTL=57
    Reply from 82.195.136.36: bytes=32 time=8ms TTL=57
    Reply from 82.195.136.36: bytes=32 time=8ms TTL=57
    Reply from 82.195.136.36: bytes=32 time=10ms TTL=57
    Reply from 82.195.136.36: bytes=32 time=15ms TTL=57
    Reply from 82.195.136.36: bytes=32 time=9ms TTL=57
    Reply from 82.195.136.36: bytes=32 time=11ms TTL=57
    Reply from 82.195.136.36: bytes=32 time=8ms TTL=57
    Reply from 82.195.136.36: bytes=32 time=6ms TTL=57
    Reply from 82.195.136.36: bytes=32 time=7ms TTL=57
    Reply from 82.195.136.36: bytes=32 time=15ms TTL=57
    Reply from 82.195.136.36: bytes=32 time=9ms TTL=57
    Reply from 82.195.136.36: bytes=32 time=8ms TTL=57
    Reply from 82.195.136.36: bytes=32 time=7ms TTL=57
    Reply from 82.195.136.36: bytes=32 time=6ms TTL=57
    Reply from 82.195.136.36: bytes=32 time=9ms TTL=57
    Reply from 82.195.136.36: bytes=32 time=6ms TTL=57
    Reply from 82.195.136.36: bytes=32 time=7ms TTL=57
    Reply from 82.195.136.36: bytes=32 time=8ms TTL=57
    Reply from 82.195.136.36: bytes=32 time=7ms TTL=57
    Reply from 82.195.136.36: bytes=32 time=6ms TTL=57
    Reply from 82.195.136.36: bytes=32 time=8ms TTL=57
    Reply from 82.195.136.36: bytes=32 time=7ms TTL=57
    Reply from 82.195.136.36: bytes=32 time=6ms TTL=57
    Reply from 82.195.136.36: bytes=32 time=6ms TTL=57
    Reply from 82.195.136.36: bytes=32 time=5ms TTL=57
    Reply from 82.195.136.36: bytes=32 time=6ms TTL=57
    Reply from 82.195.136.36: bytes=32 time=6ms TTL=57
    Reply from 82.195.136.36: bytes=32 time=6ms TTL=57
    Reply from 82.195.136.36: bytes=32 time=5ms TTL=57
    Reply from 82.195.136.36: bytes=32 time=6ms TTL=57
    Request timed out.
    Reply from 82.195.136.36: bytes=32 time=7ms TTL=57
    Reply from 82.195.136.36: bytes=32 time=13ms TTL=57
    Reply from 82.195.136.36: bytes=32 time=7ms TTL=57
    Reply from 82.195.136.36: bytes=32 time=1238ms TTL=25
    Reply from 82.195.136.36: bytes=32 time=136ms TTL=57
    Reply from 82.195.136.36: bytes=32 time=5ms TTL=57
    Reply from 82.195.136.36: bytes=32 time=6ms TTL=57
    Reply from 82.195.136.36: bytes=32 time=5ms TTL=57
    Reply from 82.195.136.36: bytes=32 time=6ms TTL=57
    Reply from 82.195.136.36: bytes=32 time=5ms TTL=57
    Reply from 82.195.136.36: bytes=32 time=6ms TTL=57

    Ping statistics for 82.195.136.36:
    Packets: Sent = 46, Received = 44, Lost = 2 (4% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 5ms, Maximum = 1238ms, Average = 38ms



    Hopefully IBB will get back to me soon. Escalated under #47256.


  • #96
    spooky donkey
    Registered Users, Registered Users 2 Posts: 5,042 ✭✭✭spooky donkey


    well 2 call to them and still no joy for me.

    6 months with them and 3 months worth of provblems!

    I think they should introduce a cap to all users this no cap thing is not working. Im looking at caped sercives now as an option.


  • Advertisement
  • #97
    gline
    Registered Users, Registered Users 2 Posts: 6,605 ✭✭✭gline


    spooky donkey wrote:
    well 2 call to them and still no joy for me.

    6 months with them and 3 months worth of provblems!

    I think they should introduce a cap to all users this no cap thing is not working. Im looking at caped sercives now as an option.

    what difference is a cap?? u blaming heavy downloaders on your crap connection?? not true, there is enough bandwidth for everyone, just IBB are unreliable, doesnt matter where you live or what mast you are on, u can experience a bad connection from them, nothing to do with heavy downloaders


  • #98
    spooky donkey
    Registered Users, Registered Users 2 Posts: 5,042 ✭✭✭spooky donkey


    Well I dont know what else it can be. Every couple of months it goes bad again. Tiger woods could hit the transmitter from my house with a good drive so its not line of site.

    Also i get good pings at 2am, no use then.


  • #99
    gline
    Registered Users, Registered Users 2 Posts: 6,605 ✭✭✭gline


    spooky donkey wrote:

    Also i get good pings at 2am, no use then.

    heavy downloaders would have their pcs on at that hour happily downloading away. its just IBB , they arent reliable full stop


  • #100
    PowerHouseDan
    Registered Users, Registered Users 2 Posts: 6,658 ✭✭✭PowerHouseDan


    Ibb are pissing me off to say they least they dont give you a proper answer usually blame your router, rang 4 times this week no call back. At present i am gettin a connection of 190 both up and down,Just over isdn speeds.:mad:


  • #101
    Adey2002
    Closed Accounts Posts: 370 ✭✭Adey2002


    I'm having exatly the same problem as Jesus Thats Gre ... Pings are ok, but every couple of minutes it times out. Not very good for gaming at all. It's not a problem my end because I do a ping to my local node and no problems. It's something beyond that that is causing the problem.


  • Advertisement
  • #102
    Adey2002
    Closed Accounts Posts: 370 ✭✭Adey2002


    Garfield,
    Heres some info for you on the problem at the moment, if you could look into it I would appreciate it. I have sent emails to support, but they are being ignored.

    Every 30-40 seconds, I lose connection for a couple of seconds.. Not very good for web phone or gaming etc..
    I did a tracert/ping and got...
    Pinging my local node (SIAC - 83.141.84.65) returns 100% at 3ms - perfect.
    Pingint the next hop (3rock - 62.231.52.169) returns 100% at max 20ms - still perfect
    I'm not sure if this has anything to do with it but the next hop switches between rte 62.231.32.182 and 62.231.52.186 when retrying the tracert. RTE returns 100%, but the other one times out about 15-20% of the time.

    Aynway, if you could have a look I would appreciate it.


  • #103
    jleavy046
    Closed Accounts Posts: 155 ✭✭jleavy046


    Hi folks,
    1mb Breeze on TreeRock mast. Will I have a Fixed IP address?

    BTW:
    Thursday night last, TreeRock was covered by a very mist/fog /whatever. I had no RipWave. Will it be the same on Breeze?

    Joe Leavy
    (Sanyford Road)


  • #104
    enno
    Registered Users, Registered Users 2 Posts: 26 ✭enno


    jleavy046 wrote:
    Hi folks,
    1mb Breeze on TreeRock mast. Will I have a Fixed IP address?
    If my experience is anything to go by, you most likely will have a fixed IP address.
    jleavy046 wrote:
    BTW:
    Thursday night last, TreeRock was covered by a very mist/fog /whatever. I had no RipWave. Will it be the same on Breeze?

    Joe Leavy
    (Sanyford Road)

    Three Rock may have had a bad hair day on Thursday. As shown by
    my automatic monitoring, my Breeze connection dropped some time
    before noon, and didn't recover until after 22:00 when I noticed and
    power-cycled the POE box. Graph should be attached.

    I've asked for an explanation. I'll not hold my breath.


  • #105
    jleavy046
    Closed Accounts Posts: 155 ✭✭jleavy046


    enno wrote:
    As shown by my automatic monitoring, my Breeze connection dropped some time before noon, and didn't recover until after 22:00 when I noticed and power-cycled the POE box. Graph should be attached.

    Can i ask what tool you are using?

    Can this tool be used to sent an SMS alert or sommit?


  • #106
    vinks
    Closed Accounts Posts: 191 ✭✭vinks


    jleavy046 wrote:
    Can i ask what tool you are using?

    Can this tool be used to sent an SMS alert or sommit?

    it looks like smokeping that he is running to monitor his connection, i use smokeping to monitor my connection and i noticed my connection dropped out for about an hour that day as well. it wasnt gone for more than an hour.


  • #107
    sikes
    Registered Users, Registered Users 2 Posts: 2,563 ✭✭✭sikes


    he is my ping result for my local statio, killiney

    --- 83.141.84.129 ping statistics ---
    71 packets transmitted, 58 received, 18% packet loss, time 70047ms
    rtt min/avg/max/mdev = 1.888/4.628/142.935/18.324 ms, pipe 2

    this is what its like all the time. what could be causing it? ibb have been no help and havent had a chance to call them again. will do again on monday if i get a chance.


  • #108
    enno
    Registered Users, Registered Users 2 Posts: 26 ✭enno


    vinks wrote:
    it looks like smokeping that he is running to monitor his connection ...
    That's right. Nifty tool. Find out more if you want from
    http://people.ee.ethz.ch/~oetiker/webtools/smokeping/


  • #109
    enno
    Registered Users, Registered Users 2 Posts: 26 ✭enno


    jleavy046 wrote:
    Can this tool be used to sent an SMS alert or sommit?
    Yes, if you can receive e-mail via SMS.


  • #110
    gsand
    Closed Accounts Posts: 414 ✭✭gsand


    after a few phone calls last week ibb came out and upgraded my equipment(im still miffed as to why they dont do this without me nagging them for the last 6 months but anyway)-guys were on time, came prepared and got the upgrade done swiftly-i was installed increased to 2megs from 512 and not only is it obviously a good deal faster speed wise but it appears to be more consistent....

    im not too demanding, i mean anything over 100k seems nice atm but i havnt had any really bad speeds at all aka 6-10k on 512k for long stretches...

    im on 3 rock and the service seems well solid-maybe its the vl gear, maybe its the upgrade, maybe its the product but its a big improvement and will certainly stop me moaning...for now :)


  • #111
    Drapper
    Registered Users, Registered Users 2 Posts: 3,814 ✭✭✭Drapper


    http://www.boards.ie/vbulletin/showthread.php?t=258724

    any comments lads?


  • Advertisement
  • #112
    jleavy046
    Closed Accounts Posts: 155 ✭✭jleavy046


    enno wrote:
    That's right. Nifty tool. Find out more if you want from
    http://people.ee.ethz.ch/~oetiker/webtools/smokeping/

    Hmm....not for Windowz i guess? :( Any other suggestions?

    Joe Leavy


  • #113
    Drapper
    Registered Users, Registered Users 2 Posts: 3,814 ✭✭✭Drapper


    jleavy046 wrote:
    Hmm....not for Windowz i guess? :( Any other suggestions?

    Joe Leavy

    www.HLSW.net

    game programme but good traceroute programme too


  • #114
    Couch Potato
    Registered Users, Registered Users 2 Posts: 481 ✭✭Couch Potato


    Getting a whopping 159kbs down/153kbs up to Ballycoolin ....

    What is going on ?????????

    It was grand before 6pm /????


    Ping statistics for 83.141.106.65:
    Packets: Sent = 20, Received = 19, Lost = 1 (5% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 3ms, Maximum = 306ms, Average = 41ms


  • #115
    pete
    Registered Users, Registered Users 2 Posts: 1,733 ✭✭✭pete


    Couch Potato wrote:
    Getting a whopping 159kbs down/153kbs up to Ballycoolin ....

    What is going on ?????????

    It was grand before 6pm /????


    Ping statistics for 83.141.106.65:
    Packets: Sent = 20, Received = 19, Lost = 1 (5% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 3ms, Maximum = 306ms, Average = 41ms

    I'm on ballycoolin too - here's what i'm seeing:
    Tracing route to www.boards.ie [82.195.136.36]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms . [192.168.2.1]
    2 3 ms 9 ms 7 ms ballycoolin-vl-vlan-3.irishbroadband.ie [62.231.44.65]
    3 6 ms 10 ms 7 ms DN03-fe-1-3-1-30-tallaght.irishbroadband.ie [62.231.32.145]
    4 16 ms 15 ms 25 ms DN42-as1-0-ibis-access.irishbroadband.ie [62.231.52.134]
    5 27 ms 32 ms 19 ms DN42-ae0-50-ibis-gw.irishbroadband.ie [62.231.52.157]
    6 12 ms 7 ms 9 ms suez-inex.hosting365.ie [193.242.111.23]
    7 13 ms 13 ms 52 ms 82.195.128.7
    8 15 ms 12 ms 8 ms www.boards.ie [82.195.136.36]

    Trace complete.

    http://www.adslguide.org.uk/tools/speedtest.asp says:
    Downstream 1012 Kbps (126.5 KB/sec) 1092 Kbps (inc. overheads)
    Upstream 935 Kbps (116.9 KB/sec) 1009 Kbps (inc. overheads)


  • #116
    Couch Potato
    Registered Users, Registered Users 2 Posts: 481 ✭✭Couch Potato


    I am on 2mb breeze to Ballycoolin - :mad: :mad: :mad:

    C:\>tracert www.boards.ie

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

    1 * 184 ms 99 ms DN40-ballycoolin-lo0.irishbroadband.ie [83.141.106.65]
    2 212 ms 107 ms 146 ms DN03-fe-1-3-1-30-tallaght.irishbroadband.ie [62.231.32.145]
    3 * 160 ms 122 ms DN42-as1-0-ibis-access.irishbroadband.ie [62.231.52.134]
    4 136 ms 135 ms 130 ms DN42-ae0-50-ibis-gw.irishbroadband.ie [62.231.52.157]
    5 137 ms 147 ms 191 ms suez-inex.hosting365.ie [193.242.111.23]
    6 * 117 ms 118 ms 82.195.128.7
    7 128 ms 142 ms 128 ms boards.ie [82.195.136.36]

    Trace complete.


  • #117
    Blaster99
    Closed Accounts Posts: 2,630 ✭✭✭Blaster99


    So where is this help that's always at hand?


  • #118
    spooky donkey
    Registered Users, Registered Users 2 Posts: 5,042 ✭✭✭spooky donkey


    Its not very fourth comming these days. That was why I started my own thread with my own problem. I also have all the info I need on that thread for when I ring tech support. When ever I ring now for tech support I get them to look at it to see all my trace routes and bad pings.


  • #119
    pete
    Registered Users, Registered Users 2 Posts: 1,733 ✭✭✭pete


    Couch Potato wrote:
    I am on 2mb breeze to Ballycoolin - :mad: :mad: :mad:

    C:\>tracert www.boards.ie

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

    1 * 184 ms 99 ms DN40-ballycoolin-lo0.irishbroadband.ie [83.141.106.65]
    2 212 ms 107 ms 146 ms DN03-fe-1-3-1-30-tallaght.irishbroadband.ie [62.231.32.145]
    3 * 160 ms 122 ms DN42-as1-0-ibis-access.irishbroadband.ie [62.231.52.134]
    4 136 ms 135 ms 130 ms DN42-ae0-50-ibis-gw.irishbroadband.ie [62.231.52.157]
    5 137 ms 147 ms 191 ms suez-inex.hosting365.ie [193.242.111.23]
    6 * 117 ms 118 ms 82.195.128.7
    7 128 ms 142 ms 128 ms boards.ie [82.195.136.36]

    Trace complete.
    that first hop alone looks totally ropey.

    as an aside - i didn't think anyone on ballycoolin was on 2mb. most importantly, i know I'm not....


  • #120
    parasite
    Registered Users, Registered Users 2 Posts: 2,078 ✭✭✭parasite


    sorry if this has been asked before (or is appropriate for this thread), but if i put in an order and I pass an los test, am i obliged to proceed, has the contract already started ..?
    just want to keep my options open ... >_>


  • Advertisement
  • #121
    jesus_thats_gre
    Registered Users, Registered Users 2 Posts: 17,442 ✭✭✭✭jesus_thats_gre


    I doubt you are obliged.. Not sure though..


Advertisement