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

rat_race

dalta5billion wrote: »

rat_race wrote: »

I'm not sure that I'm following.

You're getting timeouts at node 5 for some reason, which shouldn't happen, and in general the hop speeds around the Eircom nodes are very slow and inconsistent. From my German server, a roundtrip to r20---sn-4g57kn6r.googlevideo.com takes 6ms -- from start to finish. In your examples, it's taking much longer, around 43ms, if you're lucky. The delay is occurring on the Eircom servers. It even took 64ms on one of the  three times in a row, to get to node 7. So the speeds would vary greatly.

This will mess up streaming a video for sure.

For anyone wanting to understand traceroute a bit more, check this out:

http://networking.ringofsaturn.com/IP/traceroutedoc.php

6ms from Germany to the US breaks the laws of physics, so unless Google is doing some routing magic (anycast?), I don't think it's a fair comparison.

Also, asterisks are completely normal in traceroutes. Many servers are configured not to respond to traceroutes. They do not indicate packet loss, but rather a hop along the way that does indeed decrement the TTL in the header but does not respond with its hostname when the TTL gets to low(which is how traceroute works in the first place).

What is more interesting is the route that is being taken, or reported to be taken.

You're right regarding the 6ms, but that's what it is because simply it's not going to the US -- which is the right thing to do.

And asterisks are normal in traceroutes too, yep, BUT not when they sometimes occur and sometimes don't like in my examples (where sometimes 1 or 2 out of three requests didn't time out). And if you see the output where I tracerouted the servers you first mentioned, I wasn't getting ALL asterisks on node 5 for very similar routes. Seems strange that sometimes a server would respond, other times it wouldn't. I know we might be taking slightly different routes, but it doesn't look like it.

Additionally, I ran a lot more traceroutes than I pasted, and random timeouts and unusual times were popping up a lot.

Just had a friend with Vodafone BB do a traceroute to [font=arial, sans-serif]cnn-f.akamaihd.net[/font] (the one I originally tested)...6 node hops in total, no issues, no timeouts, an average of 30ms. With Eircom, I have 9 hops, higher average and random timeouts here and there.

dalta5billion

rat_race wrote: »

You're right regarding the 6ms, but that's what it is because simply it's not going to the US -- which is the right thing to do.

And asterisks are normal in traceroutes too, yep, BUT not when they sometimes occur and sometimes don't like in my examples (where sometimes 1 or 2 out of three requests didn't time out). And if you see the output where I tracerouted the servers you first mentioned, I wasn't getting ALL asterisks on node 5 for very similar routes. Seems strange that sometimes a server would respond, other times it wouldn't. I know we might be taking slightly different routes, but it doesn't look like it.

Additionally, I ran a lot more traceroutes than I pasted, and random timeouts and unusual times were popping up a lot.

Just had a friend with Vodafone BB do a traceroute to [font=arial, sans-serif]cnn-f.akamaihd.net[/font] (the one I originally tested)...6 node hops in total, no issues, no timeouts, an average of 30ms. With Eircom, I have 9 hops, higher average and random timeouts here and there.

You're right, it is weird.

What I meants was if you look at the "fast" vs "slow" google trace routes the reported hand off point from an Eircom IP to a Google IP is the exact same. It makes no sense that one should be faster than the other if it is indeed a congestion issue caused by Eircom's poor peering arrangements.

Edit: never mind, they're not the same

Kazuma

This thread has been eye-opening, I've been experiencing the intermittent slow (or not even at all) loading of pictures in facebook recently - thought it very odd that it was only affecting specific things.

Simon Gruber Says

Had a similar problem with Three just before I got eFibre installed, although it was more specific to YouTube. They managed to sort it out very fast though but don't know what actually caused it.

http://touch.boards.ie/thread/2057294007/1

2012paddy2012

major deegan wrote: »

Folks, this is the exact same computer generated response on the other eircom thread..As predicted it's the usual call the technical support number.The reason i'm on here is i have used that number till i'd be blue in the face and all to no avail,thought there might be help or advice available in this forum.No help to me to repetitively give me a useless phone number!

Did you ever use Vodafone ? Any difference if so? Thks

eircom: Alan

