NTL slow?

neoapple · 01-11-2005, 21:06

i live in bromley, kent
im on a 1mb conection, now when i click to load a page it takes twice as long to load it!
Its running really slow today and was not running slow yesterday, anyone else have this issue?
I cant even access windows update that fast! takes over 30 seconds to load the main page!
when i load other pages it says done but shows a white screen then after 3 seconds loads the page

i tried clearing cache, rebooting ntl set top box and a flush dns, still no luck.

Gareth · 01-11-2005, 21:51

Timing websites loading is kinda subjective... any chance you can try pinging a few servers and pasting the results in here for us to see? Ping results will be more objective than a web page loading.

neoapple · 01-11-2005, 22:38

Reply from 216.239.57.99: bytes=32 time=162ms TTL=237
Reply from 216.239.57.99: bytes=32 time=260ms TTL=237
Reply from 216.239.57.99: bytes=32 time=163ms TTL=237
Reply from 216.239.57.99: bytes=32 time=486ms TTL=237

Ping statistics for 216.239.57.99:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 162ms, Maximum = 486ms, Average = 267ms

Pinging extremephpbb.com [216.32.89.226] with 32 bytes of data:
Reply from 216.32.89.226: bytes=32 time=287ms TTL=44
Reply from 216.32.89.226: bytes=32 time=134ms TTL=44
Reply from 216.32.89.226: bytes=32 time=225ms TTL=44
Reply from 216.32.89.226: bytes=32 time=337ms TTL=44
Ping statistics for 216.32.89.226:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 134ms, Maximum = 337ms, Average = 245ms

carlingman · 01-11-2005, 22:55

Quote:

Originally Posted by neoapple

i live in bromley, kent
im on a 1mb conection, now when i click to load a page it takes twice as long to load it!
Its running really slow today and was not running slow yesterday, anyone else have this issue?
I cant even access windows update that fast! takes over 30 seconds to load the main page!
when i load other pages it says done but shows a white screen then after 3 seconds loads the page

i tried clearing cache, rebooting ntl set top box and a flush dns, still no luck.

Try changing and experimenting with a proxy server.

Take a look here

Chris W · 01-11-2005, 23:00

proxy servers only catch traffic on port 80, so the ping test results indicate that the problems lie elsewhere.

Running any peer to peer software per chance? If not have you checked for spyware/ virus infection?
__________________

as this appears not to be a proxy problem, i'm moving the thread to the ntl broadband discussion area.

carlingman · 01-11-2005, 23:05

Quote:

Originally Posted by Chris W

proxy servers only catch traffic on port 80, so the ping test results indicate that the problems lie elsewhere.

Running any peer to peer software per chance? If not have you checked for spyware/ virus infection?
__________________

as this appears not to be a proxy problem, i'm moving the thread to the ntl broadband discussion area.

Ahh its late but no excuse and I will still put my

hat on and go and sit in the corner.

Gareth · 01-11-2005, 23:10

Ouch, the pings are worse than I'd have expected... saying that, what speed have you got?

Also, can you do a tracert to one of those sites you pinged, and we'll see if that helps shed any light on the problem.

Cheers

neoapple · 01-11-2005, 23:41

i have 1mb conection
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Dan>tracert google.com
Tracing route to google.com [216.239.37.99]
over a maximum of 30 hops:
1 1 ms 2 ms 1 ms 192.168.2.1
2 9 ms 11 ms 18 ms 10.33.112.1
3 10 ms 12 ms 10 ms brom-t2cam1-a-ge93.inet.ntl.com [80.1.226.5]
4 206 ms 203 ms 199 ms brom-t2core-a-ge-wan61.inet.ntl.com [80.1.225.5]
5 12 ms 11 ms 17 ms pop-bb-a-so-210-0.inet.ntl.com [62.253.184.105]
6 15 ms 17 ms 17 ms 195.50.91.69
7 15 ms 14 ms 13 ms ge-0-3-0-0.bbr2.London1.Level3.net [4.68.128.125
]
8 84 ms 87 ms 85 ms ae-0-0.bbr2.NewYork1.Level3.net [64.159.1.42]
9 82 ms 84 ms 83 ms ae-21-52.car1.NewYork1.Level3.net [4.68.97.52]
10 * 85 ms 96 ms 4.78.164.70
11 86 ms 86 ms 90 ms 64.233.175.105
12 86 ms 85 ms 87 ms 66.249.94.235
13 94 ms 85 ms 91 ms 66.249.95.123
14 93 ms 88 ms 85 ms 64.233.174.130
15 89 ms 86 ms 87 ms 216.239.48.110
16 85 ms 85 ms 97 ms 216.239.37.99
Trace complete.
C:\Documents and Settings\Dan>

