Performance Degradation across APIs
major- Started
- Jun 27, 3:20 PM EDT
- Resolved
- Jul 1, 7:51 PM EDT
- Duration
- 100h 31m
SerpApi's updates (8)
- investigating · Jun 27, 3:20 PM EDT
We're currently experiencing longer response times and lower success rates across APIs. We're investigating the issue. Thank you for your patience in the meantime.
- investigating · Jun 27, 3:22 PM EDT
We are continuing to investigate this issue.
- monitoring · Jun 27, 5:13 PM EDT
We've recovered from the brief outage. We'll continue monitoring the performance.
- identified · Jun 28, 4:56 AM EDT
We're seeing the issue is back. Our engineer is working on a fix.
- monitoring · Jun 28, 5:50 PM EDT
The success rate is back to normal. We'll continue monitoring the performance.
- identified · Jun 29, 4:59 PM EDT
This issue has returned. We are working to restore response times and success rates to expected levels while continuing to investigate and develop a longer-term fix.
- identified · Jun 30, 5:16 PM EDT
Success rates have returned to expected levels, but response times remain elevated. Our team is continuing to work on restoring response times to normal as soon as possible. We will provide another update as soon as possible.
- resolved · Jul 1, 7:51 PM EDT
The incident appears to be resolved, success rates and response times have returned to normal. We'll continue monitoring to ensure stabillity. Thanks for your patience, and we apologize for the impact on your business and workflows.
What our checks recorded
We checked SerpApi 170 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. SerpApi posted the incident at Jun 27, 3:20 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 ↗