BarTender: Another thing worth doing is ringing up TCL (or perhaps send them an e-mail :) and ask if your provisioning is correct, since your data cap may be incorrect (if you have changed plans) or they may not have enabled "Auto MAC address detection" or something similar, this means that you don't need to reboot your cable modem if you swap between different devices connected to the surfboard.

However the random disconnects could just be caused by a new subscriber who connected to your node who has the same IP Address range on your private network.

Horace: What area are you in?

BarTender: It could be an ARP storm, two cheap routers / other boxes on the network deciding to "ARP for africa" and that could in theory take down the local default route if there was enough traffic. However since everyones upstream is capped I would think it would take a few faulty boxes to achieve this.

Always try and traceroute to google or some other international site when you are having an outage, whenever I have had the micro outage it's been on the third or fourth hop that is still somewhere within TCL's internal network, however that hasn't happened for at least 1 month+

Galta304:

I had a bizarre experience with Telstraclear (TCL) yesterday.

I am currently in the process of relocating from Seatoun Heights, Seatoun in Wellington to Brunswick Street, Lower hutt. Both areas are within TCL stated cable network zone. I currently have TCL cable service and have had so for over a year and a half. I am very satified with the service, therefore I was hoping to continue receiving the service at my new home. However when I called TCL I was told there was no availability to that specific dwelling. This, I was told, was because it was a multiunit dwelling and that there was some conflict with TCL as Telecom was connected to some of those dwellings at the complex (please note the dwellings are simply flats side by side, not an apartment complex). I enquired if there were other properties receiving TCL cable and was advised that the neighbouring properties (on the same street!) had availability. I stated that this doesn't make sense and the representive transfered me to someone else.

Representive number two stated that representive number one did not know what he was talking about and that the reason that the dwelling cannot receive cable from TCL is because it is too close to the CBD of lower hutt. The representive further stated that because of this proximity to Lower Hutt's CBD there is no availability to this dwelling as TCL is not allowed to conflict with existing fibre/cable infrastructure in the CBD area. How can this be if the neighbours are getting cable internet from TCL!

There seems to be underlying truth to this discriminatory selection of servicability, to dwellings that have cable running down there street, that TCL are not revealing.

If anyone can enlighten me as to why this is please advise.

Horace: If you do have a router, and its getting dropouts, try changing the DHCP range to a less common one, eg: 192.168.1.x, 192.168.0.x, 192.168.2.x, try changing it to a less common one, maybe 192.168.23.x, (just pick any random number). Have had that fix my problems and a few friends.

lchiu7: Well that seemed to work for me - that is change the address range of my local network from 192.168.1.xxx to 192.168.2.xxx. Alas that has also broken DHCP for me since my router only does DHCP on the 192.168.1.x range. So that meant hard coding the IP addresses etc. for 7 devices on the network :( But so far, no microoutages.

BarTender:

lchiu7: Well that seemed to work for me - that is change the address range of my local network from 192.168.1.xxx to 192.168.2.xxx. Alas that has also broken DHCP for me since my router only does DHCP on the 192.168.1.x range. So that meant hard coding the IP addresses etc. for 7 devices on the network :( But so far, no microoutages.

What sort of router are you running??? Sounds like a very wonky box unless it's a custom Linux box.  Normally most of the consumer boxes when you change the internal range it also changes the DHCP range (Linksys, DLink, etc) so I would expect somewhere in the UI is the DHCP range, which you sould probably also change so then it issues correct DHCP addresses.
Typlically I see the Internal IP address range being anything you want, and the DHCP server settings are something like "Enabled, and then x.x.x.100 - x.x.x.200, where you can only change the last octect of the DHCP range, the other parts are hard coded to whatever the internal IP Address range is.

However glad to hear that you are no longer having microoutages.