Skip to content

Outage tracker / Binance

Is Binance down?

I'm having a problem

Partially degradedchecked moments ago

Binance is answering our probes, but running at least 8.8x its 7-day median from UK. The rest of the regions we check answered at their usual speed.

As of Oct 19, 2026, 6:26 PM UTC, RealUptime's checks of Binance passed in all 10 regions that returned a reading.

Front-door checks

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

our check readinglive · checked Oct 19, 2026, 6:26 PM UTC
US-East1519 msChecks passing
US-West1433 msChecks passing
Europe1460 msChecks passing
Asia-Pacific1544 msChecks passing
US-Central850 msChecks passing
Canada577 msChecks passing
UK1455 msDegraded
Southeast Asia1475 msChecks passing
Australia445 msChecks passing
South America2640 msChecks passing
their status pagetheir claim, not our reading

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

Binance response time, by region

US-East
2.1sp95 · latest
2.5s1.3s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 910ms2026-09-21 UTC: p95 873ms2026-09-22 UTC: p95 909ms2026-09-23 UTC: p95 1.1s2026-09-24 UTC: p95 1.1s2026-09-25 UTC: p95 1.0s2026-09-26 UTC: p95 911ms2026-09-27 UTC: p95 1.1s2026-09-28 UTC: p95 948ms2026-09-29 UTC: p95 979ms2026-09-30 UTC: p95 1.0s2026-10-01 UTC: p95 1.0s2026-10-02 UTC: p95 918ms2026-10-03 UTC: p95 814ms2026-10-04 UTC: p95 1.1s2026-10-05 UTC: p95 1.0s2026-10-06 UTC: p95 769ms2026-10-07 UTC: p95 836ms2026-10-08 UTC: p95 962ms2026-10-09 UTC: p95 662ms2026-10-10 UTC: p95 1.1s2026-10-11 UTC: p95 741ms2026-10-12 UTC: p95 794ms2026-10-13 UTC: p95 1.1s2026-10-14 UTC: p95 706ms2026-10-15 UTC: p95 742ms2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 1.8s2026-10-18 UTC: p95 2.0s2026-10-19 UTC: p95 2.1s
Sep 20Oct 4Oct 19
US-West
1.9sp95 · 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-09-20 UTC: p95 742ms2026-09-21 UTC: p95 769ms2026-09-22 UTC: p95 914ms2026-09-23 UTC: p95 853ms2026-09-24 UTC: p95 534ms2026-09-25 UTC: p95 628ms2026-09-26 UTC: p95 461ms2026-09-27 UTC: p95 453ms2026-09-28 UTC: p95 475ms2026-09-29 UTC: p95 450ms2026-09-30 UTC: p95 745ms2026-10-01 UTC: p95 748ms2026-10-02 UTC: p95 747ms2026-10-03 UTC: p95 789ms2026-10-04 UTC: p95 851ms2026-10-05 UTC: p95 782ms2026-10-06 UTC: p95 753ms2026-10-07 UTC: p95 972ms2026-10-08 UTC: p95 983ms2026-10-09 UTC: p95 952ms2026-10-10 UTC: p95 1.1s2026-10-11 UTC: p95 912ms2026-10-12 UTC: p95 752ms2026-10-13 UTC: p95 833ms2026-10-14 UTC: p95 875ms2026-10-15 UTC: p95 890ms2026-10-16 UTC: p95 927ms2026-10-17 UTC: p95 1.7s2026-10-18 UTC: p95 1.8s2026-10-19 UTC: p95 1.9s
Sep 20Oct 4Oct 19
Europe
1.7sp95 · 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-09-20 UTC: p95 174ms2026-09-21 UTC: p95 201ms2026-09-22 UTC: p95 233ms2026-09-23 UTC: p95 160ms2026-09-24 UTC: p95 233ms2026-09-25 UTC: p95 292ms2026-09-26 UTC: p95 268ms2026-09-27 UTC: p95 238ms2026-09-28 UTC: p95 318ms2026-09-29 UTC: p95 459ms2026-09-30 UTC: p95 774ms2026-10-01 UTC: p95 923ms2026-10-02 UTC: p95 818ms2026-10-03 UTC: p95 789ms2026-10-04 UTC: p95 863ms2026-10-05 UTC: p95 852ms2026-10-06 UTC: p95 677ms2026-10-07 UTC: p95 895ms2026-10-08 UTC: p95 719ms2026-10-09 UTC: p95 880ms2026-10-10 UTC: p95 816ms2026-10-11 UTC: p95 729ms2026-10-12 UTC: p95 905ms2026-10-13 UTC: p95 530ms2026-10-14 UTC: p95 944ms2026-10-15 UTC: p95 730ms2026-10-16 UTC: p95 650ms2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.7s
Sep 20Oct 4Oct 19
Asia-Pacific
2.5sp95 · 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-09-20 UTC: p95 853ms2026-09-21 UTC: p95 992ms2026-09-22 UTC: p95 965ms2026-09-23 UTC: p95 1.1s2026-09-24 UTC: p95 921ms2026-09-25 UTC: p95 1.1s2026-09-26 UTC: p95 1.1s2026-09-27 UTC: p95 1.0s2026-09-28 UTC: p95 1.0s2026-09-29 UTC: p95 1.1s2026-09-30 UTC: p95 1.2s2026-10-01 UTC: p95 1.2s2026-10-02 UTC: p95 1.1s2026-10-03 UTC: p95 986ms2026-10-04 UTC: p95 1.1s2026-10-05 UTC: p95 939ms2026-10-06 UTC: p95 1.0s2026-10-07 UTC: p95 1.0s2026-10-08 UTC: p95 965ms2026-10-09 UTC: p95 1.1s2026-10-10 UTC: p95 797ms2026-10-11 UTC: p95 731ms2026-10-12 UTC: p95 1.1s2026-10-13 UTC: p95 1.3s2026-10-14 UTC: p95 1.5s2026-10-15 UTC: p95 1.7s2026-10-16 UTC: p95 1.4s2026-10-17 UTC: p95 2.2s2026-10-18 UTC: p95 2.5s2026-10-19 UTC: p95 2.5s
Sep 20Oct 4Oct 19
US-Central
1.2sp95 · 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-09-20 UTC: p95 512ms2026-09-21 UTC: p95 484ms2026-09-22 UTC: p95 470ms2026-09-23 UTC: p95 533ms2026-09-24 UTC: p95 528ms2026-09-25 UTC: p95 453ms2026-09-26 UTC: p95 437ms2026-09-27 UTC: p95 389ms2026-09-28 UTC: p95 503ms2026-09-29 UTC: p95 475ms2026-09-30 UTC: p95 741ms2026-10-01 UTC: p95 590ms2026-10-02 UTC: p95 549ms2026-10-03 UTC: p95 486ms2026-10-04 UTC: p95 493ms2026-10-05 UTC: p95 501ms2026-10-06 UTC: p95 500ms2026-10-07 UTC: p95 502ms2026-10-08 UTC: p95 448ms2026-10-09 UTC: p95 456ms2026-10-10 UTC: p95 468ms2026-10-11 UTC: p95 437ms2026-10-12 UTC: p95 478ms2026-10-13 UTC: p95 609ms2026-10-14 UTC: p95 521ms2026-10-15 UTC: p95 382ms2026-10-16 UTC: p95 542ms2026-10-17 UTC: p95 972ms2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 1.2s
Sep 20Oct 4Oct 19
Canada
807msp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 541ms2026-09-21 UTC: p95 534ms2026-09-22 UTC: p95 674ms2026-09-23 UTC: p95 508ms2026-09-24 UTC: p95 768ms2026-09-25 UTC: p95 1.0s2026-09-26 UTC: p95 1.1s2026-09-27 UTC: p95 1.2s2026-09-28 UTC: p95 1.1s2026-09-29 UTC: p95 919ms2026-09-30 UTC: p95 1.3s2026-10-01 UTC: p95 1.3s2026-10-02 UTC: p95 996ms2026-10-03 UTC: p95 1.3s2026-10-04 UTC: p95 1.4s2026-10-05 UTC: p95 1.3s2026-10-06 UTC: p95 1.3s2026-10-07 UTC: p95 1.2s2026-10-08 UTC: p95 1.3s2026-10-09 UTC: p95 1.4s2026-10-10 UTC: p95 1.2s2026-10-11 UTC: p95 1.3s2026-10-12 UTC: p95 1.4s2026-10-13 UTC: p95 1.3s2026-10-14 UTC: p95 1.2s2026-10-15 UTC: p95 1.2s2026-10-16 UTC: p95 1.4s2026-10-17 UTC: p95 697ms2026-10-18 UTC: p95 801ms2026-10-19 UTC: p95 807ms
Sep 20Oct 4Oct 19
UK
1.7sp95 · 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-09-20 UTC: p95 363ms2026-09-21 UTC: p95 453ms2026-09-22 UTC: p95 451ms2026-09-23 UTC: p95 592ms2026-09-24 UTC: p95 616ms2026-09-25 UTC: p95 554ms2026-09-26 UTC: p95 528ms2026-09-27 UTC: p95 586ms2026-09-28 UTC: p95 574ms2026-09-29 UTC: p95 417ms2026-09-30 UTC: p95 670ms2026-10-01 UTC: p95 1.0s2026-10-02 UTC: p95 953ms2026-10-03 UTC: p95 950ms2026-10-04 UTC: p95 794ms2026-10-05 UTC: p95 716ms2026-10-06 UTC: p95 858ms2026-10-07 UTC: p95 521ms2026-10-08 UTC: p95 902ms2026-10-09 UTC: p95 708ms2026-10-10 UTC: p95 178ms2026-10-11 UTC: p95 160ms2026-10-12 UTC: p95 247ms2026-10-13 UTC: p95 199ms2026-10-14 UTC: p95 268ms2026-10-15 UTC: p95 246ms2026-10-16 UTC: p95 756ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.6s2026-10-19 UTC: p95 1.7s
Sep 20Oct 4Oct 19
Southeast Asia
2.3sp95 · latest
2.5s1.3s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 1.3s2026-09-21 UTC: p95 1.9s2026-09-22 UTC: p95 1.8s2026-09-23 UTC: p95 2.0s2026-09-24 UTC: p95 1.8s2026-09-25 UTC: p95 1.9s2026-09-26 UTC: p95 1.9s2026-09-27 UTC: p95 1.9s2026-09-28 UTC: p95 1.9s2026-09-29 UTC: p95 1.8s2026-09-30 UTC: p95 1.7s2026-10-01 UTC: p95 2.1s2026-10-02 UTC: p95 2.2s2026-10-03 UTC: p95 2.1s2026-10-04 UTC: p95 1.3s2026-10-05 UTC: p95 1.4s2026-10-06 UTC: p95 1.2s2026-10-07 UTC: p95 1.3s2026-10-08 UTC: p95 1.1s2026-10-09 UTC: p95 1.4s2026-10-10 UTC: p95 1.2s2026-10-11 UTC: p95 1.2s2026-10-12 UTC: p95 1.3s2026-10-13 UTC: p95 1.3s2026-10-14 UTC: p95 1.4s2026-10-15 UTC: p95 1.4s2026-10-16 UTC: p95 1.4s2026-10-17 UTC: p95 1.9s2026-10-18 UTC: p95 2.1s2026-10-19 UTC: p95 2.3s
Sep 20Oct 4Oct 19
Australia
869msp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 742ms2026-09-21 UTC: p95 752ms2026-09-22 UTC: p95 885ms2026-09-23 UTC: p95 1.2s2026-09-24 UTC: p95 1.3s2026-09-25 UTC: p95 1.3s2026-09-26 UTC: p95 1.7s2026-09-27 UTC: p95 1.6s2026-09-28 UTC: p95 1.3s2026-09-29 UTC: p95 1.5s2026-09-30 UTC: p95 1.5s2026-10-01 UTC: p95 1.5s2026-10-02 UTC: p95 1.6s2026-10-03 UTC: p95 1.5s2026-10-04 UTC: p95 1.6s2026-10-05 UTC: p95 1.5s2026-10-06 UTC: p95 1.3s2026-10-07 UTC: p95 1.6s2026-10-08 UTC: p95 1.6s2026-10-09 UTC: p95 1.4s2026-10-10 UTC: p95 1.2s2026-10-11 UTC: p95 1.2s2026-10-12 UTC: p95 1.5s2026-10-13 UTC: p95 1.9s2026-10-14 UTC: p95 1.8s2026-10-15 UTC: p95 1.8s2026-10-16 UTC: p95 1.9s2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 869ms
Sep 20Oct 4Oct 19
South America
2.8sp95 · 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-09-20 UTC: p95 1s2026-09-21 UTC: p95 939ms2026-09-22 UTC: p95 917ms2026-09-23 UTC: p95 875ms2026-09-24 UTC: p95 919ms2026-09-25 UTC: p95 1.0s2026-09-26 UTC: p95 957ms2026-09-27 UTC: p95 968ms2026-09-28 UTC: p95 957ms2026-09-29 UTC: p95 1.1s2026-09-30 UTC: p95 1.1s2026-10-01 UTC: p95 934ms2026-10-02 UTC: p95 751ms2026-10-03 UTC: p95 996ms2026-10-04 UTC: p95 1.3s2026-10-05 UTC: p95 1.5s2026-10-06 UTC: p95 1.3s2026-10-07 UTC: p95 1.3s2026-10-08 UTC: p95 1.4s2026-10-09 UTC: p95 562ms2026-10-10 UTC: p95 1.4s2026-10-11 UTC: p95 1.3s2026-10-12 UTC: p95 1.5s2026-10-13 UTC: p95 1.6s2026-10-14 UTC: p95 1.8s2026-10-15 UTC: p95 1.8s2026-10-16 UTC: p95 1.8s2026-10-17 UTC: p95 2.6s2026-10-18 UTC: p95 2.8s2026-10-19 UTC: p95 2.8s
Sep 20Oct 4Oct 19

