AdInsight - Could not resolve host

Question

AdInsight - Could not resolve host

Eric Nagel 35

I'm making a call to GetAutoApplyOptInStatus and this was working yesterday, but doesn't work today. The error I'm getting is:

SOAP-ERROR: Parsing WSDL: Couldn't load from 'https://adinsight.api.bingads.microsoft.com/Api/Advertiser/AdInsight/v13/AdInsightService.svc?singleWsdl' :  
failed to load external entity "https://adinsight.api.bingads.microsoft.com/Api/Advertiser/AdInsight/v13/AdInsightService.svc?singleWsdl"

I checked it with curl:

curl -I "https://adinsight.api.bingads.microsoft.com/Api/Advertiser/AdInsight/v13/AdInsightService.svc?singleWsdl"
curl: (6) Could not resolve host: adinsight.api.bingads.microsoft.com

But the Status page shows "Ad Insight API" as "Good"

What's going on? Is the status page manually updated, and nobody has realized yet that the Ad Insight API is down?

Monkedia Analytics 15 Reputation points

2025-06-12T17:36:49.9966667+00:00

We are also experiencing the same issue of not being able to resolve the ___domain adinsight.api.bingads.microsoft.com. Status page shows no issues and chat support could only open a ticket and get back in the next 5 to 7 business days.
Marwood Tech 20 Reputation points

2025-06-13T07:52:34.83+00:00

We also have the same problem.

Tried pinging two API hostnames. Ad Insight API hostname doesn't resolve whereas the Bulk API hostname does:

ping adinsight.api.bingads.microsoft.com

ping: cannot resolve adinsight.api.bingads.microsoft.com: Unknown host

whereas

ping bulk.api.bingads.microsoft.com

PING bulk-api-bingads.trafficmanager.net (168.61.0.48): 56 data bytes

64 bytes from 168.61.0.48: icmp_seq=0 ttl=105 time=147.543 ms

64 bytes from 168.61.0.48: icmp_seq=1 ttl=105 time=147.785 ms

64 bytes from 168.61.0.48: icmp_seq=2 ttl=105 time=151.806 ms

64 bytes from 168.61.0.48: icmp_seq=3 ttl=105 time=147.255 ms

Surely somebody at Microsoft Ads has noticed that their Ad Insight API is down?
Navneet Bhardwaj 5 Reputation points

2025-06-13T12:02:37.8+00:00

we also facing the same issue. it is showing the below error. i guess
Fault Code: WSDL Fault String: SOAP-ERROR: Parsing WSDL: Couldn't load from 'https://adinsight.api.bingads.microsoft.com/Api/Advertiser/AdInsight/v13/AdInsightService.svc?singleWsdl' : failed to load external entity
CFJ 0 Reputation points

2025-06-13T12:19:55.7666667+00:00

We are experiencing inability to utlize the adinsight endpoint as well. Today is the second day in a row that we are getting an error when attempting to access the adinsight endpoint and getting the following:

There was no endpoint listening at https://adinsight.api.bingads.microsoft.com/Api/Advertiser/AdInsight/V13/AdInsightService.svc that could accept the message.
pratik patel 0 Reputation points

2025-06-13T12:55:27.21+00:00

I am also facing the same issue.

https://adinsight.api.bingads.microsoft.com/Api/Advertiser/AdInsight/v13/AdInsightService.svc

It's not loading from Bing server.

Jor 0

Same here.

 SOAP-ERROR: Parsing WSDL: Couldn't load from 'https://adinsight.api.bingads.microsoft.com/Api/Advertiser/AdInsight/v13/AdInsightService.svc?singleWsdl' : failed to load external entity "https://adinsight.api.bingads.microsoft.com/Api/Advertiser/AdInsight/v13/AdInsightService.svc?singleWsdl"

Second day in a row.

1 answer

Your answer

Monkedia Analytics 15 Reputation points

2025-06-12T17:36:49.9966667+00:00

We are also experiencing the same issue of not being able to resolve the ___domain adinsight.api.bingads.microsoft.com. Status page shows no issues and chat support could only open a ticket and get back in the next 5 to 7 business days.
Marwood Tech 20 Reputation points

2025-06-13T07:52:34.83+00:00

We also have the same problem.

Tried pinging two API hostnames. Ad Insight API hostname doesn't resolve whereas the Bulk API hostname does:

ping adinsight.api.bingads.microsoft.com

ping: cannot resolve adinsight.api.bingads.microsoft.com: Unknown host

whereas

ping bulk.api.bingads.microsoft.com

PING bulk-api-bingads.trafficmanager.net (168.61.0.48): 56 data bytes

64 bytes from 168.61.0.48: icmp_seq=0 ttl=105 time=147.543 ms

64 bytes from 168.61.0.48: icmp_seq=1 ttl=105 time=147.785 ms

64 bytes from 168.61.0.48: icmp_seq=2 ttl=105 time=151.806 ms

64 bytes from 168.61.0.48: icmp_seq=3 ttl=105 time=147.255 ms

Surely somebody at Microsoft Ads has noticed that their Ad Insight API is down?
Navneet Bhardwaj 5 Reputation points

2025-06-13T12:02:37.8+00:00

we also facing the same issue. it is showing the below error. i guess
Fault Code: WSDL Fault String: SOAP-ERROR: Parsing WSDL: Couldn't load from 'https://adinsight.api.bingads.microsoft.com/Api/Advertiser/AdInsight/v13/AdInsightService.svc?singleWsdl' : failed to load external entity
CFJ 0 Reputation points

2025-06-13T12:19:55.7666667+00:00

We are experiencing inability to utlize the adinsight endpoint as well. Today is the second day in a row that we are getting an error when attempting to access the adinsight endpoint and getting the following:

There was no endpoint listening at https://adinsight.api.bingads.microsoft.com/Api/Advertiser/AdInsight/V13/AdInsightService.svc that could accept the message.
pratik patel 0 Reputation points

2025-06-13T12:55:27.21+00:00

I am also facing the same issue.

https://adinsight.api.bingads.microsoft.com/Api/Advertiser/AdInsight/v13/AdInsightService.svc

It's not loading from Bing server.
Jor 0 Reputation points

2025-06-13T13:06:06.5433333+00:00

Same here.

SOAP-ERROR: Parsing WSDL: Couldn't load from 'https://adinsight.api.bingads.microsoft.com/Api/Advertiser/AdInsight/v13/AdInsightService.svc?singleWsdl' : failed to load external entity "https://adinsight.api.bingads.microsoft.com/Api/Advertiser/AdInsight/v13/AdInsightService.svc?singleWsdl"

Second day in a row.

Answer 1

JP 0

We're experiencing the same issue as above.

The ___domain

adinsight.api.bingads.microsoft.com

as referenced: https://learn.microsoft.com/en-us/advertising/guides/web-service-addresses?view=bingads-13

cannot be globally resolved:

https://dnschecker.org/#A/adinsight.api.bingads.microsoft.com

Share via

AdInsight - Could not resolve host

1 answer

Your answer