said by slyphoxj:Downstream signals look OK (36-38 dB SNR and 0 to -4 power level). My upstream is a bit below 35 (varies from 32-35) Would 32-35 on the upstream cause T3/T4 timeouts and modem reboots?
Unfortunately, Blaze Parkway has
always had marginal SNR at best. It's not bad, but it likes to fall out real fast and easy, which leads to unnecessary truck rolls, etcetera. That issue predates WOW's existence. But looks like it was a broadcast fix that just happened to impact network.
SNR of 35's on the low-but-ok side of normal. If anyone out of Blaze Parkway is over 38 stable, I'd be pretty surprised. But 32's too far out and needs looked into. I'd give it a day or three to let things settle and see if it's still dipping low first.
What I wanna know though, is how the hell they managed to break IPv6 even worse than before. I hardly thought it possible, but by god, they'll be damned if they let anyone even
think WOW is capable of operating a network that doesn't look and work like it's a decade out of date! Sigh.
EDIT: Well holy crap. Pardon me as I eat my words above. Not too much though. I just looked, have halfway stable SNR at 38.2-38.6 on the 609-627MHz segment and the 597-603MHz segment's all over 37.
Offset is, upstream power's gone to crap and they seem to have deliberately broken the service password. Not bloody happy about that considering I've got a lot more Arris licensing than WOW.