Merged-Manchester Browsing Slow. - Page 2

Mr.Moony · 12-01-2004, 12:35

As BBK also said, do not overlook the possibilty they will enable WCCP. Have run a few checks and found that a few seem to be online (or would asume by the ICMP response).

EDIT : That doesnt NOT mean they are in use.

rdhw · 12-01-2004, 13:33

Quote:

Originally Posted by th'engineer

NO PROXIES IN MANCHESTER

This might be worth re-checking now. There are ten proxies defined for Manchester in the DNS, and some or all of them might be online and working. They look as if they are NetApp NetCache appliances, rather than the old Inktomis.

altis · 12-01-2004, 13:54

Code:

Proxy	
Proxied HTTP?        	No	
Proxy IP	                 n/a  	
Proxy Name(Raw)		
Proxy Name(R-DNS)	No DNS Entry

BBKing · 12-01-2004, 13:58

Nope, there are ten (count em) pingable in Manchester at the moment.

Mr.Moony · 12-01-2004, 14:00

ten eh. I shall get onto FMT and see if I can dig up a list of the latest release of proxies. Dont hold your breath though....

altis · 12-01-2004, 14:13

I can confirm that all ten proxys (cache1 thru cache10) are working - but only by explicitly declaring them. By default, transparent proxying is still turned off in this area.

With or without them, this site still feels clunky at the moment. It takes about 5 seconds to refresh this page.

th'engineer · 12-01-2004, 15:19

we dont want to go down the proxy route again lets try to forget the NW
proxies.

For once everything is OK 2000 STB, different DNS than NTL only need an upload improvement then sorted.

badnbusy · 12-01-2004, 17:55

heres the packet loss i mentioned i was getting. Same as yesterday! It also has bad latency compared to the rest of the ntl system...

Tracing route to hhonline.co.uk [66.98.186.244]
over a maximum of 30 hops:

1 7 ms 9 ms 9 ms 10.22.48.1
2 9 ms 8 ms 8 ms oldh-t2cam1-a-ge92.inet.ntl.com [80.5.164.1]
3 9 ms 14 ms 8 ms mant-t2core-a-ge-wan62.inet.ntl.com [213.104.242.41]
4 9 ms 10 ms 9 ms man-bb-a-so-230-0.inet.ntl.com [62.253.184.57]
5 9 ms 9 ms 10 ms lee-bb-b-so-700-0.inet.ntl.com [62.253.185.194]
6 21 ms 9 ms 10 ms lee-bb-a-ae0-0.inet.ntl.com [62.253.187.185]
7 16 ms 17 ms 16 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]
8 * 48 ms * tele-ic-1-so-000-0.inet.ntl.com [62.253.185.82]
9 18 ms 18 ms 18 ms lndnuk1icx1.wcg.net [195.66.224.105]

[next hops are all fine...]

tried again:

Tracing route to hhonline.co.uk [66.98.186.244]
over a maximum of 30 hops:

1 10 ms 9 ms 8 ms 10.22.48.1
2 11 ms 19 ms 9 ms oldh-t2cam1-a-ge92.inet.ntl.com [80.5.164.1]
3 9 ms 8 ms 9 ms mant-t2core-a-ge-wan62.inet.ntl.com [213.104.242.41]
4 9 ms 8 ms 10 ms man-bb-a-so-230-0.inet.ntl.com [62.253.184.57]
5 11 ms 10 ms 10 ms lee-bb-b-so-700-0.inet.ntl.com [62.253.185.194]
6 10 ms 16 ms 10 ms lee-bb-a-ae0-0.inet.ntl.com [62.253.187.185]
7 15 ms 17 ms 27 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]
8 * * 51 ms tele-ic-1-so-000-0.inet.ntl.com [62.253.185.82]

Can anyone look into this?

badnbusy · 12-01-2004, 17:59

traceroute to nthellworld.co.uk:

