isitdownrightnow.app
  1. Home
  2. Services
  3. Google Public DNS
Google Public DNS developers.google.com

Is Google Public DNS down right now? Live status and outage tracker

No, Google Public DNS is up.

No widespread outage detected. 3 user reports in the last hour is within the normal range.

Live Data refreshes every 5 minutes
Not working for you? Help centre
User reports, last 24 hours, 15 minutes a segment: 96 flowing, 0 slow (elevated), 0 jammed (outage)

User reports, last 24 hours

11 reports in total, counted in 15-minute windows

In the last hour, 3 problem reports came in for Google Public DNS, 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 DNS (80%) and API (20%). There has been no spike in reports since 7 October. These are user reports from the US, where most people report Google Public DNS problems.

Around the world right now: normal in 71 other countries. Most reports in the last hour: Brazil 1. By country

In the past 24 hours, 11 user reports came in for Google Public DNS. 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 3 reports, in the last 15 minutes. That stays below our outage threshold, so it doesn't count as downtime.
Reports, last hour
3
None the hour before
Uptime, 24 h
100.00%
No outage windows
Last outage
None
In the last 24 hours
Busiest 15 minutes
3
3 reports, just now
Last 24 hours

Google Public DNS outages and problems

In the past 24 hours, 11 user reports came in for Google Public DNS. 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 3 reports, in the last 15 minutes. That stays below our outage threshold, so it doesn't count as downtime.

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

Google Public DNS in November 2026

Problem reports in November
1

Monthly report for November 2026

What went wrong

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

  1. DNS80%
  2. API20%

Share of 5 recent reports that said what was wrong, from every country listed below.

World map

Google Public DNS reports around the world

In the last 24 hours, 73 problem reports about Google Public DNS came in from 25 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
The US numbers above Normal 120
Brazil Normal 112
Italy Normal 04
The Netherlands Normal 03
Germany Normal 03
France Normal 03
Poland Normal 03
Thailand Normal 03
The UK Normal 02
Mexico Normal 02
Japan Normal 02
Romania Normal 02

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

Last 30 days

Google Public DNS problem spikes, last 30 days

Since 7 October, Google Public DNS 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: 2 reports
  • Thu 8 Oct: 0 reports
  • Fri 9 Oct: 0 reports
  • Sat 10 Oct: 0 reports
  • Sun 11 Oct: 0 reports
  • Mon 12 Oct: 1 report
  • Tue 13 Oct: 1 report
  • Wed 14 Oct: 0 reports
  • Thu 15 Oct: 1 report
  • Fri 16 Oct: 1 report
  • Sat 17 Oct: 0 reports
  • Sun 18 Oct: 0 reports
  • Mon 19 Oct: 2 reports
  • Tue 20 Oct: 0 reports
  • Wed 21 Oct: no data
  • Thu 22 Oct: 0 reports
  • Fri 23 Oct: 0 reports
  • Sat 24 Oct: 0 reports
  • Sun 25 Oct: 0 reports
  • Mon 26 Oct: 1 report
  • Tue 27 Oct: 4 reports
  • Wed 28 Oct: 8 reports
  • Thu 29 Oct: 32 reports
  • Fri 30 Oct: 24 reports
  • Sat 31 Oct: 11 reports
  • Sun 1 Nov: 1 report

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 US20
  • Brazil12
  • Italy4
  • Germany3
  • France3
  • The Netherlands3
  • Poland3
  • Thailand3

Country history starts on 30 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 7 October 2026. Monthly reports for all services

Troubleshooting

How to fix Google Public DNS not working

Google Public DNS 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 developers.google.com over your own connection, right now. Nothing is sent to us or stored.

  1. Confirm the addresses on your device

    Open your network adapter settings and check the DNS entries against 8.8.8.8 and 8.8.4.4. On Windows that is Settings, Network and Internet, the adapter's properties, then Internet Protocol Version 4; macOS hides the same fields under System Settings, Network, Details, DNS. A single wrong digit looks exactly like an outage, so retype both.

  2. Flush your local DNS cache

    Old records on your machine outlive a hiccup. Flushing clears them, so run ipconfig /flushdns from an administrator Command Prompt on Windows or sudo resolvectl flush-caches on Linux. On macOS, sudo dscacheutil -flushcache followed by sudo killall -HUP mDNSResponder does the same job.

  3. Query the resolver directly

    Run nslookup and give 8.8.8.8 as the server, or use dig @8.8.8.8 on Linux and macOS. Pick a domain you know resolves, then watch whether the answer comes back. A timeout or a refused response points at the network path rather than your browser.

  4. Move the queries off your router

    Your router may be rewriting or blocking DNS traffic on port 53, so set the addresses on the device itself instead of letting the router hand them out. Then restart the router, since a stuck forwarder there can fail while everything else on the network is fine. If the device still cannot resolve, switch it to a different public resolver and read the help centre at https://developers.google.com/speed/public-dns.

