Skip to content

Outage tracker / Bing

Is Bing down?

I'm having a problem

Checks passingchecked 6 minutes ago

Our checks of Bing pass from all 10 regions we check.

As of Nov 5, 2026, 2:36 PM UTC, RealUptime's checks of Bing passed in all 10 regions that returned a reading.

Front-door and live API checks

Our checks of Bing did not fail from two or more distant regions in the 89 days we have checked it (since Aug 8, 2026). This does not show Bing works for users.

our check readinglive · checked Nov 5, 2026, 2:36 PM UTC
US-East1175 msChecks passing
US-West1688 msChecks passing
Europe695 msChecks passing
Asia-Pacific1253 msChecks passing
US-Central652 msChecks passing
Canada1207 msChecks passing
UK324 msChecks passing
Southeast Asia649 msChecks passing
Australia1172 msChecks passing
South America1175 msChecks passing
their status pagetheir claim, not our reading

Bing publishes no status feed we can read, so the only reading here is our check reading on the left.

Bing response time, by region

US-East
1.8sp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 352ms2026-10-08 UTC: p95 498ms2026-10-09 UTC: p95 404ms2026-10-10 UTC: p95 404ms2026-10-11 UTC: p95 479ms2026-10-12 UTC: p95 371ms2026-10-13 UTC: p95 447ms2026-10-14 UTC: p95 368ms2026-10-15 UTC: p95 339ms2026-10-16 UTC: p95 407ms2026-10-17 UTC: p95 514ms2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 1.3s2026-10-21 UTC: p95 1.4s2026-10-22 UTC: p95 1.3s2026-10-23 UTC: p95 1.3s2026-10-24 UTC: p95 1.4s2026-10-25 UTC: p95 1.3s2026-10-26 UTC: p95 1.8s2026-10-27 UTC: p95 1.3s2026-10-28 UTC: p95 1.3s2026-10-29 UTC: p95 1.3s2026-10-30 UTC: p95 1.4s2026-10-31 UTC: p95 1.5s2026-11-01 UTC: p95 1.5s2026-11-02 UTC: p95 1.8s2026-11-03 UTC: p95 1.4s2026-11-04 UTC: p95 1.3s2026-11-05 UTC: p95 1.8s
Oct 7Oct 21Nov 5
US-West
1.4sp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 483ms2026-10-08 UTC: p95 373ms2026-10-09 UTC: p95 498ms2026-10-10 UTC: p95 365ms2026-10-11 UTC: p95 310ms2026-10-12 UTC: p95 384ms2026-10-13 UTC: p95 514ms2026-10-14 UTC: p95 343ms2026-10-15 UTC: p95 414ms2026-10-16 UTC: p95 413ms2026-10-17 UTC: p95 606ms2026-10-18 UTC: p95 792ms2026-10-19 UTC: p95 774ms2026-10-20 UTC: p95 783ms2026-10-21 UTC: p95 905ms2026-10-22 UTC: p95 1.4s2026-10-23 UTC: p95 1.3s2026-10-24 UTC: p95 1.4s2026-10-25 UTC: p95 1.4s2026-10-26 UTC: p95 1.8s2026-10-27 UTC: p95 1.4s2026-10-28 UTC: p95 1.4s2026-10-29 UTC: p95 1.4s2026-10-30 UTC: p95 1.5s2026-10-31 UTC: p95 1.4s2026-11-01 UTC: p95 1.5s2026-11-02 UTC: p95 1.7s2026-11-03 UTC: p95 1.5s2026-11-04 UTC: p95 1.8s2026-11-05 UTC: p95 1.4s
Oct 7Oct 21Nov 5
Europe
1.2sp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 421ms2026-10-08 UTC: p95 312ms2026-10-09 UTC: p95 416ms2026-10-10 UTC: p95 350ms2026-10-11 UTC: p95 278ms2026-10-12 UTC: p95 468ms2026-10-13 UTC: p95 303ms2026-10-14 UTC: p95 263ms2026-10-15 UTC: p95 408ms2026-10-16 UTC: p95 227ms2026-10-17 UTC: p95 652ms2026-10-18 UTC: p95 758ms2026-10-19 UTC: p95 975ms2026-10-20 UTC: p95 955ms2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 1.1s2026-10-23 UTC: p95 915ms2026-10-24 UTC: p95 992ms2026-10-25 UTC: p95 960ms2026-10-26 UTC: p95 1.1s2026-10-27 UTC: p95 1.0s2026-10-28 UTC: p95 1.1s2026-10-29 UTC: p95 1.2s2026-10-30 UTC: p95 1.1s2026-10-31 UTC: p95 1.1s2026-11-01 UTC: p95 1.0s2026-11-02 UTC: p95 1.2s2026-11-03 UTC: p95 1.0s2026-11-04 UTC: p95 890ms2026-11-05 UTC: p95 1.2s
Oct 7Oct 21Nov 5
Asia-Pacific
2.2sp95 · latest
5s2.5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 903ms2026-10-08 UTC: p95 1.6s2026-10-09 UTC: p95 640ms2026-10-10 UTC: p95 712ms2026-10-11 UTC: p95 821ms2026-10-12 UTC: p95 897ms2026-10-13 UTC: p95 737ms2026-10-14 UTC: p95 1.0s2026-10-15 UTC: p95 715ms2026-10-16 UTC: p95 1.3s2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.8s2026-10-19 UTC: p95 1.5s2026-10-20 UTC: p95 2.1s2026-10-21 UTC: p95 3.0s2026-10-22 UTC: p95 2.5s2026-10-23 UTC: p95 2.5s2026-10-24 UTC: p95 1.6s2026-10-25 UTC: p95 1.5s2026-10-26 UTC: p95 3.0s2026-10-27 UTC: p95 3.9s2026-10-28 UTC: p95 2.3s2026-10-29 UTC: p95 3.6s2026-10-30 UTC: p95 2.3s2026-10-31 UTC: p95 2.3s2026-11-01 UTC: p95 2.3s2026-11-02 UTC: p95 3.4s2026-11-03 UTC: p95 1.9s2026-11-04 UTC: p95 3.2s2026-11-05 UTC: p95 2.2s
Oct 7Oct 21Nov 5
US-Central
722msp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 465ms2026-10-08 UTC: p95 571ms2026-10-09 UTC: p95 563ms2026-10-10 UTC: p95 405ms2026-10-11 UTC: p95 404ms2026-10-12 UTC: p95 533ms2026-10-13 UTC: p95 470ms2026-10-14 UTC: p95 445ms2026-10-15 UTC: p95 607ms2026-10-16 UTC: p95 507ms2026-10-17 UTC: p95 453ms2026-10-18 UTC: p95 544ms2026-10-19 UTC: p95 631ms2026-10-20 UTC: p95 726ms2026-10-21 UTC: p95 859ms2026-10-22 UTC: p95 991ms2026-10-23 UTC: p95 843ms2026-10-24 UTC: p95 614ms2026-10-25 UTC: p95 749ms2026-10-26 UTC: p95 737ms2026-10-27 UTC: p95 1.1s2026-10-28 UTC: p95 1.1s2026-10-29 UTC: p95 986ms2026-10-30 UTC: p95 1.2s2026-10-31 UTC: p95 1.1s2026-11-01 UTC: p95 711ms2026-11-02 UTC: p95 1.5s2026-11-03 UTC: p95 785ms2026-11-04 UTC: p95 889ms2026-11-05 UTC: p95 722ms
Oct 7Oct 21Nov 5
Canada
1.0sp95 · latest
2.5s1.3s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 507ms2026-10-08 UTC: p95 638ms2026-10-09 UTC: p95 466ms2026-10-10 UTC: p95 589ms2026-10-11 UTC: p95 737ms2026-10-12 UTC: p95 331ms2026-10-13 UTC: p95 554ms2026-10-14 UTC: p95 386ms2026-10-15 UTC: p95 442ms2026-10-16 UTC: p95 406ms2026-10-17 UTC: p95 397ms2026-10-18 UTC: p95 269ms2026-10-19 UTC: p95 298ms2026-10-20 UTC: p95 351ms2026-10-21 UTC: p95 300ms2026-10-22 UTC: p95 334ms2026-10-23 UTC: p95 366ms2026-10-24 UTC: p95 325ms2026-10-25 UTC: p95 336ms2026-10-26 UTC: p95 303ms2026-10-27 UTC: p95 414ms2026-10-28 UTC: p95 773ms2026-10-29 UTC: p95 2.0s2026-10-30 UTC: p95 2.0s2026-10-31 UTC: p95 1.8s2026-11-01 UTC: p95 1.8s2026-11-02 UTC: p95 1.8s2026-11-03 UTC: p95 892ms2026-11-04 UTC: p95 1.1s2026-11-05 UTC: p95 1.0s
Oct 7Oct 21Nov 5
UK
570msp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 206ms2026-10-08 UTC: p95 251ms2026-10-09 UTC: p95 329ms2026-10-10 UTC: p95 359ms2026-10-11 UTC: p95 448ms2026-10-12 UTC: p95 275ms2026-10-13 UTC: p95 312ms2026-10-14 UTC: p95 375ms2026-10-15 UTC: p95 199ms2026-10-16 UTC: p95 221ms2026-10-17 UTC: p95 207ms2026-10-18 UTC: p95 208ms2026-10-19 UTC: p95 308ms2026-10-20 UTC: p95 386ms2026-10-21 UTC: p95 236ms2026-10-22 UTC: p95 267ms2026-10-23 UTC: p95 215ms2026-10-24 UTC: p95 264ms2026-10-25 UTC: p95 250ms2026-10-26 UTC: p95 330ms2026-10-27 UTC: p95 344ms2026-10-28 UTC: p95 583ms2026-10-29 UTC: p95 535ms2026-10-30 UTC: p95 498ms2026-10-31 UTC: p95 645ms2026-11-01 UTC: p95 1.2s2026-11-02 UTC: p95 513ms2026-11-03 UTC: p95 681ms2026-11-04 UTC: p95 710ms2026-11-05 UTC: p95 570ms
Oct 7Oct 21Nov 5
Southeast Asia
1.6sp95 · latest
5s2.5s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.0s2026-10-08 UTC: p95 677ms2026-10-09 UTC: p95 650ms2026-10-10 UTC: p95 811ms2026-10-11 UTC: p95 878ms2026-10-12 UTC: p95 937ms2026-10-13 UTC: p95 762ms2026-10-14 UTC: p95 1.6s2026-10-15 UTC: p95 491ms2026-10-16 UTC: p95 1.9s2026-10-17 UTC: p95 1.2s2026-10-18 UTC: p95 444ms2026-10-19 UTC: p95 740ms2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 2.7s2026-10-22 UTC: p95 2.3s2026-10-23 UTC: p95 1.3s2026-10-24 UTC: p95 3.4s2026-10-25 UTC: p95 2.9s2026-10-26 UTC: p95 1.0s2026-10-27 UTC: p95 1.4s2026-10-28 UTC: p95 2.1s2026-10-29 UTC: p95 2.1s2026-10-30 UTC: p95 1.4s2026-10-31 UTC: p95 1.7s2026-11-01 UTC: p95 1.4s2026-11-02 UTC: p95 1.8s2026-11-03 UTC: p95 1.1s2026-11-04 UTC: p95 2.8s2026-11-05 UTC: p95 1.6s
Oct 7Oct 21Nov 5
Australia
2.2sp95 · latest
5s2.5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.3s2026-10-08 UTC: p95 1.2s2026-10-09 UTC: p95 996ms2026-10-10 UTC: p95 1.6s2026-10-11 UTC: p95 1.6s2026-10-12 UTC: p95 2.4s2026-10-13 UTC: p95 1.2s2026-10-14 UTC: p95 1.6s2026-10-15 UTC: p95 1.8s2026-10-16 UTC: p95 1.5s2026-10-17 UTC: p95 1.6s2026-10-18 UTC: p95 1.9s2026-10-19 UTC: p95 2.5s2026-10-20 UTC: p95 2.0s2026-10-21 UTC: p95 2.2s2026-10-22 UTC: p95 2.1s2026-10-23 UTC: p95 1.7s2026-10-24 UTC: p95 2.5s2026-10-25 UTC: p95 1.8s2026-10-26 UTC: p95 2.4s2026-10-27 UTC: p95 2.4s2026-10-28 UTC: p95 2.8s2026-10-29 UTC: p95 3.2s2026-10-30 UTC: p95 2.2s2026-10-31 UTC: p95 2.1s2026-11-01 UTC: p95 1.8s2026-11-02 UTC: p95 2.1s2026-11-03 UTC: p95 2.3s2026-11-04 UTC: p95 2.4s2026-11-05 UTC: p95 2.2s
Oct 7Oct 21Nov 5
South America
1.7sp95 · latest
5s2.5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 865ms2026-10-08 UTC: p95 1.1s2026-10-09 UTC: p95 1.1s2026-10-10 UTC: p95 1.1s2026-10-11 UTC: p95 860ms2026-10-12 UTC: p95 1.0s2026-10-13 UTC: p95 1.4s2026-10-14 UTC: p95 1.0s2026-10-15 UTC: p95 1.3s2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 1.0s2026-10-18 UTC: p95 807ms2026-10-19 UTC: p95 830ms2026-10-20 UTC: p95 2.2s2026-10-21 UTC: p95 2.9s2026-10-22 UTC: p95 2.7s2026-10-23 UTC: p95 3.7s2026-10-24 UTC: p95 2.7s2026-10-25 UTC: p95 2.5s2026-10-26 UTC: p95 2.6s2026-10-27 UTC: p95 2.5s2026-10-28 UTC: p95 2.0s2026-10-29 UTC: p95 2.1s2026-10-30 UTC: p95 2.6s2026-10-31 UTC: p95 2.2s2026-11-01 UTC: p95 2.4s2026-11-02 UTC: p95 2.1s2026-11-03 UTC: p95 2.3s2026-11-04 UTC: p95 1.7s2026-11-05 UTC: p95 1.7s
Oct 7Oct 21Nov 5

