Is Bing / Microsoft Search APIs down?
Bing / Microsoft Search APIs is up
Right now
No. Bing / Microsoft Search APIs Search API answers UpButler's independent probe; no machine-readable official status.
No official machine-readable status
For agents
proceed
Proceed.
GET upbutler.com/status/bing/status.agent.json
MCP: upstream_status {"service":"bing"}
Bing web search results and the Microsoft search APIs. Microsoft publishes no status feed for Bing; UpButler probes it.
What Bing / Microsoft Search APIs says
Bing / Microsoft Search APIs publishes no status page; only the independent probe is shown.
Their site: bing.comWhat UpButler measured
Search API is answeringHTTP 401 · 240 ms
One request without credentials to api.bing.microsoft.com every two minutes, from eu-central (one location, not a global view). An answer (the expected "not authenticated") shows the edge, TLS and routing work. It does not prove that authenticated calls succeed.
Checked · up since 2026-10-10 06:08 UTC
Bing / Microsoft Search APIs incidents, last 90 days
Without a machine-readable source there is no incident history to show. Bing / Microsoft Search APIs keeps its own at bing.com.
Get alerted when Bing / Microsoft Search APIs goes down
No account. One email when our probe cannot reach Bing / Microsoft Search APIs for several minutes, one when it can again. You confirm the address first, and every email has a one-click unsubscribe.
On UpButler? Add Bing / Microsoft Search APIs as a dependency to route it to Slack, Teams or a webhook.
Status badge
Show Bing / Microsoft Search APIs's current status in a README or an internal wiki. It updates by itself.
[](https://upbutler.com/status/bing)Tell your outage from Bing / Microsoft Search APIs's
Declare that your project depends on Bing / Microsoft Search APIs. When one of your monitors fails while Bing / Microsoft Search APIs has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.
npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.
# upbutler.yaml
dependencies:
- bingcurl -s https://upbutler.com/status/bing/status.agent.json{
"schema": "upbutler.upstream-status/v1",
"service": "bing",
"verdict": "proceed",
"status": "operational",
"reason": "Bing / Microsoft Search APIs Search API answers UpButler's independent probe; no machine-readable official status",
"retryAfterSec": null,
"incident": null,
"probe": {
"state": "up",
"statusCode": 401
}
}Questions
- Is Bing / Microsoft Search APIs down right now?
- No. As of 2026-10-10 07:17 UTC, Bing / Microsoft Search APIs is up. This page reads the status again every 2 minutes.
- Where does this status come from?
- Bing / Microsoft Search APIs publishes no status page; only the independent probe is shown.
- What does UpButler's own Bing / Microsoft Search APIs check prove?
- Every two minutes UpButler sends one request without credentials to the Bing / Microsoft Search APIs Search API (api.bing.microsoft.com) from eu-central. Any answer from the edge, usually HTTP 401, shows that DNS, TLS and routing work from there. It does not prove that authenticated requests succeed, and it is one location, not a global view. It is most useful when it fails before their status page changes; the page then says so.
- How can my agent or app check Bing / Microsoft Search APIs status?
- Fetch https://upbutler.com/status/bing/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"bing"}, on https://upbutler.com/mcp/public.
- How do I know whether an outage is mine or Bing / Microsoft Search APIs's?
- Add "bing" to the dependencies of your UpButler workspace. When one of your monitors fails while Bing / Microsoft Search APIs has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.
Also check
UpButler is not affiliated with Bing / Microsoft Search APIs. Status and incident text belong to Bing / Microsoft Search APIs and are read from their public status source; the probe result is UpButler's own measurement.