![]() |
Dire browsing in Peterborough
Anyone else having browsing problems? 1 minute im getting 2mb the next its about 600k and thats if it responds at all.
|
Re: Dire browsing in Peterborough
I thought it was just me.....Does seem to be hit and miss at the minute
|
Re: Dire browsing in Peterborough
my pings are fine according to Dan Elwells speed test, its just downloading thats a problem. If i run dan elwells speed test the download test fails but everythnig else looks ok. If i run robin walkers speed test i get varying results from it not working at all to 3 out of the 4 tests working.
Tracert to the cableforum site times out but its way past leaving NTL |
Re: Dire browsing in Peterborough
Downloading fine for me, its the actual browsing which is slow. I'm getting quite a few sites timing out before I refresh the page, then all is fine
|
Re: Dire browsing in Peterborough
i live in letchworth and my download speeds were excellent over the weekend but from monday have been terrible.
|
Re: Dire browsing in Peterborough
This is a trace i just ran
Tracing route to cableforum.co.uk [66.199.235.18] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.1.1 2 36 ms 8 ms 17 ms 10.111.144.1 3 7 ms 8 ms 7 ms pete-t2cam1-a-ge95.inet.ntl.com [80.3.130.17] 4 19 ms 13 ms 44 ms pete-t2core-a-ge-wan61.inet.ntl.com [80.3.129.5] 5 10 ms 10 ms 13 ms nth-bb-a-so-130-0.inet.ntl.com [62.253.188.225] 6 56 ms 13 ms 15 ms gfd-bb-b-so-400-0.inet.ntl.com [62.253.185.98] 7 18 ms 14 ms 14 ms redb-ic-1-as0-0.inet.ntl.com [213.105.174.138] 8 66 ms 13 ms 15 ms linx-gw1.peer1.net [195.66.224.156] 9 94 ms 116 ms 94 ms oc12-pos5-0.nyc-telx-dis-a.peer1.net [216.187.115.225] 10 102 ms 123 ms 115 ms 64.34.84.114 11 115 ms 99 ms 100 ms 65.125.239.146 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 |
Re: Dire browsing in Peterborough
Seems fine for me here in PE1
|
Re: Dire browsing in Peterborough
Mines just as bad
Tracing route to cableforum.co.uk [66.199.235.18] over a maximum of 30 hops: 1 16 ms 40 ms 14 ms 10.111.128.1 2 28 ms 20 ms 10 ms pete-t2cam1-a-ge95.inet.ntl.com [80.3.130.17] 3 9 ms 10 ms 8 ms pete-t2core-a-ge-wan61.inet.ntl.com [80.3.129.5] 4 33 ms 58 ms 14 ms nth-bb-a-so-130-0.inet.ntl.com [62.253.188.225] 5 64 ms 49 ms 48 ms gfd-bb-b-so-400-0.inet.ntl.com [62.253.185.98] 6 33 ms 50 ms 25 ms redb-ic-1-as0-0.inet.ntl.com [213.105.174.138] 7 19 ms 18 ms 23 ms linx-gw1.peer1.net [195.66.224.156] 8 103 ms 176 ms 102 ms oc12-pos5-0.nyc-telx-dis-a.peer1.net [216.187.11 5.225] 9 111 ms 109 ms 136 ms 64.34.84.114 10 110 ms 345 ms 324 ms 65.125.239.146 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 * |
Re: Dire browsing in Peterborough
Quote:
---------- Post added at 21:23 ---------- Previous post was at 21:23 ---------- Hans can you run the same tracert for us? |
Re: Dire browsing in Peterborough
I notice you're both on 10.111.*.* UBRs (is that what the first hop is?) I'm on 10.65.*.*
---------- Post added at 21:25 ---------- Previous post was at 21:24 ---------- Tracing route to cableforum.co.uk [66.199.235.18] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.1.1 2 23 ms 41 ms 11 ms 10.65.0.1 3 20 ms 13 ms 8 ms pete-t2cam1-b-ge92.inet.ntl.com [80.3.130.129] 4 55 ms 17 ms 14 ms pete-t2core-b-ge-wan61.inet.ntl.com [80.3.129.13 3] 5 14 ms 13 ms 20 ms pete-t2core-a-ge-wan81.inet.ntl.com [80.3.129.1] 6 40 ms 35 ms 18 ms nth-bb-a-so-130-0.inet.ntl.com [62.253.188.225] 7 23 ms 15 ms 24 ms gfd-bb-b-so-400-0.inet.ntl.com [62.253.185.98] 8 25 ms 33 ms 19 ms redb-ic-1-as0-0.inet.ntl.com [213.105.174.138] 9 15 ms 15 ms 15 ms linx-gw1.peer1.net [195.66.224.156] 10 99 ms 94 ms 94 ms oc12-pos5-0.nyc-telx-dis-a.peer1.net [216.187.11 5.225] 11 117 ms 113 ms 100 ms 64.34.84.114 12 143 ms 100 ms 96 ms 65.125.239.146 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 * * Those last hops are timing out for me aswell, but my browsing is fine. Oh and dodgy pings could be because I'm downloading |
Re: Dire browsing in Peterborough
i`m having the same problems oldham area.
i spoke to ntl and they gave me this address for a speed check www.numion.com |
Re: Dire browsing in Peterborough
just spoke to NTL, there is a problem in the cable 4 area (what ever that means) this may be affecting the cable 4 1 area too which im in apparently (what ever that means!!)
funnily enough they got me to run robin walkers speed test!! |
Re: Dire browsing in Peterborough
We're having similar problems here too, ongoing for the last few weeks. Calling CS is no good whatsoever, the problem has been blamed on our router although removing it made no difference at all. Then on other occasions they have agreed yes there is a problem, and it will be resolved in 24 hours, or 48 hours, or 'soon', or whatever tosh they feel like telling you. I'm fed up with ringing them, and filling out the Responstek form was no good either - the reply I got (a week later!) told me to ring CS...................
|
Re: Dire browsing in Peterborough
Quote:
:Yikes: FIXED ITSELF, now how is it going to do that??? |
Re: Dire browsing in Peterborough
Im on 10MB in the swansea area and I am running at just over 1MB after doing several speed tests!
Nothing new though after all this is NTL. Edit: Spoke to soon im now running at 800k |
Re: Dire browsing in Peterborough
Quote:
|
Re: Dire browsing in Peterborough
Quote:
|
Re: Dire browsing in Peterborough
Quote:
|
Re: Dire browsing in Peterborough
Quote:
|
Re: Dire browsing in Peterborough
Quote:
---------- Post added at 23:24 ---------- Previous post was at 22:21 ---------- gets worse! Tue, 6 Dec 2005 23:22:40 UTC 1st 128K took 551 ms = 237880 Bytes/sec = approx 1979 kbits/sec 2nd 128K took 521 ms = 251578 Bytes/sec = approx 2093 kbits/sec 3rd 128K took 19608 ms = 6685 Bytes/sec = approx 56 kbits/sec 4th 128K took 19628 ms = 6678 Bytes/sec = approx 56 kbits/sec |
Re: Dire browsing in Peterborough
i cant believe this!!
NTL(India) are telling me that because im on the 2Meg service that a throughput of 249kbps is fine. They dont seem to understand the 249kbps id BITS and not BYTES. They are multiply 249 * 8 and saying thats 2 meg!!! WTF it should be 249 / 8 which is 31kB. ---------- Post added at 09:40 ---------- Previous post was at 08:24 ---------- Great!! theyre going to move me from UBR 1 to UBR 4. UBR 4 has known problems and thyre going to move me onto that UBR because its CLOSER!! why is it closer?? |
Re: Dire browsing in Peterborough
Quote:
Tracing route to cableforum.co.uk [66.199.235.18] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.1.1 2 9 ms 6 ms 8 ms 10.111.144.1 3 15 ms 8 ms 7 ms pete-t2cam1-a-ge95.inet.ntl.com [80.3.130.17] 4 7 ms 8 ms 8 ms pete-t2core-a-ge-wan61.inet.ntl.com [80.3.129.5] 5 9 ms 9 ms 10 ms nth-bb-a-so-130-0.inet.ntl.com [62.253.188.225] 6 13 ms 16 ms 14 ms gfd-bb-b-so-400-0.inet.ntl.com [62.253.185.98] 7 16 ms 14 ms 15 ms redb-ic-1-as0-0.inet.ntl.com [213.105.174.138] 8 14 ms 16 ms 17 ms linx-gw1.peer1.net [195.66.224.156] 9 93 ms 92 ms 93 ms oc12-pos5-0.nyc-telx-dis-a.peer1.net [216.187.115.225] 10 93 ms 95 ms 94 ms 64.34.84.114 11 95 ms 106 ms 97 ms 65.125.239.146 12 * * * Request timed out. 13 * * * Request timed out. 14 * * |
Re: Dire browsing in Peterborough
wicked that trace looks ok plus when browsing cable forum you will connect to a proxy and that proxy connects to the site. It could be you just have a bad proxy and need to specify one manually.
|
Re: Dire browsing in Peterborough
Quote:
I dont know what the cause of the slow browsing was but the cure was supposed to be a change of UBR. Maybe the last time i rebooted it changed proxy? |
Re: Dire browsing in Peterborough
If you dont specify a proxy one is picked dependant on the website you are browsing, if you browse a dozen or so sites you may well be using 3 or 4 different proxies over the period as it doesnt tie you down to 1 proxy. The only thing that stays the same is you will always use a proxy in your area so say for me I am in Leics and if there is say 6 Leics proxies then unless I specify one I will always use one of those 6 proxies.
|
| All times are GMT. The time now is 08:39. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2026, vBulletin Solutions Inc.
All Posts and Content are © Cable Forum