Check your own site while you wait on Binance

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 Binance. It cannot diagnose Binance's own systems.

Get an email when our checks of Binance 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 Binance 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 Binance'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: 1519msstatus code: 202checked: Oct 19, 2026, 6:22 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Binance normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 1433msstatus code: 202checked: Oct 19, 2026, 6:22 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Binance normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Checks passinglatency: 850msstatus code: 202checked: Oct 19, 2026, 6:17 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Binance normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 577msstatus code: 202checked: Oct 19, 2026, 6:21 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Binance normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 2640msstatus code: 202checked: Oct 19, 2026, 6:11 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Binance normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    DegradedEurope, UK
    • Europe
      Checks passinglatency: 1460msstatus code: 202checked: Oct 19, 2026, 6:17 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Binance normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Degradedlatency: 1455msstatus code: 202checked: Oct 19, 2026, 6:17 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Binance 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: 1544msstatus code: 202checked: Oct 19, 2026, 6:20 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Binance normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 1475msstatus code: 202checked: Oct 19, 2026, 6:08 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Binance normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 445msstatus code: 202checked: Oct 19, 2026, 6:26 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Binance 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 Binance, 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 Binance yet, which is not evidence that nothing is wrong.

Recent probe events

No probe events on record yet for Binance.

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

We have been measuring Binance since August 22, 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 Binance covering any window you pick, with our check readings and Binance's own claim at the time, side by side.

Full check history for Binance: 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

Put this badge in your README

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

The badge shows the share of our checks that passed over the last 30 days. The window is printed on it, so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

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

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

How our checks compare with Binance's stated SLA

At or above your target

Our checks of Binance 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 Binance'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

primary
https://www.binance.com/en

What our check can and cannot see

A pass means the service's front door answered, even though it asks automated visitors to prove they are people. It does not show what a real visitor would see, because our check cannot get past that challenge.

Host checked: www.binance.com

RealUptime is not affiliated with Binance; the name identifies what we checked, and nothing here speaks for Binance's own team. We send a single web request to Binance from 10 regions on our own schedule and time the response. We do not see inside Binance's systems, do not use an account or real transaction, and are not the same signal Binance's own team has access to. Treat this as one external data point, not a verdict. What we check for Binance is its front door only: a passing check means the endpoints above answered, not that the underlying product or account features work. Read the full methodology.