BSNL outages and service status in Kunda, Uttar Pradesh

Problems in the last 24 hours in Kunda, Uttar Pradesh

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

BSNL Issues Reports Near Kunda, Uttar Pradesh

Latest outage, problems and issue reports in Kunda and nearby locations:

• 
  Rahat Ghani Siddiqui (@RahatGhani) reported 8 minutes ago from Kunda, Uttar Pradesh

  @BSNLCorporate @rsprasad BSNL STATUS....... my 2 landlines not working since last six months......mobile network broadband not working since last night wat is BSNL upto is this your customer service

BSNL Issues Reports

Latest outage, problems and issue reports in social media:

• 
  anuraag (@raone25287706) reported 2 minutes ago

  @aravind Govt also launched bsnl sim, and we all know how pathetic service they provided,inspite offering low cost, people still choose airtel and jio

• 
  Jay Singh (@JaySingh117001) reported 9 minutes ago

  @IndianTechGuide Reservation based government baabu's can't do ****. Sorry BSNL, but your incompetent officers can't convince to leave me private sector networks even if BSNL provides me money to use it's network. END RESERVATION.

• 
  BSNLCare (@bsnl_care) reported 10 minutes ago

  @CftSoni Dear Customer, The ₹1 Freedom 2.0 SIM can be obtained through a BSNL Customer Service Centre (CSC) or authorised BSNL retailer, subject to availability. BSNL also provides an online new-connection facility through its Selfcare portal. Regards, BSNL Care (Ankit)

• 
  Sonu Kumar Productions 🇮🇳 (@sonukomar) reported 12 minutes ago

  @Ramanand06X @BSNLCorporate Do you really think that BSNL is not capable of improving and fixing its problem? It’s someone who does not want it to work properly so that it benefits private players. Sab mile hue hai

• 
  BSNLCare (@bsnl_care) reported 13 minutes ago

  @DashangMakwana1 Hi, We apologize for the inconvenience caused you. BSNL is continuously working towards improving and enhancing its network service experience.The implementation of 5G services is in progress, and we anticipate the launch very soon. Regards, BSNL Care (Sahil)

• 
  BSNLCare (@bsnl_care) reported 16 minutes ago

  @BeTechhie Dear Customer, We apologize for the inconvenience caused. Your feedback regarding network coverage, call drops, and consistent internet experience has been noted. BSNL is continuously working towards network expansion, modernization, and service enhancement to provide better connectivity and an improved customer experience. Regards, BSNL Care (Gopal)

• 
  PANKAJ JHA (@PANKAJJHA35093) reported 17 minutes ago

  BSNL MTNL mobile network coverage problem in full Mumbai city local train and metro journey all lines all route position is searching for network @IndianTechGuide

• 
  Mr Singh (@MrSingh30111726) reported 18 minutes ago

  @Ajaykumaarji @airtelindia Those who are planning to buy @BSNL avoid you will not get any network so your money totally wasted no matter which plan you use, tried multiple time got just frustration.

• 
  BSNLCare (@bsnl_care) reported 22 minutes ago

  @RameshK66538338 Hi, We sincerely apologize for the inconvenience caused to you. We would like to inform you that our team is actively working on your complaint number (H1522192521510) and will get back to you with a better resolution soon. Regards, BSNL-Care (Lokendra)

• 
  Parimal (@Fintech03) reported 23 minutes ago

  In the scorching summer of 1984, the Northern Railway reservation office at New Delhi station was a circle of hell. 100,000+ passengers descended on the station daily. Behind wooden counters sat clerks buried alive under 1000s of bound, leather-backed ledgers called Charting Sheets. To book a ticket, a clerk had to physically find the ledger, cross out a berth with a fountain pen, hand write a paper ticket, and file a duplicate slip. If you wanted a return ticket from Madras to Delhi? You could not buy it in Delhi. You had to send a physical telegram to Madras, wait 48-72 hours for a manual reply, and pray the seat was not sold twice. This is where CMC Limited (Computer Maintenance Corporation) slowly entes into the scene, a public sector company staffed by young, intense Indian systems engineers, working alongside a dedicated task force from Indian Railways. The mandate was terrifying: Digitized reservation did not exist at this scale in the developing world. Foreign vendors wanted astronomical sums for custom software. The team had to build it from scratch, using bare metal hardware. They chose VAX/VMS minicomputers and picked a language built for raw numerical calculation, not transaction processing: FORTRAN. They named the software IMPRESS (Integrated Multi-train Passenger Reservation System). On 15th Nov, 1985, a quiet pilot went live at New Delhi station for just 2 trains: the Tamil Nadu Express and the Grand Trunk Express. There were no satellite beams / grand reveals. The software was bug riddled, the clerks were terrified of the green phosphor CRT monitors, and paper backups were kept open on the desks just in case the system crashed. When the 1st green terminal screen printed a clean, automated ticket in < 60 secs without a clerk touching an ink pad, the engineers in the back room did not celebrate. They held their breath, waiting for the system memory to dump. It did not...... By 1987, IMPRESS was expanded to Bombay, Calcuttta, and Madras. But there was a catch: They were island nodes. Bombay had no idea what Calcuta was doing. A clerk in Delhi could still only sell tickets for trains originating out of Delhi. To manage this growing digital beast, Indian Railways created CRIS (Centre for Railway Information Systems). CRIS inherited 5 massive regional databases: Delhi, Bambay, Calcutta, Madras, and Secunderabad. Each region was an isolated digital kingdom running on different hardware iterations. As travel exploded in the 1990s, the "Island Problem" became a crisis. Passengers did not travel in single regions..... CRIS engineers were tasked with the ultimate computer science nightmare: How do you synchronize 5 massive, high throughput, realtime transaction databases across 4,000 KMs over unreliable copper telegraph lines and primitive telecom links? If a user in Secunderabad tried to book a seat on a train running from Howrah to Bombay while a user in Ahmedabad tried to book the exact same berth at the exact same second, how do you prevent a deadlock without crashing the entire national network? The CRIS team went to work on a master architecture: CONCERT (Country-wide Network for Computerized Enhanced Reservation and Ticketing). They had to engineer custom distributed database protocols. They built networking software that could handle dropped packets, noisy BSNL landlines, and sudden power blackouts. Where landlines failed, they rigged up hybrid data pipes, combining microwave links, leased telecom lines, and early satellite VSATs for redundant failovers. The system was rolled out region by region starting in 1994. The pressure on the CRIS software architects was unbearable, a single logic bug in memory locking could lock up 100s of 1000s of seats across the nation, halting the economy overnight. Finally, in April 1999, the final switch was flipped.... For the 1st time in human history, a passenger walking up to a remote ticket window in Guwahati could instantly query, lock, and purchase a ticket for a train running between Trivandrum and Mumbai in < 2 secs. It was a 15 year relentless siege by teams at CMC and CRIS, writing low level C and FORTRAN code, fighting hardware limitations, and building custom networking protocols long before modern cloud infrastructure existed. When IRCTC was launched in 2002 to bring ticket booking to web browsers, it did not build the core reservation engine. It simply built a web frontend that plugged into the massive, bulletproof CONCERT backend built by CRIS. Today, that same underlying architectural logic handles over 1.5M+ bookings a day, serving a population larger than entire continents. Remember, this was done without any massive VC funding. Just pure, unyielding Indian engineering built line by line in the dark.