1. Home
  2. Services
  3. Google Wallet
Google Wallet pay.google.com

Is Google Wallet down right now? Live status and outage tracker

No, Google Wallet is up.

No outage detected, and no user reports in the last hour.

Live Data refreshes every 5 minutes
User reports, last 24 hours, 15 minutes a segment: 96 flowing, 0 slow (elevated), 0 jammed (outage)

User reports, last 24 hours

No reports in this window

No problem reports came in for Google Wallet in the last hour, and at this time of day there are usually almost none. There has been no spike in reports since 9 October.

Around the world right now: normal in 72 other countries. Most reports in the last hour: Singapore 2. By country

No user reports came in for Google Wallet in the past 24 hours, and its uptime over that window is 100.00%. No 15-minute window had any reports at all, so the chart above stays flat.
Reports, last hour
0
Quiet
Uptime, 24 h
100.00%
No outage windows
Last outage
None
In the last 24 hours
Busiest 15 minutes
0
No reports
Last 24 hours

Google Wallet outages and problems

No user reports came in for Google Wallet in the past 24 hours, and its uptime over that window is 100.00%.

No 15-minute window had any reports at all, so the chart above stays flat.

No problems detected in the last 24 hoursReports for Google Wallet stayed at their usual level the whole time.
This month

Google Wallet in November 2026

Problem reports in November
0

Monthly report for November 2026

What went wrong

What people said was wrong in recent problem reports for Google Wallet worldwide.

  1. Payments100%

Share of 1 recent report that said what was wrong, from every country listed below.

World map

Google Wallet reports around the world

In the last 24 hours, 14 problem reports about Google Wallet came in from 11 countries. Right now reports are at the usual level in every country.

  • Outage now
  • Problems now
  • Normal
Each dot is a group of recent reports, coloured by how its country is doing now; bigger dots, more reports.
CountryNowLast hour24 hours
Singapore Normal 22
The UK Normal 03
The US Normal 01
Bangladesh Normal 01
Denmark Normal 01
The Dominican Republic Normal 01
India Normal 01
Israel Normal 01
Pakistan Normal 01
Spain Normal 01
The Netherlands Normal 01
Algeria Normal 00

Each country's status compares its reports with the usual level there. 60 more countries had 0 reports in the last 24 hours. Map outlines: Natural Earth.

Last 30 days

Google Wallet problem spikes, last 30 days

Since 9 October, Google Wallet had no outage spikes or periods of elevated reports.

  • Sat 3 Oct: no data
  • Sun 4 Oct: no data
  • Mon 5 Oct: no data
  • Tue 6 Oct: no data
  • Wed 7 Oct: no data
  • Thu 8 Oct: no data
  • Fri 9 Oct: 2 reports
  • Sat 10 Oct: 0 reports
  • Sun 11 Oct: 0 reports
  • Mon 12 Oct: 0 reports
  • Tue 13 Oct: 0 reports
  • Wed 14 Oct: 0 reports
  • Thu 15 Oct: 0 reports
  • Fri 16 Oct: 0 reports
  • Sat 17 Oct: 0 reports
  • Sun 18 Oct: 0 reports
  • Mon 19 Oct: 0 reports
  • Tue 20 Oct: 3 reports
  • Wed 21 Oct: no data
  • Thu 22 Oct: 0 reports
  • Fri 23 Oct: 1 report
  • Sat 24 Oct: 0 reports
  • Sun 25 Oct: 0 reports
  • Mon 26 Oct: 0 reports
  • Tue 27 Oct: 0 reports
  • Wed 28 Oct: 0 reports
  • Thu 29 Oct: 0 reports
  • Fri 30 Oct: 0 reports
  • Sat 31 Oct: 0 reports
  • Sun 1 Nov: 0 reports

By country

Each square is one day in the countries with the most reports: red when reports stayed at outage level for half an hour or more, amber when they stayed above the usual level for an hour or more, grey otherwise.

  • The UK12
  • The US8
  • Brazil4
  • Morocco4
  • Germany3
  • Austria2
  • Denmark2
  • Spain2

Country history starts on 29 October 2026. Days run from midnight to midnight, Central European time.

A spike is a sharp rise in problem reports from users, kept exactly as this page showed it at the time. This history starts on 9 October 2026. Monthly reports for all services

Troubleshooting

How to fix Google Wallet not working

Google Wallet is up on our end, so if it won't work for you, the problem is most likely on your side. Work through these in order:

