Continue with Google outages and problems
In the past 24 hours, 5 user reports came in for Continue with Google. Counting only the 15-minute windows with a spike big enough to count as an outage, that comes to 100.00% uptime for the day.
The busiest 15-minute window had 1 report, about 23 hours ago. That stays below our outage threshold, so it doesn't count as downtime.
What people can report about Continue with Google
People who report a problem with Continue with Google to the outage-report feed behind this page can tag what is affected. These are the categories they can pick; the feed shows no counts per category:
- Login
- App
- Connecting to VPN
Continue with Google reports around the world
In the last 24 hours, 7 problem reports about Continue with Google came in from 3 countries. Right now reports are at the usual level in every country.
- Outage now
- Problems now
- Normal
| Country | Now | Last hour | 24 hours |
|---|---|---|---|
| The US numbers above | Normal | 0 | 5 |
| The Philippines | Normal | 0 | 1 |
| Mexico | Normal | 0 | 1 |
| France | Normal | 0 | 0 |
| Algeria | Normal | 0 | 0 |
| Argentina | Normal | 0 | 0 |
| Australia | Normal | 0 | 0 |
| Bahrain | Normal | 0 | 0 |
| Bangladesh | Normal | 0 | 0 |
| Austria | Normal | 0 | 0 |
| Belgium | Normal | 0 | 0 |
| Brazil | Normal | 0 | 0 |
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.
Continue with Google problem spikes, last 30 days
Since 28 October, Continue with Google 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: no data
- Sat 10 Oct: no data
- Sun 11 Oct: no data
- Mon 12 Oct: no data
- Tue 13 Oct: no data
- Wed 14 Oct: no data
- Thu 15 Oct: no data
- Fri 16 Oct: no data
- Sat 17 Oct: no data
- Sun 18 Oct: no data
- Mon 19 Oct: no data
- Tue 20 Oct: no data
- Wed 21 Oct: no data
- Thu 22 Oct: no data
- Fri 23 Oct: no data
- Sat 24 Oct: no data
- Sun 25 Oct: no data
- Mon 26 Oct: no data
- Tue 27 Oct: no data
- Wed 28 Oct: 1 report
- Thu 29 Oct: 6 reports
- Fri 30 Oct: 5 reports
- Sat 31 Oct: 5 reports
- Sun 1 Nov: no data
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 US16
- Canada2
- India2
- Italy2
- Mexico2
- Thailand2
- Ukraine2
- Brazil1
Country history starts on 28 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 28 October 2026. Monthly reports for all services
How to fix Continue with Google not working
Continue with Google 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 accounts.google.com over your own connection, right now. Nothing is sent to us or stored.
Retry the Continue with Google button
Close the sign-in popup, then reload the page. Press the button again and watch for a blank window or a loop back to the same screen.
Check your Google Account in a new tab
Sign in to your Google Account, then pick the account you want from the chooser. If that works but the app still fails, remove the other Google accounts from the chooser and try the button again.
Clear cookies for the site and Google
In Chrome, click the icon next to the address bar and choose Cookies and site data. Delete the site's cookies. Try the sign-in again; if the button still loops, clear cookies for Google from the same menu.
Turn off extensions that block scripts
Open the menu in Chrome, then go to Extensions and Manage Extensions. Turn off ad blockers and privacy tools. Reload the page and try the sign-in; if it works, turn extensions back on one at a time to find the one that breaks the flow.
While Continue with Google is down: what to use instead
- Email and password If you ever set a password on the site you're trying to reach, type your Google email and that password into the normal login form, because that route doesn't depend on Google's sign-in at all.
- Forgot password link When you never created a password, most login pages will email you a reset link for the same address so you can set one and get in without the Google button.
- A device that's still signed in Your phone or another browser where you're already logged in usually keeps working, since an existing session doesn't need a fresh Google sign-in.
- Sign in with Apple or Microsoft Use another provider only if the site has already linked it to your account; otherwise you can end up with a second, empty account under a different email.
Fix Continue with Google on Windows, Mac, Android and iPhone
Continue with Google on Windows
- Fix
- Clear your browser's cookies and cache, or try using an Incognito window to complete the 'Continue with Google' sign-in. Ensure your Windows system time is correct, as mismatched clocks can block secure authentication connections.
- Check
- Check the Google Workspace Status Dashboard to see if Google's authentication services are down. You can also open your browser's Developer Tools (F12) to check for network errors when clicking 'Continue with Google'.
ping accounts.google.comTest whether Continue with Google's servers replynslookup accounts.google.comCheck that Continue with Google's DNS resolvestracert accounts.google.comTrace where the connection dropsipconfig /flushdnsClear the DNS cache, then reloadContinue with Google on Mac
- Fix
- Clear your browser history and ensure that third-party cookies are allowed in your Safari or Chrome settings to let 'Continue with Google' function. Disabling restrictive firewall or antivirus software on macOS can also resolve connection blocks.
- Check
- Attempt to use 'Continue with Google' in a private browsing window to rule out local extension interference. Verify if Google services are experiencing global outages via official status pages.
ping -c 4 accounts.google.comTest whether Continue with Google's servers replynslookup accounts.google.comCheck that Continue with Google's DNS resolvestraceroute accounts.google.comTrace where the connection dropssudo dscacheutil -flushcache; sudo killall -HUP mDNSResponderFlush the macOS DNS cache, then reloadContinue with Google on Android
- Fix
- Clear the cache for Google Play Services and the app you are trying to access, then verify your Google account is syncing in Android settings. Updating the Google System WebView app can also resolve 'Continue with Google' loading issues.
- Check
- Check if you can sign in using 'Continue with Google' on other apps or your mobile browser. Look for account sync errors or warning prompts in your Android notification shade.
Continue with Google on iPhone and iPad
- Fix
- Go to iOS Settings, select Safari, and temporarily disable 'Prevent Cross-Site Tracking' which can block the 'Continue with Google' authentication flow. Reinstalling the affected app can also reset broken login configurations.
- Check
- Test if the 'Continue with Google' prompt loads in Safari instead of the third-party app's built-in browser. Check if other Google apps on your iPhone are currently unable to connect.
What happens when Continue with Google goes down
Continue with Google lets you sign in to shopping or news apps with your Google account instead of creating a new password for every login. Outages lock you out.
When it fails, the Google account chooser often spins or closes after you tap the button, so you loop back to the app login screen. You stay signed out. On iPhone or Android the popup may stall while desktop sessions stay signed in. Because the button depends on your Google session, outages often hit new logins first and leave existing sessions alone for a while.
Continue with Google 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
- 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 118 ms
Checked from our server in Frankfurt, Germany, 11 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 Singapore (26 ms), slowest from São Paulo (1,104 ms). Every location connected through Google LLC (AS15169), using 8 different addresses.
| Location | Result | Time | Address reached |
|---|---|---|---|
| FrankfurtGermany | Up · HTTP 302 | 44 ms | 142.251.127.84data centre in Frankfurt |
| ViennaAustria | Up · HTTP 302 | 84 ms | 142.251.127.84data centre in Frankfurt |
| MilanItaly | Up · HTTP 302 | 68 ms | 142.251.127.84data centre in Frankfurt |
| ParisFrance | Up · HTTP 302 | 42 ms | 142.251.173.84 |
| AmsterdamNetherlands | Up · HTTP 302 | 33 ms | 142.250.102.84 |
| MadridSpain | Up · HTTP 302 | 102 ms | 192.178.223.84data centre in London |
| WarsawPoland | Up · HTTP 302 | 111 ms | 142.251.127.84data centre in Frankfurt |
| Los AngelesUSA | Up · HTTP 302 | 70 ms | 74.125.137.84 |
| São PauloBrazil | Up · HTTP 302 | 1,104 ms | 64.233.162.84 |
| SingaporeSingapore | Up · HTTP 302 | 26 ms | 142.251.175.84 |
| TokyoJapan | Up · HTTP 302 | 58 ms | 142.251.169.84 |
Checked with check-host.net from its servers in these cities 11 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.
Continue with Google FAQ
Is Continue with Google down right now?
Why does Continue with Google show 'This browser or app may not be secure'?
My Continue with Google sign-in keeps looping on iPhone or Android. What should I try?
Google Workspace says 'Access blocked: This app's request is invalid' when I use the Google button. Who fixes it?
Why does Continue with Google fail on a supervised child account or school Chromebook?
How we track Continue with Google
The status on this page comes from user-submitted problem reports for Continue with Google, counted in 15-minute windows over the last 24 hours. Each window is compared with the normal level for Continue with Google, 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 Continue with Google'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.