Skip to content

Outage tracker / Binance

Is Binance down?

I'm having a problem

Operationalchecked 1 minute ago

We reached Binance from all 10 regions we check.

As of Oct 5, 2026, 8:15 PM UTC, Binance answered RealUptime's probes in all 10 regions that returned a reading.

Reachability verified

No outage recorded in the 44 days we have measured Binance (since Aug 22, 2026).

our independent probeslive · checked Oct 5, 2026, 8:15 PM UTC
US-East561 msOperational
US-West514 msOperational
Europe90 msOperational
Asia-Pacific142 msOperational
US-Central131 msOperational
Canada416 msOperational
UK105 msOperational
Southeast Asia1001 msOperational
Australia1372 msOperational
South America1107 msOperational
their status pagetheir claim, not our reading

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

Binance response time, by region

US-East
1.0sp95 · 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-09-06 UTC: p95 891ms2026-09-07 UTC: p95 804ms2026-09-08 UTC: p95 878ms2026-09-09 UTC: p95 831ms2026-09-10 UTC: p95 882ms2026-09-11 UTC: p95 814ms2026-09-12 UTC: p95 839ms2026-09-13 UTC: p95 880ms2026-09-14 UTC: p95 905ms2026-09-15 UTC: p95 863ms2026-09-16 UTC: p95 1.1s2026-09-17 UTC: p95 995ms2026-09-18 UTC: p95 984ms2026-09-19 UTC: p95 1.1s2026-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.0s
Sep 6Sep 20Oct 5
US-West
780msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 671ms2026-09-07 UTC: p95 543ms2026-09-08 UTC: p95 589ms2026-09-09 UTC: p95 306ms2026-09-10 UTC: p95 366ms2026-09-11 UTC: p95 275ms2026-09-12 UTC: p95 372ms2026-09-13 UTC: p95 533ms2026-09-14 UTC: p95 424ms2026-09-15 UTC: p95 783ms2026-09-16 UTC: p95 828ms2026-09-17 UTC: p95 870ms2026-09-18 UTC: p95 723ms2026-09-19 UTC: p95 795ms2026-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 780ms
Sep 6Sep 20Oct 5
Europe
858msp95 · 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-06 UTC: p95 244ms2026-09-07 UTC: p95 247ms2026-09-08 UTC: p95 216ms2026-09-09 UTC: p95 1.0s2026-09-10 UTC: p95 1.0s2026-09-11 UTC: p95 986ms2026-09-12 UTC: p95 959ms2026-09-13 UTC: p95 852ms2026-09-14 UTC: p95 398ms2026-09-15 UTC: p95 345ms2026-09-16 UTC: p95 254ms2026-09-17 UTC: p95 210ms2026-09-18 UTC: p95 211ms2026-09-19 UTC: p95 228ms2026-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 858ms
Sep 6Sep 20Oct 5
Asia-Pacific
943msp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 885ms2026-09-07 UTC: p95 892ms2026-09-08 UTC: p95 681ms2026-09-09 UTC: p95 612ms2026-09-10 UTC: p95 936ms2026-09-11 UTC: p95 925ms2026-09-12 UTC: p95 898ms2026-09-13 UTC: p95 840ms2026-09-14 UTC: p95 737ms2026-09-15 UTC: p95 784ms2026-09-16 UTC: p95 880ms2026-09-17 UTC: p95 838ms2026-09-18 UTC: p95 867ms2026-09-19 UTC: p95 825ms2026-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 943ms
Sep 6Sep 20Oct 5
US-Central
490msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 434ms2026-09-07 UTC: p95 372ms2026-09-08 UTC: p95 624ms2026-09-09 UTC: p95 557ms2026-09-10 UTC: p95 525ms2026-09-11 UTC: p95 444ms2026-09-12 UTC: p95 434ms2026-09-13 UTC: p95 458ms2026-09-14 UTC: p95 416ms2026-09-15 UTC: p95 436ms2026-09-16 UTC: p95 520ms2026-09-17 UTC: p95 466ms2026-09-18 UTC: p95 404ms2026-09-19 UTC: p95 526ms2026-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 490ms
Sep 6Sep 20Oct 5
Canada
1.3sp95 · 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-06 UTC: p95 549ms2026-09-07 UTC: p95 562ms2026-09-08 UTC: p95 504ms2026-09-09 UTC: p95 631ms2026-09-10 UTC: p95 626ms2026-09-11 UTC: p95 589ms2026-09-12 UTC: p95 535ms2026-09-13 UTC: p95 708ms2026-09-14 UTC: p95 604ms2026-09-15 UTC: p95 546ms2026-09-16 UTC: p95 604ms2026-09-17 UTC: p95 577ms2026-09-18 UTC: p95 593ms2026-09-19 UTC: p95 556ms2026-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.3s
Sep 6Sep 20Oct 5
UK
729msp95 · 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-06 UTC: p95 321ms2026-09-07 UTC: p95 431ms2026-09-08 UTC: p95 444ms2026-09-09 UTC: p95 395ms2026-09-10 UTC: p95 522ms2026-09-11 UTC: p95 538ms2026-09-12 UTC: p95 392ms2026-09-13 UTC: p95 320ms2026-09-14 UTC: p95 352ms2026-09-15 UTC: p95 343ms2026-09-16 UTC: p95 375ms2026-09-17 UTC: p95 496ms2026-09-18 UTC: p95 367ms2026-09-19 UTC: p95 413ms2026-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 729ms
Sep 6Sep 20Oct 5
Southeast Asia
1.4sp95 · 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-06 UTC: p95 804ms2026-09-07 UTC: p95 990ms2026-09-08 UTC: p95 1.1s2026-09-09 UTC: p95 1.0s2026-09-10 UTC: p95 1.1s2026-09-11 UTC: p95 906ms2026-09-12 UTC: p95 916ms2026-09-13 UTC: p95 990ms2026-09-14 UTC: p95 922ms2026-09-15 UTC: p95 865ms2026-09-16 UTC: p95 997ms2026-09-17 UTC: p95 1.0s2026-09-18 UTC: p95 1.3s2026-09-19 UTC: p95 1.3s2026-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.4s
Sep 6Sep 20Oct 5
Australia
1.6sp95 · 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-06 UTC: p95 928ms2026-09-07 UTC: p95 794ms2026-09-08 UTC: p95 787ms2026-09-09 UTC: p95 728ms2026-09-10 UTC: p95 635ms2026-09-11 UTC: p95 1.0s2026-09-12 UTC: p95 658ms2026-09-13 UTC: p95 1.2s2026-09-14 UTC: p95 717ms2026-09-15 UTC: p95 876ms2026-09-16 UTC: p95 754ms2026-09-17 UTC: p95 780ms2026-09-18 UTC: p95 597ms2026-09-19 UTC: p95 829ms2026-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.6s
Sep 6Sep 20Oct 5
South America
1.5sp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.0s2026-09-07 UTC: p95 1.0s2026-09-08 UTC: p95 1.2s2026-09-09 UTC: p95 847ms2026-09-10 UTC: p95 1.1s2026-09-11 UTC: p95 963ms2026-09-12 UTC: p95 958ms2026-09-13 UTC: p95 873ms2026-09-14 UTC: p95 929ms2026-09-15 UTC: p95 993ms2026-09-16 UTC: p95 985ms2026-09-17 UTC: p95 1.2s2026-09-18 UTC: p95 1.0s2026-09-19 UTC: p95 1.3s2026-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.5s
Sep 6Sep 20Oct 5

