Slow speeds on UPC all week.

Oat23

http://www.upc.nl/internet/snel_internet/speedtest/
Result = 4.33MB down, 0.54MB up

http://www.smarttelecom.ie/speed/speed_checker.aspx
Result = 4.67Mb down, 0.72MB up.

docmol

Dublin_Gunner wrote: »

From that, it certainly could be assumed that the problem lies with speedtest, and not UPC.

However, I'm now wondering if it is a UPC problem, related to a specific routing to servers based in Dublin and/or servers that require UPC route through a particular Dublin node?

It's a UPC problem as they are the only ones who can fix it. Like most of us I was fine until Saturday. My bad pings are to England as well as to speedtests Dublin server. Ping times went up by an order of magnitude overnight!

docmol

coldfire1x wrote: »

Thats a valid question.

Have a go at the UPC very own speedtest as well.

http://www.upc.nl/internet/snel_internet/speedtest/

For me its showing 9.6mb download speed.

Just tried the UPC speedtest. No latency figures!!
Showed me 10.8mb/.85mb
Immediately ran Digiweb speedtest

:rolleyes:

docmol

FrankGrimes wrote: »

Rang them there, waited 20 minutes to get through.

He went quiet and seemed to run a line test and then told me that there were 2 line signal areas of concern/faults and that an engineer would need to come out and update my modem (Motorola Surfmobile from around 2 years ago) and test the line though he did also say 'it's bordering on being a possible area problem but no area faults are listed on the system'.

Engineer coming out on Friday afternoon. Will post back with outcome.

