- Level
- confirmed
- Worst impact
- Degraded
- Components
- Search API, Search API
- Down Index
- 20of 100
What to do
Check whether you use SerpApi Search API, Search API. 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 3h 10m it lasted.
Anything that failed between 2026-04-09 18:17 UTC and 2026-04-09 21:27 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 2
- monitoring
We experienced a performance degradation starting around 5:00 AM PST, primarily affecting our Google Search and Google Search Light APIs. Latency peaked around 7:00 AM PST. Our team is continuing to apply optimizations to ensure latency returns to expected levels. Response times have been steadily improving since then. We're continuing to monitor this.
provider
- resolved
The issue have been resolved. Response times have returned to normal levels. We’re very sorry for the impact this issue caused and appreciate your patience while we worked to resolve it.
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-626fb0f444
Is SerpApi still down?
No, this incident was resolved 2026-04-09 21:27 UTC. For SerpApi's live state, see https://down.guide/serpapi.
How long did it last?
3h 10m, from 2026-04-09 18:17 UTC to 2026-04-09 21:27 UTC, by the times SerpApi posted.
What was affected?
SerpApi named Search API, Search API.
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.