looks like a ntl issue

Chris W · 01-11-2005, 23:49

that is as i would expect- one slow hop is normally just because the router is busy (a core would be) and gives lowest priority to icmp traffic.

Are you using peer to peer software and have you done full spyware/ virus scans?

neoapple · 02-11-2005, 10:14

its on a newly formatted pc. i have none of that installed. i have avg pro installed and updated.

hjf288 · 02-11-2005, 16:42

2Mbit - Web performance is dismal

Tools / What's my proxy?

Results:

You are an ntl customer but do not appear to be using a proxy.

Your Real IP address is xxx.xxx.xxx.xxx

All IP test and proxy test sites report im using no proxy at all now..

Tracing route to www.msn.co.uk [213.199.154.54]
over a maximum of 30 hops:
1 17 ms 7 ms 6 ms 10.21.112.1
2 8 ms 7 ms 30 ms oldh-t2cam1-b-ge-wan43-117.inet.ntl.com [80.5.16
4.197]
3 36 ms 7 ms 8 ms manc-t3core-1b-ge-011-0.inet.ntl.com [213.104.24
2.169]
4 13 ms 9 ms 8 ms man-bb-b-so-400-0.inet.ntl.com [213.105.242.245]
5 14 ms 20 ms 33 ms win-bb-a-so-300-0.inet.ntl.com [62.253.185.138]
6 15 ms 14 ms 15 ms gfd-bb-b-so-500-0.inet.ntl.com [213.105.172.130]
7 26 ms 28 ms 15 ms tele-ic-2-so-110-0.inet.ntl.com [62.253.185.74]
8 * 212.250.14.58 reports: Destination net unreachable.

inetnum: 212.250.14.0 - 212.250.15.255
netname: NTL
descr: NTL Infrastructure - Private Peering
country: GB
admin-c: NNMC1-RIPE
tech-c: NNMC1-RIPE
status: ASSIGNED PA
mnt-by: AS5089-MNT
remarks: INFRA-AW
changed: **********@ntli.net 20030331
source: RIPE
route: 212.250.0.0/16
descr: NTL-UK-IP-BLOCK-2
origin: AS5089
mnt-by: AS5089-MNT
changed: ***********@ntli.net 19990810
source: RIPE

C:\Documents and Settings\Henry J. Fallon>tracert www.microsoft.com
Tracing route to lb1.www.ms.akadns.net [207.46.19.60]
over a maximum of 30 hops:
1 7 ms 8 ms 7 ms 10.21.112.1
2 8 ms 9 ms 5 ms oldh-t2cam1-a-ge-wan43-117.inet.ntl.com [80.5.16
4.69]
3 31 ms 6 ms 7 ms manc-t3core-1a-ge-012-0.inet.ntl.com [213.104.24
2.73]
4 7 ms 9 ms 29 ms man-bb-a-so-400-0.inet.ntl.com [213.105.172.241]
5 36 ms 14 ms 22 ms ren-bb-b-so-000-0.inet.ntl.com [62.253.185.169]
6 14 ms 11 ms 11 ms ren-bb-a-ae0-0.inet.ntl.com [62.253.185.185]
7 34 ms 40 ms 18 ms bre-bb-b-so-200-0.inet.ntl.com [62.253.185.166]
8 18 ms 19 ms 28 ms bre-bb-a-ae0-0.inet.ntl.com [213.105.172.86]
9 40 ms 22 ms 25 ms redb-ic-1-so-010-0.inet.ntl.com [62.253.188.106]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.

Chrysalis · 02-11-2005, 18:29

this should be in proxy section.

hjf288 · 02-11-2005, 20:37

Quote:

Originally Posted by Chrysalis

this should be in proxy section.

Why? The guy and myself are complaining about general slowness of the connection.

FTP isnt affected by proxies nor is NNTP

HTTP doesnt appear to be since I dont have a proxy and have checked via numerous methods.

Chrysalis · 03-11-2005, 14:58

sorry I didnt see ftp and nntp mentioned my apologies.

Chris W · 03-11-2005, 21:08

Quote:

Originally Posted by Chrysalis

this should be in proxy section.

nope it shouldn't... It was there, and i moved it here when we established it is not a proxy issue.

If you feel a thread is in the wrong place, please do not post in the thread stating this, as it is often a long time before one of the team will read the post (like i have only just got round to reading this now). Reporting a post is the easiest way to bring something to the Teams attention- i see no reason why reporting cannot be used for threads that are in the wrong place.