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

Are Eircom happy to ignore Residential customers since they feel no threat from UPC?

Options
13»

Comments

  • Closed Accounts Posts: 11,631 ✭✭✭✭Hank Scorpio


    Can an Eircom rep give a final verdict on this situation


  • Closed Accounts Posts: 11,631 ✭✭✭✭Hank Scorpio


    C:\Users\xxxx PC>ping 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=367ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=289ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=330ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=364ms TTL=58

    Ping statistics for 86.43.38.8:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 289ms, Maximum = 367ms, Average = 337ms

    e6vsxl.png


  • Closed Accounts Posts: 71 ✭✭Wireless net


    eircom ping on DSL is very erratic of late, see below the best pings i was seeing on a line that i manage, this erratic latency kills of FTP jobs that i have running in remote offices, every night around 1am..... it goes as high as 1000ms +

    eircom constantly say there is no problem, and have spent lots of time looking into the issue, without resolution!



    64 bytes from 86.43.38.8: icmp_seq=4 ttl=58 time=98.654 ms
    64 bytes from 86.43.38.8: icmp_seq=5 ttl=58 time=74.944 ms
    64 bytes from 86.43.38.8: icmp_seq=6 ttl=58 time=82.498 ms
    64 bytes from 86.43.38.8: icmp_seq=7 ttl=58 time=90.267 ms
    64 bytes from 86.43.38.8: icmp_seq=8 ttl=58 time=95.615 ms
    64 bytes from 86.43.38.8: icmp_seq=9 ttl=58 time=94.400 ms
    64 bytes from 86.43.38.8: icmp_seq=10 ttl=58 time=117.253 ms
    64 bytes from 86.43.38.8: icmp_seq=11 ttl=58 time=81.747 ms
    64 bytes from 86.43.38.8: icmp_seq=12 ttl=58 time=79.627 ms
    64 bytes from 86.43.38.8: icmp_seq=13 ttl=58 time=94.020 ms
    64 bytes from 86.43.38.8: icmp_seq=14 ttl=58 time=95.536 ms
    64 bytes from 86.43.38.8: icmp_seq=15 ttl=58 time=99.368 ms
    64 bytes from 86.43.38.8: icmp_seq=16 ttl=58 time=99.209 ms
    64 bytes from 86.43.38.8: icmp_seq=17 ttl=58 time=90.266 ms
    64 bytes from 86.43.38.8: icmp_seq=18 ttl=58 time=87.331 ms
    64 bytes from 86.43.38.8: icmp_seq=19 ttl=58 time=96.008 ms
    64 bytes from 86.43.38.8: icmp_seq=20 ttl=58 time=97.606 ms
    64 bytes from 86.43.38.8: icmp_seq=21 ttl=58 time=87.134 ms
    64 bytes from 86.43.38.8: icmp_seq=22 ttl=58 time=83.078 ms
    64 bytes from 86.43.38.8: icmp_seq=23 ttl=58 time=92.455 ms
    64 bytes from 86.43.38.8: icmp_seq=24 ttl=58 time=100.937 ms
    64 bytes from 86.43.38.8: icmp_seq=25 ttl=58 time=91.674 ms
    64 bytes from 86.43.38.8: icmp_seq=26 ttl=58 time=86.186 ms
    64 bytes from 86.43.38.8: icmp_seq=27 ttl=58 time=87.549 ms
    64 bytes from 86.43.38.8: icmp_seq=28 ttl=58 time=98.644 ms
    64 bytes from 86.43.38.8: icmp_seq=29 ttl=58 time=79.749 ms
    64 bytes from 86.43.38.8: icmp_seq=30 ttl=58 time=96.643 ms
    64 bytes from 86.43.38.8: icmp_seq=31 ttl=58 time=101.901 ms
    64 bytes from 86.43.38.8: icmp_seq=32 ttl=58 time=85.739 ms
    64 bytes from 86.43.38.8: icmp_seq=33 ttl=58 time=98.030 ms
    64 bytes from 86.43.38.8: icmp_seq=34 ttl=58 time=95.419 ms
    64 bytes from 86.43.38.8: icmp_seq=35 ttl=58 time=90.462 ms
    64 bytes from 86.43.38.8: icmp_seq=36 ttl=58 time=86.702 ms
    64 bytes from 86.43.38.8: icmp_seq=37 ttl=58 time=89.055 ms


  • Registered Users Posts: 986 ✭✭✭Fogmatic


    Just in case you weren't aware of it nuxxx, it's not only the Broadband forum that overlaps with this one subject-wise; there's also Nets & Comms, & Ireland Offline (which is under Hosted). I'm no expert, but have even found helpful info in the Servers & Systems forum.
    Threads are quite often moved from one to another (whether by the OP or a Mod), if they're not in the ideal forum, or if the focus of the discussion changes.


  • Closed Accounts Posts: 11,631 ✭✭✭✭Hank Scorpio


    Thanks, I'm aware of the other forums. I think this forum is ok in relation to the thread(s) I created, unhappy Eircom customer posts in Eircom consumer forum. :)


  • Advertisement
  • Registered Users Posts: 3,712 ✭✭✭Praetorian


    nuxxx wrote: »
    Thanks, I'm aware of the other forums. I think this forum is ok in relation to the thread(s) I created, unhappy Eircom customer posts in Eircom consumer forum. :)

    "Are Eircom happy to ignore Residential customers since they feel no threat from UPC?"

    Sometimes Eircom don't bother to reply to threads at all :)


  • Registered Users Posts: 986 ✭✭✭Fogmatic


    Maybe worth starting a new thread nuxxx (if you have any energy left)? (Using cut-& paste to minimise retyping?)
    This one's taking a long time to read though now.
    And hope you don't mind me saying, but the question doesn't exactly shout "easy to answer"!

    Your earlier thread seems to be addressed to fellow users, with Eircom juggling conversations with all comers instead of focusing on your particular case.

    This forum does seem to need patience. Apart from the Eircom people's limited numbers & hours, experts aren't often the clearest communicaters.


  • Closed Accounts Posts: 11,631 ✭✭✭✭Hank Scorpio


    Not making another thread, already made two and its getting me no where :(. Thanks for your input. Not trying to be smart but I think 10 months is enough patience. :)

    Pinging home.eircom.net [86.43.38.8] with 32 bytes of data:
    Reply from 86.43.38.8: bytes=32 time=336ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=272ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=230ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=279ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=323ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=300ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=327ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=325ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=315ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=321ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=324ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=214ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=214ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=242ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=226ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=258ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=272ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=305ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=352ms TTL=58
    Request timed out.
    Reply from 86.43.38.8: bytes=32 time=294ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=328ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=331ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=372ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=230ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=278ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=326ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=347ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=245ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=215ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=309ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=330ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=344ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=310ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=369ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=329ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=362ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=228ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=267ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=305ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=360ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=345ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=355ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=269ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=335ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=356ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=351ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=266ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=322ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=274ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=295ms TTL=58

    2hzinur.png

    Editing my post, posted in an angry manner. Problem still has not been corrected. Could an Eircom rep just tell me to stop wasting my time or something, at least then I`ll give up any string of hope I got left to get this fixed.


  • Registered Users Posts: 413 ✭✭neiphin


    Eircom are a joke, I have a friend who's phone line stopped working, eircom came out and said the fault is inside their property under the ground and are refusing to do anything. I no they have the equipment to do it and it wouldn't take long to run in a new cable just to the front door. Shower of lazy you know what.
    to be fair ,its not the employees, its the company , penny pinching dragging the last cent out, screwing the people for the very last penny
    i hold no gra for eircon
    but the workers are not the enemy


  • Registered Users Posts: 986 ✭✭✭Fogmatic


    I agree with neiphin.
    After years of frustration & aggravation with Eircom's helpline etc, it took an engineer on the ground to tell us that our line could only ever support a theoretical maximum of 16 kbps. And that was only thanks to my sharp-eyed spouse spotting him at work re one of our regular fault reports, and rushing out & buttonholing him (the schedules they're given don't allow time for talk).


  • Advertisement
  • Closed Accounts Posts: 11,631 ✭✭✭✭Hank Scorpio


    Reply from 86.43.38.8: bytes=32 time=355ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=335ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=365ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=296ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=279ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=377ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=332ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=317ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=350ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=318ms TTL=58


  • Closed Accounts Posts: 11,631 ✭✭✭✭Hank Scorpio


    Pinging home.eircom.net [86.43.38.8] with 32 bytes of data:
    Reply from 86.43.38.8: bytes=32 time=322ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=346ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=351ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=213ms TTL=58

    Ping statistics for 86.43.38.8:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 213ms, Maximum = 351ms, Average = 308ms


  • Closed Accounts Posts: 11,631 ✭✭✭✭Hank Scorpio


    :mad:


  • Registered Users Posts: 67 ✭✭.Bob


    nuxxx wrote: »
    :mad:

    :)


  • Closed Accounts Posts: 11,631 ✭✭✭✭Hank Scorpio


    jr4dba.png


  • Closed Accounts Posts: 77 ✭✭IE2012


    nuxxx wrote: »
    Contacted comreg about this, unfortunately didn't help.

    Tonight :)

    Reply from 86.43.38.8: bytes=32 time=288ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=247ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=201ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=188ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=159ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=213ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=182ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=141ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=109ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=77ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=225ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=251ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=229ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=171ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=153ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=195ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=223ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=184ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=208ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=218ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=219ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=231ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=268ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=289ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=162ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=173ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=124ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=154ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=231ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=178ms TTL=58
    Reply from 86.43.38.8: bytes=32 time=201ms TTL=58

    Here's my brother on his UPC connection to the same eircom.net address

    Reply from 86.43.38.8: bytes=32 time=13ms TTL=55
    Reply from 86.43.38.8: bytes=32 time=14ms TTL=55
    Reply from 86.43.38.8: bytes=32 time=14ms TTL=55
    Reply from 86.43.38.8: bytes=32 time=13ms TTL=55
    Reply from 86.43.38.8: bytes=32 time=13ms TTL=55

    :(

    i had the same problem with eircom and high ping times, on one of our lines, I moved it to vodafone and the connection is vastly better


    68898868.png

    however lost 1MB in doing so, but the latency is much lower now, router now syncing as ADSL2 , where as before with eircom was GDMT.

    2157353879.png

    2157361991.png

    68899378.png



    ping www.eircom.net -t

    Pinging home.eircom.net [86.43.38.8] with 32 bytes of data
    Reply from 86.43.38.8: bytes=32 time=14ms TTL=54
    Reply from 86.43.38.8: bytes=32 time=13ms TTL=54
    Reply from 86.43.38.8: bytes=32 time=14ms TTL=54
    Reply from 86.43.38.8: bytes=32 time=14ms TTL=54
    Reply from 86.43.38.8: bytes=32 time=14ms TTL=54
    Reply from 86.43.38.8: bytes=32 time=12ms TTL=54
    Reply from 86.43.38.8: bytes=32 time=14ms TTL=54
    Reply from 86.43.38.8: bytes=32 time=14ms TTL=54
    Reply from 86.43.38.8: bytes=32 time=13ms TTL=54
    Reply from 86.43.38.8: bytes=32 time=14ms TTL=54
    Reply from 86.43.38.8: bytes=32 time=14ms TTL=54
    Reply from 86.43.38.8: bytes=32 time=13ms TTL=54
    Reply from 86.43.38.8: bytes=32 time=13ms TTL=54
    Reply from 86.43.38.8: bytes=32 time=14ms TTL=54
    Reply from 86.43.38.8: bytes=32 time=13ms TTL=54
    Reply from 86.43.38.8: bytes=32 time=15ms TTL=54
    Reply from 86.43.38.8: bytes=32 time=13ms TTL=54
    Reply from 86.43.38.8: bytes=32 time=14ms TTL=54
    Reply from 86.43.38.8: bytes=32 time=14ms TTL=54
    Reply from 86.43.38.8: bytes=32 time=13ms TTL=54
    Reply from 86.43.38.8: bytes=32 time=14ms TTL=54
    Reply from 86.43.38.8: bytes=32 time=14ms TTL=54


  • Closed Accounts Posts: 11,631 ✭✭✭✭Hank Scorpio


    Good to see you got sorted, mines still as bad as ever unfortunately


  • Registered Users Posts: 986 ✭✭✭Fogmatic




  • Closed Accounts Posts: 7,230 ✭✭✭Solair


    I love the way they say "your line has failed" as if it's some kind of issue caused by your failing to take care of the line properly or something.

    They never say "Sorry, our line has failed to provide adequate service as we haven't spent any money in your area since ... (insert year)."


  • Registered Users Posts: 986 ✭✭✭Fogmatic


    And the way their tech people fnd that my email is 'working perfecly'...

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


  • Advertisement
Advertisement