Live  /  SerpApi  /  Incident

SerpApi: [DuckDuckGo Search API] Performance Degradation

SerpApi · serpapi.comMinor incidentResolved2026-11-06 01:53 UTC
Public — what happened

Summary

SerpApi said its DuckDuckGo Search API was returning a high number of errors and responding more slowly than normal, starting at 17:46 UTC on 2026-11-05. The company classed the incident as minor, apologized for the inconvenience, and said it would share more once it had new information or performance steadied. The incident is marked resolved as of 01:53 on 2026-11-06, though the text provided does not state a cause.

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.