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

Many sites extremely slow/unusable (past week on eFibre)

Options
1235713

Comments

  • Banned (with Prison Access) Posts: 10 trapattack


    Gone to crap again, have to purchase a VPN to get sites to load.

    Will ye for the love of god getting a simple issue fixed.


  • Registered Users Posts: 7 Niallthebomb


    Having read this thread earlier today.

    Just wanted to add my observations.

    E-fibre Customer here.

    Speedtest working fine. Downloads in general working ok.

    Did a couple of tracerts to the problem sites posted in earlier posts this afternoon @ 2pm'ish.

    These were using the eircom DNS.

    C:\Windows\system32>tracert cnn-f.akamaihd.net

    Tracing route to a513.w23.akamai.net [92.123.72.119]

    over a maximum of 30 hops:

     1     1 ms     1 ms    <1 ms  MitraStar.Home [192.168.1.254]

     2     9 ms    11 ms     6 ms  86-44-82-1-dynamic.agg2.mhz.blp-srl.eircom.net [86.44.82.1]

     3     5 ms     4 ms     4 ms  86.43.12.157

     4     5 ms     5 ms     5 ms  tenge-5-2-1.core2.bdt.core.eircom.net [86.43.253.5]

     5     6 ms     7 ms     5 ms  86.43.13.154

     6     6 ms     5 ms     6 ms  83.71.115.186

     7     7 ms     8 ms     6 ms  inex-dub1.netarch.akamai.com [193.242.111.55]

     8     7 ms     7 ms     6 ms  a92-123-72-119.deploy.akamaitechnologies.com [92.123.72.119]

    Trace complete.

    C:\Windows\system32>tracert youtube.com

    Tracing route to youtube.com [74.125.138.190]

    over a maximum of 30 hops:

     1    <1 ms    <1 ms     2 ms  MitraStar.Home [192.168.1.254]

     2     5 ms     4 ms     8 ms  86-44-82-1-dynamic.agg2.mhz.blp-srl.eircom.net [86.44.82.1]

     3     5 ms     *        7 ms  86.43.12.161

     4     9 ms     7 ms     8 ms  86.43.252.88

     5     7 ms     6 ms     6 ms  lag-1.core2.prp.core.eircom.net [86.43.252.50]

     6     *        8 ms     6 ms  86.47.63.110

     7     6 ms     6 ms     6 ms  72.14.205.72

     8     7 ms     6 ms     6 ms  209.85.252.198

     9     7 ms     8 ms     6 ms  209.85.253.125

    10     *        *        *     Request timed out.

    11     6 ms     6 ms     6 ms  dn-in-f190.1e100.net [74.125.138.190]

    Trace complete.

    Just did a couple more @ 21.30 (still using Eircom DNS)

    C:\Windows\system32>tracert youtube.com

    Tracing route to youtube.com [74.125.24.93]

    over a maximum of 30 hops:

     1     1 ms     2 ms     1 ms  MitraStar.Home [192.168.1.254]

     2    18 ms     6 ms     9 ms  86-44-82-1-dynamic.agg2.mhz.blp-srl.eircom.net [86.44.82.1]

     3    15 ms     6 ms     6 ms  86.43.12.157

     4     6 ms     6 ms     7 ms  tenge-6-1-1.core2.srl.core.eircom.net [86.43.253.137]

     5     8 ms     6 ms     7 ms  tenge-3-2-1.core2.dbn.core.eircom.net [86.43.252.41]

     6     *        *        *     Request timed out.

     7    69 ms     *       91 ms  72.14.205.72

     8     8 ms     8 ms     9 ms  209.85.252.196

     9     8 ms     9 ms     8 ms  72.14.235.189

    10     *        *        *     Request timed out.

    11     8 ms     8 ms     7 ms  de-in-f93.1e100.net [74.125.24.93]

    Trace complete.

    C:\Windows\System32>tracert cnn-f.akamaihd.net

    Tracing route to a513.w23.akamai.net [92.122.48.88]

    over a maximum of 30 hops:

     1    <1 ms    <1 ms    <1 ms  MitraStar.Home [192.168.1.254]

     2    14 ms     6 ms     5 ms  86-44-82-1-dynamic.agg2.mhz.blp-srl.eircom.net [86.44.82.1]

     3     5 ms     5 ms     7 ms  86.43.12.161

     4     7 ms     5 ms     6 ms  tenge-3-1-1.core1.srl.core.eircom.net [86.43.252.85]

     5    16 ms     *        *     tenge-2-2-1.pe1.thn.the-thn.eircom.net [86.43.253.114]

     6    17 ms    16 ms    16 ms  ge7-1-0.corea.thn.london.eircom.net [86.43.244.194]

     7    16 ms    17 ms    16 ms  xe-2-3-2.lon11.ip4.gtt.net [77.67.76.161]

     8    40 ms     *       41 ms  xe-1-2-0.mil21.ip4.gtt.net [89.149.181.45]

     9    40 ms    41 ms    40 ms  a92-122-48-88.deploy.akamaitechnologies.com [92.122.48.88]

    Trace complete.

    Finally, a couple more at 21.35 (using Google DNS)

    C:\Windows\System32>tracert cnn-f.akamaihd.net

    Tracing route to a513.w23.akamai.net [92.123.72.175]

    over a maximum of 30 hops:

     1    <1 ms    <1 ms    <1 ms  192.168.1.254

     2     5 ms    14 ms    19 ms  86-44-82-1-dynamic.agg2.mhz.blp-srl.eircom.net [86.44.82.1]

     3     6 ms     5 ms     7 ms  86.43.12.157

     4     6 ms     5 ms     6 ms  tenge-5-2-1.core2.bdt.core.eircom.net [86.43.253

    .5]

     5     5 ms     5 ms     5 ms  86.43.13.154

     6     5 ms     6 ms     5 ms  83.71.115.186

     7     6 ms     6 ms     6 ms  inex-dub1.netarch.akamai.com [193.242.111.55]

     8     6 ms     6 ms     7 ms  a92-123-72-175.deploy.akamaitechnologies.com [92

    .123.72.175]

    Trace complete.


    C:\Windows\System32>tracert youtube.com

    Tracing route to youtube.com [74.125.24.136]
    over a maximum of 30 hops:

      1     2 ms    <1 ms     2 ms  192.168.1.254
      2    23 ms     8 ms    18 ms  86-44-82-1-dynamic.agg2.mhz.blp-srl.eircom.net [86.44.82.1]
      3     5 ms     4 ms     5 ms  86.43.12.157
      4     7 ms     6 ms     6 ms  tenge-6-1-1.core2.srl.core.eircom.net [86.43.253.137]
      5    23 ms     8 ms     6 ms  tenge-3-2-1.core2.dbn.core.eircom.net [86.43.252.41]
      6     *             7 ms     6 ms  86.47.63.114
      7    29 ms    24 ms    20 ms  72.14.205.72
      8     7 ms     7 ms     7 ms  209.85.252.198
      9     7 ms     7 ms     7 ms  72.14.235.139
     10     *        *        *     Request timed out.
     11     9 ms     7 ms     7 ms  de-in-f136.1e100.net [74.125.24.136]

    Trace complete.

    I'm sure this probably is a routing issue but some of the hop times appear to be a lot better with the google DNS

    I hope this is of some use to eircom so they can get this sorted.


  • Registered Users Posts: 1,679 ✭✭✭scargill


    I'm on eFibre - just noticed it is painfully slow to load common websites the last few days.
    Speedtest is reporting speeds anywhere from 3mbps to 12 mbps - far short of what it should be.
    Will ring eircom tomorrow eve.


  • Closed Accounts Posts: 715 ✭✭✭Cianmcliam


    Had a more consistent connection when we had a 2MB line, this is crazy. YouTube videos are crawling and Vimeo just gives up. Facebook photos are either invisible or made out of 10 solid blocks. Are Meteor using same servers/routers? Noticed my 3G sim has also gone downhill in last week or two.


  • Moderators, Technology & Internet Moderators, Regional North East Moderators Posts: 10,869 Mod ✭✭✭✭PauloMN


    Ran some traces just now, will try again tomorrow during the day to compare, but I noticed earlier that both YouTube and Facebook were slow. Speedtest results are as expected:
    3902148507.png
    C:\Users\PH>tracert youtube.com
    
    Tracing route to youtube.com [74.125.24.93]
    over a maximum of 30 hops:
    
    &#160; 1 &#160; &#160;<1 ms &#160; &#160;<1 ms &#160; &#160;<1 ms &#160;MitraStar.Home [192.168.1.254]
    &#160; 2 &#160; &#160; 8 ms &#160; &#160;16 ms &#160; &#160;11 ms &#160;86-44-172-1-dynamic.arg1.trm.dbc-mgr.eircom.net
    [86.44.172.1]
    &#160; 3 &#160; &#160; 8 ms &#160; &#160; 8 ms &#160; &#160; 8 ms &#160;86.43.13.101
    &#160; 4 &#160; &#160; 9 ms &#160; &#160; 8 ms &#160; &#160; 8 ms &#160;86.43.11.237
    &#160; 5 &#160; &#160;11 ms &#160; &#160;10 ms &#160; &#160;11 ms &#160;tenge-2-1-1.core2.bdt.core.eircom.net [86.43.252
    .253]
    &#160; 6 &#160; &#160;13 ms &#160; &#160;11 ms &#160; &#160;11 ms &#160;tenge-3-2-1.core2.prp.core.eircom.net [86.43.252
    .22]
    &#160; 7 &#160; &#160;12 ms &#160; &#160; * &#160; &#160; &#160; &#160;* &#160; &#160; 86.47.63.110
    &#160; 8 &#160; &#160; * &#160; &#160; &#160; 81 ms &#160; &#160;86 ms &#160;72.14.205.72
    &#160; 9 &#160; &#160;11 ms &#160; &#160;12 ms &#160; &#160;11 ms &#160;209.85.252.196
    &#160;10 &#160; &#160;11 ms &#160; &#160;11 ms &#160; &#160;15 ms &#160;72.14.235.189
    &#160;11 &#160; &#160; * &#160; &#160; &#160; &#160;* &#160; &#160; &#160; &#160;* &#160; &#160; Request timed out.
    &#160;12 &#160; &#160;11 ms &#160; &#160;12 ms &#160; &#160;11 ms &#160;de-in-f93.1e100.net [74.125.24.93]
    
    Trace complete.
    
    C:\Users\PH>tracert facebook.com
    
    Tracing route to facebook.com [173.252.120.6]
    over a maximum of 30 hops:
    
    &#160; 1 &#160; &#160;<1 ms &#160; &#160;<1 ms &#160; &#160;<1 ms &#160;MitraStar.Home [192.168.1.254]
    &#160; 2 &#160; &#160; 8 ms &#160; &#160; 8 ms &#160; &#160; 8 ms &#160;86-44-172-1-dynamic.arg1.trm.dbc-mgr.eircom.net
    [86.44.172.1]
    &#160; 3 &#160; &#160; 8 ms &#160; &#160; 8 ms &#160; &#160; 8 ms &#160;86.43.13.101
    &#160; 4 &#160; &#160; 9 ms &#160; &#160; 9 ms &#160; &#160; 9 ms &#160;86.43.11.241
    &#160; 5 &#160; &#160;18 ms &#160; &#160;11 ms &#160; &#160;18 ms &#160;86.43.13.145
    &#160; 6 &#160; &#160; * &#160; &#160; &#160; 23 ms &#160; &#160;22 ms &#160;tenge-2-2-1.pe1.thn.the-thn.eircom.net [86.43.25
    3.114]
    &#160; 7 &#160; &#160;21 ms &#160; &#160;21 ms &#160; &#160;21 ms &#160;ge7-1-0.corea.thn.london.eircom.net [86.43.244.1
    94]
    &#160; 8 &#160; &#160;22 ms &#160; &#160;21 ms &#160; &#160; * &#160; &#160; linx.br01.lhr1.tfbnw.net [195.66.225.69]
    &#160; 9 &#160; &#160;79 ms &#160; &#160;79 ms &#160; &#160;81 ms &#160;ae1.bb01.lhr2.tfbnw.net [31.13.30.174]
    &#160;10 &#160; 176 ms &#160; 166 ms &#160; 170 ms &#160;be11.bb01.ewr2.tfbnw.net [31.13.30.98]
    &#160;11 &#160; 113 ms &#160; &#160; * &#160; &#160; &#160;114 ms &#160;be44.bb02.iad3.tfbnw.net [31.13.26.5]
    &#160;12 &#160; 172 ms &#160; 175 ms &#160; 167 ms &#160;ae13.bb03.frc3.tfbnw.net [31.13.24.80]
    &#160;13 &#160; 174 ms &#160; 183 ms &#160; 171 ms &#160;ae1.dr09.frc3.tfbnw.net [31.13.29.43]
    &#160;14 &#160; &#160; * &#160; &#160; &#160; &#160;* &#160; &#160; &#160; &#160;* &#160; &#160; Request timed out.
    &#160;15 &#160; &#160; * &#160; &#160; &#160; &#160;* &#160; &#160; &#160; &#160;* &#160; &#160; Request timed out.
    &#160;16 &#160; &#160; * &#160; &#160; &#160; &#160;* &#160; &#160; &#160; &#160;* &#160; &#160; Request timed out.
    &#160;17 &#160; 173 ms &#160; 173 ms &#160; 170 ms &#160;edge-star-shv-12-frc3.facebook.com [173.252.120.
    6]
    
    Trace complete.
    
    C:\Users\PH>tracert bbc.co.uk
    
    Tracing route to bbc.co.uk [212.58.244.20]
    over a maximum of 30 hops:
    
    &#160; 1 &#160; &#160;<1 ms &#160; &#160;<1 ms &#160; &#160;<1 ms &#160;MitraStar.Home [192.168.1.254]
    &#160; 2 &#160; &#160; 8 ms &#160; &#160; 8 ms &#160; &#160; 8 ms &#160;86-44-172-1-dynamic.arg1.trm.dbc-mgr.eircom.net
    [86.44.172.1]
    &#160; 3 &#160; &#160; 8 ms &#160; &#160; 8 ms &#160; &#160; 8 ms &#160;86.43.13.101
    &#160; 4 &#160; &#160; 9 ms &#160; &#160; 9 ms &#160; &#160; 9 ms &#160;86.43.11.241
    &#160; 5 &#160; &#160;11 ms &#160; &#160;11 ms &#160; &#160;11 ms &#160;86.43.13.145
    &#160; 6 &#160; &#160;23 ms &#160; &#160;23 ms &#160; &#160;50 ms &#160;tenge-2-2-1.pe1.thn.the-thn.eircom.net [86.43.25
    3.114]
    &#160; 7 &#160; &#160;27 ms &#160; &#160;43 ms &#160; &#160;21 ms &#160;ge7-1-0.corea.thn.london.eircom.net [86.43.244.1
    94]
    &#160; 8 &#160; &#160;22 ms &#160; &#160; * &#160; &#160; &#160; 23 ms &#160;bbc-linx.pr01.thdow.bbc.co.uk [195.66.224.103]
    &#160; 9 &#160; &#160; * &#160; &#160; &#160; &#160;* &#160; &#160; &#160; &#160;* &#160; &#160; Request timed out.
    &#160;10 &#160; &#160; * &#160; &#160; &#160; &#160;* &#160; &#160; &#160; &#160;* &#160; &#160; Request timed out.
    &#160;11 &#160; &#160;32 ms &#160; &#160;82 ms &#160; &#160;22 ms &#160;ae0.er01.telhc.bbc.co.uk [132.185.254.109]
    &#160;12 &#160; &#160;24 ms &#160; &#160;23 ms &#160; &#160;23 ms &#160;132.185.255.149
    &#160;13 &#160; &#160;81 ms &#160; &#160;80 ms &#160; &#160;79 ms &#160;fmt-vip71.telhc.bbc.co.uk [212.58.244.20]
    
    Trace complete.
    


  • Advertisement
  • Registered Users Posts: 18 FiReStOrM xIx


    I'm the same, getting consistent speeds of 95mbps download and 18mbps upload during the day... after 5 or 6pm the speed tests range from anywhere between 0.16mbps down to 90mbps down within minutes of each other. Absolutely ridiculous. Even when I'm achieving a 'speed' of 80mbps download after 6pm i can't download a 100mb file.... takes ages... v v angry customer, on the highest package as i use for online games and download from netflix. Not fit for purpose as i work during the day. The answer of 'it'll take a few weeks to sort' while they still take our money simply is not good enough. 


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


    Joke alright, im so fed up. Had nothing but problems with this company


  • Registered Users Posts: 332 ✭✭dave_t


    Seems even worse tonight. Not just videos but loading websites. Facebook is crawling with wifi on my phone but fine on 3G. This isn't a service!


  • Moderators, Technology & Internet Moderators, Regional North East Moderators Posts: 10,869 Mod ✭✭✭✭PauloMN


    Same traces from last night, pings lower this morning.  The problem is evening peak traffic, same as it was when I was on NGB.
    C:\Users\PH>tracert youtube.com
    
    Tracing route to youtube.com [74.125.24.136]
    over a maximum of 30 hops:
    
    &#160; 1 &#160; &#160; 1 ms &#160; &#160;<1 ms &#160; &#160;<1 ms &#160;MitraStar.Home [192.168.1.254]
    &#160; 2 &#160; &#160;13 ms &#160; &#160; 9 ms &#160; &#160; 8 ms &#160;86-44-172-1-dynamic.arg1.trm.dbc-mgr.eircom.net
    [86.44.172.1]
    &#160; 3 &#160; &#160; 9 ms &#160; &#160; 9 ms &#160; &#160; 8 ms &#160;86.43.13.101
    &#160; 4 &#160; &#160; 9 ms &#160; &#160; 8 ms &#160; &#160; 8 ms &#160;86.43.11.237
    &#160; 5 &#160; &#160;11 ms &#160; &#160;11 ms &#160; &#160;10 ms &#160;tenge-2-1-1.core2.bdt.core.eircom.net [86.43.252
    .253]
    &#160; 6 &#160; &#160;12 ms &#160; &#160;12 ms &#160; &#160;11 ms &#160;tenge-3-2-1.core2.prp.core.eircom.net [86.43.252
    .22]
    &#160; 7 &#160; &#160;12 ms &#160; &#160; * &#160; &#160; &#160; 11 ms &#160;86.47.63.110
    &#160; 8 &#160; &#160;11 ms &#160; &#160;15 ms &#160; &#160;11 ms &#160;72.14.205.72
    &#160; 9 &#160; &#160;15 ms &#160; &#160;11 ms &#160; &#160;17 ms &#160;209.85.252.196
    &#160;10 &#160; &#160;11 ms &#160; &#160;11 ms &#160; &#160;11 ms &#160;66.249.95.3
    &#160;11 &#160; &#160; * &#160; &#160; &#160; &#160;* &#160; &#160; &#160; &#160;* &#160; &#160; Request timed out.
    &#160;12 &#160; &#160;11 ms &#160; &#160;12 ms &#160; &#160;12 ms &#160;de-in-f136.1e100.net [74.125.24.136]
    
    Trace complete.
    
    C:\Users\PH>tracert facebook.com
    
    Tracing route to facebook.com [173.252.120.6]
    over a maximum of 30 hops:
    
    &#160; 1 &#160; &#160;<1 ms &#160; &#160;<1 ms &#160; &#160;<1 ms &#160;MitraStar.Home [192.168.1.254]
    &#160; 2 &#160; &#160;14 ms &#160; &#160; 8 ms &#160; &#160; 7 ms &#160;86-44-172-1-dynamic.arg1.trm.dbc-mgr.eircom.net
    [86.44.172.1]
    &#160; 3 &#160; &#160; 8 ms &#160; &#160; 8 ms &#160; &#160; 8 ms &#160;86.43.13.101
    &#160; 4 &#160; &#160; 9 ms &#160; &#160; 9 ms &#160; &#160; 9 ms &#160;86.43.11.241
    &#160; 5 &#160; &#160;12 ms &#160; &#160;11 ms &#160; &#160;11 ms &#160;86.43.13.145
    &#160; 6 &#160; &#160;23 ms &#160; &#160;23 ms &#160; &#160;22 ms &#160;tenge-2-2-1.pe1.thn.the-thn.eircom.net [86.43.25
    3.114]
    &#160; 7 &#160; &#160;21 ms &#160; &#160;21 ms &#160; &#160;21 ms &#160;ge7-1-0.corea.thn.london.eircom.net [86.43.244.1
    94]
    &#160; 8 &#160; &#160;21 ms &#160; &#160; * &#160; &#160; &#160; 21 ms &#160;linx.br01.lhr1.tfbnw.net [195.66.225.69]
    &#160; 9 &#160; &#160;23 ms &#160; &#160;23 ms &#160; &#160;23 ms &#160;ae1.bb01.lhr2.tfbnw.net [31.13.30.174]
    &#160;10 &#160; 116 ms &#160; 116 ms &#160; &#160; * &#160; &#160; be11.bb01.ewr2.tfbnw.net [31.13.30.98]
    &#160;11 &#160; 114 ms &#160; 115 ms &#160; 114 ms &#160;be44.bb02.iad3.tfbnw.net [31.13.26.5]
    &#160;12 &#160; 118 ms &#160; 115 ms &#160; &#160; * &#160; &#160; be24.bb02.frc3.tfbnw.net [173.252.64.206]
    &#160;13 &#160; 119 ms &#160; 116 ms &#160; 123 ms &#160;ae1.bb04.frc3.tfbnw.net [173.252.65.127]
    &#160;14 &#160; 116 ms &#160; 115 ms &#160; 116 ms &#160;ae2.dr09.frc3.tfbnw.net [31.13.29.45]
    &#160;15 &#160; &#160; * &#160; &#160; &#160; &#160;* &#160; &#160; &#160; &#160;* &#160; &#160; Request timed out.
    &#160;16 &#160; &#160; * &#160; &#160; &#160; &#160;* &#160; &#160; &#160; &#160;* &#160; &#160; Request timed out.
    &#160;17 &#160; &#160; * &#160; &#160; &#160; &#160;* &#160; &#160; &#160; &#160;* &#160; &#160; Request timed out.
    &#160;18 &#160; 116 ms &#160; 115 ms &#160; 115 ms &#160;edge-star-shv-12-frc3.facebook.com [173.252.120.
    6]
    
    Trace complete.
    
    C:\Users\PH>tracert bbc.co.uk
    
    Tracing route to bbc.co.uk [212.58.244.20]
    over a maximum of 30 hops:
    
    &#160; 1 &#160; &#160;<1 ms &#160; &#160;<1 ms &#160; &#160;<1 ms &#160;MitraStar.Home [192.168.1.254]
    &#160; 2 &#160; &#160;11 ms &#160; &#160; 8 ms &#160; &#160; 8 ms &#160;86-44-172-1-dynamic.arg1.trm.dbc-mgr.eircom.net
    [86.44.172.1]
    &#160; 3 &#160; &#160; 8 ms &#160; &#160; 8 ms &#160; &#160; 8 ms &#160;86.43.13.101
    &#160; 4 &#160; &#160; 9 ms &#160; &#160; 8 ms &#160; &#160; 9 ms &#160;86.43.11.241
    &#160; 5 &#160; &#160;11 ms &#160; &#160;10 ms &#160; &#160;11 ms &#160;86.43.13.145
    &#160; 6 &#160; &#160;23 ms &#160; &#160;22 ms &#160; &#160;23 ms &#160;tenge-2-2-1.pe1.thn.the-thn.eircom.net [86.43.25
    3.114]
    &#160; 7 &#160; &#160;21 ms &#160; &#160;21 ms &#160; &#160;21 ms &#160;ge7-1-0.corea.thn.london.eircom.net [86.43.244.1
    94]
    &#160; 8 &#160; &#160;22 ms &#160; &#160; * &#160; &#160; &#160; 22 ms &#160;bbc-linx.pr01.thdow.bbc.co.uk [195.66.224.103]
    &#160; 9 &#160; &#160; * &#160; &#160; &#160; &#160;* &#160; &#160; &#160; &#160;* &#160; &#160; Request timed out.
    &#160;10 &#160; &#160; * &#160; &#160; &#160; &#160;* &#160; &#160; &#160; &#160;* &#160; &#160; Request timed out.
    &#160;11 &#160; &#160;23 ms &#160; &#160;23 ms &#160; &#160;23 ms &#160;ae0.er01.telhc.bbc.co.uk [132.185.254.109]
    &#160;12 &#160; &#160;23 ms &#160; &#160;23 ms &#160; &#160;23 ms &#160;132.185.255.149
    &#160;13 &#160; &#160;23 ms &#160; &#160;23 ms &#160; &#160;23 ms &#160;fmt-vip71.telhc.bbc.co.uk [212.58.244.20]
    
    Trace complete.
    


  • Registered Users Posts: 332 ✭✭dave_t


    Any further update on this?


  • Advertisement
  • Registered Users Posts: 4 Monty Almighty


    It seems to be ok for me today.
    I saw a load of Eircom vans driving around Greystones earlier this morning so they could be fixing what ever is causing the problem.


  • Registered Users Posts: 1,034 ✭✭✭dalta5billion


    This Akamai server 159.134.172.152 (sometimes Vimeo videos are served through this one)  is absolutely crawling tonight: oddly it seems to peer directly with eircom, but not at INEX.
    traceroute to 159.134.172.152 (159.134.172.152), 30 hops max, 60 byte packets
    &#160;1 &#160;MitraStar.Home (192.168.1.254) &#160;5.896 ms &#160;6.607 ms &#160;6.608 ms
    &#160;2 &#160;95.45.62.1 (95.45.62.1) &#160;7.282 ms &#160;9.531 ms &#160;10.757 ms
    &#160;3 &#160;86.43.11.49 (86.43.11.49) &#160;9.064 ms &#160;9.148 ms &#160;9.282 ms
    &#160;4 &#160;tenge-4-1-1.core1.dbn.core.eircom.net (86.43.252.205) &#160;9.662 ms &#160;10.113 ms &#160;10.204 ms
    &#160;5 &#160;lag-1.core2.dbn.core.eircom.net (86.43.252.30) &#160;10.263 ms &#160;10.367 ms &#160;10.804 ms
    &#160;6 &#160;* * tenge-1-2-1.pe2.crz.crz-crz.eircom.net (86.43.252.138) &#160;8.559 ms
    &#160;7 &#160;159.134.172.152 (159.134.172.152) &#160;9.905 ms &#160;10.356 ms &#160;10.359 ms
    

    EDIT: that IP is registered to Eircom, not Akamai, yet still serves content. Hmmm. Maybe I'll fire off an email to Akamai.


  • Registered Users Posts: 14,392 ✭✭✭✭ednwireland


    my account manager told me there was no problem in donegal town on Tuesday despite every business I talked to who were with eircom couldn't get Internet access.


  • Closed Accounts Posts: 5,115 ✭✭✭Pacifico


    Shocking service at the moment...silverlight downloading at 44KB/s!!


  • Registered Users Posts: 475 ✭✭jspuds


    Pacifico wrote: »
    Shocking service at the moment...silverlight downloading at 44KB/s!!
    Getting similar woeful speeds


  • Registered Users Posts: 13 starvinm


    Pinging fbstatic-a.akamahid.net [69.43.161.145] with 32 bytes of data:

    Reply from 69.43.161.145: bytes=32 time=739ms TTL=54
    Reply from 69.43.161.145: bytes=32 time=762ms TTL=54
    Reply from 69.43.161.145: bytes=32 time=786ms TTL=54
    Reply from 69.43.161.145: bytes=32 time=280ms TTL=54

    Ping statistics for 69.43.161.145:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 280ms, Maximum = 786ms, Average = 641ms

    This is getting absolutely ridiculous. Eircom sort it out. NGB my arse!


  • Registered Users Posts: 554 ✭✭✭doctorg


    If this was happening in the states, there would be a lawsuit by now and everyone this forum would be onboard that ship.

    At least have the decency to update us what you doing to fix it and how its coming along. 


  • Closed Accounts Posts: 6,831 ✭✭✭eircom: Alan


    doctorg wrote: »
    If this was happening in the states, there would be a lawsuit by now and everyone this forum would be onboard that ship.

    At least have the decency to update us what you doing to fix it and how its coming along. 
    Hi doctorg

    I understand the frustration this can cause, unfortunately I do not have an update to offer you but I have been advised we should have more news next week.

    Al


  • Registered Users Posts: 222 ✭✭major deegan


    Hi doctorg

    I understand the frustration this can cause, unfortunately I do not have an update to offer you but I have been advised we should have more news next week.

    Al

    Ahh news next week..will all this poor service be considered as down time ??


  • Registered Users Posts: 554 ✭✭✭doctorg


    doctorg wrote: »
    If this was happening in the states, there would be a lawsuit by now and everyone this forum would be onboard that ship.

    At least have the decency to update us what you doing to fix it and how its coming along. 
    Hi doctorg

    I understand the frustration this can cause, unfortunately I do not have an update to offer you but I have been advised we should have more news next week.

    Al
    If i'm not mistake, you told us the same thing last week...

    Can you atleast tell us what you HAVE done till date, other than getting customers do work for you (trace route).

    I would like to ask, do you have Eircom broadband yourself? 


  • Advertisement
  • Registered Users Posts: 7 Niallthebomb


    Certain websites are just unbrowsable (if that's a word).
    I use this line for business, works great during the daytime. Thankfully, I don't use it much in the evening but tonight I am better off on 3G....get your act together eircom. This is ridiculous.

    See samples below.



    C:\Windows\System32>ping cnn.com

    Pinging cnn.com [157.166.226.25] with 32 bytes of data:
    Reply from 157.166.226.25: bytes=32 time=207ms TTL=119
    Reply from 157.166.226.25: bytes=32 time=209ms TTL=119
    Reply from 157.166.226.25: bytes=32 time=215ms TTL=119
    Reply from 157.166.226.25: bytes=32 time=201ms TTL=119

    Ping statistics for 157.166.226.25:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 201ms, Maximum = 215ms, Average = 208ms

    C:\Windows\System32>tracert cnn-f.akamaihd.net

    Tracing route to a513.w23.akamai.net [80.231.241.66]
    over a maximum of 30 hops:

      1    <1 ms    <1 ms    <1 ms  192.168.1.254
      2    15 ms     6 ms     5 ms  86-44-82-1-dynamic.agg2.mhz.blp-srl.eircom.net [86.44.82.1]
      3     5 ms     5 ms     5 ms  86.43.12.161
      4     6 ms     5 ms    11 ms  tenge-3-1-1.core1.srl.core.eircom.net [86.43.252.85]
      5     7 ms     5 ms     5 ms  ge3-0-0.peering1.csg.dublin.eircom.net [86.43.244.54]
      6    89 ms     *       82 ms  195.16.170.41
      7     *       92 ms    93 ms  ae-3-80.edge5.Paris1.Level3.net [4.69.168.136]
      8    98 ms     *      104 ms  ae-3-80.edge5.Paris1.Level3.net [4.69.168.136]
      9    98 ms    97 ms   100 ms  ix-20-0.tcore1.PVU-Paris.as6453.net [80.231.153.
    65]
     10   101 ms   100 ms   113 ms  80.231.241.66

    Trace complete.

    C:\Windows\System32>


  • Registered Users Posts: 1,034 ✭✭✭dalta5billion


    Update as of Saturday 15th November

    YouTube content appears to be fixed (to me)

    Akamai servers on the other hand remain congested if they are routed through eircom's peering with gtt.net. This affects among others Vimeo and Facebook.

    Eircom also appear to have peered with some more networks in LINX (London) since last I checked, and it would appear they have an unsaturated link running to LINX, so are trying to route as much traffic as possible through there.


  • Closed Accounts Posts: 6,831 ✭✭✭eircom: Alan


    Update as of Saturday 15th November

    YouTube content appears to be fixed (to me)

    Akamai servers on the other hand remain congested if they are routed through eircom's peering with gtt.net. This affects among others Vimeo and Facebook.

    Eircom also appear to have peered with some more networks in LINX (London) since last I checked, and it would appear they have an unsaturated link running to LINX, so are trying to route as much traffic as possible through there.

    Thanks for sharing this dalta5billion

    As soon as I have an official update I'll update this thread right away.

    Thanks
    Al


  • Registered Users Posts: 988 ✭✭✭rat_race


    Update as of Saturday 15th November

    YouTube content appears to be fixed (to me)

    Akamai servers on the other hand remain congested if they are routed through eircom's peering with gtt.net. This affects among others Vimeo and Facebook.

    Eircom also appear to have peered with some more networks in LINX (London) since last I checked, and it would appear they have an unsaturated link running to LINX, so are trying to route as much traffic as possible through there.
    Yes, certain routes are better now. But still, many are not. They're probably focusing on the busiest sites to shut the majority of us up.


  • Moderators, Technology & Internet Moderators, Regional North East Moderators Posts: 10,869 Mod ✭✭✭✭PauloMN


    Haven't tried YouTube over the past few days, but my FTP connections to my office are worse than ever.

    Terrible ping times to a site on a UPC (ntlworld.ie), and one which last week was fast for me has now slowed down a lot (magnet.ie).


  • Registered Users Posts: 1,034 ✭✭✭dalta5billion


    HEAnet downloads via INEX were also pretty slow, which they never were before.


  • Closed Accounts Posts: 6,831 ✭✭✭eircom: Alan


    Hey guys

    I will be unable to comment on specific server/locations or routes but as soon as I have official clarification in relation to planned improvements I will of course post to this thread.

    All trace routes much appreciate though.

    Thanks
    Al


  • Registered Users Posts: 1,893 ✭✭✭rex-x


    Hey guys

    I will be unable to comment on specific server/locations or routes but as soon as I have official clarification in relation to planned improvements I will of course post to this thread.

    All trace routes much appreciate though.

    Thanks
    Al
    Any information regarding waiving efibre bills for the period of this massive problem?


  • Registered Users Posts: 222 ✭✭major deegan


    rex-x wrote: »
    Any information regarding waiving efibre bills for the period of this massive problem?

    You wont get an answer to that question anyway, even though their own customers are working to help fix eircom's problem... They dont want to hear about credit for down time.


  • Advertisement
  • Registered Users Posts: 232 ✭✭gramo


    You wont get an answer to that question anyway, even though their own customers are working to help fix eircom's problem... They dont want to hear about credit for down time.

    I sent a formal complaint email two weeks ago, I stated that I will no longer pay my bill until the issue has been resolved. Haven't heard anything back yet. Surely we would be in a position to cancel our contract?


Advertisement