Google Voice outages and problems
User reports, last 24 hours
11 reports in total, counted in 15-minute windows
No problem reports came in for Google Voice in the last hour, and at this time of day there are usually almost none. Over the last 24 hours there were 11 reports. Worldwide, most recent reports were about app (67%) and automation & workflows (33%). There has been no spike in reports since 28 October. These are user reports from the US, where most people report Google Voice problems.
Around the world right now: normal in 47 other countries. By country
- NormalClose to the usual level24 h · 11 reports
- ElevatedMore than 1.5 times the usual levelNone in this chart
- OutageMore than twice the usual level and far above the day's averageNone in this chart
- Usual levelWhat a usual day sees at that timeAlmost none at this time of day
In the past 24 hours, 11 user reports came in for Google Voice. 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 2 reports, about 12 hours ago. That stays below our outage threshold, so it doesn't count as downtime.
Google Voice in November 2026
- Problem reports in November
- 185
Monthly report for November 2026
What went wrong
What people said was wrong in recent problem reports for Google Voice worldwide.
Share of 3 recent reports that said what was wrong, from every country listed below.
Google Voice reports around the world
In the last 24 hours, 38 problem reports about Google Voice 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 | 1 | 34 |
| Pakistan | Normal | 0 | 3 |
| Japan | Normal | 0 | 1 |
| The UK | Normal | 0 | 0 |
| Argentina | Normal | 0 | 0 |
| Australia | Normal | 0 | 0 |
| Austria | Normal | 0 | 0 |
| Belgium | Normal | 0 | 0 |
| Brazil | Normal | 0 | 0 |
| Canada | Normal | 0 | 0 |
| Chile | Normal | 0 | 0 |
| Colombia | Normal | 0 | 0 |
Each country's status compares its reports with the usual level there. 36 more countries had 0 reports in the last 24 hours. Map outlines: Natural Earth.
Google Voice problem spikes, last 30 days
Since 28 October, Google Voice had no outage spikes or periods of elevated reports.
- 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: 3 reports
- Thu 29 Oct: 15 reports
- Fri 30 Oct: 7 reports
- Sat 31 Oct: 2 reports
- Sun 1 Nov: 2 reports
- Mon 2 Nov: 20 reports
- Tue 3 Nov: 9 reports
- Wed 4 Nov: 7 reports
- Thu 5 Nov: 10 reports
- Fri 6 Nov: 6 reports
- Sat 7 Nov: 3 reports
- Sun 8 Nov: 6 reports
- Mon 9 Nov: 3 reports
- Tue 10 Nov: 6 reports
- Wed 11 Nov: 5 reports
- Thu 12 Nov: 43 reports
- Fri 13 Nov: 52 reports
- Sat 14 Nov: 10 reports
- Sun 15 Nov: 3 reports
By country
In the last 19 days, most Google Voice problem reports came from the US (200), Brazil (8) and Pakistan (8). None of these countries had a day at outage level.
- The USNo spikes200
- BrazilNo spikes8
- PakistanNo spikes8
- The PhilippinesNo spikes6
- CanadaNo spikes5
- The UKNo spikes4
- EgyptNo spikes3
- FranceNo spikes3
- Outage spike
- Elevated reports
- Normal
- No data yet
Each square is one day. It turns red when reports stayed at outage level for half an hour or more, and amber when they stayed above the usual level for an hour or more. The number on the right is the country's total since 28 October 2026, when country history starts. A wider gap marks a Monday. Point at a square, or tap it, for that day's numbers. 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 Google Voice not working
Google Voice 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:
Check the official status page
Open Google's official status page first. Look for an incident that names Voice, because the entries there tell you whether to wait or keep digging. A clear page points the problem back at your device or account.
Sign in with the account that owns the number
Several Google Accounts can be signed in at once. The one that loads may not be the one tied to your number, so switch it: click your profile picture in the top right of the web app and pick the right account. On the phone, open the menu and read the address at the top of settings.
Stop calls from skipping to voicemail
When calls go straight to voicemail, Do Not Disturb is the first thing to check. Open settings in the web app, choose Calls, and switch Do not disturb off. A linked number that was removed or needs verifying also blocks the ring, so look at what shows under Account.
Reinstall the app
Delete the app and install it again from the Play Store or the App Store. Sign back in with the same account, and your number should reappear on its own. If a bad update caused the trouble, reinstalling clears the local data that update left behind; the help centre covers what it does not fix.
While Google Voice is down: what to use instead
- Web version in a browser If the phone app won't load your messages or keeps failing to connect, open Voice in a browser on your computer, since an app problem doesn't always affect the web client.
- Your carrier's own calling and texts Use your phone's built-in dialer and messaging app for anything urgent, but remember the other person sees your carrier number instead of your Voice number.
- WhatsApp WhatsApp handles calls and texts over Wi-Fi or mobile data when the other person has it installed.
- Google Meet Send a Meet link for a quick audio or video call; the other person can join from a browser.
Fix Google Voice on Windows, Mac, Android and iPhone
Google Voice on Windows
- Fix
- Clear your browser cache and cookies, or try using a supported browser like Google Chrome to access the Google Voice website. Ensure microphone and notification permissions are enabled for the site.
- Check
- Check if you can access the Google Voice website and if outgoing calls fail with a connection error. You can also verify if other Google services are loading to rule out a wider outage.
ping voice.google.comTest whether Google Voice's servers replynslookup voice.google.comCheck that Google Voice's DNS resolvestracert voice.google.comTrace where the connection dropsipconfig /flushdnsClear the DNS cache, then reloadGoogle Voice on Mac
- Fix
- Verify that your browser has permission to access your microphone in macOS System Settings, and clear the browser's website data for Google Voice. Restarting the browser can also resolve audio routing issues.
- Check
- Attempt to sign into your Google Voice account via a Mac web browser and check if the interface loads or if calls immediately drop. Check the Google Workspace Status Dashboard for service-wide disruptions.
ping -c 4 voice.google.comTest whether Google Voice's servers replynslookup voice.google.comCheck that Google Voice's DNS resolvestraceroute voice.google.comTrace where the connection dropssudo dscacheutil -flushcache; sudo killall -HUP mDNSResponderFlush the macOS DNS cache, then reloadGoogle Voice on Android
- Fix
- Update the Google Voice app from the Google Play Store and clear its cache in your Android settings. Ensure the app has permissions for contacts, microphone, and phone.
- Check
- Open the Google Voice app to see if it displays a connection error banner or fails to sync your text messages. Try sending a test text to see if it fails to deliver.
Google Voice on iPhone and iPad
- Fix
- Update the Google Voice app via the Apple App Store and ensure that microphone access is enabled in your iOS settings. Reinstalling the app can also resolve persistent connection issues.
- Check
- Check if the Google Voice app fails to load your call logs or if you receive a notification that a call could not be placed. Verify if the app crashes upon opening or fails to send messages.
When people report Google Voice problems
The busiest hour for reports about Google Voice is 21:00 to 22:00 Central European time, and the busiest day is Thursday.
By hour of the day
- 00:00 to 01:00: 0.24 reports on an average day
- 01:00 to 02:00: 0.22 reports on an average day
- 02:00 to 03:00: 0.18 reports on an average day
- 03:00 to 04:00: 0.14 reports on an average day
- 04:00 to 05:00: 0.22 reports on an average day
- 05:00 to 06:00: 0.1 reports on an average day
- 06:00 to 07:00: 0.04 reports on an average day
- 07:00 to 08:00: 0 reports on an average day
- 08:00 to 09:00: 0.08 reports on an average day
- 09:00 to 10:00: 0.05 reports on an average day
- 10:00 to 11:00: 0.05 reports on an average day
- 11:00 to 12:00: 0 reports on an average day
- 12:00 to 13:00: 0.11 reports on an average day
- 13:00 to 14:00: 0.07 reports on an average day
- 14:00 to 15:00: 0.1 reports on an average day
- 15:00 to 16:00: 0.28 reports on an average day
- 16:00 to 17:00: 0.26 reports on an average day
- 17:00 to 18:00: 0.28 reports on an average day
- 18:00 to 19:00: 0.2 reports on an average day
- 19:00 to 20:00: 0.5 reports on an average day
- 20:00 to 21:00: 0.75 reports on an average day
- 21:00 to 22:00: 0.75 reports on an average day
- 22:00 to 23:00: 0.46 reports on an average day
- 23:00 to 00:00: 0.3 reports on an average day
By day of the week
- Monday: 4.3 reports on an average Monday
- Tuesday: 2.5 reports on an average Tuesday
- Wednesday: 3 reports on an average Wednesday
- Thursday: 13 reports on an average Thursday
- Friday: 11 reports on an average Friday
- Saturday: 2.5 reports on an average Saturday
- Sunday: 2.1 reports on an average Sunday
Each bar is the average number of user reports in that hour, or on that day of the week, from 39 days of reports since 5 October 2026. The busiest bar is highlighted. Spikes in reports are left out, so one outage does not set the pattern.
What happens when Google Voice goes down
Google Voice gives you a phone number for calls, texts, voicemail, and call forwarding. You may use it as a second line for work or home, and an outage can cut off incoming calls, outgoing calls, text messages, and voicemail alerts on the web and in the mobile apps.
During an outage, the mobile app may stall while connecting or signing in, and the web inbox may fail to load. Calls can fail to connect or drop mid-call, texts can queue or fail to send, and voicemail recordings or transcripts may not appear. Sign-in and inbox loading often break first, before call and text delivery. Problems are often partial or regional, hitting a subset of numbers or carriers rather than every account at once.
Google Voice IP address, servers and network
- IPv4 addresses
- 142.251.14.100
Show all 6
- 142.251.14.101
- 142.251.14.102
- 142.251.14.113
- 142.251.14.138
- 142.251.14.139
- IPv6 addresses
- 2a00:1450:4001:c13::65
Show all 4
- 2a00:1450:4001:c13::66
- 2a00:1450:4001:c13::8a
- 2a00:1450:4001:c13::8b
- Network
- AS15169 · Google LLC, registered in the United States
- Served through
- DNS hosted by
- HTTPS certificate
- Issued by Google Trust Services, valid until 26 Jan 2027 (72 days)
- HTTP/3
- Supported
- Our check
- Answered in 95 ms
Checked from our server in Frankfurt, Germany, 37 h ago, for workspace.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 12 places around the world
All 12 locations got an answer from workspace.google.com. Fastest from Amsterdam (129 ms), slowest from Tokyo (2,099 ms). Every location connected through Google LLC (AS15169), using 12 different addresses.
| Location | Result | Time | Address reached |
|---|---|---|---|
| FrankfurtGermany | Up | 289 ms | 142.251.127.138data centre in Frankfurt |
| ViennaAustria | Up | 259 ms | 142.251.141.46data centre in Munich |
| MilanItaly | Up | 276 ms | 142.251.27.138 |
| ParisFrance | Up | 203 ms | 74.125.206.113 |
| AmsterdamNetherlands | Up | 129 ms | 192.178.24.142data centre in Amsterdam |
| MadridSpain | Up | 434 ms | 216.58.206.14data centre in Madrid |
| WarsawPoland | Up | 280 ms | 142.250.109.101 |
| DallasUSA | Up | 199 ms | 172.253.156.138 |
| Los AngelesUSA | Up | 138 ms | 142.251.215.238data centre in Los Angeles |
| São PauloBrazil | Up | 1,271 ms | 142.250.219.46data centre in Rio de Janeiro |
| SingaporeSingapore | Up | 581 ms | 172.253.118.102 |
| TokyoJapan | Up | 2,099 ms | 142.250.178.110data centre in Oslo |
Checked with check-host.net from its servers in these cities 37 h ago, for workspace.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.
Google Voice FAQ
Is Google Voice down right now?
Why do my Google Voice calls fail with a 'Couldn't complete your call' message?
Why did Google Voice stop sending texts on my iPhone or Android?
Why can't I claim a new Google Voice number or link my existing number?
Why does Google Voice voicemail not forward to my phone or show up in the app?
Contact Google Voice support
- Official status pagegoogle.com/appsstatus/dashboard
- Help centresupport.google.com/voice
- Websitevoice.google.com
Tip: when Google Voice is down, its official status page is the quickest way to confirm the cause and see when a fix is expected.
About Google Voice
- Category
- VoIP / Telephony
- Country
- United States
How we track Google Voice
The status on this page comes from user-submitted problem reports for Google Voice, counted in 15-minute windows over the last 24 hours. Each window is compared with the normal level for Google Voice, 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 Voice'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.