Live / SerpApi / Incident
SerpApi: Yelp Performance Degradation
SerpApi · serpapi.comMinor incidentResolved2026-11-09 15:52 UTC
Public — what happened
Summary
SerpApi said its Yelp Search API and Yelp Place API began producing a high number of errors on 2026-11-02 at 17:45 UTC, and it labeled the incident minor. After several days of investigation, the company said on 2026-11-05 that it had found a solution and was working to put it in place. On 2026-11-07 it said a fix was in place for the Yelp Search API while problems with the Yelp Place API were still being worked on. The incident was marked resolved on 2026-11-09 at 15:52.
Affected
Search API, Place API
Timeline
- Started — 2026-11-02 17:45 UTC
- Investigating — 2026-11-02 17:45 UTC (2 updates)
- Identified — 2026-11-05 07:57 UTC (2 updates)
- Resolved — 2026-11-09 15:52 UTC · 7 days after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach SerpApi against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for SerpApi: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the SerpApi report →
More from SerpApi
Covered in The Squid’s Ink, Week 46, 2026, our weekly internet health report.