S
Outage recap · SerpApi

SerpApi outage — September 17, 2026

On September 17, 2026, SerpApi had 4 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 Local API] Performance Degradation

major
Started
Sep 17, 6:05 PM EDT
Resolved
Sep 26, 9:03 PM EDT
Duration
218h 58m

SerpApi's updates (4)

  1. investigating · Sep 17, 6:05 PM EDT

    We are currently investigating long response times for Google Local API searches. A Public Roadmap issue can be found here: https://github.com/serpapi/public-roadmap/issues/4306

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

    We're continuing to investigate this issue.

  3. monitoring · Sep 26, 7:20 PM EDT

    Our team has deployed changes to address the performance degradation affecting Google Local API, and we are seeing success rates and response times return to normal. We are continuing to monitor closely.

  4. resolved · Sep 26, 9:03 PM EDT

    The issue affecting the Google Local API has been resolved. We’re very sorry for any disruption and appreciate your patience while we worked to resolve this issue.

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 152 ms, against 144 ms over the 24 hours before. SerpApi posted the incident at Sep 17, 6:05 PM EDT.

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

[Google News API] Performance Degradation

major
Started
Sep 17, 6:09 PM EDT
Resolved
Sep 23, 2:07 PM EDT
Duration
139h 58m

SerpApi's updates (4)

  1. investigating · Sep 17, 6:09 PM EDT

    We are currently investigating elevated response times and decreased success rates for the Google News API. You can view the Public Roadmap issue here: https://github.com/serpapi/public-roadmap/issues/4307

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

    We're continuing to investigate this issue.

  3. monitoring · Sep 22, 8:37 AM EDT

    A fix has been implemented and we are monitoring.

  4. resolved · Sep 23, 2:07 PM EDT

    Performance has remained stable. This is resolved.

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 152 ms, against 144 ms over the 24 hours before. SerpApi posted the incident at Sep 17, 6:09 PM EDT.

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

[Google Shopping API] Performance Degradation

major
Started
Sep 17, 6:12 PM EDT
Resolved
Sep 23, 2:06 PM EDT
Duration
139h 55m

SerpApi's updates (4)

  1. investigating · Sep 17, 6:12 PM EDT

    We are currently investigating elevated response times and decreased success rates for the Google Shopping API. The Public Roadmap issue documenting this can be found here: https://github.com/serpapi/public-roadmap/issues/4308

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

    We're continuing to investigate this issue.

  3. monitoring · Sep 22, 8:45 AM EDT

    A fix has been implemented and we are monitoring.

  4. resolved · Sep 23, 2:06 PM EDT

    Performance has remained stable. This is resolved.

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 152 ms, against 144 ms over the 24 hours before. SerpApi posted the incident at Sep 17, 6:12 PM EDT.

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

[Google Scholar API] Elevated Response Times

major
Started
Sep 17, 6:21 PM EDT
Resolved
Sep 21, 6:36 PM EDT
Duration
96h 15m

SerpApi's updates (4)

  1. investigating · Sep 17, 6:21 PM EDT

    We're currently seeing longer response times for Google Scholar API queries. You can find the Public Roadmap issue for this here: https://github.com/serpapi/public-roadmap/issues/4309

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

    We're continuing to investigate this issue.

  3. monitoring · Sep 20, 4:32 PM EDT

    We’ve deployed a fix and are seeing response times decrease. We’ll continue to monitor closely to ensure performance remains stable. If you continue to experience high response times with the Google Scholar API, please reach out to us at contact@serpapi.com.

  4. resolved · Sep 21, 6:36 PM EDT

    Response times have stayed low. This incident is resolved. Please feel free to reach out if you are still facing high response times or errors with Google Scholar API.

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 152 ms, against 145 ms over the 24 hours before. SerpApi posted the incident at Sep 17, 6:21 PM EDT.

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.