Maybe a rouge tech person did NOT reset your modem something else external caused it and the tech was merely trying to fix it because he or she was alerted of it thru the remote monitoring?
I have had a situation where short flicker of my hydro off and back on caused my modem to go into some strange "stuck" state where it had lost its settings and needed to be re-initialized.
But yeah having a tech email you to let you know a ticket is open is a first for me, never seen rogers do this before, must be a new thing?
@gurnblansten wrote:
I'm having the same issues and rolling brown outs are not making life with Ignite sustainable.
Which issue are you experiencing? The Ignite gateway rebooting spontaneously (and NOT due to power issues in your area) OR that you have power issues in your area and that your local node is going down as a result?
I have the critical equipment in my home connected to a UPS, and I am fortunate that my local node has at least that much battery backup power available as well, so power outages are usually not a problem for me. Even if the batteries in your local node are aging, I would hope that it could get the Rogers equipment in your neighbourhood through a brown-out.
Knocks out my 3rd party router and screws everything up. Rogers seems to want to block, inhibit using 3rd party gear and it has become increasingly frustrating since the forced migration from the Hitron to whatever Ignite uses.
I'm running Ignite TV over my own 3rd-party network gear; I have for years, with zero issues whatsoever. Rogers won't officially support that configuration, but they also don't take any steps to block you from putting an Ignite gateway into Bridge Mode and using your own router.
Yes, I get cranky here, from time to time, and voice displeasure when something about the Ignite hardware or software really annoys me, but that's also to remind Rogers that there are users out there where a one-size-fits-all-solution doesn't... and I'm happy that we have options.
@gurnblansten wrote:
The Ignite box has been replaced. The primary Asus router has been replaced and swapped with another model at great expense. The common thread is Ignite. There where zero issues, no UPS prior using Hitron and basically same speed service I have now with Ignite.
I think that this is just a coincidence. From a technical perspective, Ignite Internet is still DOCSIS, and uses the same infrastructure in your neighbourhood as the legacy Rogers Internet service. Some would even argue that the Broadcom chipset in the Technicolor Ignite gateways is superior to the (Intel) Puma 7 chipset that is used in the Hitron CODA, and the Arris Ignite gateways are also Puma 7-based. Your speeds (on comparable plans) and the stability of your Internet service should not be any worse (or any better) with Ignite.
If you are running the Ignite gateway in Bridge Mode and using your own router, any IP connectivity breakage is between you and your CMTS router. If Rogers makes certain changes to their IP network overnight, they can do things that may break your IP connectivity. It doesn't matter whether you have Ignite Internet or the legacy Rogers Internet, there may be times when you may need to reboot your router or reset your router's WAN interface. Rogers can reboot your modem/gateway when they perform such work but they cannot reboot your router.
I suspect that if you still had legacy Rogers Internet and your Hitron CODA modem today, you would still be experiencing these same issues.
@gurnblansten wrote:
The "coincidence" of fundamentally not being able to safely reboot the Rogers Ingnite, previous or current 3rd party router to restore connections is ongoing since day 1 on Ignite. Two close friends in Tech field have ditched Rogers because Ignite simply does not play well in bridged mode with Rogers modem being used. Netgear Nightwing, Asus ROG AC5300 and RT-AX88U all have same results. Switching to Start/Teksavvy issues went away because upfront they offer bridged modems, no overhead bloat.
I don't work for Rogers. I'm also not here to irritate anybody or to defend Rogers. I just try to help others here as best as I can. I have been an Ignite TV customer for more than three years, and I run Ignite TV over my own network gear. I'm pretty familiar with all the quirks of the Ignite hardware. I'm not a fan of the (limited) "router/firewall" functionality on the Ignite gateways but they work, and they work fine in Bridge Mode.
Takes 10 business days to switch so hopefully coordinate a weekend switch. Cost with outage, switch to Ignite equals - 4-5 network overhauls, one lost day work, second emergency trip into office plus 12 hours last weekend sorting out connectivity which never happened pre-Ignite. Been with Rogers for years but can't continue with this level of problems and certainly isn't coincidence.
If you are experiencing issues with your Rogers service now, DO NOT switch to a TPIA provider. Years ago, I used to be a Rogers Digital Cable / Rogers Internet customer. I had zero issues with my Internet service but all sorts of problems with TV. Bell's Internet was HORRIBLE in my area, so I then switched to a TPIA. For the first few months, my rCable TPIA Internet service worked FLAWLESSLY. Signal levels were great, no uncorrectable codeword errors, no problems whatsoever. The TPIA provider's Internet service was fairly priced and fast. Then, suddenly, overnight, my signal levels changed, the errors (across ALL channels) SKYROCKETED, and my speeds plunged. Rogers did not care at all, would not investigate the problem and would not dispatch a tech. The service was basically unusable. Rogers would not respond to escalations, and absolutely refused to take any action to fix problems with their service. It was an absolutely miserable experience. Rogers also suddenly started sending me win-back offers; perhaps a coincidence... but also quite possibly intentional.
If you are a TPIA customer, your cables are tagged with a special tag. If a direct Rogers customer is experiencing problems with their service, your (TPIA) connection will be the first to be fed off of a splitter or moved onto a bad tap. If a contractor tech "accidentally" messes your service up while fixing another customer's problem, good luck getting Rogers to investigate.
You may have a great experience with Start or Teksavvy. However, it could also turn out to be a horrific train wreck. Have a "Plan B" in mind if your service should suddenly become unusable all of a sudden.
@gurnblansten Again, I can't relate to any of the issues that you are seeing.
I can understand legacy Rogers Internet customers being frustrated with the switch, especially if they use their Hitron CODA in gateway mode, switch to Ignite, then find that they lose a ton of configuration options with the Ignite gateway and/or have to use a mobile app for many admin functions. (Not a problem for non-technical folks, who enjoy the simplified, more polished experience for managing their network.)
For Bridge Mode users, who would prefer a basic, simple cable modem, with nothing to configure, the Ignite gateway will seem weird. In Bridge Mode, the Ignite gateway still has internal services running on it and there are still some hidden WiFi networks active. It also has internal Bluetooth LE and Zigbee radios, for IoT device connectivity, although Rogers is not currently selling any "connected home" services as of yet. Also, Home Phone is still running as well as support for a Home Security service. However, extra useless stuff notwithstanding, in Bridge Mode, my XB7 functions as a passive device and does not get in the way of anything that I have connected to it. I don't use any of the value-added features that Ignite Internet offers.
Re: needing to reboot my router, I have not had to do this in years. Ages ago, there were a few days straight where I had broken IPv6 connectivity each and every morning. As far as I could tell, Rogers was making configuration changes and their routers basically "forgot" the IPv6 PD that they had allocated to me, and stopped routing IPv6 traffic to that destination through my router. I reset my router's WAN6 interface, and the same IPv6 PD got delegated to me again, and everything started working again.
I have not had to reboot my router in years, not to fix any broken network connectivity anyway. There is no reason why your Ignite gateway (in Bridge Mode) should not perform any differently that any other cable modem.
If your ASUS routers need to be rebooted on a regular basis, they may require a minor configuration change. (Possibly due to changes that Rogers made in their network; possibly due to changes that ASUS made in their firmware.) If you are looking for expert advice with ASUS routers, @Datalink may be able to help stabilize your setup. If, for whatever reason, you would like to go back to using the Hitron CODA modem, you can always switch to Rogers Business Internet. (Fido Home Internet is another option for some, but they do not sell anything faster than 100Mb/s anymore.)
Regardless of what you decide to do, I hope that your issues get straightened out. If you want to try to get your current setup working normally, there are a number of folks here in the Community that will do their very best to help.
-
4440 views
-
2 Likes
-
-
