Skip to main content
SerpApi

Performance Degradation

Degraded Lasted 4h 24m · started · SerpApi's page

Level
confirmed
Worst impact
Degraded
Components
API
Down Index
21of 100

What to do

  • Check whether you use SerpApi 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 24m it lasted.

    Anything that failed between 2026-05-15 23:23 UTC and 2026-05-16 03:47 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

  1. identified

    We're currently experiencing longer response times and lower success rates across APIs. Our engineers have identified the source of the problem and we are working on a solution.

    provider

  2. resolved

    This incident has been resolved.

    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-1f9f72846c

Is SerpApi still down?

No, this incident was resolved 2026-05-16 03:47 UTC. For SerpApi's live state, see https://down.guide/serpapi.

How long did it last?

4h 24m, from 2026-05-15 23:23 UTC to 2026-05-16 03:47 UTC, by the times SerpApi posted.

What was affected?

SerpApi named 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.