Hi All,

These issues remain under investigation at the highest level and as soon as I have more information I'll update this thread you right away.

Many thanks to everybody who have PM'd trace routes - it's greatly appreciated. Also if anybody is having specific issues with yourube can you try youtube.ie and see if the issues remain?

Thanks
Al

major deegan

2012paddy2012 wrote: »

Did you ever use Vodafone ? Any difference if so? Thks

Yeah was with Vodafone for 3 years until Eircom sales rep came to the door with the "next big thing". The vodafone router was installed in a central location of the house to ensure even coverage and worked perfect for the duration.When Eircom 'engineer' arrived he insisted their router HAD to go in living room?? Which is at end of house (hence good coverage out on the lawn) giving lots of dead spots within the house!!! Also well well shy of the 70 mbs promised during sales pitch.I've wasted hours on phone trying to get a decent service but all to no avail. Had 4 no shows by 'technician' callouts!!! Total pain in the arse.. With zero help from customer service!!! Anyway vodafone were spot on for my needs with no problems for my time with them. Dunno what they're like now for efibre but they have to be better than eircom.

trixiebust

Having the same problems since the switch to e fibre two months ago... Every day between 5 and 11.30 p.m the internet and wifi lights on my router constantly flash and its impossible to stream anything between those hours. Speedtest shows a 40 mb wifi connection but this can't be right because it takes about 1.5 hours to watch a 30min show, constantly buffering. After 11.30 p.m all the lights are a stable green, no flashing, and all works perfect. All the problems are between peak hours, every day, so annoying!!

_Whimsical_

I really feel this sort of fault should be enough to cancel a contract with Eircom. Watching steaming tv services has become a basic requirement of an internet connection, lots of us use it as a primary tv service. We also will be paying a tv/entertainment licence to avail of these services instead of the traditional tv licence. It's just not an adequate service while an issue like this remains.

dalta5billion

UPDATE - Thursday 30th October

Having problems with Vimeo again tonight.

Some of the time the Vimeo/Akamai DNS returns an IP that eircom- (presumably correctly) -routes through INEX in Dublin directly to Akamai's network: See below

traceroute pdl.vimeocdn.com
traceroute to pdl.vimeocdn.com (92.123.72.102), 30 hops max, 60 byte packets
 1  MitraStar.Home (192.168.1.254)  4.604 ms  4.682 ms  4.789 ms
 2  95.45.62.1 (95.45.62.1)  12.848 ms  13.713 ms  14.154 ms
 3  86.43.11.49 (86.43.11.49)  7.640 ms  7.745 ms  8.666 ms
 4  tenge-4-1-1.core1.dbn.core.eircom.net (86.43.252.205)  8.779 ms  8.903 ms  9.010 ms
 5  * * *
 6  83.71.115.181 (83.71.115.181)  9.969 ms  8.842 ms  9.537 ms
 7  inex-dub1.netarch.akamai.com (193.242.111.55)  11.193 ms  11.004 ms  11.320 ms
 8  a92-123-72-102.deploy.akamaitechnologies.com (92.123.72.102)  9.261 ms  10.301 ms  10.165 ms

However, other IPs returned by Vimeo/Akamai appear to route through gtt in London:

traceroute pdl.vimeocdn.com
traceroute to pdl.vimeocdn.com (77.67.21.48), 30 hops max, 60 byte packets
 1  MitraStar.Home (192.168.1.254)  4.324 ms  5.279 ms  5.370 ms
 2  95.45.62.1 (95.45.62.1)  6.985 ms  7.929 ms  7.931 ms
 3  86.43.11.49 (86.43.11.49)  8.212 ms  8.341 ms  8.453 ms
 4  tenge-4-1-1.core1.dbn.core.eircom.net (86.43.252.205)  9.486 ms * *
 5  * * *
 6  * 83.71.115.181 (83.71.115.181)  7.250 ms  6.884 ms
 7  xe-1-1-0.dub20.ip4.gtt.net (77.67.64.161)  7.383 ms  7.375 ms  7.932 ms
 8  xe-3-0-5.lon10.ip4.gtt.net (141.136.106.253)  21.815 ms  22.294 ms  22.289 ms
 9  77.67.21.48 (77.67.21.48)  22.866 ms  22.862 ms  23.784 ms

