Forum Discussion
wh1
1 month agoOrganizer
WiFi Boost 7 Restarting Everyday Around 1AM
Hello, I've been encountering an issue which seems to have only started recently. The WiFi boost 7 I got as part of upgrade to 1.5G on Jan 2026 has recently been restarting itself around 1AM-1:30AM ...
- 18 days ago
Third day and it looks like the restarting has stopped.
Telus must have fixed something on their end in which it kept telling the wifi boost to restart at the same time every day. No idea if this post brought any visibility into the issue
I appreciate that the issue is fixed, but I did not like how it was treated as if the boost restarting every day was normal given that the firmware version was the same after every restart. Additionally, the callback request mentioned here still did not happen (I'm sure they have this supposed call recorded and could find it or even see the length of this call) and me mentioning as such did not trigger another request for a call for some reason. I just wanted to help troubleshoot the issue and raise awareness of it.
At the end of the day, I just wanted the constant restarts to stop and I'm glad that it did eventually.
TELUS_Support
Official Support Team
30 days agoYour instinct was actually spot on. This is highly likely to be an automated system update. Our network teams frequently push overnight firmware updates, security patches, and network optimizations around this time (usually between 1:00 - 4:00am) to minimize disrupting your day to day usage. While it shouldn't happen every night indefinitely, a cluster of restarts over a week usually means your node is pulling sequential updates or retrying a patch that requires a reboot.
Our Network Access Hub (the main fiber modem) often links to the Boost 7 via a 2.5 Gbps port interface. Because a 2.5G connection is incredibly fast but technically lower than the port's maximum 10G capacity, the hardware turns Orange to negotiate that specific speed. It is not an error light; it simply indicates the current handshake speed. You should still be getting your full 1.5G throughput!
A few things to check though of course would be to go in to your My TELUS app and look under the network tab to make sure your firmware version doesn't show a 'pending update' status. Also, if you want you can always try a hard power cycle by unplugging the power cord from the back of your Boost for a full minute, and then plugging it back in. This forces it to clear its temporary cache and cleanly apply any possibly stuck updates.
- wh124 days agoOrganizer
Here's the boost 7's system logs at time of reboot as well
30.05.2026 01:27:01 CloudCheck[CC_Reboot]: Reboot
04.12.2025 04:07:42 Current booting firmware version is 1.05.10_build06
04.12.2025 04:07:46 REBOOT REASON is 6
04.12.2025 04:07:46 REBOOT TIMESTAMP is 1780129621
04.12.2025 04:07:49 [WanDetectDhcp] doing booting DHCP check
04.12.2025 04:07:49 [WanDetectDhcp] DEF_MODE=0
04.12.2025 04:07:51 Router Mode is 0
04.12.2025 04:09:17 [BH] wlan backhaul init
04.12.2025 04:09:17 [BH] DBS is enable
04.12.2025 04:09:23 start
- florida23 days agoNeighbour
Hi! Are you still experiencing the reboots or was someone able to help? I'm dealing with something seemingly very similar if not identical, it seems.
I noticed my Boost 7 device rebooting around 1:15am several nights in a row and now after checking the device logs, I can see it's been happening consistently since May 13. The log entries are identical to yours, apart from specific timestamps. Same firmware, etc.
- TELUS_Support22 days ago
Official Support Team
These restarts are usually the unit rebooting after updates have been pushed to the firmware.
- wh129 days agoOrganizer
Ah okay, so it was most likely trying to update the firmware.
I believe you meant the "telus connect" app as the "my telus" app, I'm not seeing a network tab. Firmware version I'm not seeing "pending update". This screenshot is from this morning (9:06AM PST) and you can see the uptime is 7hr 38min which means it restarted again around 1:30AM. This screenshot was also before I did the hard power cycle but the firmware version stayed the same when I checked after: "1.05.10_build06"