Fido outages and service status in Raymond, Alberta

Problems in the last 24 hours in Raymond, Alberta

The chart below shows the number of Fido reports we have received in the last 24 hours from users in Raymond, Alberta and surrounding areas. An outage is declared when the number of reports exceeds the baseline, represented by the red line.

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.

Fido Issues Reports

Latest outage, problems and issue reports in social media:

• 
  TundeRich (@Dunumi) reported 4 minutes ago

  @Fidomobile @nsafiys Pls I need help with my Fido account. Got a called yesterday from Fido to make a complain and the next mail I got was my account has been changed to a mobile plan of $45 monthly This is really wrong and I didn’t request for such. *** Fido should contact me immediately to correct

• 
  Kevin (@Kevin55515892) reported 5 minutes ago

  @cptsilvertooth @Fidomobile I cancelled my service with Fido too. Everyone else should do the same

• 
  Jim (@Jim_363) reported 7 minutes ago

  @FidoMobile, I’m extremely disappointed with the current customer service experience. After 30 minutes navigating an AI system with no resolution, the only option to speak with a representative was to schedule an appointment a week in advance. As a customer of 20 years, this level of service is unacceptable and has led me to reconsider my loyalty. @Bell, do you currently offer access to live customer service agents for long-term customers?

• 
  Vince Ltd. (@Vince_Ltd) reported 10 minutes ago

  @Fidomobile Hey, I upgraded my phone online and ordered a store pick up. This was nov 16th, but I havnt gotten an update yet to pick up the phone! What's going on??? I called into CE and they say they cant help. Store wont pick up my call. 😠 😡 😤

• 
  Silent Eyes (@ryanavi21) reported 12 minutes ago

  @Fidomobile @CBC @CP24 Dear Fido! Your customer service was best till few yrs back. Now, it's worst among all. To get hold of customer service, one has to wait almost a week. What a pathetic service..... I guess Bell is far better.... SHAME....

• 
  Shrikant Gupta (@Shrikan15918909) reported 14 minutes ago

  @Fidomobile @RogersHelps I was convinced to return with the promise of FREE US calling but now I’m being charged. A/C No 507570791. Called brand ambassador team many times.lady who sold me the plan is “never at her desk” & no callback yet. This feels misleading. Please fix ASAP

• 
  liane bisaillon 🇨🇦 (@Lianebisaillon) reported 16 minutes ago

  @Fidomobile lately on my cell people can't seem to hear me properly.They say it sounds like I'm underwater, far away or words are missing. I phoned your customer service & they'll help me Wed at the earliest. You call that customer service? Unimpressed

• 
  richard breath (@richbreath420) reported 17 minutes ago

  @Fidomobile does not want to help any customers

• 
  Evan (@evanoftheyukon) reported 18 minutes ago

  @Fidomobile I originally signed up because of their $27 plan for 80gb Can/US/Mex, overall a great deal. Thing is, the service is really bad in my area. I can currently get around 500mbps down with Bell where I live, and with Fido I consistently get 2-3, maybe up to around 20mbps. (2/21)

• 
  Sarah Anderson (@SpirituallyFam) reported 18 minutes ago

  After months of trying to resolve ongoing billing issues with @Fidomobile — including data overcharges that occurred while parental controls were active — I’m still waiting for a fair resolution. Partial credits don’t fix the underlying problem. Families deserve transparency and accountability, not exhaustion and confusion. Too many families just concede and pay because they don’t know how to fight back — allowing millions to be made off a faulty system. I won’t quietly accept that. A full reversal and goodwill credit are fair, considering the time, stress, and system failure that caused this. @CCTS_CRTC