- Level
- confirmed
- Worst impact
- Major outage
- Components
- API, Search API, Search API, Images Light API, AI Mode API, News Light API, AI Overview API, Shopping Light API, Videos Light API, Forums API, Images API, Immersive Product API, Jobs API, Lens API, Local API, News API, Scholar API, Shopping API, Short Videos API, Videos API
- Regions
- us
- Down Index
- 49of 100
What to do
Check whether you use SerpApi API, Search API, Search API, Images Light API and 16 more in us. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 7d 6h it lasted.
Anything that failed between 2026-09-10 15:59 UTC and 2026-09-17 22:40 UTC may need a replay.Subscribe to SerpApi's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=serpapi works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from SerpApi 16
- investigating
We currently experience service outage across all of our APIs. https://github.com/serpapi/public-roadmap/issues/4265
provider
- investigating
The team has deployed a temporary fix to mitigate the severity of the issue. We continue working on a long-term fix.
provider
- investigating
We are continuing to investigate this issue.
provider
- identified
The issue is due to recent changes on Google's side, which are causing searches to fail or time out. Our engineers have deployed a partial mitigation that is currently restoring a portion of traffic, and continue testing additional fixes to fully resolve the issue.
provider
- monitoring
We have made several improvements - success rates and response times should be recovering. Note that there is one remaining known issue that we are still working to resolve - the location and uule parameters are not currently reliable for locations outside the US. We have implemented a fix and are testing it now. Until it goes live, please use the gl, hl, and google_domain parameters to specify non-US locations. We’ll continue monitoring performance to ensure stability. Please don't hesitate to reach out if you have any questions or experience any further issues.
provider
- monitoring
We are continuing to monitor for any further issues.
provider
- monitoring
We are continuing to monitor for any further issues.
provider
- investigating
We are experiencing higher error rates and response times again. We're actively working on the issue with the highest urgency.
provider
- identified
We've made several improvements, and are seeing signs of recovery on several of the affected APIs. We're continuing to work on further improvements to ensure stability for Google engines.
provider
- investigating
We see another performance degradation. The team is investigating and working on remediation.
provider
- investigating
We're seeing a good trend in the success rate and response time for the last few hours. We'll keep working and monitoring the status.
provider
- investigating
We are still working on improvements to restore stable performance across engines. While we're noticing recovery on many engines, we're working to ensure success rates and response times continue improving. We'll continue to provide updates as the situation progresses. Thank you again for your patience.
provider
- monitoring
We're seeing much better, more stable overall performance over the past few hours. A few of our engines are still affected, and we're working to restore good performance across the board.
provider
- monitoring
You may have noticed another increase in response times since the most recent update. This was related to an improvement we attempted. That change has since been reverted until it can be further fine-tuned. Success rates and response times are recovering. We'll follow up with further updates soon, thanks again for your patience.
provider
- monitoring
Performance has improved significantly for several engines, while others continue to experience degradation. We'll continue monitoring, and working to restore functionality to affected APIs.
provider
- resolved
Performance has remained stable for many of the APIs initially affected by this issue. For updates on engines that are still experiencing degradation, you can check the relevant Public Roadmap issue: [Google Shopping API] Performance Degradation [Google News API] Performance Degradation [Google Ads API] Performance Degradation [Google Jobs API] Degraded Performance [Google Local API] Performance Degradation [Google Scholar API] Elevated Response Times [Google Forums API] Performance Degradation Alternatively, up to date information about any ongoing incidents can be found here: https://status.serpapi.com/ Thanks again for your patience.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-4ec622f424
Is SerpApi still down?
No, this incident was resolved 2026-09-17 22:40 UTC. For SerpApi's live state, see https://down.guide/serpapi.
How long did it last?
7d 6h, from 2026-09-10 15:59 UTC to 2026-09-17 22:40 UTC, by the times SerpApi posted.
What was affected?
SerpApi named API, Search API, Search API, Images Light API and 16 more in us.
What caused it?
SerpApi hasn't published a root cause. If it does, it shows here.
Where does this come from?
SerpApi's official status page, https://status.serpapi.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.