Live  /  SerpApi  /  Incident

SerpApi: Irrelevant/poisoned search results returned intermittently

SerpApi · serpapi.comMinor incidentinvestigating2026-11-10 02:28 UTC
Public — what happened

Summary

SerpApi said its Bing search results were intermittently returning irrelevant or "poisoned" results, which it had been seeing for several weeks before posting on 2026-11-06 at 01:06 UTC. Later that day it said it had deployed a fix for basic Bing queries, but advanced queries using site:, filetype:, or OR were still affected. On 2026-11-09 the company said irrelevant results were still possible even for basic queries, and on 2026-11-10 it said an engineer was looking into the problem. The incident is not marked resolved.

Affected

Search API

As listed on SerpApi’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach SerpApi against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for SerpApi: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the SerpApi report →

More from SerpApi

Covered in The Squid’s Ink, Week 46, 2026, our weekly internet health report.

The full archive is on the SerpApi status & history page.

Related: SerpApi status & history. SquidGrid is not affiliated with SerpApi.