I was told somthing similar, but with no reference to a modem. Engineer also due out on Friday. What area are you in? (I'm in Cabra, Dublin 7)

Dublin_Gunner

coldfire1x wrote: »

Thats a valid question.

Have a go at the UPC very own speedtest as well.

http://www.upc.nl/internet/snel_internet/speedtest/

For me its showing 9.6mb download speed.

Hmm, that still uses ookla - just like speedtest.net - so can't imagine it offers anything more (getting 7.8down, 0.76 up on that). Interestingly, it doesn;t give your ping...

I could be on to something here.

Tested London


Dublin


Galway


Derry


Cork & Limerick gave similar results to Dublin / Derry / London - which was leading me to believe that maybe UPC were routing all their Atlantic traffic through some node in Galway - hence the speeds were always testing good, as well as ping (as they would have this reserved for high traffic).

Then Paris ruined my hypothethis:
Paris


It appears, that for whatever reason, presumably only known to UPC - their speeds and pings are directly connected (pardon the pun) to the location to which your routed.

I'm not arsed doing a tracert to servers based in locations where I did the speedtests - but this is very erratic.

BTW - all tests were done one straight after the other, and done a second time to ensure the reults are dependable.

foldup

This past week has been a nightmare on UPC broadband. Im on a 3 Mb line in the Dublin area. Download speeds have been all over the place.

Trying to download large files is a particular problem, where as im getting a problem i just discovered called "packet loss" - which apparently means that the download fails or quits due to "bottlenecking" on the network.

Im also having issues when streaming videos on youtube and quicktime where the video only streams approx. 20% of the content and then simply "stops" and then doesnt continue to stream. It just doesnt budge, even if i refresh it or try to click it forward! The same problem occurs when i try to stream movie trailers on the apple trailers website.

Somethings definitely gone wrong with UPC broadband this week and its a difficult problem to convey to them over the phone because ... yeah, the internet works... but its just sh*te!!!

hightower1

I think its something local in yer own areas TBH. My connection is fine and seems like any UPC ip address routs through this 84.116.238.22 ip. Possibly their launching point on to Aorta (if you note after this its all Euro locals). I tested on three diff UPC ip's and all getting low pings from 84.116.238.22. I am running to a google ip but the destination ip doesnt matter as I have said they all get routerd through this. So if the server 84.116.238.22 is giving low pings (under 30ms) for only some it seems like its specific to some particular areas.

Poss the best way to the bottom of this would be to post trace rt's to a common ip noting the MS through the suspect ip address.....Hope it helps.

SaKuRa

Hightower have u run these in the last hour or so?As there seems to be a pattern,between 9am and about 11am,and then 4pm to about 5.30pm every thing is fine,all other times the pings go very high,Ive done a speedtest to Dublin and its now 10ms,but when I hop on the PC tonite to try an online game it will be 182ms.

game4it70

hightower1 wrote: »

I think its something local in yer own areas TBH. My connection is fine and seems like any UPC ip address routs through this 84.116.238.22 ip. Possibly their launching point on to Aorta (if you note after this its all Euro locals). I tested on three diff UPC ip's and all getting low pings from 84.116.238.22. I am running to a google ip but the destination ip doesnt matter as I have said they all get routerd through this. So if the server 84.116.238.22 is giving low pings (under 30ms) for only some it seems like its specific to some particular areas.

Poss the best way to the bottom of this would be to post trace rt's to a common ip noting the MS through the suspect ip address.....Hope it helps.

I totally agree with you.

Mine is back to full speed again (for the time being i suspect).
I can ping 84.116.238.22 at any time and get less than 30ms from it but when my net is playing up and i pass through that IP that it is where the problems starts.

And for anyone who thinks its server issues with speedtest.net rule that out and try ping/tracert the likes of bbc.co.uk (routes through 84.116.238.22)or any european IP for that matter and more the likely you will get close to 200ms.
Yahoo.co.uk is fine for me as it route through 84.116.238.21 as opposed tp .22

I was talking to a supervisor about this on monday evening (who has read this thread btw) but has not even mailed me back with any updates about all the tests i had sent him.They too all pointed to that IP as the problem.
So like all of you in the same boat i'm getting more than a little agrieved at the lack of UPC support in this matter.

Skittle

That doesn't make sense that it'd be a local thing, it has to be a network routing type issue. If you look back on my post, with the tracert's, you'll see that one trace is fine and doesn't go through the Austrian node, and another tracert to another machine host by the same company in the same physical location in London, goes through the Austrian node and has crap pings.

game4it70

SaKuRa wrote: »

Hightower have u run these in the last hour or so?As there seems to be a pattern,between 9am and about 11am,and then 4pm to about 5.30pm every thing is fine,all other times the pings go very high,Ive done a speedtest to Dublin and its now 10ms,but when I hop on the PC tonite to try an online game it will be 182ms.

I have tested it at 5.30am the last to mornings and its fine then but yes it goes crap from 11am onwards.Yesterday was weird that it was fine for maybe 40-60 mins as you said around 5pm approx then crap for the rest of the night.So we are all looking at the same fault i'd say and i dobt an enginner call out is gonna fix it.

hightower1

Ok so lets agree on an ip address we can trace rt and pass through the 84.116.238.22 and see if we all get the same MS for it? If we dont then we can see its only area specific? we can compare ping times then?

game4it70

Skittle wrote: »

That doesn't make sense that it'd be a local thing, it has to be a network routing type issue. If you look back on my post, with the tracert's, you'll see that one trace is fine and doesn't go through the Austrian node, and another tracert to another machine host by the same company in the same physical location in London, goes through the Austrian node and has crap pings.

I run two game servers based in london and one has far better pings than the other when net goes bad.
I would presume that both IP's are on the same network 193.93.45.162 and 193.93.45.159 but with the 2nd IP i dont route through 84.116.238.22 so it pings at about 50ish where the first IP ping around 180,


Hightower do you want to post an IP and i will test now?

game4it70

Bang on 11.30 and its going bad again.Speed slowing and pings rising:mad::mad::mad:

FFS UPC get your act together!!!

docmol

Tracert to the two gaming servers listed above


C:\Users\dave>tracert 193.93.45.162
Tracing route to 193.93.45.162 over a maximum of 30 hops
1 1 ms 1 ms 1 ms 192.168.1.1
2 7 ms 5 ms 6 ms 10.94.192.1
3 1045 ms 23 ms 9 ms 089-101-173033.ntlworld.ie [89.101.173.33]
4 8 ms 8 ms 7 ms 84.116.238.6
5 28 ms 28 ms 28 ms nl-ams05a-rd1-gige-3-0.aorta.net [213.46.160.97]
6 28 ms 23 ms 24 ms fr-par02a-ra2-ge-0-0-0_0.aorta.net [213.46.163.9
0]
7 25 ms 24 ms 37 ms xe-0-1-0-117.par20.ip4.tinet.net [213.200.76.133
]
8 98 ms 40 ms 34 ms xe-10-3-0.lon20.ip4.tinet.net [89.149.184.45]
9 33 ms 34 ms 32 ms rackage-gw.ip4.tinet.net [213.200.79.246]
10 33 ms 34 ms 35 ms 193.93.45.162
Trace complete.
C:\Users\dave>tracert 193.93.45.159
Tracing route to 193.93.45.159 over a maximum of 30 hops
1 1 ms 1 ms 1 ms 192.168.1.1
2 8 ms 8 ms 10 ms 10.94.192.1
3 27 ms 8 ms 10 ms 089-101-173001.ntlworld.ie [89.101.173.1]
4 15 ms 9 ms 10 ms 84.116.238.2
5 80 ms 80 ms 82 ms 84.116.238.22
6 110 ms 109 ms 117 ms nl-ams05a-rd1-gige-3-0.aorta.net [213.46.160.97]
7 110 ms 111 ms 106 ms fr-par02a-ra2-ge-0-0-0_0.aorta.net [213.46.163.9
0]
8 113 ms 139 ms 109 ms xe-0-1-0-117.par20.ip4.tinet.net [213.200.76.133
]
9 113 ms 109 ms 109 ms xe-10-3-0.lon20.ip4.tinet.net [89.149.184.45]
10 113 ms 121 ms 114 ms rackage-gw.ip4.tinet.net [213.200.79.246]
11 116 ms 116 ms 118 ms 193.93.45.159
Trace complete.

Better than usual, but still unacceptable.
84.116.238.22 seems to be the problem allright

Dublin_Gunner

docmol wrote: »

Tracert to the two gaming servers listed above


C:\Users\dave>tracert 193.93.45.162
Tracing route to 193.93.45.162 over a maximum of 30 hops
1 1 ms 1 ms 1 ms 192.168.1.1
2 7 ms 5 ms 6 ms 10.94.192.1
3 1045 ms 23 ms 9 ms 089-101-173033.ntlworld.ie [89.101.173.33]
4 8 ms 8 ms 7 ms 84.116.238.6
5 28 ms 28 ms 28 ms nl-ams05a-rd1-gige-3-0.aorta.net [213.46.160.97]
6 28 ms 23 ms 24 ms fr-par02a-ra2-ge-0-0-0_0.aorta.net [213.46.163.9
0]
7 25 ms 24 ms 37 ms xe-0-1-0-117.par20.ip4.tinet.net [213.200.76.133
]
8 98 ms 40 ms 34 ms xe-10-3-0.lon20.ip4.tinet.net [89.149.184.45]
9 33 ms 34 ms 32 ms rackage-gw.ip4.tinet.net [213.200.79.246]
10 33 ms 34 ms 35 ms 193.93.45.162
Trace complete.
C:\Users\dave>tracert 193.93.45.159
Tracing route to 193.93.45.159 over a maximum of 30 hops
1 1 ms 1 ms 1 ms 192.168.1.1
2 8 ms 8 ms 10 ms 10.94.192.1
3 27 ms 8 ms 10 ms 089-101-173001.ntlworld.ie [89.101.173.1]
4 15 ms 9 ms 10 ms 84.116.238.2
5 80 ms 80 ms 82 ms 84.116.238.22
6 110 ms 109 ms 117 ms nl-ams05a-rd1-gige-3-0.aorta.net [213.46.160.97]
7 110 ms 111 ms 106 ms fr-par02a-ra2-ge-0-0-0_0.aorta.net [213.46.163.9
0]
8 113 ms 139 ms 109 ms xe-0-1-0-117.par20.ip4.tinet.net [213.200.76.133
]
9 113 ms 109 ms 109 ms xe-10-3-0.lon20.ip4.tinet.net [89.149.184.45]
10 113 ms 121 ms 114 ms rackage-gw.ip4.tinet.net [213.200.79.246]
11 116 ms 116 ms 118 ms 193.93.45.159
Trace complete.

Better than usual, but still unacceptable.
84.116.238.22 seems to be the problem allright

Eh, 89.101.173.33 seems to have a bit of an issue also........

docmol

True, but I should be asleep at this ungodly hour, so I missed it!

game4it70

Excuse the long reply but from the same ips above before and after the dreaded 11.30am downturn of service.

11am
Tracing route to 193.93.45.162 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 5 ms 5 ms 6 ms 10.96.192.1
3 7 ms 8 ms 7 ms 089-101-170161.ntlworld.ie [89.101.170.161]
4 6 ms 6 ms 9 ms 84.116.238.2
5 6 ms 8 ms 7 ms 84.116.238.22
6 24 ms 24 ms 23 ms nl-ams05a-rd1-gige-3-0.aorta.net [213.46.160.97]

7 26 ms 22 ms 24 ms fr-par02a-ra2-ge-0-0-0_0.aorta.net [213.46.163.9
0]
8 33 ms 36 ms 25 ms xe-0-1-0-117.par20.ip4.tinet.net [213.200.76.133
]
9 32 ms 30 ms 36 ms xe-10-2-0.lon20.ip4.tinet.net [89.149.185.210]
10 33 ms 31 ms 32 ms rackage-gw.ip4.tinet.net [213.200.79.246]
11 30 ms 34 ms 33 ms 193.93.45.162

Trace complete.



11am
Tracing route to 193.93.45.159 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 7 ms 12 ms 10.96.192.1
3 6 ms 9 ms 13 ms 089-101-170193.ntlworld.ie [89.101.170.193]
4 6 ms 5 ms 6 ms 84.116.238.6
5 24 ms 31 ms 25 ms nl-ams05a-rd1-gige-3-0.aorta.net [213.46.160.97]

6 23 ms 26 ms 24 ms fr-par02a-ra2-ge-0-0-0_0.aorta.net [213.46.163.9
0]
7 24 ms 23 ms 23 ms xe-0-1-0-117.par20.ip4.tinet.net [213.200.76.133
]
8 35 ms 31 ms 31 ms xe-7-1-0.lon20.ip4.tinet.net [89.149.185.58]
9 31 ms 34 ms 31 ms rackage-gw.ip4.tinet.net [213.200.79.246]
10 31 ms 32 ms 30 ms 193.93.45.159

Trace complete.












11.35am
Tracing route to 193.93.45.159 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 31 ms 6 ms 5 ms 10.96.192.1
3 7 ms 7 ms 7 ms 089-101-170193.ntlworld.ie [89.101.170.193]
4 7 ms 30 ms 16 ms 84.116.238.6
5 24 ms 23 ms 23 ms nl-ams05a-rd1-gige-3-0.aorta.net [213.46.160.97]

6 27 ms 23 ms 26 ms fr-par02a-ra2-ge-0-0-0_0.aorta.net [213.46.163.9
0]
7 24 ms 31 ms 24 ms xe-0-1-0-117.par20.ip4.tinet.net [213.200.76.133
]
8 30 ms 31 ms 32 ms xe-7-1-0.lon20.ip4.tinet.net [89.149.185.58]
9 32 ms 31 ms 33 ms rackage-gw.ip4.tinet.net [213.200.79.246]
10 33 ms 31 ms 31 ms 193.93.45.159

Trace complete.



11.35am
Tracing route to 193.93.45.162 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 6 ms 6 ms 4 ms 10.96.192.1
3 6 ms 5 ms 6 ms 089-101-170161.ntlworld.ie [89.101.170.161]
4 7 ms 5 ms 6 ms 84.116.238.2
5 58 ms 61 ms 60 ms 84.116.238.22
6 74 ms 73 ms 73 ms nl-ams05a-rd1-gige-3-0.aorta.net [213.46.160.97]

7 74 ms 75 ms 76 ms fr-par02a-ra2-ge-0-0-0_0.aorta.net [213.46.163.9
0]
8 83 ms 80 ms 81 ms xe-0-1-0-117.par20.ip4.tinet.net [213.200.76.133
]
9 97 ms 104 ms 93 ms xe-10-2-0.lon20.ip4.tinet.net [89.149.185.210]
10 93 ms 91 ms 92 ms rackage-gw.ip4.tinet.net [213.200.79.246]
11 92 ms 90 ms 92 ms 193.93.45.162

Trace complete.

FloatingVoter

In Dublin 8, off Cork St on 20 Mbs package. Two weeks ago it was a congested node (fixed by upc without them ever admitting to it officially) and now this. A new isp beckons methinks.:(

PrivateSmokey

Seems to be dropping altogether now on & off.
Ive lost connection off 3 game servers over 20mins.
One miniut i test it I get ping of 28ms next min 240ms then it fine again its getting beyond rediculas

game4it70

Back working again and no problems with 84.116.238.22
I did a tracert on my two game servers and the .162 server has swapped route with .159 server:eek: BUT hey if they stay like they are woot woot.

Last thing was before it came back to normal i saw an engineer just finishing up messing with there equipment near my house so will just have to wait and see if he fixed it or is it just the same as yesterday,only bak for a short time.

Burgo

back to normal for the time being.

Oat23

If it goes bad again at 5.30pm, well there's no point even defending UPC.

Dublin_Gunner

I'll test again when I'm at home later. Hopefully they have done something to alleviate the problem. Somehow I doubt it..........

Oat23

Ping has risen slowly from 28 to 117 in the last 30 mins.

SaKuRa

Seems ok here 10ms to Dublin server,but for how long?Engineer coming tomorrow afternoon,typically if will be fine when they come.

game4it70

Speeds have stayed good on most speedtest servers(used to get bad results)



Galway and Coventry servers have gone bad now (used to get good results)



My two game servers have swaped routes,i now have 45+ pings on one and 140+ on the other.Again it starts with that 84.116.238.22 ping

In my very unexperienced opinion it looks like basically all they have done is rerouted there traffic but its still not right.

pixelburp

Nope, mine is still poor;

http://www.speedtest.net/result/538426331.png

This is most frustrating

mccreesj

Downloaded a 100mb file from Rapidshare, took 1 minute exactly at a speed of 1690kb/s.

Although that'll probably fluctuate now.

FloatingVoter

Dublin 8 (Cork St.) still poor...



ignore the stated time, snapped at 7.04 pm Dublin time.