Starting at 2:06 AM PST on May 15th, 2017, Bing Ads starting reporting problems with their APIs.
We noticed problems with Bing Ads Reporting through the API, although normal performance reports did run correctly in the Bing Ads Interface.
If you’re using a reporting platform like Supermetrics, you will also be unable to download the Daily Bing Performance Reports (weekly and monthly seems resolved now). The error message for daily Bing Ads Supermetrics reports is still “Error: No data found”.
Worse yet, Bing reported that performance reports might be missing account level data. That means if you’re using automated bidding platforms like Kenshoo or Marin, you might be seeing bidding problems as a result of this outage.
If you’re going to submit new campaigns through a bulk API upload, you might want to hold off until this is resolved.
We reached out to Bing and will update this page when we hear back.
In the meantime, you can check the Bing API status here for updates.
Some customers using Bing Ads Editor or Bulk API services may experience errors when downloading accounts
Some users of the Bulk API and/or Bing Ads Editor may notice that account downloads are failing with either “Bing Ads is experiencing problems at this time. Please try again later” (in BAE) or “InternalError” (Bulk API). Our engineering teams are aware of this issue and are actively working to mitigate. We apologize for the inconvenience. Thank you
7:00 PM, 5/15
Engineering has resolved the issue and BAE can now synchronize accounts.
3:03 PM, 5/15
Our engineering team has identified the root cause and is currently working to mitigate this issue. Thank you for your patience on this.
2:06 AM, May 15 (Pacific Daylight Time)
Starting on May 15th 2017 at 11AM UTC+1, users monitoring advertiser performance data through the UI, API or via scheduled reports may find that not all selected accounts will be returned when running across multiple accounts.
3:56 PM, 5/15
The issue is now resolved. Users monitoring data via API or UI are advised to rerun reports that span May 12 to 15, 2017, as data will now display correctly. We appreciate your patience and apologize for any inconvenience this may have caused.
4:00 AM, May 15 (Pacific Daylight Time)