While Google Public DNS is down: what to use instead

  • Cloudflare DNS Replace 8.8.8.8 and 8.8.4.4 with 1.1.1.1 and 1.0.0.1 in your router or network settings, and your lookups go to Cloudflare instead while everything else on your connection stays the same.
  • Quad9 It answers on 9.9.9.9 and blocks known malware domains.
  • OpenDNS Cisco runs it on 208.67.222.222 and 208.67.220.220, and you can point a device at those addresses without signing up for anything.
  • Your ISP's DNS Set your device or router back to getting DNS automatically; you then use your provider's resolvers, which is the quickest fix if you'd rather not type in addresses.
Your device

Fix Google Public DNS on Windows, Mac, Android and iPhone

Google Public DNS on Windows

Fix
To fix Google Public DNS issues on Windows, open your Network Connections, access your active adapter's properties, and verify the IPv4 addresses are set to 8.8.8.8 and 8.8.4.4. You can also temporarily switch to automatic DNS settings to restore your connection.
Check
To check if Google Public DNS is down on Windows, try pinging a public IP address like 8.8.8.8 in the Command Prompt. If the IP responds but websites fail to load by name, the DNS service may be experiencing an outage.
Command Prompt
ping developers.google.comTest whether Google Public DNS's servers reply
nslookup developers.google.comCheck that Google Public DNS's DNS resolves
tracert developers.google.comTrace where the connection drops
ipconfig /flushdnsClear the DNS cache, then reload

Google Public DNS on Mac

Fix
To resolve Google Public DNS issues on macOS, navigate to Network settings, select your active connection, and ensure 8.8.8.8 and 8.8.4.4 are listed in the DNS servers tab. You can also try flushing your DNS cache or toggling your network connection.
Check
Check if Google Public DNS is down on macOS by testing if you can access websites using their raw IP addresses but not their domain names. If switching to your ISP's default DNS resolves the issue, Google Public DNS is likely down.
Terminal
ping -c 4 developers.google.comTest whether Google Public DNS's servers reply
nslookup developers.google.comCheck that Google Public DNS's DNS resolves
traceroute developers.google.comTrace where the connection drops
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponderFlush the macOS DNS cache, then reload

Google Public DNS on Android

Fix
If Google Public DNS is not working on Android, go to your Network settings and verify that the Private DNS provider hostname is correctly set to 'dns.google'. If issues persist, switch Private DNS to Automatic or Off to restore your internet access.
Check
To tell if Google Public DNS is down on Android, check if your device displays a 'Private DNS server cannot be accessed' error. You can also try disabling Private DNS to see if web browsing immediately resumes.

Google Public DNS on iPhone and iPad

Fix
To fix Google Public DNS on iOS, open your Wi-Fi settings, tap the information icon next to your network, and ensure the DNS is configured with Google's IP addresses. If you use a custom DNS profile or VPN, try disabling it to restore your connection.
Check
Determine if Google Public DNS is down on iOS by checking if Safari fails to load web pages while you still have an active internet connection. Switching your Wi-Fi DNS configuration back to Automatic will confirm if Google's servers are the issue.
About

What happens when Google Public DNS goes down

Google Public DNS is a free, public DNS resolver that turns domain names into IP addresses for people who set it on a router, phone, computer, or browser. When it has trouble, new sites and apps that need a fresh lookup fail to open even if your internet connection itself is still up.

If the service stops answering, cached pages and already open connections can keep working for a while; the first failures hit new domains and fresh app launches. Then you see browser errors such as 'DNS server not responding' or 'server IP address could not be found'; streaming apps and game launchers may hang or drop with connection errors. Problems are often regional or partial. Two people on different networks might get different results, and a router that only points to this resolver may lose name resolution for every device behind it.

