[Bing Search API] Empty result for advanced search operators
minor- Started
- Oct 14, 1:42 AM EDT
- Resolved
- Nov 5, 8:10 PM EST
- Duration
- 547h 28m
SerpApi's updates (5)
- investigating · Oct 14, 1:42 AM EDT
We are currently investigating an issue where searches using advanced operators on the Bing Search API are returning empty results. Our team is actively looking into this, and we will share another update once we have more information. You can track the progress of this issue on our public roadmap: https://github.com/serpapi/public-roadmap/issues/2566
- identified · Oct 19, 6:42 AM EDT
Our engineers are currently exploring and working on different solutions which have shown good early response for this issue. We'll keep updating any improvements here.
- identified · Oct 26, 4:30 PM EDT
Our engineers are making progress in evaluating possible fixes, but additional testing is still underway to confirm their effectiveness. We'll provide another update when we have more information. Thank you for your patience in the meantime.
- identified · Nov 2, 7:11 AM EST
We are continuing to evaluate possible fixes for empty results on Bing Search API searches that use advanced operators. Further testing is still needed to confirm their effectiveness, so affected searches may continue to return empty results for now. We will share another update as soon as we have more information.
- resolved · Nov 5, 8:10 PM EST
Post further analysis we have observed that Bing Search API is returning results when advanced operators are used. We have identified a different issue where intermittently the search results are irrelevant or do not follow the rules provided in advanced parameters. We are further investigating this under the below incident, https://status.serpapi.com/incidents/whqvwk9d9wg5 Thanks for your patience and understanding. In case of any queries or concerns, kindly reach out to us on contact@serpapi.com.
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 168 ms, against 141 ms over the 24 hours before. SerpApi posted the incident at Oct 14, 1:42 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 ↗