Skip to main content
SerpApi

[Google Trends API] Performance degradation

Major outage Lasted 11d 23h · started · SerpApi's page

Level
confirmed
Worst impact
Major outage
Components
Trends API
Down Index
45of 100

What to do

  • Check whether you use SerpApi Trends 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 11d 23h it lasted.

    Anything that failed between 2026-07-29 11:06 UTC and 2026-08-10 10:06 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 3

  1. investigating

    We are currently investigating elevated response times for our Google Trends API. https://github.com/serpapi/public-roadmap/issues/4086

    provider

  2. monitoring

    The performance is stable now. We'll continue monitoring.

    provider

  3. resolved

    The issue has been resolved and the performance is stable for the past week.

    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-7782d80dcb

Is SerpApi still down?

No, this incident was resolved 2026-08-10 10:06 UTC. For SerpApi's live state, see https://down.guide/serpapi.

How long did it last?

11d 23h, from 2026-07-29 11:06 UTC to 2026-08-10 10:06 UTC, by the times SerpApi posted.

What was affected?

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