← Binance status page

Binance WS · connection outage, 9 min on 20 AUG 2026

Binance WS — 33% of windows failing over the last minute (conn). up24 opened this incident from its own measurements of Binance's public API on 20 AUG 2026 02:07 UTC. It lasted 9 min and ended 20 AUG 2026 02:16 UTC, when the component started answering again.

OUTAGEWS · connection · the shared socket
DURATION
9 min
STARTED
20 AUG 2026 02:07 UTC
ENDED
20 AUG 2026 02:16 UTC
VS THEIR NOTICE
NOT ACKNOWLEDGED

WHAT HAPPENED

  1. 20 AUG 2026 02:07 UTC
    up24 opened the incident at outage, conn.
  2. 20 AUG 2026 02:16 UTC
    The component started answering again. up24 dates the incident from this moment, not from when its clearing rule finished.

HOW IT FAILED

Stream measurements are kept for seven days, and this incident is older than that. The incident itself is permanent; the ten-second windows behind it are not.

— p50‑ ‑ p95
axis 0 – 1000ms
01:38 · 20 AUG02:12 · 20 AUG02:46 · 20 AUG

A stream has no latency of its own — a feed either delivers or it does not — so this is Binance's REST endpoints over the same window, per minute, as the median across them. It answers the question the timeline cannot: whether the rest of the exchange was fine while this feed was down.

DID BINANCE SAY SO?

Binance publishes a status feed and nothing in it lines up with this incident. That is not proof they stayed silent; it is what their feed says.

up24 opened 38 incidents for Binance in the last 90 days. Nothing Binance published lines up with any of them.

BINANCE — OTHER INCIDENTS

Measured by up24's own probe against Binance's public API, BTCUSDT against USDT, every 5s. This page is generated from the incident's own rows — 2 recorded transitions — and nothing on it is reported by Binance.