Note that Vimeo/Akamai also serve content via av.vimeo.com - this domain suffers from the same problems, with some IP's being routed more directly than others:

traceroute av.vimeo.com
traceroute to av.vimeo.com (159.134.172.153), 30 hops max, 60 byte packets
 1  MitraStar.Home (192.168.1.254)  3.924 ms  4.060 ms  4.412 ms
 2  95.45.62.1 (95.45.62.1)  12.397 ms  13.062 ms  13.061 ms
 3  86.43.11.49 (86.43.11.49)  8.710 ms  8.823 ms  8.946 ms
 4  tenge-4-1-1.core1.dbn.core.eircom.net (86.43.252.205)  9.097 ms  9.213 ms  9.336 ms
 5  lag-1.core2.dbn.core.eircom.net (86.43.252.30)  11.908 ms  12.011 ms  12.135 ms
 6  tenge-1-2-1.pe2.crz.crz-crz.eircom.net (86.43.252.138)  10.237 ms  7.182 ms  7.288 ms
 7  159.134.172.153 (159.134.172.153)  7.508 ms  7.990 ms  7.919 ms

traceroute 'av.vimeo.com'
traceroute to av.vimeo.com (77.67.21.64), 30 hops max, 60 byte packets
 1  MitraStar.Home (192.168.1.254)  5.052 ms  5.070 ms  5.191 ms
 2  95.45.62.1 (95.45.62.1)  7.893 ms  8.628 ms  8.627 ms
 3  86.43.11.49 (86.43.11.49)  9.684 ms  10.071 ms  10.158 ms
 4  tenge-4-1-1.core1.dbn.core.eircom.net (86.43.252.205)  10.284 ms * *
 5  * * *
 6  * * *
 7  * xe-1-1-0.dub20.ip4.gtt.net (77.67.64.161)  10.180 ms  6.645 ms
 8  xe-3-0-5.lon10.ip4.gtt.net (141.136.106.253)  21.013 ms  22.406 ms  22.398 ms
 9  77.67.21.64 (77.67.21.64)  22.401 ms  22.391 ms  22.380 ms

EDIT: Akamai don't declare the gtt-routed IP's at INEX, so maybe this is an Akamai GeoDNS issue. This still doesn't account for why the London gtt link would be so congested.


EDIT2:
Here's a fast googlevideo server:

traceroute r3---sn-xpgjvh-q0ce.googlevideo.com
traceroute to r3---sn-xpgjvh-q0ce.googlevideo.com (86.43.63.14), 30 hops max, 60 byte packets
 1  MitraStar.Home (192.168.1.254)  4.899 ms  4.980 ms  5.603 ms
 2  95.45.62.1 (95.45.62.1)  6.661 ms  8.136 ms  11.443 ms
 3  86.43.11.49 (86.43.11.49)  8.700 ms  9.072 ms  9.193 ms
 4  tenge-3-1-1.core1.prp.core.eircom.net (86.43.252.201)  9.313 ms  9.437 ms  9.560 ms
 5  tenge-3-2-1.core1.bdt.core.eircom.net (86.43.252.9)  10.974 ms  11.986 ms  12.609 ms
 6  lag-1.core2.bdt.core.eircom.net (86.43.252.2)  14.155 ms  8.451 ms  8.455 ms
 7  tenge-1-2-1.pe1.cwm.cwm-cwm.eircom.net (86.43.252.174)  8.475 ms  8.598 ms  8.716 ms
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

And here's a slow one:

traceroute r11---sn-q0c7dn76.googlevideo.com
traceroute to r11---sn-q0c7dn76.googlevideo.com (173.194.138.112), 30 hops max, 60 byte packets
 1  MitraStar.Home (192.168.1.254)  3.978 ms  4.589 ms  5.532 ms
 2  95.45.62.1 (95.45.62.1)  11.303 ms  24.001 ms  26.299 ms
 3  86.43.11.49 (86.43.11.49)  9.041 ms  9.225 ms  9.355 ms
 4  tenge-4-1-1.core1.dbn.core.eircom.net (86.43.252.205)  9.479 ms  9.594 ms  9.727 ms
 5  * * *
 6  83.71.115.181 (83.71.115.181)  11.216 ms  10.496 ms  22.900 ms
 7  74.125.51.185 (74.125.51.185)  88.064 ms  88.065 ms  88.061 ms
 8  66.249.95.91 (66.249.95.91)  24.811 ms  24.822 ms  24.825 ms
 9  173.194.138.112 (173.194.138.112)  24.807 ms  24.810 ms  24.808 ms

