Network problems Tonight ? - Page 3

Chrysalis · 08-08-2005, 01:39

I believe the linx issue is resolved so if the problem still exists it could be something to do with ntl or another point of failure.
__________________

seems to be a problem with hop 16 tho

14 163 ms 168 ms 162 ms p14-0.core01.san01.atlas.cogentco.com [66.28.4.6
]
15 171 ms 166 ms 180 ms p4-0.core01.lax01.atlas.cogentco.com [66.28.4.77
]
16 273 ms 246 ms 258 ms filefront-allyance.dmarc.cogentco.com [38.112.29
.134]
17 248 ms 247 ms 276 ms node.www.la.ioerror.com [66.117.8.41]
__________________

Quote:

Originally Posted by IanUK

I'm not

I have a 3meg NTL connection, and use the AOL client in 'Bring your own access' mode on the top. Using that client routes all content through AOL's proxies rather than NTL's, all sites work at full speed through it, which is much better than the NTL Poplar Proxies which are quite frankly awful.

Sounds interesting, what url is it to use that and do you need to be an aOL customer?

I did speedtests for you full speed on both ntl auto proxy and my own proxy.

IanUK · 08-08-2005, 08:29

Link looks good at the moment, but its too early to tell - fingers crossed !

I'm getting full speed from my own Proxy at the moment.

AOL BYOA is only available if you call them I think, its ÃƒÆ’Ã†â€™ÃƒÂ¢Ã¢â€šÂ¬Ã…Â¡ÃƒÆ’Ã¢â‚¬Å¡Ãƒâ€šÃ‚Â£6.99 a month and you get all their content. To be honest a lot of their content is available elsewhere, but the radio stations are cool, and I get full speed through their client pretty much everywhere - so their proxies must be better than NTL's.

IanUK · 08-08-2005, 10:43

The trace looks good still but suddenly my speeds through my default proxy are terrible again (sub 20k)

Target Name: www.froopter.com
IP: 66.98.246.48
Date/Time: 08/08/2005 11:44:55
2 5 ms 5 ms 6 ms 5 ms [10.82.176.1]
3 14 ms 7 ms 8 ms 8 ms wapk-t2cam1-a-ge-wan41-112.inet.ntl.com [80.1.170.57]
4 7 ms 7 ms 7 ms 7 ms popl-t2core-a-ge-wan64.inet.ntl.com [62.255.81.65]
5 7 ms 7 ms 12 ms 8 ms pop-bb-a-so-330-0.inet.ntl.com [213.105.174.113]
6 8 ms 8 ms 8 ms 8 ms pop-bb-b-ae0-0.inet.ntl.com [213.105.172.77]
7 9 ms 8 ms 8 ms 9 ms tele-ic-1-so-010-0.inet.ntl.com [62.253.185.82]
8 14 ms 13 ms 13 ms 15 ms [212.250.14.62]
9 85 ms 85 ms 85 ms 85 ms p10-0.core01.bos01.atlas.cogentco.com [130.117.0.46]
10 105 ms 105 ms 106 ms 105 ms p5-0.core01.ord01.atlas.cogentco.com [66.28.4.110]
11 104 ms 104 ms 110 ms 105 ms p15-0.core02.ord01.atlas.cogentco.com [66.28.4.62]
12 117 ms 116 ms 116 ms 118 ms p12-0.core01.mci01.atlas.cogentco.com [66.28.4.33]
13 130 ms 130 ms 130 ms 130 ms p12-0.core01.iah01.atlas.cogentco.com [66.28.4.105]
14 132 ms 130 ms 132 ms 133 ms g0-2.na21.b015619-0.iah01.atlas.cogentco.com [66.28.64.66]
15 131 ms 131 ms 131 ms 132 ms everyones_internet_2.demarc.cogentco.com [38.112.25.158]
16 115 ms 114 ms 115 ms 115 ms gphou-66-98-241-27.ev1.net [66.98.241.27]
17 115 ms 114 ms 120 ms 115 ms gphou-66-98-241-125.ev1.net [66.98.241.125]
18 115 ms 115 ms 115 ms 115 ms srv1.froopter.com [66.98.246.48]

The baguely Proxy gives me back full speed again, surely it must be the Proxy(ies) ??

I don't understand this

Chrysalis · 08-08-2005, 12:33

It is the proxies by the sounds of things, I wonder if this thread can be moved to the proxy section?

IanUK · 08-08-2005, 19:44

The problem hasn't been fixed with that hop unfortunately.

Downloads are still sub 20k

Target Name: www.froopter.com
IP: 66.98.246.48
Date/Time: 08/08/2005 20:43:20
2 6 ms [10.82.176.1]
3 14 ms wapk-t2cam1-a-ge-wan41-112.inet.ntl.com [80.1.170.57]
4 8 ms popl-t2core-a-ge-wan64.inet.ntl.com [62.255.81.65]
5 12 ms pop-bb-a-so-330-0.inet.ntl.com [213.105.174.113]
6 8 ms pop-bb-b-ae0-0.inet.ntl.com [213.105.172.77]
7 9 ms tele-ic-1-so-010-0.inet.ntl.com [62.253.185.82]
8 155 ms [212.250.14.62]
9 226 ms p10-0.core01.bos01.atlas.cogentco.com [130.117.0.46]
10 247 ms p5-0.core01.ord01.atlas.cogentco.com [66.28.4.110]
11 253 ms p15-0.core02.ord01.atlas.cogentco.com [66.28.4.62]
12 261 ms p12-0.core01.mci01.atlas.cogentco.com [66.28.4.33]
13 273 ms p12-0.core01.iah01.atlas.cogentco.com [66.28.4.105]
14 274 ms g0-2.na21.b015619-0.iah01.atlas.cogentco.com [66.28.64.66]
15 278 ms everyones_internet_2.demarc.cogentco.com [38.112.25.158]
16 118 ms gphou-66-98-241-27.ev1.net [66.98.241.27]
17 121 ms gphou-66-98-241-125.ev1.net [66.98.241.125]
18 116 ms srv1.froopter.com [66.98.246.48]

