Binance REST · ping degradation, 20s on 11 SEP 2026
Binance REST · ping — 100% of checks 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 20 seconds. up24 opened this incident from its own measurements of Binance's public API on 11 SEP 2026 00:06 UTC. It lasted 20s and ended 11 SEP 2026 00:07 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
Over the window, 2 of 1,452 checks failed: http_4xx ×732, timeout ×2.
REST latency for the failing endpoint, per minute, from 10 SEP 2026 23:36 UTC to 11 SEP 2026 00:37 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.