Is it Binance, or is it you?

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 we see Binance go down, and when it is back

Get told when we measure this

We will tell you when our probes stop reaching Binance, and again when they can reach it again. That is our own measurement from ten regions, not Binance's status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

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 we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 561msstatus code: 202checked: Oct 5, 2026, 8:09 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
      Operationallatency: 514msstatus code: 202checked: Oct 5, 2026, 8:08 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
      Operationallatency: 131msstatus code: 202checked: Oct 5, 2026, 8:14 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
      Operationallatency: 416msstatus code: 202checked: Oct 5, 2026, 8:10 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
    Operationallatency: 1107msstatus code: 202checked: Oct 5, 2026, 8:03 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
    OperationalEurope, UK
    • Europe
      Operationallatency: 90msstatus code: 202checked: Oct 5, 2026, 8:09 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
      Operationallatency: 105msstatus code: 202checked: Oct 5, 2026, 8:07 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
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 142msstatus code: 202checked: Oct 5, 2026, 8:15 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
      Operationallatency: 1001msstatus code: 202checked: Oct 5, 2026, 8:15 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
      Operationallatency: 1372msstatus code: 202checked: Oct 5, 2026, 8:08 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 outages

No outages on record yet for Binance.

measured 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 measurements and Binance's own claim at the time, side by side.

Full availability history for Binance: 90-day availability by region, month-by-month uptime, and every incident 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 measured by RealUptimeLive, from this page's own readings.
[![Binance uptime measured by RealUptime](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 measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and 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: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Binance's SLA implies, from our measurement

At or above your target

We measured none of downtime for Binance over the last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, 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
RealUptime is not affiliated with Binance; the name identifies what we measured, 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 proves reachability only: the endpoints above answer, but that does not confirm the underlying product or account features work. Read the full methodology.