Live  /  SerpApi  /  Incident

SerpApi: [Google Search API] Requests timing out while using tbm=nws with advanced parameters

SerpApi · serpapi.comMajor incidentResolved2026-10-19 01:56 UTC
Public — what happened

Summary

SerpApi said that Google Search API requests using the news setting (tbm=nws) were timing out, and it first reported the problem on 2026-08-26 at 14:30 UTC. On 2026-10-12 the company said it had found that searches combining that setting with the site: operator were no longer supported, and it suggested using its Google News API or leaving out site:. By 2026-10-16 it said such searches returned a clear error message rather than timing out, and that it was still working on failures involving other advanced search terms such as AND and OR. SerpApi marked the incident resolved on 2026-10-19 at 01:56.

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

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

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