Shaw outages and service status in St. Andrews, Manitoba
No problems detected
If you are having issues, please submit a report below.
- Shaw generated 0 outage signals in the last 24 hours around St. Andrews, including 0 direct reports.
- The most common problems reported in this area mention Internet.
- Internet (100%)
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 St. Andrews, Manitoba
The chart below shows the number of Shaw reports we have received in the last 24 hours from users in St. Andrews, Manitoba 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 St. Andrews, Manitoba
The most recent Shaw outage reports came from the following cities: Selkirk.
| City | Problem Type | Report Time |
|---|---|---|
|
|
Internet | 25 days ago |
|
|
Phone | 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 St. Andrews, Manitoba
Latest outage, problems and issue reports in St. Andrews and nearby locations:
-
Braydon Maz (@Maz204) reported from Selkirk, ManitobaI’m never signing a contract with @Shawhelp again. This company is absolutely ridiculous.
-
JeffScharer (@SantosLHalper) reported from St. Andrews, Manitoba@Shawhelp no TV signal in Lockport, MB. Tried resetting my TV box and still no signal
-
JeffScharer (@SantosLHalper) reported from St. Andrews, Manitoba@Shawhelp what is going on with Cable service? The channel guide comes up no problem, but all I get is a black screen when I tune in
-
JeffScharer (@SantosLHalper) reported from St. Andrews, Manitoba@Shawhelp lost tv signal for the 2nd time thus week...resetting it doesn't seem to be working
Shaw Issues Reports
Latest outage, problems and issue reports in social media:
-
always smile 🇨🇦 (@cari_goncalves) reported@Shawhelp @gfliverpool9966 Not working for me either. Ridiculous
-
Rick Alsop (@RickAlsop) reported@Shawhelp Yes still issues as its not working
-
Don T Beakunt (@truebusterflash) reported@Shawhelp As an fyi, Xfinity stream is not working
-
O.A (@dae_j01) reported@Shawhelp today is the third day I have been trying to contact your technical support and it is heartbreaking. On one of those days I waited on the call for over 5 hours and no one answered. Can someone reach out to me please? Thank you.
-
🇻🇨🇺🇦 G.F. Liverpool™© 🇺🇦🇹🇹 (#DERB NOW) 🧩 (@gfliverpool9966) reported@Shawhelp Well, you are very lucky in this matter. Able to sign in on Google Chrome through Apple.
-
Arnold K (Taylor's Version) (@aroc88) reported@Shawhelp Nothing has been updated since 1248pm. This sucks.
-
Faulty (@Line_Fault) reported@Shawhelp my packet loss is 50% 7.8Mbps down! Screaming fast. Chat said it's too busy to help me... literally. Standard every 6 ish month problem
-
Jennifer & Devina “The Ginja Ninja” 🇨🇦❤️🇺🇦 (@JenniferKingsb6) reportedHey @Shawhelp , those of us in Port Moody/Coquitlam who are now at nearly 12+ hours without service(s) will be looking for a credit on our next bill! And whomever’s responsible for the outage should be penalized.
-
TC-VAN (@RageGeist) reported@Shawhelp I'm now on day 3 without internet. I contacted support and they gave me case number CCS000011835796. Please have a manager contact me with a resolution timeline. This is atrocious service and I'll be cancelling as soon as I'm able
-
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.