- Level
- confirmed
- Worst impact
- Degraded
- Components
- Search API
- Down Index
- 21of 100
What to do
Check whether you use SerpApi 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 4h 36m it lasted.
Anything that failed between 2026-03-30 18:24 UTC and 2026-03-30 23:00 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
- identified
Response times are currently longer for the Google Search API due to a temporary fix we have in place for a high priority issue. We apologize for the inconvenience, and are actively working toward a stable solution without the added latency. Thanks for your patience in the meantime.
provider
- resolved
Thank you for your patience - Google Search API response times should now have returned to what's expected.
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-cf37775ad6
Is SerpApi still down?
No, this incident was resolved 2026-03-30 23:00 UTC. For SerpApi's live state, see https://down.guide/serpapi.
How long did it last?
4h 36m, from 2026-03-30 18:24 UTC to 2026-03-30 23:00 UTC, by the times SerpApi posted.
What was affected?
SerpApi named 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.