Your browser tries to reach pay.google.com over your own connection, right now. Nothing is sent to us or stored.

  1. Check the official status page first

    Open https://pay.google.com/status/ and read what the service says about itself. A tap that fails at one till means little, but the same failure at several shops in one day usually points at the service rather than your phone, and no setting on your phone will fix that.

  2. Turn on NFC and set the default tap and pay app

    Swipe down the quick settings shade and check the NFC tile; on most phones the full path is Settings, Connected devices, Connection preferences, NFC. Then open Settings, Apps, Default apps, Tap and pay, and pick Google Wallet. If a different wallet holds that slot, your taps go there and the card in this app never gets used.

  3. Force stop the app and clear its cache

    Open Settings, Apps, See all apps, tap the wallet, and hit Force stop; the wording shifts a little between phone makers. Under Storage and cache, choose Clear cache. Skip Clear storage, which wipes every saved card, then check the Play Store for a pending update to the app and to Google Play services.

  4. Remove the card and add it again

    Tap the card inside the app, open the overflow menu in the corner, and choose Remove payment method. Then add it back, either with the camera or by typing the number, and approve the verification your bank sends. If setup still stops halfway, call the bank: some cards need to be switched on for digital wallets on their side, and the help centre at https://support.google.com/pay lists what they need from you.

While Google Wallet is down: what to use instead

  • Physical card When the app will not show your saved card, pull the plastic card from your wallet and use the terminal directly.
  • Cash For small purchases in person, cash avoids the terminal and the app entirely.
  • Samsung Wallet On a Samsung phone, the built-in wallet can tap to pay at stores with cards you add there.
  • Transit card If you keep a train or bus pass in the app, a physical transit card or paper ticket works at the gate when the phone pass will not load.
Your device

Fix Google Wallet on Windows, Mac, Android and iPhone

Google Wallet on Windows

Fix
Clear your browser's cache and cookies, or disable conflicting extensions that might block Google Wallet from loading. Ensure your web browser is updated to the latest version and your internet connection is stable.
Check
To check if Google Wallet is down on Windows, visit the Google Workspace Status Dashboard or try loading the Google Wallet website in an incognito browser window. If the page fails to load or shows a server error, the service may be experiencing an outage.
Command Prompt
ping pay.google.comTest whether Google Wallet's servers reply
nslookup pay.google.comCheck that Google Wallet's DNS resolves
tracert pay.google.comTrace where the connection drops
ipconfig /flushdnsClear the DNS cache, then reload

Google Wallet on Mac

Fix
Resolve Google Wallet loading issues on a Mac by clearing your browser data or testing the site in a private window. You can also try temporarily disabling your VPN or firewall, which might interfere with Google's secure payment gateways.
Check
Determine if Google Wallet is down on macOS by checking third-party status checkers or attempting to access the Google Wallet web portal. If you encounter timeout errors across multiple browsers, the issue is likely on Google's end.
Terminal
ping -c 4 pay.google.comTest whether Google Wallet's servers reply
nslookup pay.google.comCheck that Google Wallet's DNS resolves
traceroute pay.google.comTrace where the connection drops
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponderFlush the macOS DNS cache, then reload

Google Wallet on Android

Fix
Update the Google Wallet app from the Google Play Store and clear its cache in your device's app settings. If problems persist, ensure Google Play Services is updated and your phone's NFC setting is turned on.
Check
To see if Google Wallet is down on Android, check for error messages like "network connection error" when opening the app, or verify if other users are reporting issues. You can also try loading a web page to ensure your mobile data or Wi-Fi is functioning.

Google Wallet on iPhone and iPad

Fix
Clear your browser cache in your iOS settings or try accessing the Google Wallet site using a different network. Ensure your iOS device is updated to the latest software version to prevent compatibility issues.
Check
Since Google Wallet is accessed via a web browser on iOS, check if the service is down by trying to load the Google Wallet site on Safari or Chrome. If the page fails to load while other websites work, Google's servers may be temporarily offline.
About

What happens when Google Wallet goes down

You use Google Wallet to keep payment cards, transit passes, event tickets, and loyalty cards on Android phones and Wear OS watches. When it fails, your tap can stop working and passes may not load.

Tap to pay often breaks first. You hold your phone to the reader, and the terminal declines or does nothing, while transit passes, event tickets, loyalty cards, and boarding passes may open to a blank screen or an error. Adding a new card can hang before it finishes. Problems tend to be partial: one bank's cards fail while another works, one transit agency's passes won't scan, some Android phones error out, and Wear OS watches behave differently; the status at the top of this page counts user problem reports in 15-minute windows over the last 24 hours to show when they are above the usual level, not live tests from this site, so check the official status page and help centre for service-side updates.

Servers and network

Google Wallet IP address, servers and network

IPv4 address
142.251.127.84
IPv6
2a00:1450:4001:c21::54
Network
AS15169 · Google LLC, registered in the United States
Served through
Google
DNS hosted by
its own name servers (sslip.io)
HTTPS certificate
Issued by Google Trust Services, valid until 30 Dec 2026 (59 days)
HTTP/3
Supported
Our check
Answered in 530 ms

