1. Home
  2. Companies
  3. Fido
  4. Antrim
Fido

Fido outages and service status in Antrim, Ontario

No problems detected

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

Full Outage Map
  • Fido generated 0 outage signals in the last 24 hours around Antrim, including 0 direct reports.

Fido Solutions is a Canadian cellular service provider offering mobile phone and mobile internet service. Fido owned by Rogers Communications.

Problems in the last 24 hours in Antrim, Ontario

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

Fido Issues Reports

Latest outage, problems and issue reports in social media:

  • FranzThomas
    Franz Thomas™ (@FranzThomas) reported

    How is @Fidomobile an actual “tele-communications” company? 🤷🏾 how can you not be able to talk to anyone? I’m embarrassed to say I’ve been a customer for 20 years! 🤬 Their “Artificial Intelligence” is built off their “Actual Intelligence” so nothing works #IKNOWFRANZ

  • kirito_9668
    Kirito96 (@kirito_9668) reported

    @Fidomobile whoever is working on your AI needs to be let go. Other companies out of the box AI will do better than the **** you have. Now hard to train your AI.

  • IosonoLf
    Linny (@IosonoLf) reported

    @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?

  • _FucknBossChick
    Unapologetic Queen✨ (@_FucknBossChick) reported

    @soban_shaikh @Fidomobile Yeah. Their customer service has really gone downhill the last few years. I stayed with them so long because of the customer service but now it’s why I will be leaving unfortunately.

  • floofydoofbkup
    Pete (@floofydoofbkup) reported

    @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

  • floofydoofbkup
    Pete (@floofydoofbkup) reported

    @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

  • Sandy_DEWfan
    Sandra A (@Sandy_DEWfan) reported

    @Fidomobile hey Fido thought when there’s an outage my cell should work. Barely does with this @rogers outage today. One bar and I have tons of cellular data. 😡😡😡😡 funny it works here on x go figure!

  • Buraaq1976
    Buraaq (@Buraaq1976) reported

    @zeeinmilton @Fidomobile Bro, this is why I left them. I was a customer for over 20 years

  • Vince_Ltd
    Vince Ltd. (@Vince_Ltd) reported

    @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. 😠 😡 😤

  • SpirituallyFam
    Sarah Anderson (@SpirituallyFam) reported

    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