Check your own site while you wait on Bing

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Bing. It cannot diagnose Bing's own systems.

What we measured, function by function

Bing answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing

Get an email when our checks of Bing fail from two or more distant regions, and again when they pass

Get an email when our checks change

We will email you when our checks of Bing fail from two or more distant regions, and again when they pass. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when our checks fail from two or more distant regions, one when they pass, and a one-click unsubscribe in every one. We do not send anything else to this address.

This is our own reading from outside. It is not Bing's official status.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 1175msstatus code: 200checked: Nov 5, 2026, 2:26 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Bing normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 1688msstatus code: 200checked: Nov 5, 2026, 2:14 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Bing normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Checks passinglatency: 652msstatus code: 200checked: Nov 5, 2026, 2:05 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Bing normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 1207msstatus code: 200checked: Nov 5, 2026, 2:03 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Bing normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 1175msstatus code: 200checked: Nov 5, 2026, 2:27 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Bing normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 695msstatus code: 200checked: Nov 5, 2026, 2:07 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Bing normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Checks passinglatency: 324msstatus code: 200checked: Nov 5, 2026, 1:51 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Bing normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 1253msstatus code: 200checked: Nov 5, 2026, 1:57 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Bing normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 649msstatus code: 200checked: Nov 5, 2026, 2:36 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Bing normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 1172msstatus code: 200checked: Nov 5, 2026, 2:15 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Bing normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Bing, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Bing yet, which is not evidence that nothing is wrong.