Liamario

dalta5billion wrote: »

UPDATE - Thursday 30th October

Having problems with Vimeo again tonight.

Some of the time the Vimeo/Akamai DNS returns an IP that eircom- (presumably correctly) -routes through INEX in Dublin directly to Akamai's network: See below

traceroute pdl.vimeocdn.com
traceroute to pdl.vimeocdn.com (92.123.72.102), 30 hops max, 60 byte packets
 1  MitraStar.Home (192.168.1.254)  4.604 ms  4.682 ms  4.789 ms
 2  95.45.62.1 (95.45.62.1)  12.848 ms  13.713 ms  14.154 ms
 3  86.43.11.49 (86.43.11.49)  7.640 ms  7.745 ms  8.666 ms
 4  tenge-4-1-1.core1.dbn.core.eircom.net (86.43.252.205)  8.779 ms  8.903 ms  9.010 ms
 5  * * *
 6  83.71.115.181 (83.71.115.181)  9.969 ms  8.842 ms  9.537 ms
 7  inex-dub1.netarch.akamai.com (193.242.111.55)  11.193 ms  11.004 ms  11.320 ms
 8  a92-123-72-102.deploy.akamaitechnologies.com (92.123.72.102)  9.261 ms  10.301 ms  10.165 ms

However, other IPs returned by Vimeo/Akamai appear to route through gtt in London:

traceroute pdl.vimeocdn.com
traceroute to pdl.vimeocdn.com (77.67.21.48), 30 hops max, 60 byte packets
 1  MitraStar.Home (192.168.1.254)  4.324 ms  5.279 ms  5.370 ms
 2  95.45.62.1 (95.45.62.1)  6.985 ms  7.929 ms  7.931 ms
 3  86.43.11.49 (86.43.11.49)  8.212 ms  8.341 ms  8.453 ms
 4  tenge-4-1-1.core1.dbn.core.eircom.net (86.43.252.205)  9.486 ms * *
 5  * * *
 6  * 83.71.115.181 (83.71.115.181)  7.250 ms  6.884 ms
 7  xe-1-1-0.dub20.ip4.gtt.net (77.67.64.161)  7.383 ms  7.375 ms  7.932 ms
 8  xe-3-0-5.lon10.ip4.gtt.net (141.136.106.253)  21.815 ms  22.294 ms  22.289 ms
 9  77.67.21.48 (77.67.21.48)  22.866 ms  22.862 ms  23.784 ms

Note that Vimeo/Akamai also serve content via av.vimeo.com - this domain suffers from the same problems, with some IP's being routed more directly than others:

traceroute av.vimeo.com
traceroute to av.vimeo.com (159.134.172.153), 30 hops max, 60 byte packets
 1  MitraStar.Home (192.168.1.254)  3.924 ms  4.060 ms  4.412 ms
 2  95.45.62.1 (95.45.62.1)  12.397 ms  13.062 ms  13.061 ms
 3  86.43.11.49 (86.43.11.49)  8.710 ms  8.823 ms  8.946 ms
 4  tenge-4-1-1.core1.dbn.core.eircom.net (86.43.252.205)  9.097 ms  9.213 ms  9.336 ms
 5  lag-1.core2.dbn.core.eircom.net (86.43.252.30)  11.908 ms  12.011 ms  12.135 ms
 6  tenge-1-2-1.pe2.crz.crz-crz.eircom.net (86.43.252.138)  10.237 ms  7.182 ms  7.288 ms
 7  159.134.172.153 (159.134.172.153)  7.508 ms  7.990 ms  7.919 ms

