S
Outage recap · SerpApi

SerpApi outage — August 26, 2026

On August 26, 2026, SerpApi had 2 reported incidents on SerpApi's official status page. Below is what was reported — impact, timing, and the AI services the same upstream outage could affect.

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

major
Started
Aug 26, 10:30 AM EDT
Resolved
Oct 18, 9:56 PM EDT
Duration
1283h 26m

SerpApi's updates (5)

  1. investigating · Aug 26, 10:30 AM EDT

    Google searches with the tbm=nws parameter are currently timing out. We're investigating the issue and will follow up with updates. https://github.com/serpapi/public-roadmap/issues/4185

  2. investigating · Sep 19, 7:33 PM EDT

    We're continuing to investigate this issue. We'll keep you updated as soon as we have any progress or new information to share.

  3. identified · Oct 12, 4:49 AM EDT

    We're working on implementing a fix. The team noticed that the advanced inline site: operator is no longer supported in the Google Search API when using the tbm=nws flag. We recommend switching to our Google News API (https://serpapi.com/google-news-api) or dropping the site: parameter from nws searches. We'll follow up as soon as we have additional updates.

  4. identified · Oct 16, 5:00 PM EDT

    As mentioned earlier, Google doesn't serve the News tab (tbm=nws) for site: queries to signed-out users anymore. We have updated our documentation to reflect this: https://serpapi.com/search-api#api-parameters-search-query-q Those searches now result in an appropriate error message instead of timing out. You can specify example.com instead of site:example.com in your query as a workaround, or use the Google News API. We are still working on addressing requests failing with queries containing other advanced parameters such as AND and OR.

  5. resolved · Oct 18, 9:56 PM EDT

    Google searches using tbm=nws along with advanced parameters are now working normally. Note that Google no longer supports the site: operator for tbm=nws searches by signed-out users. Requests that use this combination will return an error message. Alternate solution is to use Google News API or other News APIs such as Bing News API, DuckDuckGo API. Separately, some requests with advanced parameters (with or without tbm=nws) are timing out. We are tracking that here: https://status.serpapi.com/incidents/pts4x92phsq8, and updates will be posted on that page. We appreciate your patience. If you have questions or need help, kindly reach out to us on contact@serpapi.com.

What our checks recorded

We checked SerpApi 576 times from SerpApi's start time to its resolution, once every five minutes. Every one of them reached SerpApi's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 196 ms, against 236 ms over the 24 hours before. SerpApi posted the incident at Aug 26, 10:30 AM EDT.

Updates are SerpApi's own words from its status page (status: resolved); we never add an inferred cause. The vendor's incident page ↗

Searches with advanced operators time out intermittently

major
Started
Aug 26, 10:33 AM EDT
Resolved
—
Duration
not marked resolved

SerpApi's updates (10)

  1. identified · Aug 26, 10:33 AM EDT

    We've been experiencing issues with Google Search API executing very slowly or timing out entirely when advanced search operators are used in query. We've identified the issue and are currently working on a fix. https://github.com/serpapi/public-roadmap/issues/4080

  2. identified · Aug 29, 3:51 PM EDT

    Queries with advanced search operators may also be returning an HTTP 500 error: https://github.com/serpapi/public-roadmap/issues/4213 We're continuing to work toward a fix. Thank you for your patience in the meantime.

  3. identified · Sep 19, 7:31 PM EDT

    We're continuing to work on a fix for this issue. We'll let you know once it's implemented.

  4. monitoring · Sep 21, 4:30 PM EDT

    We have implemented a fix to resolve this issue. We are continuing to monitor closely.

  5. investigating · Sep 22, 8:56 AM EDT

    We're seeing higher error rates on advanced searches again. We're investigating.

  6. investigating · Oct 12, 4:50 AM EDT

    We are continuing our work on the issue. The team has tested multiple approaches so far, but none has proved to be a long-term solution. We'll get back with additional updates as soon as possible. Thank you for your patience, and apologies for the disruption.

  7. investigating · Oct 15, 11:29 AM EDT

    We're continuing to work on a fix for this issue. We'll reach out with additional updates as soon as possible.

  8. investigating · Oct 26, 4:24 PM EDT

    Our engineering team is still working to resolve this issue. We apologize for the continued disruption and will share updates as progress is made.

  9. investigating · Nov 2, 7:12 AM EST

    Our engineering team is continuing to work on Google Search API searches that use advanced operators and run slowly or time out. We do not have a confirmed fix yet, and affected searches may still time out intermittently. We apologize for the continued disruption and will share more information as soon as we have it.

  10. investigating · Nov 9, 11:14 AM EST

    We are still working to resolve this issue. We're sorry again for the difficulties. We'll notify you as soon as there is an update. Thanks for your patience in the meantime.

What our checks recorded

We checked SerpApi 576 times from SerpApi's start time to its last update, once every five minutes. Every one of them reached SerpApi's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 196 ms, against 235 ms over the 24 hours before. SerpApi posted the incident at Aug 26, 10:33 AM EDT.

Updates are SerpApi's own words from its status page (status: investigating); we never add an inferred cause. The vendor's incident page ↗

AIDownCheck is not affiliated with SerpApi. This recap summarizes incidents published on SerpApi's official status page.