Space for ads
Checked every 5 minutes · How we measure this
As of 00:25 EDT on 22 Sep 2026, google.com responded to our check in 63 ms, with 100.00% availability over the last 24 hours.
Checked every 5 minutes · last checked 8 minutes ago
The line is response time measured from our probe to google.com, which rises when the service slows down. Shaded red marks intervals where checks actually failed. It excludes your own connection and browser rendering.
0 problem reports
Google outage
DownBits detected an outage on Google between 18 Sep 2026, 13:30 – 13:40 IST, lasting ongoing. Detected across 2 consecutive automated checks of google.com.
Detected by DownBits probe
Google is responding normally. Our last automated check of google.com completed 8 minutes ago and succeeded in 63 ms. Over the past 24 hours the service answered 100.00% of our checks.
Measured from our automated checks, Google has been available 100.00% over 24 hours, 99.85% over 7 days, 99.86% over 30 days. We recorded 1 incident in the last 30 days.
Google has averaged 75 ms across our successful checks in the past 24 hours, which is fast — comfortably within what a healthy service should return. Response time is measured from our probe to google.com and does not include rendering time in your browser.
The most recent incident DownBits recorded for Google began on 18 September 2026 at 13:30 IST and lasted 10 min. It was logged as outage. Detected by DownBits probe.
Our probe is reaching google.com normally right now, so the problem is more likely to be local to you than a full outage. Use the report button on this page to add your own signal — when several people report the same problem within a short window, it appears on the chart above.
Mobile apps and the website often run on different infrastructure. If Google fails in the app but works at google.com in a browser, an app update or a cache clear inside the app usually resolves it.
Open any other site. If nothing loads, the issue is your network rather than Google. On Windows run ping google.com and nslookup google.com in Command Prompt; on macOS or Linux use Terminal. A DNS failure and a server failure look identical in a browser but are very different problems.
Load google.com in a private or incognito window. If it works there, clear cookies and site data for google.com in your normal browser rather than clearing everything.
Switch from Wi-Fi to mobile data, or vice versa. Regional ISP routing problems are common and often affect one carrier while others are unaffected.
We link the vendor status page so you can check our reading against theirs.
No comments received