traceroute 'av.vimeo.com'
traceroute to av.vimeo.com (77.67.21.64), 30 hops max, 60 byte packets
 1  MitraStar.Home (192.168.1.254)  5.052 ms  5.070 ms  5.191 ms
 2  95.45.62.1 (95.45.62.1)  7.893 ms  8.628 ms  8.627 ms
 3  86.43.11.49 (86.43.11.49)  9.684 ms  10.071 ms  10.158 ms
 4  tenge-4-1-1.core1.dbn.core.eircom.net (86.43.252.205)  10.284 ms * *
 5  * * *
 6  * * *
 7  * xe-1-1-0.dub20.ip4.gtt.net (77.67.64.161)  10.180 ms  6.645 ms
 8  xe-3-0-5.lon10.ip4.gtt.net (141.136.106.253)  21.013 ms  22.406 ms  22.398 ms
 9  77.67.21.64 (77.67.21.64)  22.401 ms  22.391 ms  22.380 ms

EDIT: Akamai don't declare the gtt-routed IP's at INEX, so maybe this is an Akamai GeoDNS issue. This still doesn't account for why the London gtt link would be so congested.


EDIT2:
Here's a fast googlevideo server:

traceroute r3---sn-xpgjvh-q0ce.googlevideo.com
traceroute to r3---sn-xpgjvh-q0ce.googlevideo.com (86.43.63.14), 30 hops max, 60 byte packets
 1  MitraStar.Home (192.168.1.254)  4.899 ms  4.980 ms  5.603 ms
 2  95.45.62.1 (95.45.62.1)  6.661 ms  8.136 ms  11.443 ms
 3  86.43.11.49 (86.43.11.49)  8.700 ms  9.072 ms  9.193 ms
 4  tenge-3-1-1.core1.prp.core.eircom.net (86.43.252.201)  9.313 ms  9.437 ms  9.560 ms
 5  tenge-3-2-1.core1.bdt.core.eircom.net (86.43.252.9)  10.974 ms  11.986 ms  12.609 ms
 6  lag-1.core2.bdt.core.eircom.net (86.43.252.2)  14.155 ms  8.451 ms  8.455 ms
 7  tenge-1-2-1.pe1.cwm.cwm-cwm.eircom.net (86.43.252.174)  8.475 ms  8.598 ms  8.716 ms
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

And here's a slow one:

traceroute r11---sn-q0c7dn76.googlevideo.com
traceroute to r11---sn-q0c7dn76.googlevideo.com (173.194.138.112), 30 hops max, 60 byte packets
 1  MitraStar.Home (192.168.1.254)  3.978 ms  4.589 ms  5.532 ms
 2  95.45.62.1 (95.45.62.1)  11.303 ms  24.001 ms  26.299 ms
 3  86.43.11.49 (86.43.11.49)  9.041 ms  9.225 ms  9.355 ms
 4  tenge-4-1-1.core1.dbn.core.eircom.net (86.43.252.205)  9.479 ms  9.594 ms  9.727 ms
 5  * * *
 6  83.71.115.181 (83.71.115.181)  11.216 ms  10.496 ms  22.900 ms
 7  74.125.51.185 (74.125.51.185)  88.064 ms  88.065 ms  88.061 ms
 8  66.249.95.91 (66.249.95.91)  24.811 ms  24.822 ms  24.825 ms
 9  173.194.138.112 (173.194.138.112)  24.807 ms  24.810 ms  24.808 ms

I have no clue what all that data means, but I can confirm that I too have been having problems with Vimeo, as well as YouTube lately. At least Eircom have acknowledged that there is something up. :-/

dub45

eircom: Alan wrote: »

Hi All,

These issues remain under investigation at the highest level and as soon as I have more information I'll update this thread you right away.

Many thanks to everybody who have PM'd trace routes - it's greatly appreciated. Also if anybody is having specific issues with yourube can you try youtube.ie and see if the issues remain?

Thanks
Al

What exactly does "at the highest level" mean? Has the acting Chief Executive joined in or is it just a bland platitude?

Have Eircom not got proper network monitoring tools in place to prevent these sort of issues occuring?

flyingsnail

Glad I stumbled across this thread, I thought it was just me.

will56

