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

ping is dreadful for the last 4 nights

Options
  • 09-07-2012 10:59pm
    #1
    Headshot
    Registered Users Posts: 54,341 ✭✭✭✭


    So I rang eircom support on Saturday and was told they'll investigate it

    Ping is all over the place tonight 100ms using eircoms speed test. The jitter is the biggest headache, its just not steady, my ping is constantly up and down

    Im wondering has the engineer looked into the problem at the exchange yet?

    my broadband specs

    eircom Broadband: Connected
    DSL Mode: ADSL_G.dmt
    Speed: 3072 kbps /384 kbps
    Line Attenuation (Down/Up): 10 dB /7 dB
    DSL Noise Margin: 28 dB /15 dB
    WAN IP Address: 86.41.118.112
    Default Gateway: 159.134.155.2
    First DNS: 159.134.0.1(dns1.eircom.net)
    Secondary DNS: 159.134.0.2(dns2.eircom.net)
    Tertiary DNS: 0.0.0.0

    Iv no other connections in use so to get such crap ping is very frustrating


Comments

  • Options
    #2
    eircom: Ant
    Closed Accounts Posts: 1,138 ✭✭✭eircom: Ant


    Headshot wrote: »
    So I rang eircom support on Saturday and was told they'll investigate it

    Ping is all over the place tonight 100ms using eircoms speed test. The jitter is the biggest headache, its just not steady, my ping is constantly up and down

    Im wondering has the engineer looked into the problem at the exchange yet?

    my broadband specs

    eircom Broadband: Connected
    DSL Mode: ADSL_G.dmt
    Speed: 3072 kbps /384 kbps
    Line Attenuation (Down/Up): 10 dB /7 dB
    DSL Noise Margin: 28 dB /15 dB
    WAN IP Address: 86.41.118.112
    Default Gateway: 159.134.155.2
    First DNS: 159.134.0.1(dns1.eircom.net)
    Secondary DNS: 159.134.0.2(dns2.eircom.net)
    Tertiary DNS: 0.0.0.0

    Iv no other connections in use so to get such crap ping is very frustrating


    Hi Headshot,

    I've checked with Broadband Support. They've advised your broadband speed was reported at an average speed of 2.5Mb. or the norm for a 3Mb connection. Your connection on the eircom authentication server was and still is relatively solid - Alive.

    Generally, unless the ping results are above 85ms, you shouldn't need to worry, providing you're getting the correct average speed. Broadband Support report your ping tests showed 77 and 85 ms (and may be from the speedtest website). While a direct ping test to eircom.net resulted in 33ms.

    Can you try a ping test from your computer using the command prompt to confirm this again. Check if your ping results are over 100ms when you ping www.eircom.net .
    PM me if necessary with the results, along with a mobile contact number in case anengineer needs to call you directly, once this is escalated.

    I will PM you with your case reference from Broadband support.


    Broadband Technical Support : 1890 260260 (locall); Hours : 08:00 - 22:00 (7 days).

    Best wishes,
    Ant


  • Options
    #3
    Headshot
    Registered Users Posts: 54,341 ✭✭✭✭Headshot


    Again tonight my ping is all over the place

    using eircoms speed test im over 90ms

    using cmd I get a requested timed out and then I keep trying it and eventually I get Minimum = 47ms, Maximum = 94ms, Average = 67ms

    That certainly isnt my usual. I use to get better results than this

    Ant you dont get it. My ping is up and down, just not stable

    btw I didnt get your pm which doesnt surprise me with eircom

    The person I was talking to on the phone on saturday notice something wrong with my connection and was told they'll get an engineer to check it out

    Its really frustrating being with eircom, get treated like im making things up


  • Options
    #4
    eircom: Ant
    Closed Accounts Posts: 1,138 ✭✭✭eircom: Ant


    Headshot wrote: »
    Again tonight my ping is all over the place

    using eircoms speed test im over 90ms

    using cmd I get a requested timed out and then I keep trying it and eventually I get Minimum = 47ms, Maximum = 94ms, Average = 67ms

    That certainly isnt my usual. I use to get better results than this

    Ant you dont get it. My ping is up and down, just not stable

    btw I didnt get your pm which doesnt surprise me with eircom

    The person I was talking to on the phone on saturday notice something wrong with my connection and was told they'll get an engineer to check it out

    Its really frustrating being with eircom, get treated like im making things up


    Thanks Headshot and apologies for the delay.

    I have been checking your phoneline and have noticed there is a fault. I wanted to be sure after rechecking your phoneline that the fault was re-occurring.

    I've re-logged this with our Faults Team and have sent you a PM with your case reference.

    Please temporarily remove any private equipment from your internal phoneline, while engineers are testing over the next few days. (e.g: Sky box(s), fax, private phone cable, etc. )

    Previously I had checked your broadband sync results. Broadband Support had earlier opened a case which I have updated with your recent sync results as well as your phoneline stats. Both these did appear to be fine when I had checked your stats yesterday afternoon. I have sent you more information on this by PM. The broadband case logged by Broadband Support will now be superseded by your current phoneline fault (Please see your ref on the PM. You can also quote this reference, if you need to call Phoneline Faults for an update (See contact and 'My eircom' information below)

    Once your phoneline fault is repaired, please re-check your ping results. If possible try to use your computer's command prompt solely and ignore the results you get from the Speedtest website at the moment (just in case the website is inaccurate).

    I'm hoping that the phoneline fault is the cause of your intermittent ping.

    Let me know if your ping times improve after your phoneline has been repaired.

    If you need an update at any time you can check this on our 'My eircom' service, below:

    www.eircom.net/myeircom

    'My eircom' - Help & Support, Check BB Usage, See current products -View or Pay your bill online - bit.ly/myeircom - 'My eircom'

    You can also freecall 1901 and check the status of your phoneline fault at any time.

    Best wishes,
    Ant


  • Options
    #5
    Headshot
    Registered Users Posts: 54,341 ✭✭✭✭Headshot


    Ant im sorry to say that fix hasnt worked

    have a look at this

    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.

    ping -t www.eircom.net

    Pinging home.eircom.net [86.43.38.8] with 32 bytes of data:
    Reply from 86.43.38.8: bytes=32 time=58ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=69ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=96ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=86ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=82ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=81ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=77ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=90ms TTL=57
    Request timed out.
    Reply from 86.43.38.8: bytes=32 time=70ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=107ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=99ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=75ms TTL=57
    Request timed out.
    Reply from 86.43.38.8: bytes=32 time=71ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=55ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=57ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=63ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=91ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=88ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=69ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=68ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=85ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=85ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=56ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=73ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=46ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=36ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=59ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=97ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=36ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=40ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=34ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=39ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=35ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=39ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=42ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=80ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=57ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=54ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=53ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=40ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=43ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=47ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=76ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=75ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=73ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=44ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=65ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=73ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=58ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=47ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=36ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=73ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=40ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=69ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=77ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=58ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=38ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=90ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=74ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=63ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=77ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=90ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=69ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=79ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=90ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=88ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=40ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=79ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=90ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=70ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=72ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=54ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=71ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=42ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=34ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=37ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=63ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=90ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=52ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=52ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=47ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=35ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=48ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=41ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=50ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=73ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=61ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=36ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=49ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=49ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=73ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=47ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=47ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=67ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=72ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=42ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=46ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=75ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=47ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=69ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=52ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=68ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=103ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=60ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=89ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=41ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=38ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=40ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=40ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=52ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=49ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=53ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=52ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=231ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=52ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=41ms TTL=57
    Request timed out.
    Request timed out.
    Reply from 86.43.38.8: bytes=32 time=68ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=49ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=49ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=110ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=170ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=82ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=181ms TTL=57

    I could keep going with results but it gives you an idea how bad its at the moment


  • Options
    #6
    Hank Scorpio
    Closed Accounts Posts: 11,631 ✭✭✭✭Hank Scorpio


    Mine was like that a while back, its much worse now. Wouldn't hold out much hope


  • Advertisement
  • Options
    #7
    Headshot
    Registered Users Posts: 54,341 ✭✭✭✭Headshot


    There shouldnt be an excuse since I live a few seconds from the exchange


  • Options
    #8
    Hank Scorpio
    Closed Accounts Posts: 11,631 ✭✭✭✭Hank Scorpio


    Me 2, its literally a 20 second walk from here. Problem is congestion


  • Options
    #9
    Headshot
    Registered Users Posts: 54,341 ✭✭✭✭Headshot


    Hello eircom representative how come you havent replied

    New stats


    ping -t www.eircom.net

    Pinging home.eircom.net [86.43.38.8] with 32 bytes of data:
    Reply from 86.43.38.8: bytes=32 time=68ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=75ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=107ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=94ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=96ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=84ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=70ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=73ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=93ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=60ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=79ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=82ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=88ms TTL=57
    Request timed out.
    Reply from 86.43.38.8: bytes=32 time=91ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=87ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=79ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=69ms TTL=57


    Its atrocious readings


  • Options
    #10
    eircom: Ant
    Closed Accounts Posts: 1,138 ✭✭✭eircom: Ant


    Headshot wrote: »
    Ant im sorry to say that fix hasnt worked

    have a look at this


    I could keep going with results but it gives you an idea how bad its at the moment


    Thanks Headshot,

    Appreciate the reply.

    I checked the phoneline fault logged with the Faults team and this was resolved on the 12/07/2012. I've retested the phoneline and this is showing no faults. That's not to say it is a definite that the phone line is working perfectly. If necessary I can re-escalate the phoneline fault with the Faults team.

    As for broadband, it appears to be syncing perfect from what I see up to the main socket in your premises, with excellent attainable rates.

    Port is UP (has sync) and status is NORMAL
    Synced at: 3072kbps
    Attenuation: Up: 6.9dB Down: 11dB (v/good)
    Noise margin: Up: 21.9dB Down: 26.5dB (v/good)

    As previously, Broadband Support tend not too worry once your ping results are below 85ms.

    My concern would be your actual phone line. Again, it may be best to re-escalate this as a fault. Any improvement here would certainly have a knock on effect on your broadband.

    If you want to check your broadband directly with a Technician, call Technical Support directly. Quote your last case id or phone number and they will re-check or escalate if necessary.

    Best regards,
    Ant


  • Options
    #11
    Headshot
    Registered Users Posts: 54,341 ✭✭✭✭Headshot


    Have you checked your system last night? Each night between 9 and midnight, my ping is all over the place as you can see from the ping -t


  • Advertisement
Advertisement