It's a simple topic where the subject says it all. For the past 24 to 48 hours, when running a search utilising the "site:" keyword, Bing almost always returns an error. At random intervals, it will return the expected results, after which running the same search continues to return those results (i.e. it's akin to a cached experience) but eventually, it's reverting to the broken behaviour. I feel like there may be a regional-/locale-specific component to this as when trying the same search from another environment, it's working more often than not, but I'm not clear on whether we can do much in the way of diagnosis for Bing. Has anyone else had issues with searches using the "site:" keyword? Cheers,Lain

LainRobertson Closing this out as a likely service issue as the "site:" keyword is reliably working again. Cheers,Lain

Advanced searches using the "site" keyword are not reliably working.

2 Replies

LainRobertson

Silver Contributor

Apr 20, 2023

Dumping some support information from "edge://version" and the developer tools (F12).

Edge version information

Microsoft Edge	112.0.1722.48 (Official build) (64-bit)
Revision	d0924f8b9cb98fefc118ffd258a343383cf7cecc
Chromium version	112.0.5615.121
Operating system	Windows 10 Version 20H2 (Build 19042.2846)
JavaScript	V8 11.2.13.9
User agent	Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/112.0.0.0 Safari/537.36 Edg/112.0.1722.48

Developer tool information

Link address

https://s.bingparachute.com/search?q=site%3Amicrosoft.com%20excel&mkt=en-au&muid=06647437518666ED05DF66CE50456720&impressionguid=B79ECC18FEA14722AD891C8FE8D4FEAC&traceid=6440fbea95764fad903c0a3b2f6c4301&refid=Ref%20A%3A%20F8A9C8CC147740EF864870AE3379176F%20Ref%20B%3A%20PER311000106049%20Ref%20C%3A%202023-04-20T08%3A46%3A34Z

Request headers

GET /search?q=site%3Amicrosoft.com%20excel&mkt=en-au&muid=06647437518666ED05DF66CE50456720&impressionguid=B79ECC18FEA14722AD891C8FE8D4FEAC&traceid=6440fbea95764fad903c0a3b2f6c4301&refid=Ref%20A%3A%20F8A9C8CC147740EF864870AE3379176F%20Ref%20B%3A%20PER311000106049%20Ref%20C%3A%202023-04-20T08%3A46%3A34Z HTTP/1.1
Accept: */*
Accept-Encoding: gzip, deflate, br
Accept-Language: en-AU,en;q=0.9
Connection: keep-alive
Host: s.bingparachute.com
Origin: https://www.bing.com
Referer: https://www.bing.com/
Sec-Fetch-Dest: empty
Sec-Fetch-Mode: cors
Sec-Fetch-Site: cross-site
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/112.0.0.0 Safari/537.36 Edg/112.0.1722.48
sec-ch-ua: "Chromium";v="112", "Microsoft Edge";v="112", "Not:A-Brand";v="99"
sec-ch-ua-mobile: ?0
sec-ch-ua-platform: "Windows"

Response headers

HTTP/1.1 404 Not Found
Accept-Ranges: bytes
Content-Length: 10
Server: AkamaiNetStorage
Date: Thu, 20 Apr 2023 08:46:34 GMT
Connection: keep-alive
Access-Control-Max-Age: 86400
Access-Control-Allow-Credentials: false
Access-Control-Allow-Headers: *
Access-Control-Allow-Methods: GET,POST
Access-Control-Allow-Origin: *
report-to: {"group":"network-errors","max_age":604800,"endpoints":[{"url":"https://aefd.nelreports.net/api/report?cat=bingparachute"}]}
nel: {"report_to":"network-errors","max_age":604800,"success_fraction":0.01,"failure_fraction":1.0}

Stack trace

pfetch @ https://www.bing.com/search?q=site%3Amicrosoft.com+excel&qs=n&form=QBRE&sp=-1&lq=0&pq=site%3Amicrosoft.com+excel&sc=0-24&sk=&cvid=CECE5D00328E4B379A34C120D09A720E&ghsh=0&ghacc=0&ghpl=&rdr=1&rdrig=D65DA2890BB54128945CE1C450BF8CFC:45
loadCachedPage @ https://www.bing.com/search?q=site%3Amicrosoft.com+excel&qs=n&form=QBRE&sp=-1&lq=0&pq=site%3Amicrosoft.com+excel&sc=0-24&sk=&cvid=CECE5D00328E4B379A34C120D09A720E&ghsh=0&ghacc=0&ghpl=&rdr=1&rdrig=D65DA2890BB54128945CE1C450BF8CFC:45
(anonymous) @ https://www.bing.com/search?q=site%3Amicrosoft.com+excel&qs=n&form=QBRE&sp=-1&lq=0&pq=site%3Amicrosoft.com+excel&sc=0-24&sk=&cvid=CECE5D00328E4B379A34C120D09A720E&ghsh=0&ghacc=0&ghpl=&rdr=1&rdrig=D65DA2890BB54128945CE1C450BF8CFC:45

Cheers,

Lain

LainRobertson
Silver Contributor
Apr 23, 2023
LainRobertson

Closing this out as a likely service issue as the "site:" keyword is reliably working again.

Cheers,
Lain

Forum Discussion