BB seems a little slow
 

Tue, 19 Aug 2003 17:04:46 UTC
1st 128K took 1833 ms = 71507 Bytes/sec = approx 595 kbits/sec
2nd 128K took 1862 ms = 70393 Bytes/sec = approx 586 kbits/sec
3rd 128K took 1783 ms = 73512 Bytes/sec = approx 612 kbits/sec
4th 128K took 1903 ms = 68877 Bytes/sec = approx 573 kbits/sec


600K BB and it seems really sluggish, anyone else having problems?

Your Speedtest looks fine, What exactly are you having problems with? Surfing, Or downloads?

surfing really, webpages seem to take forever to load up.
been checking services on XP pro and doesnt appear that anything is running I dont know about.
Network usage is almost non existant, processor usage is negligable.
Its taking approx 15-20 seconds for www.ntlworld.com to load

Could be a DNS problem?

Ping times to ntlworld.com are fluctuating between 26 and 66ms
Normally they are never higher than 22.


Gonna re-boot see if it clears up


*EDIT* rebooted and its got a little worse :(

Taking between 30-40 secs for any webpage to fully load here in the north west

It's happening to me as well. I think it's got something to with the constant battering that my firewall is reporting.
....I'm on 1 mb

Agreed, my firewall has been under constant attack for the best part of a week. Opinion elsewhere on this site last week was that it could be due to the extra network traffic created by the MSblast worm. Of course, there is now another worm doing the rounds, ostensibly trying to help eliminate MSblast but actually just causing more network congestion ...

http://news.bbc.co.uk/1/hi/technology/3163001.stm

the north west is bad (very slow), it looks like the dns servers, if you run a trace route it takes ages to resolves the names but the pings are not to bad

My fire wall is under constant port 88 hits, all from NTL !
every 30 seconds or so !

Wed, 2003-08-20 19:16:48 - ICMP packet - Source:81.103.188.15,[Echo Request],WAN - Destination:81.104.200.88,LAN

Any one know what's going on ?

I'm having the same problem in Peterborough, my firewall is taking a right hammering via ICMP (Ping) requests (see a sample below) from the rest of the NTL subnet. I believe that this is related to the "benign" virus thats supposed to fix the blaster worm.

I cant believe there are ppl out there who know what broadband is but dont see the need to keep patched up or firewalled.......

Firewall logs:
ate: 08/20 22:19:20 Name: ICMP PING CyberKit 2.2 Windows
Priority: 3 Type: Misc activity
IP info: 80.2.255.115:n/a -> 80.3.152.24:n/a

Date: 08/20 22:19:22 Name: ICMP PING CyberKit 2.2 Windows
Priority: 3 Type: Misc activity
IP info: 80.6.161.54:n/a -> 80.3.152.24:n/a

Date: 08/20 22:19:24 Name: ICMP PING CyberKit 2.2 Windows
Priority: 3 Type: Misc activity
IP info: 80.3.242.188:n/a -> 80.3.152.24:n/a

Date: 08/20 22:19:36 Name: ICMP PING CyberKit 2.2 Windows
Priority: 3 Type: Misc activity
IP info: 80.6.52.200:n/a -> 80.3.152.24:n/a

Date: 08/20 22:19:51 Name: ICMP PING CyberKit 2.2 Windows
Priority: 3 Type: Misc activity
IP info: 80.3.103.32:n/a -> 80.3.152.24:n/a

Date: 08/20 22:19:52 Name: ICMP PING CyberKit 2.2 Windows
Priority: 3 Type: Misc activity
IP info: 80.3.152.42:n/a -> 80.3.152.24:n/a

Date: 08/20 22:20:01 Name: ICMP PING CyberKit 2.2 Windows
Priority: 3 Type: Misc activity
IP info: 80.5.233.65:n/a -> 80.3.152.24:n/a

Date: 08/20 22:20:07 Name: ICMP PING CyberKit 2.2 Windows
Priority: 3 Type: Misc activity
IP info: 80.3.231.78:n/a -> 80.3.152.24:n/a

Date: 08/20 22:20:09 Name: ICMP PING CyberKit 2.2 Windows
Priority: 3 Type: Misc activity
IP info: 80.6.240.27:n/a -> 80.3.152.24:n/a

Date: 08/20 22:20:11 Name: ICMP PING CyberKit 2.2 Windows
Priority: 3 Type: Misc activity
IP info: 80.1.217.231:n/a -> 80.3.152.24:n/a

Date: 08/20 22:20:24 Name: ICMP PING CyberKit 2.2 Windows
Priority: 3 Type: Misc activity
IP info: 80.0.204.29:n/a -> 80.3.152.24:n/a

Date: 08/20 22:20:24 Name: ICMP PING CyberKit 2.2 Windows
Priority: 3 Type: Misc activity
IP info: 80.1.175.187:n/a -> 80.3.152.24:n/a

Date: 08/20 22:20:28 Name: ICMP PING CyberKit 2.2 Windows
Priority: 3 Type: Misc activity
IP info: 80.2.171.98:n/a -> 80.3.152.24:n/a

Date: 08/20 22:20:34 Name: ICMP PING CyberKit 2.2 Windows
Priority: 3 Type: Misc activity
IP info: 80.3.211.58:n/a -> 80.3.152.24:n/a

Date: 08/20 22:20:38 Name: ICMP PING CyberKit 2.2 Windows
Priority: 3 Type: Misc activity
IP info: 80.6.162.145:n/a -> 80.3.152.24:n/a

Date: 08/20 22:20:41 Name: ICMP PING CyberKit 2.2 Windows
Priority: 3 Type: Misc activity
IP info: 80.3.100.175:n/a -> 80.3.152.24:n/a

Date: 08/20 22:20:43 Name: ICMP PING CyberKit 2.2 Windows
Priority: 3 Type: Misc activity
IP info: 80.5.230.103:n/a -> 80.3.152.24:n/a

Date: 08/20 22:20:43 Name: ICMP PING CyberKit 2.2 Windows
Priority: 3 Type: Misc activity
IP info: 80.4.128.210:n/a -> 80.3.152.24:n/a

Date: 08/20 22:20:46 Name: ICMP PING CyberKit 2.2 Windows
Priority: 3 Type: Misc activity
IP info: 80.4.66.13:n/a -> 80.3.152.24:n/a

Bombarded too. It was going on before the worm's cure.