All service status Checked every 5 minutes

Is Google Pay Down?

Our server checks pay.google.com every five minutes. Below is the latest result, the past 24 hours, and how many visitors reported trouble with Google Pay in the last hour.

Google Pay status right now

13:35 IST

Google Pay was online at our last check

Checked less than a minute ago: pay.google.com replied normally with HTTP 200 in 1,295 ms.

Answered, last 24 h
100%
Average response
1,234 ms
Checks, last 24 h
25
Address checked
pay.google.com

Is Google Pay failing for you?

0 reports in the last hour, 0 in the last 24 hours.

One report per visitor per hour. The counts are real button presses on this page and nothing else.

Our checks over the last 24 hours

  1. 14:30 to 15:30 IST: no checks
  2. 15:30 to 16:30 IST: no checks
  3. 16:30 to 17:30 IST: no checks
  4. 17:30 to 18:30 IST: no checks
  5. 18:30 to 19:30 IST: no checks
  6. 19:30 to 20:30 IST: no checks
  7. 20:30 to 21:30 IST: no checks
  8. 21:30 to 22:30 IST: no checks
  9. 22:30 to 23:30 IST: no checks
  10. 23:30 to 00:30 IST: no checks
  11. 00:30 to 01:30 IST: no checks
  12. 01:30 to 02:30 IST: no checks
  13. 02:30 to 03:30 IST: no checks
  14. 03:30 to 04:30 IST: no checks
  15. 04:30 to 05:30 IST: no checks
  16. 05:30 to 06:30 IST: no checks
  17. 06:30 to 07:30 IST: no checks
  18. 07:30 to 08:30 IST: no checks
  19. 08:30 to 09:30 IST: no checks
  20. 09:30 to 10:30 IST: no checks
  21. 10:30 to 11:30 IST: no checks
  22. 11:30 to 12:30 IST: 11 of 11 checks answered, average 1,185 ms
  23. 12:30 to 13:30 IST: 12 of 12 checks answered, average 1,277 ms
  24. 13:30 to 14:30 IST: 2 of 2 checks answered, average 1,244 ms
  • All answered
  • Some failed
  • All failed
  • No data
Latest checks of pay.google.com, times in IST
Time (IST)ResultHTTPResponse
17 Oct, 13:35 Online 200 1,295 ms
17 Oct, 13:30 Online 200 1,194 ms
17 Oct, 13:25 Online 200 1,110 ms
17 Oct, 13:20 Online 200 1,275 ms
17 Oct, 13:15 Online 200 1,334 ms
17 Oct, 13:10 Online 200 1,137 ms
17 Oct, 13:05 Online 200 1,143 ms
17 Oct, 13:00 Online 200 1,145 ms
17 Oct, 12:55 Online 200 1,278 ms
17 Oct, 12:50 Online 200 1,364 ms
17 Oct, 12:45 Online 200 1,330 ms
17 Oct, 12:40 Online 200 1,479 ms

Checked from one VPSLake server outside India. To test any other website live, use the Website Down Checker.

Read this page in four steps

Everything above updates on its own. Reload the page for the newest result.

  1. 1

    Start with the latest check

    The coloured box says whether pay.google.com answered our last request, with the HTTP code, the response time and how long ago it ran.

  2. 2

    Look at the 24-hour strip

    Each block is one hour: green when every check answered, gold when some failed, red when all failed. One gold block is often a short blip; several red blocks in a row mean a real outage.

  3. 3

    Compare with visitor reports

    If the site check is fine but reports are climbing, the problem is probably in the app, payments or the network rather than the website.

  4. 4

    Report it or get official help

    Press Report a problem if Google Pay fails for you, then use the official links further down for updates or a complaint.

What we check for Google Pay

Every five minutes we request Google Pay's web address, pay.google.com. In India the GPay app also depends on UPI and on your bank, so the user reports matter. The check records the HTTP code and response time and nothing else: it does not sign in, move money or open the app.

What to try when Google Pay is not working

"Bank server busy" in Google Pay comes from the bank, not from Google. Pay from a different linked account or give it ten minutes. If the app will not open at all, update it and clear its cache.

Independent check, one location

VPSLake has no connection with Google Pay. The check runs from a single server outside India, so a problem limited to one region, mobile network or bank may not appear here, and some sites answer foreign monitors differently from local visitors. Treat this page as one signal alongside the visitor reports and official announcements.

Google Pay Status FAQ

At 13:35 IST on 17 Oct, pay.google.com replied normally with HTTP 200 in 1,295 ms. In the past hour 0 visitors reported a problem with Google Pay here. The check repeats every five minutes.
Every five minutes our server requests Google Pay's web address, pay.google.com. In India the GPay app also depends on UPI and on your bank, so the user reports matter. It records whether an answer arrived, the HTTP status and the response time, and keeps seven days of results. It does not log in, pay, or use the mobile app.
A working public website does not guarantee that logins, payments, the app or your own connection are fine. Try mobile data instead of Wi-Fi, update the app, and press Report a problem so others can see it is not only them. Several reports within the same hour usually point to a genuine outage.
"Bank server busy" in Google Pay comes from the bank, not from Google. Pay from a different linked account or give it ten minutes. If the app will not open at all, update it and clear its cache.
No. The report saves the service, the time and a salted one-way hash that only stops the same visitor being counted twice in an hour. The hash is wiped after an hour and the report itself after seven days.
No. VPSLake runs this as an independent check and has no link with Google Pay. For official updates use the help links on this page.