Checked from our server in Frankfurt, Germany, 4 h ago, for accounts.google.com. A service behind a CDN answers from many data centres, usually the one nearest to you, so these addresses are where its traffic enters, not where its own servers stand. Visitors elsewhere may see different addresses.

Checked from 11 places around the world

All 11 locations got an answer from accounts.google.com. Fastest from Amsterdam (23 ms), slowest from São Paulo (322 ms). Every location connected through Google LLC (AS15169), using 8 different addresses.

LocationResultTimeAddress reached
FrankfurtGermanyUp · HTTP 30240 ms142.251.127.84data centre in Frankfurt
ViennaAustriaUp · HTTP 30283 ms142.251.127.84data centre in Frankfurt
MilanItalyUp · HTTP 30281 ms142.251.127.84data centre in Frankfurt
ParisFranceUp · HTTP 30243 ms142.251.168.84
AmsterdamNetherlandsUp · HTTP 30223 ms142.250.27.84
MadridSpainUp · HTTP 302103 ms192.178.223.84data centre in London
WarsawPolandUp · HTTP 302107 ms142.251.127.84data centre in Frankfurt
Los AngelesUSAUp · HTTP 30290 ms142.250.141.84
São PauloBrazilUp · HTTP 302322 ms142.251.0.84
SingaporeSingaporeUp · HTTP 30236 ms172.217.194.84
TokyoJapanUp · HTTP 30257 ms192.178.230.84

Checked with check-host.net from its servers in these cities 4 h ago, for accounts.google.com. Time is how long each server took to load the page. Data-centre cities come from the names the network gives its servers.

Questions

Google Wallet FAQ

Is Google Wallet down right now?

Look at the status at the top of this page: it counts user problem reports in 15-minute windows over the last 24 hours and shows whether those reports sit above the level the service usually gets. Nothing here pings or probes Google, so a quiet bar means few people complained, which is not the same thing as a working payment. If a tap gets refused or your card will not load, check the official status page at https://pay.google.com/status/ for a listed incident. To rule out your own end, try the same card on a different phone, then try a physical card at the same terminal; if the physical card works, the trouble sits in your handset, your account, or the store's reader.

Why does tap to pay work with one card and fail with another?

Banks decide which of their cards can be used for contactless payments through the app, and some block that feature or block adding the card at all. Remove the failing card, add it again, and finish the verification your bank sends by text or through its own app. If it still will not work, call the bank and ask whether they allow that card in Google Wallet, since nothing on the Google side can override their block.

Google Wallet keeps closing the moment I open it. Can I fix that myself?

Force stop the app, clear its cache, and open it again. If it still shuts down, clear storage as well, which wipes your saved cards and payment setup. Update the app from the Play Store and restart the phone. You will have to add each card back and verify it with your bank once storage is cleared, so keep the physical cards nearby.

I moved to a new phone and my saved cards vanished. Where did they go?

Cards stay tied to the Google account you added them with, so sign in with that same account first, then look under the payment setup to see what is listed. Most phones make you add each card again and re-verify it with the bank, because the old device's approval does not carry over. A watch or tablet needs that same setup. Cards do not travel between devices on their own.

Why can't I add a loyalty card or a transit pass?

Loyalty cards go in by scanning the barcode, and if the scanner will not read it, you can type the number in by hand. Transit passes work only where the local transport agency has joined, so a pass for a city that is not on the supported list will not add no matter how you enter it. If the app refuses a pass with no explanation, ask the agency, and the help centre at https://support.google.com/pay is the place to look for what the app can hold.
For your site

Put the Google Wallet status badge on your site

Paste one of these into a web page, a blog post or a README. The badge shows the same status as this page, based on user problem reports. Browsers can keep a copy for up to 4 hours. It links back here.

Google Wallet status badge, as it looks now

HTML
<a href="https://isitdownrightnow.app/services/google-wallet/"><img src="https://isitdownrightnow.app/badge/google-wallet.svg" alt="Google Wallet status" height="20"></a>
Markdown, for README files
[![Google Wallet status](https://isitdownrightnow.app/badge/google-wallet.svg)](https://isitdownrightnow.app/services/google-wallet/)

The badge is a plain image: no scripts, no cookies. People who see it on your page load it from our server.

How we track Google Wallet

The status on this page comes from user-submitted problem reports for Google Wallet, counted in 15-minute windows over the last 24 hours. Each window is compared with the normal level for Google Wallet, so a few complaints on a quiet day don't trigger anything, but a sudden jump well above normal does.

When reports climb well above normal, the status here changes to partial outage or major outage and the chart moves with it. This is separate from Google Wallet's official status page: user reports tend to show a problem early, while the official page confirms the cause. If the two disagree, check both.

Elsewhere

Check other services