Skip to main content
SerpApi

Brief service disruption

Degraded Lasted 0m · started · SerpApi's page

Level
confirmed
Worst impact
Degraded
Components
API, Website
Down Index
8of 100

What to do

  • Check whether you use SerpApi API, Website. 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 0m it lasted.

    Anything that failed between 2026-05-31 07:24 UTC and 2026-05-31 07:24 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 1

  1. resolved

    We've experienced a brief service disruption between ~6-7 AM UTC on Sunday, May 31st. This might have resulted in valid searches returning 522/525 errors. We're still investigating the issue in depth, but the observations suggest our servers may have been temporarily overloaded. The issue is now resolved. Our sincerest apologies for the inconvenience and trouble caused by the issue.

    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-d497c40f5f

Is SerpApi still down?

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

How long did it last?

0m, from 2026-05-31 07:24 UTC to 2026-05-31 07:24 UTC, by the times SerpApi posted.

What was affected?

SerpApi named API, Website.

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.