Engine stats - bing

Engine name

Scores

Result count

Response time

Reliability

bing

0.5

1.1

	Total	HTTP
Median	1.1	1.1
P80	1.8	1.8
P95	2.7	2.7

100

Errors and exceptions

Exception	searx.exceptions.SearxEngineAPIException	Percentage	0
Parameter	Expected results to start at 1, but got results starting at 59
Filename	searx/engines/bing.py:191
Function	response
Code	raise SearxEngineAPIException(msg)

Message	timeout	Percentage	0
Filename	searx/search/processors/abstract.py:100
Function	handle_exception
Code	count_error(self.engine_name, exception_or_message)

Exception	searx.exceptions.SearxEngineAPIException	Percentage	0
Parameter	Expected results to start at 1, but got results starting at 78
Filename	searx/engines/bing.py:191
Function	response
Code	raise SearxEngineAPIException(msg)

Exception	searx.exceptions.SearxEngineAPIException	Percentage	0
Parameter	Expected results to start at 1, but got results starting at 3
Filename	searx/engines/bing.py:191
Function	response
Code	raise SearxEngineAPIException(msg)

Exception	searx.exceptions.SearxEngineAPIException	Percentage	0
Parameter	Expected results to start at 21, but got results starting at 11
Filename	searx/engines/bing.py:191
Function	response
Code	raise SearxEngineAPIException(msg)

Exception	searx.exceptions.SearxEngineAPIException	Percentage	0
Parameter	Expected results to start at 21, but got results starting at 1
Filename	searx/engines/bing.py:191
Function	response
Code	raise SearxEngineAPIException(msg)

Exception	searx.exceptions.SearxEngineAPIException	Percentage	0
Parameter	Expected results to start at 11, but got results starting at 1
Filename	searx/engines/bing.py:191
Function	response
Code	raise SearxEngineAPIException(msg)

**Version of SearXNG, commit number if you are using on master branch and stipulate if you forked SearXNG**
Repository: https://github.com/searxng/searxng
Branch: master
Version: 2025.7.16+62fac1c

**How did you install SearXNG?**

**What happened?**

**How To Reproduce**

**Expected behavior**

**Screenshots & Logs**

**Additional context**

**Technical report**

Error
  * Error: searx.exceptions.SearxEngineAPIException
  * Percentage: 0
  * Parameters: `('Expected results to start at 1, but got results starting at 59',)`
  * File name: `searx/engines/bing.py:191`
  * Function: `response`
  * Code: `raise SearxEngineAPIException(msg)`

Error
  * Error: timeout
  * Percentage: 0
  * Parameters: `()`
  * File name: `searx/search/processors/abstract.py:100`
  * Function: `handle_exception`
  * Code: `count_error(self.engine_name, exception_or_message)`

Error
  * Error: searx.exceptions.SearxEngineAPIException
  * Percentage: 0
  * Parameters: `('Expected results to start at 1, but got results starting at 78',)`
  * File name: `searx/engines/bing.py:191`
  * Function: `response`
  * Code: `raise SearxEngineAPIException(msg)`

Error
  * Error: searx.exceptions.SearxEngineAPIException
  * Percentage: 0
  * Parameters: `('Expected results to start at 1, but got results starting at 3',)`
  * File name: `searx/engines/bing.py:191`
  * Function: `response`
  * Code: `raise SearxEngineAPIException(msg)`

Error
  * Error: searx.exceptions.SearxEngineAPIException
  * Percentage: 0
  * Parameters: `('Expected results to start at 21, but got results starting at 11',)`
  * File name: `searx/engines/bing.py:191`
  * Function: `response`
  * Code: `raise SearxEngineAPIException(msg)`

Error
  * Error: searx.exceptions.SearxEngineAPIException
  * Percentage: 0
  * Parameters: `('Expected results to start at 21, but got results starting at 1',)`
  * File name: `searx/engines/bing.py:191`
  * Function: `response`
  * Code: `raise SearxEngineAPIException(msg)`

Error
  * Error: searx.exceptions.SearxEngineAPIException
  * Percentage: 0
  * Parameters: `('Expected results to start at 11, but got results starting at 1',)`
  * File name: `searx/engines/bing.py:191`
  * Function: `response`
  * Code: `raise SearxEngineAPIException(msg)`

Start submitting a new issue on GitHub

Please check for existing bugs about this engine on GitHub

I confirm there is no existing bug about the issue I encounter

If this is a public instance, please specify the URL in the bug report