1. Home
  2. Companies
  3. Shaw
  4. Wetaskiwin
Shaw

Shaw outages and service status in Wetaskiwin, 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 Wetaskiwin, 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 Wetaskiwin, Alberta

The chart below shows the number of Shaw reports we have received in the last 24 hours from users in Wetaskiwin, 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!

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:

  • Noosiekins
    Vanessa (@Noosiekins) reported

    @Shawhelp It's still down. I was told shawmail doesn't work when I am out of Canada and am overseas according to your tech support!

  • truebusterflash
    Don T Beakunt (@truebusterflash) reported

    @Shawhelp As an fyi, Xfinity stream is not working

  • PoCoello
    Chris (@PoCoello) reported

    @Shawhelp internet outage in poco?? Flashing yellow light 78 people in tech support queue and your ai is useless

  • gfliverpool9966
    🇻🇨🇺🇦 G.F. Liverpool™© 🇺🇦🇹🇹 (#DERB NOW) 🧩 (@gfliverpool9966) reported

    @Shawhelp I think we have a Shaw Webmail outage. I can’t send or receive email. I can’t even forward an exteral email from Google to my shaw email account. Not getting any emails on my phone.

  • BlackBlazeE
    Release the files (@BlackBlazeE) reported

    Due to issues with @ShawInfo 's internet service, today's raid on the DOJ stream will be canceled unless something drastically changes. We here at the Black Blaze Collective assume that either the @TheJusticeDept is once again trying to stop us, or that Rogers/Shaw also defends pedos. The most likely case is sheer incompetence given what we know about the structure within Rogers/Shaw, but our narrative sounds better. Indoctrination broadcasts will resume ASAP.

  • slackerman10
    Ryan Brackenbury (@slackerman10) reported

    Nobody should sign up for @Shawhelp useless customer service that only got worse since the merger. Billions made by these clowns and can’t even get to my house to fix recurrent issues for 48 hours. The amount I pay you should a guy on standby 24/7. #joke #ridiculous #Rogerssucks

  • Alex_Deggs
    Alex Deggs (@Alex_Deggs) reported

    @Shawhelp I have tried all before contacting you. Besides I have tried to login on different devices that I have never used my Rogers account on and it’s the same. Takes me back to login page. Is there somewhere I can be referred to for more help. My security cameras are super important

  • NoDronesCanada
    No Drones Canada (@NoDronesCanada) reported

    .@ShawInfo You are blocking my personal emails to any Shaw email customer. How do I change this? I sent a simple email with an inoffensive graphic, and it triggered some sort of block.

  • Alex_Deggs
    Alex Deggs (@Alex_Deggs) reported

    @Shawhelp I can no longer access the Xfinity app to view my security cameras ever since this single sign on update. I have tried different devices and it’s the same. It keeps taking me back to the sign in page after entering my credentials. Please help asap

  • ZiadFazel
    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.