Servers and network

Google Public DNS IP address, servers and network

IPv4 addresses
142.251.110.100
Show all 6
  • 142.251.110.101
  • 142.251.110.102
  • 142.251.110.113
  • 142.251.110.138
  • 142.251.110.139
IPv6 addresses
2a00:1450:4001:c15::64
Show all 4
  • 2a00:1450:4001:c15::71
  • 2a00:1450:4001:c15::8a
  • 2a00:1450:4001:c15::8b
Network
AS15169 · Google LLC, registered in the United States
Served through
Google
DNS hosted by
its own name servers (nip.io)
HTTPS certificate
Issued by Google Trust Services, valid until 30 Dec 2026 (59 days)
HTTP/3
Supported
Our check
Answered in 396 ms

Checked from our server in Frankfurt, Germany, 5 days ago, for developers.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 developers.google.com. Fastest from Tokyo (305 ms), slowest from São Paulo (1,469 ms). Every location connected through Google LLC (AS15169), using 11 different addresses.

LocationResultTimeAddress reached
FrankfurtGermanyUp387 ms142.251.110.138
ViennaAustriaUp904 ms142.250.120.113
MilanItalyUp431 ms192.178.194.113
ParisFranceUp1,022 ms172.217.20.46data centre in Stockholm
AmsterdamNetherlandsUp491 ms192.178.24.110data centre in Amsterdam
MadridSpainUp597 ms216.58.205.46data centre in Madrid
WarsawPolandUp610 ms142.251.13.100
Los AngelesUSAUp324 ms142.251.215.238data centre in Los Angeles
São PauloBrazilUp1,469 ms142.251.38.110data centre in Stockholm
SingaporeSingaporeUp511 ms172.217.194.101
TokyoJapanUp305 ms192.178.226.101data centre in Tokyo

Checked with check-host.net from its servers in these cities 3 days ago, for developers.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 Public DNS FAQ

Is Google Public DNS down right now?
The status at the top of this page shows whether problem reports for it are above their usual level, counted in 15-minute windows over the last 24 hours. It does not ping or probe the service. To see if the trouble sits only on your side, switch your device to mobile data or another Wi-Fi network and try the same site, then set DNS back to automatic or test another resolver; if pages load, your router or device DNS settings are the likely cause.

Why does 8.8.8.8 work on my phone but not on my router?
Routers often keep their own DNS settings, and some ignore the addresses you enter or only pass them to certain devices. Check the WAN DNS fields, not just the LAN DHCP settings; if the router has a DNS proxy, your phone may still use the router as its resolver. Reboot the router after saving, then test from a computer connected to its Wi-Fi.

Can I set Google Public DNS as Private DNS on Android?
Yes, Android's Private DNS setting accepts a hostname, so enter the DNS-over-TLS hostname from the Google Public DNS help centre rather than one of the raw IP addresses. If the hostname does not save or sites fail to load after you apply it, switch Private DNS back to Automatic and test again. Some networks block DNS-over-TLS on port 853, which can make that mode look broken even when the resolver is fine.

Why do some sites fail with Google Public DNS but load with my ISP's resolver?
This can come from CDN geolocation, a local block, a filter on your network, or split-horizon DNS. Google Public DNS may return a different edge server than your ISP resolver, and some sites or captive portals expect the resolver to be on the same network. Try the site in a private window, then compare results with automatic DNS; if it loads only on automatic, the site or your ISP is the issue.

Does Google Public DNS block malware or adult sites?
No, it returns DNS answers without filtering content. It is not a family filter and it does not offer ad blocking. If you need blocking, use a filtering resolver or your router's parental controls, and keep in mind that DNS filtering alone is easy to bypass.
For your site

Put the Google Public DNS 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 Public DNS status badge, as it looks now

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

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 Public DNS

The status on this page comes from user-submitted problem reports for Google Public DNS, counted in 15-minute windows over the last 24 hours. Each window is compared with the normal level for Google Public DNS, 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. Google Public DNS doesn't publish a public status page that we know of, so user reports are often the quickest sign that something is wrong on their side.

Elsewhere

Check other services

See all 500+ services

Problems elsewhere right now

Strips: user reports, last 6 hours, 15 minutes a segment.