Fido outages and service status in Agassiz, British Columbia

Problems in the last 24 hours in Agassiz, British Columbia

The chart below shows the number of Fido reports we have received in the last 24 hours from users in Agassiz, British Columbia 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:

• 
  Aman Bhargava (@Amanbhargava23) reported 7 minutes ago

  @Fidomobile I AM BEING CHARGED EXTRA AS A FRAUD GOR THE SERVICES I HAVENT HIRED I NEED HELP

• 
  Morena (@_thiccmorena) reported 7 minutes ago

  @Fidomobile haven’t had my phone plan for a year and already you’re increasing the rate? Wtf. It’s been like 10 months since I switched to Fido. Tried to contact someone through chat but it seems only option is phone call. I’m deaf, I prefer taking to someone chat

• 
  Vince Ltd. (@Vince_Ltd) reported 7 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. 😠 😡 😤

• 
  Harmanpreet Kaur (@amberjagra) reported 8 minutes ago

  @Fidomobile Worst mobile company to deal with! Charged me an activation fee on my bill when the girl in store told me there will be no fee on my account. Went back to the store to talk, told me to call customer service and now they scheduling a call back for after a week. CRAZY!!

• 
  Lizzie Fry (@liz_boof) reported 8 minutes ago

  @Fidomobile I ended my contract with you on August 25th, yet you still bombard me with emails claiming I owe you $200+. Your online chat team won’t resolve it and I can’t visit in store or call because I no longer live in Canada. Please fix this before you ruin my credit score.

• 
  Shrikant Gupta (@Shrikan15918909) reported 9 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

• 
  Linny (@IosonoLf) reported 10 minutes ago

  @Fidomobile Hello Fido - we’ve tried calling you three times now and we keep getting nowhere. We keep having to schedule a call to speak to anyone. Can anyone help us?

• 
  Mama bless (@zoomieking00) reported 10 minutes ago

  Why can’t I talk to a real person when I call @Fidomobile I just called right now and they are booking appointments for call backs on Monday, nothing earlier. Why do I have to wait until Monday to speak to a live person or get my problem resolved, that is ridiculous!!

• 
  gebilaowang (@kuailenanhai111) reported 12 minutes ago

  @Fidomobile I have already left Canada since June 2025 and will no longer use this plan and phone number. However, Fido keep charging me for 5 months. I can not cancel my plan online and also I can not talk to a specialist. Please help me to cancel my plan and STOP CHARGING ME anymore!

• 
  Sarah Anderson (@SpirituallyFam) reported 13 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