Vodafone Idea (Vi) Outage Report in Bhagwantnagar, Unnāo, Uttar Pradesh
No problems detected
If you are having issues, please submit a report below.
Vodafone Idea Limited d/b/a Vi is an Indian telecom operator with its headquarters based in Mumbai and Gandhinagar. Vodafone Idea, also known as Vi, is a pan-India integrated GSM operator offering 2G, 4G, 4G+, VoLTE, and VoWiFi services.
Full Outage Map
E-mailProblems in the last 24 hours in Bhagwantnagar, Uttar Pradesh
The chart below shows the number of Vodafone Idea (Vi) reports we have received in the last 24 hours from users in Bhagwantnagar 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 Vodafone Idea (Vi). Are you experiencing issues or an outage? Leave a message in the comments section!
Most Reported Problems
The following are the most recent problems reported by Vodafone Idea (Vi) users through our website.
-
Internet (58%)
-
Total Blackout (20%)
-
Phone (18%)
-
E-mail (4%)
-
Wi-fi (%)
-
TV (%)
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.
Vodafone Idea (Vi) Issues Reports Near Bhagwantnagar, Uttar Pradesh
Latest outage, problems and issue reports in Bhagwantnagar and nearby locations:
-
suchitra verma
(@suchitraverma) reported
from
Bhagwantnagar, Uttar Pradesh
@VodafoneIN bad network in bakser bighapur unnao area even no signals most of the time
Vodafone Idea (Vi) Issues Reports
Latest outage, problems and issue reports in social media:
-
Shrenik Jain
(@kinersH64) reported
Post 1/2 @ViCustomerCare You have charged for VAS which I did not subscribe to and have been harassing me over and again to pay for @ViCustomerCare's mistake. Pathetic call service and rude behaviour by customer care - you guys work like a bunch of liars.
-
Kaushik মজিন্দাৰ Baruah
(@KaushikBaruah) reported
@ViCustomerCare Hi team. I am abroad and my Vi sim which was with my wife got stolen. Your Vi Store team is refusing to reissue the number. Please help
-
Shaktisinh Chudasama
(@shakti_1111) reported
from
Rājkot, State of Gujarāt
@ViCustomerCare Facing the problem since 4 years at my home location and getting table story from customer care
-
Noufal basheer
(@NOUFAL02066000) reported
I am doing monthly recharge without any fail but i am really ****** up with the service that you are providing @ViCustomerCare #Vinetwork
-
Arora Chetan
(@AroraChetan2) reported
@ViCustomerCare @TRAI stop sending me emails for overdue charges as already confirmed earlier solve my issues and get your pending amount from me. Don’t make base for all this as I know your last step what it will. Your goons will not stopping calling me and harassing for same.
-
Akhil S
(@AkhilS90335984) reported
@ViCustomerCare Is it necessary that you keep doing this all the time? All my previous queries & clarifications are still pending and now you impose unnecessary additional charges in the monthly bill. Utterly disappointed with the poor customer service. You guys should shut down your business!
-
Prasanna R.S.
(@prasannars87) reported
from
Munirābād, State of Karnataka
@ViCustomerCare Hi, I took duplicate sms. I am unable to send or receive sms. Please help
-
prince mahajan
(@princemahajan88) reported
@ViCustomerCare Hey team mobile network is a issue these days, keep on and off these days Pincode 180013 Kindly do the needful
-
Akash Mishra
(@imakash91) reported
from
Bhopal, Madhya Pradesh
@ViVodaidea @ViCustomerCare Very bad service and behaviour at VI customer care point at bhopal I am feeling stuck why I choose VI service, 4 times I am visited at care centre but they are not doing single work they every time they make mistake and say please come again.
-
avinash shah અવિનાશ શાહ 🇮🇳
(@avinaszh) reported
@ViCustomerCare Your standard questioners is not what's going to resolve the issue. I have already pointed it out to you in my earlier tweets in this thread.