S
Outage recap · SerpApi

SerpApi outage — October 13, 2026

On October 13, 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.

[Brave AI Mode API] API calls fail for all queries

critical
Started
Oct 13, 4:26 AM EDT
Resolved
Oct 13, 6:36 AM EDT
Duration
2h 10m

SerpApi's updates (2)

  1. investigating · Oct 13, 4:26 AM EDT

    Brave AI Mode API has been fully down since Saturday 10/10. The team is investigating the issue.

  2. resolved · Oct 13, 6:36 AM EDT

    We deployed a fix and the API is back up.

What our checks recorded

We checked SerpApi 26 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 130 ms, against 131 ms over the 24 hours before. SerpApi posted the incident at Oct 13, 4:26 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 returning irrelevant/poisoned results

major
Started
Oct 13, 11:09 AM EDT
Resolved
—
Duration
not marked resolved

SerpApi's updates (8)

  1. investigating · Oct 13, 11:09 AM EDT

    We've been observing Google returning irrelevant/poisoned results for the past few weeks. It appears to have escalated recently. The team is looking into it urgently and working on potential fixes. https://github.com/serpapi/public-roadmap/issues/3781

  2. investigating · Oct 14, 9:53 AM EDT

    Our engineering team has deployed an update that should reduce the number of instances in which poisoned results are returned instead of valid output. We're still working on fully addressing the issue. Thank you for understanding.

  3. investigating · Oct 19, 6:38 PM EDT

    Google Shopping API is also now affected by this issue, you can see the related issue here: https://github.com/serpapi/public-roadmap/issues/4475 We’ll continue working on a complete solution for all APIs and will provide further updates as more information becomes available. Thank you for your understanding.

  4. investigating · Oct 26, 7:47 AM EDT

    The current benchmarks our engineers have run show that about 6% of the results are returned as poisoned. The team continues to make further updates to resolve the issue. Thank you all for your patience.

  5. investigating · Oct 28, 1:05 PM EDT

    We have released a fix for the Google Shopping API. You can see the related issue here: https://github.com/serpapi/public-roadmap/issues/4475. Now you should be able to see relevant results again. If Google rolls out another update affecting this, please let us know. Thanks for your patience.

  6. investigating · Nov 2, 2:34 AM EST

    We have observed irrelevant or fewer results on Google Shopping API in some cases and are further investigating it. GitHub issue: https://github.com/serpapi/public-roadmap/issues/4475 has been re-opened. We are actively working on solving this and will be sharing further updates as more information becomes available. Thanks for your patience and understanding.

  7. investigating · Nov 9, 11:49 AM EST

    We are continuing to investigate and resolve this issue affecting our Google Search and Google Shopping APIs. We'll notify you as soon as there is an update. Thanks for your patience.

  8. investigating · Nov 16, 3:23 PM EST

    Our Engineering team continues to work on improving the reliability of Google Search results. While we've made progress in reducing irrelevant results, the issue hasn't been fully resolved yet. In the meantime, if you only need organic search results, we recommend trying udm=web, which may help reduce the occurrence of irrelevant results. 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 152 ms, against 150 ms over the 24 hours before. SerpApi posted the incident at Oct 13, 11:09 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.