Binance REST · depth degradation, 8 min on 07 SEP 2026
Binance REST · depth — p95 1370ms over the last five minutes, 5.1× the 7-day baseline of 271ms — from Carlstadt, US and Lauterbourg, FR. up24 opened this incident from its own measurements of Binance's public API on 07 SEP 2026 16:35 UTC. It lasted 8 min and ended 07 SEP 2026 16:43 UTC, when the component started answering again.
WHAT HAPPENED
- up24 opened the incident at degraded.
- The component started answering again. up24 dates the incident from this moment, not from when its clearing rule finished.
HOW IT FAILED
Over the window, 816 of 2,446 checks failed: http_4xx ×816.
REST latency for the failing endpoint, per minute, from 07 SEP 2026 16:05 UTC to 07 SEP 2026 17:13 UTC. The gap in the line is where nothing answered.
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.