1. Home
  2. Companies
  3. ACT
  4. Bhīlwāra
ACT

ACT outages and service status in Bhīlwāra, Rajasthan

No problems detected

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

Full Outage Map
  • ACT generated 0 outage signals in the last 24 hours around Bhīlwāra, including 0 direct reports.

ACT offers fiber to the home services under the brand name "ACT Fibernet" and digital television services under the "ACT Digital" brand. The company provides services in Karnataka, Telangana, Andhra Pradesh, Tamil Nadu and Delhi.

Problems in the last 24 hours in Bhīlwāra, Rajasthan

The chart below shows the number of ACT reports we have received in the last 24 hours from users in Bhīlwāra, Rajasthan 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 ACT. 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.

ACT Issues Reports

Latest outage, problems and issue reports in social media:

  • _4Ruffle
    Ruchi (@_4Ruffle) reported

    @ACTFibernet That’s pretty smart I see. Well you closed the earlier ticket cause it had 10AM eta. New ticket got 2pM next day so you get more time. I have already lost entire day worth of it, reopened the closed ticket. Why no resolution or follow up yet.

  • Sanntosh33
    Santosh Gupta (@Sanntosh33) reported

    @ACTFibernet Checking will not resolve my problem. I need to look for other alternatives which are available apart from you. I have been your customer for the last 10 yrs. Time has changed and if the service is not at par with others then u will lose your clients.

  • NileshP28391464
    Nilesh Patel (@NileshP28391464) reported

    @ACTFibernet We are fed up with your Wi-Fi service; frequent connection outages have become the norm, and we are suffering losses every day because of this. If you cannot provide proper service, why don't you just shut down your company?

  • ash_winu
    ashwinu (@ash_winu) reported

    @ACTFibernet Facing connection disruption multiple times from this location. I request you to take proper action to rectify the issue. It’s being only few days facing trouble with internet again New ticket for same: SR11480747292414 @ACTFibernet

  • preethamdesh
    Preetham Deshpande (@preethamdesh) reported

    @ACTFibernet @ACTFibernetHYD this is the worst net I have ever seen snce 2 days u have not solved theissue ...it's almost 2days iam not getting net ..4 complaints Cs saying wait wait wait..guys be alert before taking @ACTFibernet , CS don't even know when it will be solved

  • rahulthakur000
    rahul thakur (@rahulthakur000) reported

    @ACTFibernet one of the pathetic ISP and customer care. Took new connection 15 days back 300mbps with mesh,i started seeing packet drop 37-40% every 5 mints. Raised request but kept on changing ETA, now i have disconnected connection but haven’t received any refund communication

  • mishraabhinn
    अभिन्न मिश्रा (@mishraabhinn) reported

    @ACTFibernet I have taken 200 mbps plann only 10 mbsps speed comes. Please fix

  • sanjaydebnath86
    Sanjay Debnath (@sanjaydebnath86) reported

    @ACTFibernet The Internet is not working during office hours. My office meeting going on. Please restore. #ACTBroadbandNotReliable #ACTInternetStoppedDuringOfficeHours

  • vamsivallurik
    karthik valluri (@vamsivallurik) reported

    @ACTFibernet Your technician called and once I told him its same issue, he cut the call as he knows he made a mistake earlier.

  • UrsVz7
    Nation1st (@UrsVz7) reported

    @ACTFibernet what's going on? Is there anyone to look into the issue? More than 48hrs no update, just keep on sending revised resolution date n time. Very bad service never expected this.