S
Outage recap · SerpApi

SerpApi outage — November 5, 2026

On November 5, 2026, SerpApi had 3 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.

[DuckDuckGo Search API] Performance Degradation

minor
Started
Nov 5, 12:46 PM EST
Resolved
Nov 5, 8:53 PM EST
Duration
8h 7m

SerpApi's updates (2)

  1. investigating · Nov 5, 12:46 PM EST

    Our DuckDuckGo Search API is currently experiencing a high level of errors and increased response time. We’re very sorry for the inconvenience and will share another update once we have more information or performance has stabilized.

  2. resolved · Nov 5, 8:53 PM EST

    We have implemented a fix post which DuckDuckGo Search API is operational now. Apologies for the inconvenience caused due to this incident. In case of any queries or concerns, kindly reach out to contact@serpapi.com and we would be happy to assist you.

What our checks recorded

We checked SerpApi 97 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 174 ms, against 159 ms over the 24 hours before. SerpApi posted the incident at Nov 5, 12:46 PM EST.

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

Irrelevant/poisoned search results returned intermittently

minor
Started
Nov 5, 8:06 PM EST
Resolved
—
Duration
not marked resolved

SerpApi's updates (5)

  1. investigating · Nov 5, 8:06 PM EST

    We have been observing Bing return irrelevant/poisoned search results intermittently over the last few weeks. Our team is working on fixing this on priority. Apologies for the inconvenience caused due to this. We will be sharing further updates as more information becomes available.

  2. identified · Nov 6, 5:12 PM EST

    We have deployed a fix for basic Bing Search API queries. Advanced queries using `site:`, `filetype:`, or `OR` remain affected and may still return irrelevant results. We are continuing to work on these queries and will share further updates as they become available.

  3. investigating · Nov 9, 11:00 AM EST

    Even though we recently deployed a fix for basic queries, it's still possible to get irrelevant results. We're sorry for the difficulties. Our team is continuing to work on this issue. Thanks for your patience in the meantime.

  4. investigating · Nov 9, 9:28 PM EST

    Our engineer is currently looking into this issue. Here is the GitHub issue for reference: https://github.com/serpapi/public-roadmap/issues/4565

  5. investigating · Nov 16, 3:22 PM EST

    Our Engineering team continues to work on improving the reliability of Bing results. While we've made progress in reducing irrelevant results, the issue hasn't been fully resolved yet. We're continuing to monitor the situation and work toward a more permanent solution. Thank you for your patience!

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 140 ms, against 173 ms over the 24 hours before. SerpApi posted the incident at Nov 5, 8:06 PM EST.

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

[Google Trends Trending Now API] All requests failing

minor
Started
Nov 5, 11:49 PM EST
Resolved
Nov 6, 5:17 PM EST
Duration
17h 29m

SerpApi's updates (2)

  1. identified · Nov 5, 11:49 PM EST

    Google Trends Trending Now API requests are failing with the error "Failed to retrieve the data". We have identified a solution and are currently reviewing it before deployment. Apologies for the inconvenience caused. We will be sharing an update as soon as this is fixed.

  2. resolved · Nov 6, 5:17 PM EST

    We have deployed a fix for the Google Trends Trending Now API. Requests are now retrieving data successfully, and this incident is resolved. Thank you for your patience.

What our checks recorded

We checked SerpApi 210 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 165 ms, against 178 ms over the 24 hours before. SerpApi posted the incident at Nov 5, 11:49 PM EST.

Updates are SerpApi's own words from its status page (status: resolved); 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.