Bing Search API ERROR: 503, message='Service Unavailable'

sogary 20 Reputation points
2025-01-10T02:26:07.88+00:00

Dear Support Team,

I have been experiencing continuous errors since January 8, 2025 (2025.01.08).

The error message is '503, Service Unavailable', and most of the API queries are failing.

I verified that my API key is within the quota limits (QPS), so it does not appear to be a quota issue.

Below is the error log for your reference. I am using Squid Proxy as the forward proxy server. Could you please check what might be causing this issue?

Additionally, the proxy server is using an internal IP address (http://xx.yy.zz.ww)

Error Log:

  • URL: https://api.bing.microsoft.com/v7.0/search
  • Status: 503
  • Message: 'Service Unavailable'
  • Proxy Address: http://xx.yy.zz.ww
  • Query Parameters:
    • q: "Headcount index using Excel INDEX function"
    • mkt: "en-US"
    • safeSearch: "Strict"
    • count: 6

Additionally, I would like to provide specific details about the implementation. I'm making the call using an instance of ClientSession from the aiohttp library in Python.

Thank you for your support.

Bing Web Search
Bing Web Search
A Bing service that gives you enhanced search details from billions of web documents.
170 questions
{count} votes

Accepted answer
  1. Saideep Anchuri 1,285 Reputation points Microsoft Vendor
    2025-01-10T05:24:05.7333333+00:00

    Hi sogary

    Welcome to Microsoft Q&A Forum, thank you for posting your query here!

    Yes, there are ongoing issues on eastus2 region. Posting the update from Azure portal service health page for reference.

    last updated at 03:48 UTC on 10 January 2025

    Impact Statement:

    we noticed a partial impact to some of the Azure Services in East US2 due to a configuration change in a regional networking service. The configuration change caused inconsistent service state. This could have resulted in intermittent Virtual machine connectivity issues or failures in allocating resources or communicating with resources in the region. The services impacted include Azure Databricks, Azure Container Apps, Azure Function Apps, Azure App Service, SQL Managed Instances, Azure Data Factory, Azure Container Instances, PowerBI, VMSS, PostgreSQL flexible servers etc. Customers using resources with Private Endpoint NSG communicating with other services would also be impacted.

    Current Status: To avoid any further impact, we are validating the fix on one of the partitions, and once that is confirmed, the mitigation will be applied to the other unhealthy partitions as well. We do not have an ETA available at this time, but we expect to be able to share more details on our progress in the next update. We continue to advise customers to execute Disaster Recovery to expedite recovery of their impacted services. Customers that have already failed out of the region should not fail back until this incident is fully mitigated. The next update will be provided in 1 hour or as events warrant.

    Could check in other available regions aside east us 2.

    Kindly refer below link: https://azure.status.microsoft/en-us/status

    Hope this helps. Do let us know if you any further queries.


    If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

    Thank You.


0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.