Recent probe events

No probe events on record yet for Bing.

check entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Bing since August 8, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Bing covering any window you pick, with our check readings and Bing's own claim at the time, side by side.

Full check history for Bing: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter

Put this badge in your README

Bing uptime by RealUptime's checksLive, from this page's own readings.
[![Bing uptime by RealUptime's checks](https://realuptime.io/outages/bing/badge.svg?days=30)](https://realuptime.io/outages/bing)
<a href="https://realuptime.io/outages/bing"><img src="https://realuptime.io/outages/bing/badge.svg?days=30" alt="Bing uptime by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

To cite this page: RealUptime, "Is Bing down?", https://realuptime.io/outages/bing. The readings change with every check, so give the date you read them.

How our checks compare with Bing's stated SLA

At or above your target

Our checks of Bing failed for none over the last 30 days, which is 100% uptime by our checks. A 99.9% target allows 43 minutes over that period.

Our checks show no gap in this period. That does not rule out one you saw.

These figures come from our own checks of one public endpoint per service. They are not the service's real uptime. This is computed from our own checks, not from Bing's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional: live API
https://api.bing.com/osjson.aspx?query=test
secondary
https://www.bing.com/

What our check can and cannot see

A pass means a public route of the service's API answered our request normally. We do not check what it returned, so it does not show that the data is right, that sign-in works or that the rest of the product works.

Host checked: api.bing.com

RealUptime is not affiliated with Bing; the name identifies what we checked, and nothing here speaks for Bing's own team. We send a single web request to Bing from 10 regions on our own schedule and time the response. We do not see inside Bing's systems, do not use an account or real transaction, and are not the same signal Bing's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Bing is a real functional API call (marked “functional” above), not just a landing page, so a passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.