Is Paytm down in Bīkaner, Bīkāner, State of Rājasthān?

Problems detected at Paytm

Users are reporting problems related to: transactions, mobile app and login.

The latest reports from users having issues in Bīkaner come from postal codes 334001.

Paytm is an Indian e-commerce payment system and digital wallet company that lets consumers pay for services including prepaid mobile and data services, direct-to-home tv service and toll services.

Paytm problems in the last 24 hours in Bīkaner, State of Rājasthān

The following chart shows the number of reports that we have received about Paytm over the past 24 hours from users in Bīkaner and near by areas. An outage is determined when the number of reports are higher than the baseline, represented by the red line.

Paytm Outage Chart in Bīkaner, Bīkāner, State of Rājasthān 07/04/2022 07:25

July 04: Problems at Paytm

Paytm is having issues since 11:10 AM IST. Are you also affected? Leave a message in the comments section!

Most Reported Problems:

  • Transactions 52.13% Transactions
  • Mobile App 21.16% Mobile App
  • Login 13.40% Login
  • Transfer 7.17% Transfer
  • Website 3.33% Website
  • Withdrawals 2.82% Withdrawals

Paytm Outage Map Near Bīkaner, Bīkāner, State of Rājasthān

The most recent outage reports and issues originated from Bīkaner.

IndiaBīkaner Transactions

Paytm in Bīkaner, State of Rājasthān Comments

Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.

Paytm Issues Reports

Latest outage, problems and issue reports in social media:
  • kiranbayapuredd kiran bayapureddy (@kiranbayapuredd) reported

    @Paytm 0120-4606060 This stupid number not at all working

  • kiranbayapuredd kiran bayapureddy (@kiranbayapuredd) reported

    @Paytm Hello do you really have customer care??????

  • akshaygeenwal Akshay (@akshaygeenwal) reported

    @Paytmcare I need call back thats it! Concern is related to my fastag. I already tried thrice to call your customer support. But there is no option to connect with executivem

  • ak76824 ARVIND KUMAR (@ak76824) reported

    @Paytm @Paytmcare DEAR SIR / Madam I would like to know about the process regarding ticket id 3192783976 i.e money sent to wrong account number please update me and give me satisfied time period of refund of my money in my account. Please help to sort it out . Thanks and regards

  • ArvindSudra Arvind Sudra (@ArvindSudra) reported

    @paytmbankcare @Paytmcare Dear Paytm …. You have one of the most stupid customer care platform. I have an issue with one of my postpaid transactions and to my surprise, I have no way to communicate. I feel very handicapped at the moment. Can someone please call me up to resolve ……

  • PdPanthi हरि (@PdPanthi) reported

    @Paytm @Paytmcare suddenly my paytm account is stopped. You guys opened a new account for my same number how is it possible? Try to connect your customer care, but nothing happened. What kind of service is this.I have been using paytm since 6,7 years.Time to quit now.

  • praneethhr Arvind63Mann92💂💂 (@praneethhr) reported

    @Paytm Tell me why should a customers Paytm wallet should be Credit freezed to do a KYC going to a shop when his KYC is fully verified in the first place...I do regular transactions on Paytm and with this issue i have already moved to other wallets #Nomorepaytm

  • KasarVinil Vinil Kasar (@KasarVinil) reported

    There is some technical issue on my paytm sound box its not working and not even starting, am calling in helpline number since a week and they always ask me for complain number which i didn't received yet. Kindly please assist. @Paytmcare @Paytm @vijayshekhar

  • Ramacha35004098 Ramachandra rao (@Ramacha35004098) reported from New Delhi, National Capital Territory of Delhi

    @Paytmcare you guys really suck . You act as an intermediary, draw money from the customer levy your charges and still not make the payment to the ultimate beneficiary @RBI @nsitharamanoffc

  • _Nishant_S Nishant Saharia (@_Nishant_S) reported

    @Paytmcare Reply to my DM explained the issue there itself.