Binance WS · connection degradation, 40s on 01 SEP 2026
Binance WS — 100% of windows failing over the last minute (http_4xx) — from Singapore, SG and Carlstadt, US — re-graded on 12 Sep 2026: an outage grade now needs two minutes, and this lasted 40 seconds. up24 opened this incident from its own measurements of Binance's public API on 01 SEP 2026 16:32 UTC. It lasted 40s and ended 01 SEP 2026 16:33 UTC, when the component started answering again.
WHAT HAPPENED
- up24 opened the incident at degraded, http_4xx.
- 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.
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.