Sasktel outages and service status in Richmond, British Columbia
Service-wide status: Sasktel
No problems detected
If you are having issues, please submit a report below.
- Sasktel generated 0 outage signals in the last 24 hours around Richmond, including 0 direct reports.
Sasktel (Saskatchewan Telecommunications) offers mobile and landline based communications services to businesses and individuals in in Saskatchewan. Services include mobile phone and mobile internet as well as broadband internet, dial-up internet and internet TV (IPTV).
Problems in the last 24 hours in Richmond, British Columbia
Sasktel signals over the past 24 hours, with local activity from Richmond, British Columbia and nearby areas. The dashed baseline applies to service-wide activity, not to local outage confirmation.
- Service-wide signals
- Service-wide baseline
At the moment, we haven't detected any problems at Sasktel. 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.
Sasktel Issues Reports
Latest outage, problems and issue reports in social media:
-
RCMP Saskatchewan (@RCMPSK) reportedSaskTel is aware of the issue and are working on a solution. Once service has been restored, we can provide an update. We do not have an estimated time for restoration of full phone service. 2/2
-
RUSHing BLADES of steel (@Horinstoon) reported@alaylm85 @BladesHockey The Blades are a better road team, not sure why but they never do well at SaskTel Center.
-
Kid Krayon (@kidkrayon) reported~25 minutes ago, the Internet went down for me here; no info from @sasktel/@SaskTelSupport as to what occurred. It seems to be back now, so I'll attempt to start at 9:50 p.m. MDT. Sorry. πππ»πΆ
-
Commissioner Miner (@fanCRTCProfling) reportedFew New #CRTC tariffs, Support Structure amendments (not 404 this time): 1. T/N: 0580, Telus 2. T/N 0978, Bell 3. T/N 1180, NWTel 4. T/N 0377, SaskTel 5. T/N 0655, Telus (carrier access).
-
Courtney B. (@whatsupcourtney) reported@SaskTelSupport β hi there, do you have representatives from Sasktel out in Swift Current today regarding updating/upgrading the internet due to service complaints? Just want to make sure this isnβt a scam!
-
Brad (@Bradtk421) reported@BillboardChris I don't know about Sasktel to be honest. When Bell bought out MTS we got higher prices on somethings and did not get much better service.
-
βπππππ π¦ΈββοΈ πππ₯π₯ππ (@HiddenKitteh) reportedWill the Sasktel saga never end? 2 months now, no home internet. Neighbour has been in her home a week and today Sasktel is parking in MY driveway to install her internet.... *sigh*. It's ok, I really didn't want to leave the house to get stuff done today anyway....
-
Nick (@Nickster1619) reported@Latenite72 @frank_seravalli Lol no ****. Iβm just saying you said you were at the game but posted a picture at the Sasktel centre when the game tonight is played in Regina.
-
Matthew Szpakowski (@nskgrower) reported@VentureAgri @SaskTel Its way worse. I've got cell boosters where we use phones for correction signals. Dont think anything would work if it wasn't for that. Have you had problems with modems getting signals?
-
TD (@oOTD83Oo) reported@SaskTel @sskroughriders Now it's just working, I never found a purchase button or anything... Top notch
Recent Sasktel reports in Richmond, British Columbia
Latest available direct user reports from this city and nearby areas. These are individual observations, not confirmed incidents or a complete outage history.
- Vancouver: TV
- Vancouver: Phone
- Vancouver: Internet
- Vancouver: Phone
- Burnaby: Internet
- Vancouver: E-mail
Sasktel detected incident history
These records describe service-wide increases in reported problems. They do not confirm an outage at every address. Recorded end times describe our detection window, not a provider-confirmed repair.
-
Detected:
Detection ended: (116 minutes) -
Detected:
Detection ended: (123 minutes) -
Detected:
No end recorded. This alone does not establish the current status. -
Detected:
No end recorded. This alone does not establish the current status. -
Detected:
No end recorded. This alone does not establish the current status. -
Detected:
Detection ended: (83 minutes)