1 9 ms 8 ms 8 ms 10.22.48.1
2 25 ms 8 ms 8 ms oldh-t2cam1-a-ge92.inet.ntl.com [80.5.164.1]
3 15 ms 9 ms 26 ms mant-t2core-a-ge-wan64.inet.ntl.com [213.104.242.53]
4 9 ms 10 ms 10 ms man-bb-a-so-230-0.inet.ntl.com [62.253.184.57]
5 9 ms 10 ms 9 ms lee-bb-b-so-700-0.inet.ntl.com [62.253.185.194]
6 10 ms 11 ms 11 ms lee-bb-a-ae0-0.inet.ntl.com [62.253.187.185]
7 15 ms 17 ms 20 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]
8 * 54 ms 50 ms tele-ic-1-so-000-0.inet.ntl.com [62.253.185.82]
9 20 ms 19 ms 18 ms lndnuk1icx1.wcg.net [195.66.224.105]
10 * 130 ms 128 ms nycmny2wcx2-oc12.wcg.net [64.200.87.149]
11 129 ms 131 ms 127 ms hrndva1wcx2-pos5-0.wcg.net [64.200.210.97]
12 129 ms 128 ms 130 ms hrndva1wcx3-oc48.wcg.net [64.200.95.74]
13 129 ms 129 ms 128 ms drvlga1wcx2-pos.wcg.net [64.200.210.57]
14 129 ms 128 ms 132 ms drvlga1wcx1-oc48.wcg.net [64.200.127.49]
15 129 ms 128 ms 130 ms dllstx1wcx3-oc48.wcg.net [64.200.240.21]
16 130 ms 127 ms 128 ms dllstx1wcx2-oc48.wcg.net [64.200.110.73]
17 128 ms * 128 ms hstntx1wce2-pos4-0.wcg.net [64.200.240.74]
18 * * 130 ms hstntx1wce2-everyonesinternet-gige.wcg.net [65.77.93.54]
19 119 ms 120 ms 119 ms ivhou-207-218-223-34.ev1.net [207.218.223.34]
20 * * *

This one shows problems with ntl, and with the provider of this site, ev1servers.net

iadom · 12-01-2004, 18:02

I can confirm that 62.253.185.244 is showing 70% packet loss on my trace to that IP from the same area as B&B.

Mr.Moony · 12-01-2004, 18:05

If one you two (if not both) would PM me your IP addy allong with MAC, I shall email this and get is escalated asap

(I will investiage first)

badnbusy · 12-01-2004, 18:07

PM sent

badnbusy · 12-01-2004, 18:10

Something not right here:

Pinging 62.253.185.82 with 32 bytes of data:

Reply from 62.253.185.82: bytes=32 time=120ms TTL=248
Reply from 62.253.185.82: bytes=32 time=42ms TTL=248
Reply from 62.253.185.82: bytes=32 time=77ms TTL=248
Request timed out
Reply from 62.253.185.82: bytes=32 time=30ms TTL=248
Request timed out
Request timed out
Reply from 62.253.185.82: bytes=32 time=72ms TTL=248
Reply from 62.253.185.82: bytes=32 time=35ms TTL=248
Reply from 62.253.185.82: bytes=32 time=88ms TTL=248
Request timed out
Reply from 62.253.185.82: bytes=32 time=118ms TTL=248
Reply from 62.253.185.82: bytes=32 time=51ms TTL=248
Reply from 62.253.185.82: bytes=32 time=59ms TTL=248
Reply from 62.253.185.82: bytes=32 time=55ms TTL=248
Request timed out
Request timed out
Request timed out
Reply from 62.253.185.82: bytes=32 time=39ms TTL=248
Reply from 62.253.185.82: bytes=32 time=100ms TTL=248
Reply from 62.253.185.82: bytes=32 time=30ms TTL=248
Reply from 62.253.185.82: bytes=32 time=125ms TTL=248
Reply from 62.253.185.82: bytes=32 time=30ms TTL=248
Reply from 62.253.185.82: bytes=32 time=25ms TTL=248
Reply from 62.253.185.82: bytes=32 time=90ms TTL=248
Reply from 62.253.185.82: bytes=32 time=26ms TTL=248
Request timed out
Request timed out
Reply from 62.253.185.82: bytes=32 time=32ms TTL=248
Reply from 62.253.185.82: bytes=32 time=71ms TTL=248
Reply from 62.253.185.82: bytes=32 time=84ms TTL=248
Request timed out
Reply from 62.253.185.82: bytes=32 time=56ms TTL=248
Reply from 62.253.185.82: bytes=32 time=65ms TTL=248

br3ach · 12-01-2004, 18:17

Check your PM's Moony, I need some info and Ill do the searchs for you then

Florence · 12-01-2004, 18:41

Still no problems here

Tracing route to www.ntlworld.com [62.253.162.30]
over a maximum of 30 hops:

1 10 ms 10 ms 10 ms 10.11.32.1
2 10 ms 10 ms 10 ms oldh-t2cam1-a-ge-wan51-120.inet.ntl.com [80.5.16
4.81]
3 10 ms 20 ms 10 ms mant-t2core-a-ge-wan62.inet.ntl.com [213.104.242
.41]
4 30 ms 10 ms 10 ms man-bb-a-so-230-0.inet.ntl.com [62.253.184.57]
5 20 ms 10 ms 10 ms man-bb-b-ae0-0.inet.ntl.com [62.253.187.178]
6 20 ms 20 ms 10 ms win-bb-a-so-300-0.inet.ntl.com [62.253.185.138]

7 30 ms 20 ms 10 ms win-dc-a-v902.inet.ntl.com [62.253.187.222]
8 20 ms 20 ms 10 ms www.ntlworld.com [62.253.162.30]

Trace complete.