Shaw outages and service status in Grande Prairie, Alberta
No problems detected
If you are having issues, please submit a report below.
Full Outage Map
- Shaw generated 0 outage signals in the last 24 hours around Grande Prairie, including 0 direct reports.
- The most common problems reported in this area mention TV.
- TV (100%)
The latest reports from users having issues in Grande Prairie come from postal codes T8W .
Shaw offers broadband internet, TV and phone services to businesses and individuals. Shaw mainly serves clients in British Columbia and Alberta.
Problems in the last 24 hours in Grande Prairie, Alberta
The chart below shows the number of Shaw reports we have received in the last 24 hours from users in Grande Prairie, Alberta and surrounding areas. An outage is declared when the number of reports exceeds the baseline, represented by the red line.
At the moment, we haven't detected any problems at Shaw. Are you experiencing issues or an outage? Leave a message in the comments section!
Live Outage Map Near Grande Prairie, Alberta
The most recent Shaw outage reports came from the following cities: Grande Prairie.
| City | Problem Type | Report Time |
|---|---|---|
 Grande Prairie
|
TV | 19 days ago |
|
Grande Prairie
|
Internet | 2 months ago |
Community Discussion
Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.
Beware of "support numbers" or "recovery" accounts that might be posted below. Make sure to report and downvote those comments. Avoid posting your personal information.
Shaw Issues Reports
Latest outage, problems and issue reports in social media:
-
️Mike Fricker 🇨🇦 Christian Priest AuDHD CPTSD☯🖖 (@M_S_Fricker) reported@ShawInfo @Rogers Things got worse. Especially your customer service.
-
Don T Beakunt (@truebusterflash) reported@Shawhelp I messaged you days ago without a response. Your app also won’t work so attempting to chat with tech support is not an option and now I’ve been on hold for 40min. Your sales calling to lock me in again is poor timing considering the current issues.
-
Hugh Gillis 🇨🇦 (@hgillis) reported@Shawhelp I haven't been able to login to my account in 2 months. I can't stream from any of my devices because I can't login. I"ve called your support 4 times and just keep getting told to try again in a week. Are you ever going to fix this problem?
-
Ugabug (@MaryPChipman) reported@Shawhelp Now the old TV box doesn't work & the new one to replace the defective one sent us won't arrive until Friday. This 'easy self-install' cost me a half-day & cost Rogers Shaw 3 hours of tech time, just so it could save a few bucks by not sending a techie. And we pay $$$$ for this.
-
bc_2027 (@bc_2025_vision) reported@Shawhelp We really need wait times & callback from Rogers with Shaw support. We had this for > 10 years before it was stopped. Now TELUS has these services and Rogers with Shaw does not. @Rogers Customer service should not be a hardship on hold … no clue whether we will wait hours😟
-
OC_2030 (@oc_2030_vision) reported@Shawhelp No. It looks like someone found the issue when they came back to work on Monday … next time, please just have someone go to a TV and check for me please. Sometimes the easy way can be easy …
-
Ugabug (@MaryPChipman) reported@Shawhelp It took a few minutes to get back. I checked the HDMI connection, the WiFi signal which was fine & turned the TV off & on again
-
Don T Beakunt (@truebusterflash) reported@Shawhelp Your link says outages are unavailable. wtf?
-
Jennifer & Devina “The Ginja Ninja” 🇨🇦❤️🇺🇦 (@JenniferKingsb6) reported@Shawhelp Yes, but that’s not the point. The point is releasing an app that doesn’t support iOS 26.4.2 - and thereby angering EVERY customer who has an Apple device. Fix it ASAP, and ensure future updates work for everyone before releasing it.
-
Ziad 😷 Fazel 🇨🇦🇺🇦💉 (@ZiadFazel) reported@Shawhelp You’ve admitted you can’t access my account. So what good is sending you a DM? This is my real name. Tell your management to look up my file in your records and fix the problem identified and admitted in your own logs. Entire problem + solution are WITHIN @Rogers. So fix it.