← Binance status page

Binance WS · connection outage, 4 min on 03 SEP 2026

Binance WS — 100% of windows failing over the last minute (http_4xx) — from Lauterbourg, FR and Carlstadt, US. up24 opened this incident from its own measurements of Binance's public API on 03 SEP 2026 05:15 UTC. It lasted 4 min and ended 03 SEP 2026 05:20 UTC, when the component started answering again.

OUTAGEWS · connection · the shared socket
DURATION
4 min
STARTED
03 SEP 2026 05:15 UTC
ENDED
03 SEP 2026 05:20 UTC
VS THEIR NOTICE
NOT ACKNOWLEDGED

WHAT HAPPENED

  1. 03 SEP 2026 05:15 UTC
    up24 opened the incident at outage, http_4xx.
  2. 03 SEP 2026 05:20 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 – 500ms
04:46 · 03 SEP05:18 · 03 SEP05:50 · 03 SEP

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.