Shaw outages and service status in Sylvan Lake, Alberta
No problems detected
If you are having issues, please submit a report below.
- Shaw generated 0 outage signals in the last 24 hours around Sylvan Lake, including 0 direct reports.
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 Sylvan Lake, Alberta
The chart below shows the number of Shaw reports we have received in the last 24 hours from users in Sylvan Lake, 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 Sylvan Lake, Alberta
The most recent Shaw outage reports came from the following cities: Red Deer.
| City | Problem Type | Report Time |
|---|---|---|
|
|
Internet | 2 months ago |
|
|
TV | 2 months ago |
|
|
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 Near Sylvan Lake, Alberta
Latest outage, problems and issue reports in Sylvan Lake and nearby locations:
-
Ryan Veldkamp (@RyanV86) reported from Sylvan Lake, AlbertaSo frustrated with @Shawhelp today. Cable and Internet both went down for over an hour. Internet back at 50% speed and cable is still out. Earliest appointment for a tech to check it out is January 16th(!!). Service outages apparently get slotted into “standard” service calls 👎🏻
Shaw Issues Reports
Latest outage, problems and issue reports in social media:
-
Bri (@cyberqt) reported@TSN_Sports @Shawhelp why does F1 sound like they are yelling down a tin hallway? It's only the show, not the commercials. It's awful. It was both TSN channels(practice and qualifying)
-
Kathryn Taylor (@katinedmonton) reportedWhat is wrong with @Rogers . My husband called twice, was on hold for 20 minutes then you hung up. Will the 3rd time be the charm. I hate that @ShawInfo became @Rogers , terrible service
-
Rick Alsop (@RickAlsop) reported@Shawhelp how long will the Internet be down? My busiest day of the month
-
Sleepless in YYC🇨🇦🇬🇧 (@kvlovely19) reported@Shawhelp is there an outage in Calgary? I've got no TV and internet i think is down too. I've unplugged both modem and cable box, plugged back in and nothing
-
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
-
Lindsay I.R Wiebe (@LindsayWiebeRD) reported@Shawhelp Because it’s a loud modem from the start/ in general. The worst modem I’ve ever had. I honestly miss our old modem.
-
Guy_Barnabe (@GuyBarnabe) reported@Shawhelp problems with ABC this morning in Winnipeg: XRE-031 37 This channel is temporarily unavailable…. Tried on multiple terminals and via Rogers watch-online website…
-
Don T Beakunt (@truebusterflash) reported3 ******* hours @Shawhelp of hold and chat only to be told to call back tomorrow because your system can’t book an appointment for more than 2 days out. BS! And then you have the nerve to call and try to sign me up for a new contact. **** that.
-
Les Stelmach 🇨🇦🇺🇦 (@LesIsMore1) reported@slackerman10 @Shawhelp Any company (telcos, banks, util, etc) whose phone line REGULARLY says “we are experiencing higher than normal call volumes” is just short-staffing. They are optimizing cost over service. What is the maximum tolerance for a customer, etc. it’s obviously worse for oligopoly
-
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.