Management Portal recovered
Timeline · 1 update
- resolved Jun 15, 2026, 08:15 AM UTC
Management Portal recovered
Serper had 18 outages in the last 2 years totaling 196h 40m of downtime — averaging 0.7 incidents per month.
There were 18 Serper outages since January 16, 2025 totaling 196h 40m of downtime. Each is summarised below — incident details, duration, and resolution information.
Management Portal recovered
We're experiencing issues at the moment. We're actively looking into it.
Latency and success rate have recovered again. We'll keep on monitoring closely.
API recovered
Google just made a change to Google Images impacting a subset of /images queries. We're looking into it.
Performance is back to normal again.
We’re observing spikes in timeouts on Google Search again, resulting in increased latency for a subset of queries.
Latency for the affected queries has come back down and things appear to have recovered.
It seems Google isn't showing Google Maps reviews for non-logged-in users currently. We'll be monitoring this to see if it's a temporary or permanent change.
We've deployed an update to the reviews endpoint. It now pulls reviews from Google Places/Local Business profiles.
We've been getting reports that for a subset of queries users have been getting organic results full of videos. We're looking into it.
It seems Google has resolved the issue
We’ve observed an increase in queries returning 0 organic results. This currently affects a small subset of requests. We’re monitoring this closely.
It seems Google has resolved the issue
We’re observing intermittent timeout spikes from google.com, impacting latency for a subset of queries. We’re looking into it.
It seems to have stabilized again.
We’re still seeing sporadic spikes in 502 errors from google.com due to infrastructure issues on Google’s end: https://downdetector.com/status/google/
Seems to be recovered for now.
We’re still seeing sporadic spikes in 502 errors from google.com due to infrastructure issues on Google’s end: https://downdetector.com/status/google/
Seems to be recovering.
We're observing intermittent 502 errors for google.com
It seems google.com is stable again.
We’re currently experiencing a partial outage and are investigating the issue. Performance may be degraded.
The API has stabilized, and we’re continuing to monitor it closely.
All endpoints are currently experiencing issues. We're looking into it.
The issues appear to have recovered. We're still investigating the root cause, but we observed a surge in timeouts from Google during the incident.
Some parts of our service are currently experiencing higher than normal latency and an increased number of 429 (rate limit) errors. We're actively looking into it. We're actively investigating the issue and working to restore normal performance as quickly as possible.
Service performance has returned to normal. We encountered unexpected scaling issues with our cloud provider, which led to increased latency and a higher number of 429 (rate limit) errors. We've provisioned additional resources to mitigate the impact and are continuing to monitor closely. Thank you for your patience.
We’re currently experiencing an issue affecting analytics data, usage insights, and dashboards. Our team is investigating and working to restore full functionality as soon as possible. Core services are unaffected and continue to operate normally.
Analytics and dashboard functionality has been fully restored and is now operating normally. Please note that some search requests and queries from the past hour may not have been captured in usage insights. Thank you for your patience and understanding.
We're currently experiencing an outage of our search api.
The API is stable again. The recent disruption was caused by Google's enhanced anti-bot measures, which affected our service. We've implemented the necessary adjustments to restore full functionality and are actively monitoring to ensure continued stability. Thank you for your patience! If you encounter any further issues, please don't hesitate to reach out.
We are experiencing another outage at the moment and our team is actively investigating the problem.
We've successfully implemented a more stable solution and confirmed that all API endpoints are operating normally again. We'll continue to monitor the API performance closely to ensure stability. Thank you for your patience while we resolved these issues.