S
Outage recap · SerpApi

SerpApi outage — October 1, 2026

On October 1, 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] [Google Light API] Performance Degradation

major
Started
Oct 1, 5:15 AM EDT
Resolved
Oct 7, 5:48 PM EDT
Duration
156h 32m

SerpApi's updates (7)

  1. investigating · Oct 1, 5:15 AM EDT

    We're seeing a sharp increase in error rates for our Google Search API. We're currently investigating the issue and will follow up with updates. https://github.com/serpapi/public-roadmap/issues/4376

  2. monitoring · Oct 1, 9:35 PM EDT

    Performance has stabilized now and we continue to monitor this API.

  3. investigating · Oct 2, 3:24 AM EDT

    We're seeing elevated error rates and response times. We're investigating.

  4. investigating · Oct 6, 5:08 AM EDT

    The team continues their efforst on addressing the issue and finding solution as soon as possible.

  5. investigating · Oct 7, 5:44 PM EDT

    We are continuing to investigate this issue.

  6. investigating · Oct 7, 5:46 PM EDT

    We're continuing to work toward a solution. Since the issue now affects other APIs, the status can now be tracked here: https://status.serpapi.com/incidents/5pybr6gr3dq4 This is incident will be closed to prevent duplicate notifications. Thanks for your continued patience.

  7. resolved · Oct 7, 5:48 PM EDT

    Closed as duplicate

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 134 ms over the 24 hours before. SerpApi posted the incident at Oct 1, 5:15 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 ↗

[Yandex Search API] Increased Error Rate

critical
Started
Oct 1, 6:00 PM EDT
Resolved
Oct 1, 11:12 PM EDT
Duration
5h 12m

SerpApi's updates (3)

  1. investigating · Oct 1, 6:00 PM EDT

    We are currently investigating an increased error rate affecting the Yandex Search API: https://github.com/serpapi/public-roadmap/issues/4034

  2. investigating · Oct 1, 10:04 PM EDT

    Performance has further degraded and now all requests to this API are failing. We are actively investigating this and will be sharing further updates.

  3. resolved · Oct 1, 11:12 PM EDT

    We have implemented a fix and now the Yandex API service is operational again. We apologize for the inconvenience caused here and thank you for your patience. Feel free to reach out to contact@serpapi.com in case of any queries.

What our checks recorded

We checked SerpApi 62 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 147 ms, against 136 ms over the 24 hours before. SerpApi posted the incident at Oct 1, 6:00 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.