I'm on "Up to" 7mbs Broadband
Last night recorded speeds of .3mbs with pings in the high hundred.

Some fantastic service right there :rolleyes:
Live chat with eircom rep boils down to "too many devices connected" "should be connected by cable to modem", "Modem needs to be moved" - Modem has been in the same spot for the last 2 years without this problem !

nemoisback66

I'm glad to see this thread. Its only been in the last week or so that I am having the same issues. Youtube, FB, Sky on Demand taking a full 12 hours to download a 500mb video and a speed test of 65mb + and 20mb down. I tried everything to fix it changing routers, dns, disconnecting any devices on the line and still the same.
Only thing that works is using a vpn on the laptop and everything loads perfectly. Hopefully this is sorted asap.

dave_t

Any update before the weekend, eircom? Even some idea of what the issue is, what steps are being taken to resolve it and when it is expected to be fixed?

Thanks

ED E

will56 wrote: »

I'm on "Up to" 7mbs Broadband
Last night recorded speeds of .3mbs with pings in the high hundred.

Some fantastic service right there :rolleyes:
Live chat with eircom rep boils down to "too many devices connected" "should be connected by cable to modem", "Modem needs to be moved" - Modem has been in the same spot for the last 2 years without this problem !

Up to 7 = legacey exchange. Thats a totally different issue ( your service will be even worse).

rat_race

ED E wrote: »

will56 wrote: »

I'm on "Up to" 7mbs Broadband
Last night recorded speeds of .3mbs with pings in the high hundred.

Some fantastic service right there :rolleyes:
Live chat with eircom rep boils down to "too many devices connected" "should be connected by cable to modem", "Modem needs to be moved" - Modem has been in the same spot for the last 2 years without this problem !

Up to 7 = legacey exchange. Thats a totally different issue ( your service will be even worse).

Why is it a different issue? This has nothing to do with exchanges or contention, in my opinion. This is about routing, much further downstream -- and Eircom doesn't have two networks for newer broadband vs. old broadband, it has one network for all broadband (and probably dialup too). So all broadband is on the same (bad) network. That's just my common sense speaking there, I could be wrong and will happily be corrected!

ED E

rat_race wrote: »

Why is it a different issue? This has nothing to do with exchanges or contention, in my opinion. This is about routing, much further downstream -- and Eircom doesn't have two networks for newer broadband vs. old broadband, it has one network for all broadband (and probably dialup too). So all broadband is on the same (bad) network. That's just my common sense speaking there, I could be wrong and will happily be corrected!

If his only issue was the london link crapping out his tests wouldn't be 0.3mb, they'd be where they should be. His connection is congested on a point to point radio miles before it even hits the core network. In a sense he's double congested, even when they fix the problem this thread is about his service will still crawl.

will56

ED E wrote: »

rat_race wrote: »

Why is it a different issue? This has nothing to do with exchanges or contention, in my opinion. This is about routing, much further downstream -- and Eircom doesn't have two networks for newer broadband vs. old broadband, it has one network for all broadband (and probably dialup too). So all broadband is on the same (bad) network. That's just my common sense speaking there, I could be wrong and will happily be corrected!

If his only issue was the london link crapping out his tests wouldn't be 0.3mb, they'd be where they should be. His connection is congested on a point to point radio miles before it even hits the core network. In a sense he's double congested, even when they fix the problem this thread is about his service will still crawl.

I was hitting around 3mbs in the evenings, nothing to rave about but very useable. I would be willing to settle for that until such time as I get upgraded (fingers crossed for 2016 !)
Speeds in the last couple of weeks mean I can't use my laptop in the evenings at all, facebook won't open and other sites take an eternity to do anything.

Wold prefer Eircom to acknowledge the issue rather than tell me I'm not testing my speeds correctly

Hank Scorpio

dave_t wrote: »

Any update before the weekend, eircom? Even some idea of what the issue is, what steps are being taken to resolve it and when it is expected to be fixed?

Thanks

:rolleyes:

