Is Google Scholar down? Live status and outage map
No, Google Scholar is up right now.
It answered in 174 ms. If it isn't working for you, the problem is probably on your side, so see what to try below.
Checked from EU (Falkenstein) · Check from other countries
Not working for you? Tell others what's wrong. Reports are anonymous; we don't store IP addresses.
- Response time
- 174msHTTP 200 OK
- Uptime, 24 hours
- 100%273 checks
- Uptime, 30 days
- 100%2,004 checks
- SSL certificate
- 72daysValid until Jan 26, 2027
Notify me when Google Scholar is down
Leave your email and we'll write to you when our checks find Google Scholar down. No account needed.
Google Scholar outage map
Reached from EU (Falkenstein)
The big dot is our server in EU (Falkenstein), which decides the status above. Small dots are home and mobile connections, one per country. Countries are shaded as visitors run the connection test below or report problems.
Check from other countries
0 of 5 picked
Pick up to 5 countries and watch them on the map. One home or mobile connection in each opens scholar.google.com through Globalping, so you can see whether a problem is limited to some places. You can do this 3 times an hour.
Last 24 hours
Last 15 checks
| Time | Result | Answer | Response | From |
|---|---|---|---|---|
| Scheduled | Up | 200 OK | 174 ms | EU (Falkenstein) |
| Scheduled | Up | 200 OK | 690 ms | EU (Falkenstein) |
| Scheduled | Up | 200 OK | 645 ms | EU (Falkenstein) |
| Scheduled | Up | 200 OK | 713 ms | EU (Falkenstein) |
| Scheduled | Up | 200 OK | 649 ms | EU (Falkenstein) |
| Scheduled | Up | 200 OK | 735 ms | EU (Falkenstein) |
| Scheduled | Up | 200 OK | 195 ms | EU (Falkenstein) |
| Scheduled | Up | 200 OK | 170 ms | EU (Falkenstein) |
| Scheduled | Up | 200 OK | 662 ms | EU (Falkenstein) |
| Scheduled | Up | 200 OK | 157 ms | EU (Falkenstein) |
| Scheduled | Up | 200 OK | 179 ms | EU (Falkenstein) |
| Scheduled | Up | 200 OK | 642 ms | EU (Falkenstein) |
| Scheduled | Up | 200 OK | 673 ms | EU (Falkenstein) |
| Scheduled | Up | 200 OK | 663 ms | EU (Falkenstein) |
| Scheduled | Up | 200 OK | 662 ms | EU (Falkenstein) |
Test from your connection
Your browser tries to reach scholar.google.com directly, the same way it would if you opened it. We compare that with our own check to tell whether the problem is the site or your connection.
We record only whether the test worked, how long it took and your country. Ad blockers can block the test for some sites.
Problem reports
Nobody has reported a problem with Google Scholar in the last 7 days. If it isn't working for you, say so at the top of this page.
Comments
No comments yet
Google Scholar outage history
No outages in the last 90 days
If Google Scholar isn't working for you
Reload without the cache
Press Ctrl+F5 on Windows or Cmd+Shift+R on a Mac, or open the site in a private window.
Try another network
Switch between Wi-Fi and mobile data. If it works on one, the problem is your network or provider.
Pause extensions and VPN
Ad blockers, VPNs and proxies are common causes of sites failing to load.
Restart the app or device
For mobile apps, also check for an update.
Check your clock
A wrong date or time on your device breaks secure connections.
Refresh your DNS
If only Google Scholar fails, restart your router or switch to a public DNS resolver.
Common questions about Google Scholar
- Is Google Scholar down for everyone or just for me?
- Most likely just you. Google Scholar answered our server in EU (Falkenstein) on its last check. Use "Test from your connection" on this page to see whether your own browser can reach scholar.google.com.
- What problems do people report with Google Scholar?
- Nobody has reported a problem in the last 7 days. If Google Scholar isn't working for you, add a report at the top of this page so the next visitor knows.
- How often does Google Scholar go down?
- Over the last 30 days Google Scholar was reachable in 100% of our 2,004 scheduled checks. We have not logged an outage in the last 90 days.
- How do you check whether Google Scholar is down?
- Every 5 minutes our server in EU (Falkenstein) looks up scholar.google.com, connects to it and times how long the homepage takes to start answering. A failed check is repeated before it counts as an outage.