Binance REST · ping degradation, 4 min on 31 AUG 2026
Binance REST · ping — p95 638ms over five minutes, 4.9× the 7-day baseline of 131ms — from Carlstadt, US and Singapore, SG. up24 opened this incident from its own measurements of Binance's public API on 31 AUG 2026 13:18 UTC. It lasted 4 min and ended 31 AUG 2026 13:22 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, 748 of 2,238 checks failed: http_4xx ×748.
REST latency for the failing endpoint, per minute, from 31 AUG 2026 12:48 UTC to 31 AUG 2026 13:52 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.