Fido outages and service status in Bradford West Gwillimbury, Ontario

Problems in the last 24 hours in Bradford West Gwillimbury, Ontario

The chart below shows the number of Fido reports we have received in the last 24 hours from users in Bradford West Gwillimbury, Ontario 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 Near Bradford West Gwillimbury, Ontario

Latest outage, problems and issue reports in Bradford West Gwillimbury and nearby locations:

• 
  kingofthelycans (@LycanKing89) reported 30 minutes ago from New Tecumseth, Ontario

  Worst decision was getting Fido over bell ! *******! In my basement apartment and I have to sit with one ass cheek In the air tilted on a 90 degree angle if I want to make a phone call or answer a call

Fido Issues Reports

Latest outage, problems and issue reports in social media:

• 
  Canadian Crimes (@canadian_crimes) reported 2 minutes ago

  @Fidomobile how is reception even worse with 5g plus zero customer support

• 
  Leanne Schira (@lschira) reported 2 minutes ago

  @FidoSolutions @Fidomobile @fidoso so he just waited over 2 hours on hold and they now just disconnected him.... HELP!!

• 
  Lina Serratos (@CaroSerratos) reported 3 minutes ago

  @Fidomobile I am close to phone rage at this time. How hard can it be to get human assistance and cancel my contract with you? This is precisely why I’m done with #Fido - the ridiculously expensive service too.

• 
  Kv N (@KvEncela) reported 3 minutes ago

  @Fidomobile was signing for a new plan and as usual nothing worked , submitted license and photo then shows message need more information and a contact number shows that is not in service, bunch of incompetent…

• 
  Pete (@floofydoofbkup) reported 4 minutes ago

  @Fidomobile its impossible to get thru to an actual person in customer service and i am heavily considering leaving my contract early because of this

• 
  Ian Kendall (@ianserena2045) reported 8 minutes ago

  @Fidomobile Fido is down in manitoba cant make calls or receive cant text and no data bill is fully paid cant get to speak to a person at fido its been down for over 2 hrs now

• 
  Francisco A E Diaz (@F_Ash_Diaz) reported 13 minutes ago

  @CircularLogic89 @Fidomobile Would it be too much to ask that these service providers put some sort of a check to charge the roaming like home daily charge only if the data used for the day is over 1MB, especially when they know about these issues ?

• 
  Philomena Gunk (@macaghalla) reported 14 minutes ago

  I've had @Fidomobile since 1996. 30 ******* years. Today, I had to schedule a call back with an agent so that I can escalate an issue to a Supervisor, who will call me back in 48-72 business hours. Needless to say, I'm taking recommendations for a new provider.

• 
  Zee Hamid (@zeeinmilton) reported 14 minutes ago

  @Fidomobile - your service absolutely sucks! My dad's eSIM isn't working and there's no way to talk to a human. Your chatbot tells me that a human will call me on Tuesday evening! It's Friday! Who has time to wait 4 days.

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