The issue appears to have been resolved over the weekend. Tested a couple of API calls to the Ad Insights API, and they worked.
Furthermore, the following HEAD request:
curl -I "https://adinsight.api.bingads.microsoft.com/Api/Advertiser/AdInsight/v13/AdInsightService.svc?singleWsdl"
now returns this
HTTP/2 400
content-length: 0
server: Microsoft-IIS/10.0
x-starttick: 638856624705320265
x-serverduration: 2ms
x-endtick: 638856624705340405
x-powered-by: ASP.NET
strict-transport-security: max-age=31536000; includeSubDomains; preload
date: Mon, 16 Jun 2025 09:21:09 GMT