Working with a DSL support group for a Texas based ISP that uses cisco 678 routers, and being a cable user at home I often see both sides of service outages. At no time during the Code Red storms did a DSL line go down, nor was service not provided. The DSL lines were up and passing traffic. The problem was that the traffic was causing buffer overflows in the Cisco CBOS on the 67x routers. DSL providers usually provide unfiltered access and they did...an ISP cannot be held responsible for mailicious activity online. They don't create the viruses and neither do they hold your hand while you are online.
Most of the time the routers in question are the property of the customer. If it is the customers equipment, then it is the customers responsibility to maintain the equipment. I think that is why ISPs prefer to give the stuff away...less need for maintenance on their end.
If the problem occurring was because the ISP had IIS servers running their DNS, DHCP and so on I can see that as being an offense worthy of a refund...but why should they be held responsible against an attack against you?
Slashdot Mirror
Are the last few comments a joke? Otherwise I would have to say that anti-social is a little on the light side to describe such hostility.
Working with a DSL support group for a Texas based ISP that uses cisco 678 routers, and being a cable user at home I often see both sides of service outages. At no time during the Code Red storms did a DSL line go down, nor was service not provided. The DSL lines were up and passing traffic. The problem was that the traffic was causing buffer overflows in the Cisco CBOS on the 67x routers. DSL providers usually provide unfiltered access and they did...an ISP cannot be held responsible for mailicious activity online. They don't create the viruses and neither do they hold your hand while you are online.
Most of the time the routers in question are the property of the customer. If it is the customers equipment, then it is the customers responsibility to maintain the equipment. I think that is why ISPs prefer to give the stuff away...less need for maintenance on their end.
If the problem occurring was because the ISP had IIS servers running their DNS, DHCP and so on I can see that as being an offense worthy of a refund...but why should they be held responsible against an attack against you?