1. Home
  2. Companies
  3. Shaw
  4. Armour Heights
Shaw

Shaw outages and service status in Armour Heights, Ontario

No problems detected

If you are having issues, please submit a report below.

Full Outage Map
  • Shaw generated 1 outage signal in the last 24 hours around Armour Heights, including 1 direct report.
  • The most common problems reported in this area mention Internet and Wi-fi.
  • The most recent signal from this area was received Jul 12, 1:36 AM EDT.
  • 67% Internet (67%)
  • 33% Wi-fi (33%)

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 Armour Heights, Ontario

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

The most recent Shaw outage reports came from the following cities: Toronto, North York, Mississauga, Toronto county, and Markham.

CityProblem TypeReport Time
Toronto Internet 4 hours ago
North York Internet 3 days ago
Toronto Wi-fi 11 days ago
Mississauga Internet 12 days ago
Toronto Internet 16 days ago
Toronto Wi-fi 27 days ago

Nearby cities with recent reports

Toronto

1 recent signals

4 hours ago
North York

1 recent signals

3 days 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 Armour Heights, Ontario

Latest outage, problems and issue reports in Armour Heights and nearby locations:

  • DelroyDyer89
    Delroy Dyer 🇻🇨🇨🇦 (@DelroyDyer89) reported from Toronto, Ontario

    Today's #rogersoutage is yet another reason the government needs to divest @FreedomMobile from any sale of @ShawInfo. While all @Rogers brands including #chatr #fido are down, freedom customers have service because it's a separate network still.

  • AlsoKnownAs_AA
    Algis Akstinas (@AlsoKnownAs_AA) reported from Toronto, Ontario

    @Mark_Goldberg @ShawInfo Good for people in AB & B.C. that can and want to bundle. But not focused on the underserved or accessibility. Have to have a fixed service, qualify. And accept zoned plan limitations. If you followed the Wireless Industry Review closely @TD_Canada these were some of key points.

  • DelroyDyer89
    Delroy Dyer 🇻🇨🇨🇦 (@DelroyDyer89) reported from Toronto, Ontario

    @ShawInfo needs to sell @FreedomMobile at a discount. They have neglected the network. It's unacceptable that in this day and age rain interrupts mobile data.

  • MisterJustinT
    Justin T (@MisterJustinT) reported from Toronto, Ontario

    @CM02051985 @smFISHMAN @ShawInfo Enter your info, it might redirect you to the Network. I get a Rogers pop up to enter my info, that might just be how it works for Shaw.

Shaw Issues Reports

Latest outage, problems and issue reports in social media:

  • bc_2025_vision
    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😟

  • superdaddoo
    D (@superdaddoo) reported

    PSA: Filed a CCTS complaint against @Rogers & Shaw (@ShawInfo) today. Shaw/Rogers has stated that their internet infrastructure in my community is unable to provide the 2Gbps download speeds during peak times. 50% to 70% bandwidth loss in peak times. But charging people for it.

  • Danrek77
    Dave (@Danrek77) reported

    @Shawhelp No timeline, no email confirmation, and I’m not a new customer. I’m being billed for 2 gigabit now, without the hardware for it. I am hesitant to send this beat up box back without knowing I will be getting hardware to actually use the service

  • genadxn
    Gena Dixon (@genadxn) reported

    @Shawhelp internet has been awful the last two days in NW Calgary cut out for hours at a time. Cell service too.

  • kvlovely19
    Sleepless in YYC🇨🇦🇬🇧 (@kvlovely19) reported

    @YYCCowboy @Autumblues @Shawhelp I don't I did try to check their website on my phone for outages and it's giving me only bc not Alberta. so I logged into my account and that's how I found out when the outage started

  • RogersHelps
    RogersHelps (@RogersHelps) reported

    @jcnhooper @Shawhelp Hi James. Please connect with technical support at 1-888-764-3771 so we can ensure proper steps are being taken to resolve any technical issues you are experiencing. -Eric

  • Line_Fault
    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

  • jskapin
    Jenn (@jskapin) reported

    @Shawhelp What can I do to speak with an actual representative? I was emailed to call or login to update my billing info. The app doesn’t work, logging into my account doesn’t work (I get the “oops! Something went wrong!” page), and I get disconnected when I call in to speak with

  • RaviPoojara_rp
    Ravi Poojara (@RaviPoojara_rp) reported

    @Rogers and @ShawInfo are most unethical companies. When I’m moving out to another province where they are not able to provide fiber internet service, they are asking for early contact break fine. I’m ready to continue with the contract, it is their inability to provide the

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