We`ll be in the same boat this time next week, but at least we know they are "very sorry" about the problems

major deegan

dave_t wrote: »

Any update before the weekend, eircom? Even some idea of what the issue is, what steps are being taken to resolve it and when it is expected to be fixed?

Thanks

Agree, some form of acknowledgement to all the posters having problems with eircom would be appreciated...An update before the weekend seems unlikely now.
Disgraceful treatment of customers.

2012paddy2012

Dom1978 wrote: »

I'm in Midleton and for most of the weekend speeds have dropped from 17-18MB/s to a lowly 1-2MB/s, friends using Eircom are reporting similar stories so there seems to be a fault somewhere.

hi is 17 -18 mb fairly fast I mean quick to download ? thks sorry for jumping in

dave_t

Well??

rat_race

dave_t wrote: »

Well??

Yep. Same problems, as bad as ever. Trying to steam a 45 second video from BBC news. Not happening.

Eircom, please give us an update and an ETA of a fix. Or else say "we haven't a clue, sorry".

dave_t

rat_race wrote: »

Yep. Same problems, as bad as ever. Trying to steam a 45 second video from BBC news. Not happening.

Eircom, please give us an update and an ETA of a fix. Or else say "we haven't a clue, sorry".

It's so frustrating. If they gave us something other than a vague response saying they're working on it (we're not even getting that at the moment!), it wouldn't be half as bad.

eircom: Alan

dave_t wrote: »

rat_race wrote: »

Yep. Same problems, as bad as ever. Trying to steam a 45 second video from BBC news. Not happening.

Eircom, please give us an update and an ETA of a fix. Or else say "we haven't a clue, sorry".

It's so frustrating. If they gave us something other than a vague response saying they're working on it (we're not even getting that at the moment!), it wouldn't be half as bad.

Hi dave_t

I've updated & replied to a number of other threads advising that these issues are indeed being investigated and I am regularly providing reports from users both here and our community forums. I have also asked that if some users who are confident is running trace-routes PM or post their results I will add them to my reports.

Thanks
Al

Liamario

As suggested-

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

C:\Users\Liam>tracert youtube.com

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

  1     3 ms     3 ms     3 ms  MitraStar.Home [192.168.1.254]
  2    12 ms     7 ms     7 ms  95.44.4.1
  3     9 ms     8 ms     8 ms  lag-18.pe1.dbc.dbc-mgr.eircom.net [86.43.59.225]

  4    28 ms    11 ms    11 ms  tenge-2-1-1.core2.bdt.core.eircom.net [86.43.252
.253]
  5    11 ms     *        *     86.43.13.154
  6    10 ms     9 ms     9 ms  83.71.115.186
  7    79 ms    81 ms   106 ms  74.125.51.185
  8    10 ms    11 ms    11 ms  209.85.252.198
  9    10 ms    10 ms    10 ms  72.14.235.139
 10     *        *        *     Request timed out.
 11    11 ms    10 ms    10 ms  de-in-f91.1e100.net [74.125.24.91]

Trace complete.

eircom: Alan

Liamario wrote: »

As suggested-

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

C:\Users\Liam>tracert youtube.com

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

  1     3 ms     3 ms     3 ms  MitraStar.Home [192.168.1.254]
  2    12 ms     7 ms     7 ms  95.44.4.1
  3     9 ms     8 ms     8 ms  lag-18.pe1.dbc.dbc-mgr.eircom.net [86.43.59.225]

  4    28 ms    11 ms    11 ms  tenge-2-1-1.core2.bdt.core.eircom.net [86.43.252
.253]
  5    11 ms     *        *     86.43.13.154
  6    10 ms     9 ms     9 ms  83.71.115.186
  7    79 ms    81 ms   106 ms  74.125.51.185
  8    10 ms    11 ms    11 ms  209.85.252.198
  9    10 ms    10 ms    10 ms  72.14.235.139
 10     *        *        *     Request timed out.
 11    11 ms    10 ms    10 ms  de-in-f91.1e100.net [74.125.24.91]

Trace complete.

Many thanks Liamario

Al

FiReStOrM xIx

Hi, I've been experiencing serious issue with my efibre connection also rrecently. I get 100mb download speed but in the evenings it varies wildy.... sometimes going from 80mb to 4mb download within the space of one minute. I've logged with technical support and am awaiting reply....