IanUK · 08-08-2005, 21:10

Even worse now

Less than 11k a sec

Target Name: www.froopter.com
IP: 66.98.246.48
Date/Time: 08/08/2005 23:30:47
2 7 ms 6 ms [10.82.176.1]
3 8 ms 7 ms wapk-t2cam1-a-ge-wan41-112.inet.ntl.com [80.1.170.57]
4 7 ms 8 ms popl-t2core-a-ge-wan64.inet.ntl.com [62.255.81.65]
5 6 ms 7 ms pop-bb-a-so-330-0.inet.ntl.com [213.105.174.113]
6 7 ms 8 ms pop-bb-b-ae0-0.inet.ntl.com [213.105.172.77]
7 9 ms 14 ms tele-ic-1-so-010-0.inet.ntl.com [62.253.185.82]
8 323 ms 318 ms [212.250.14.62]
9 388 ms 390 ms p10-0.core01.bos01.atlas.cogentco.com [130.117.0.46]
10 406 ms 412 ms p5-0.core01.ord01.atlas.cogentco.com [66.28.4.110]
11 407 ms 415 ms p15-0.core02.ord01.atlas.cogentco.com [66.28.4.62]
12 421 ms 421 ms p12-0.core01.mci01.atlas.cogentco.com [66.28.4.33]
13 434 ms 435 ms p12-0.core01.iah01.atlas.cogentco.com [66.28.4.105]
14 434 ms 434 ms g0-2.na21.b015619-0.iah01.atlas.cogentco.com [66.28.64.66]
15 433 ms 436 ms everyones_internet_2.demarc.cogentco.com [38.112.25.158]
16 115 ms 115 ms gphou-66-98-241-27.ev1.net [66.98.241.27]
17 115 ms 118 ms gphou-66-98-241-125.ev1.net [66.98.241.125]
18 123 ms 116 ms srv1.froopter.com [66.98.246.48]

Got an answer to my ticket with EV1 re: them changing the route:

-------
Dear Customer,

You will need to talk to your ISP about rerouting it other than that you'll
need to wait for them to fix the issue if they can't.

Thank you for choosing ev1servers

Hollie F.
Ev1servers Support.
-------

So I guess thats a no then...

Chrysalis · 09-08-2005, 09:06

Thats an absurb reply, I have server's in various datacentres and each one has been able to change routes for me in the past.

IanUK · 09-08-2005, 09:26

I'm piggy in the middle it seems, NTL don't seem to want to fix it (although a big thank you to ignition for trying to help) and EV1 are just pointing the finger at NTL.

Meanwhile its me stuck with sub 11k access to a server I pay for

ben1004 · 10-08-2005, 12:38

This is an absolute nightmare to be honest, I'm a member of a board based in the states which has recently been running like a pig for certain members. Lo and behold it's the cogent link's that are killing access for me and others...

Im sure NTL should be doing something about this, but whether they will/are is a different matter entirely I suppose....

Chrysalis · 10-08-2005, 13:25

Well I still say its the fault of EV1 and other providers who have similiar setup's, they run a BGP setup which announces the ip's on these providers. As far as I am aware they just need to change the announce to exclude cogent then the traffic will not be routed using that provider, I have seen this done when I have asked for rerouting to be done in the past with other datacentres.

IanUK · 10-08-2005, 14:36

It would be nice to get a definative answer on this.

The route 'appears' to have been fixed, but I'm not so sure - speeds are better but I'm never sure if its the proxy or not.

At night speeds are still terrible, but the trace stays good.
But using the Bagaley proxy returns full speed, so it looks like an NTL proxy/routing problem - EV1 are adamant that it is an NTL problem.
They trace to my proxy and its awful, they trace to my ip and its good.

Come on guys, this has been going on for over a week now

Chrysalis · 11-08-2005, 07:01

Do both your ip and the proxy route the same way? You are talking about 2 different issues here I think.

IanUK · 11-08-2005, 08:59

I think its pretty clear that its a routing issue, my proxy presumably takes a different route to Cogent than the Bageley proxy, hence Bageley stays good 24 hours, the Poplar route gets congested after about 4pm, this seems to be verified by other posts complaining about Cogent connections both here (http://www.cableforum.co.uk/board/sh...084#post548084) and elsewhere.

It seems another of those occasions where NTL are neglecting to maintain their proxy servers properly

ben1004 · 11-08-2005, 09:54

Quote:

It seems another of those occasions where NTL are neglecting to maintain their proxy servers properly

I'm going through one of the Notts proxies, I've changed mine and unsurprisingly it now appears that it is working again although it's still slower than it used to be

Why don't they just fix the boogers

ben1004 · 11-08-2005, 19:03

I've just had a response to my 'feedback' that I sent Ntl, asking for me to provide traceroute's etc to them so that they could investigate further just exactly what/when the problems are appearing...

Luckily for them, I've provided them with my saved ones from both my connection and from LINX where I used the looking glass tools.. ;-)

So, IMHO I'll give Ntl 9/10 for their resolution of the problem, if they fix it they can have a 10

They were also pointed across here so that they can have a looksee at whats been going on