← all exchanges
BIT

Bitstamp API status

OPERATIONAL
btcusd · www.bitstamp.net · 3 REST endpoints · 2 streams
UPTIME · 90D
99.98%
TYPICAL P50 · 24H
15ms
TYPICAL P95 · 24H
96ms
INCIDENTS · 90D
1

UPTIME · LAST 90 DAYS · ALL REST ENDPOINTS

■ operational■ degraded■ outage■ not measured
16 MAY29 JUN13 AUG

API LATENCY · 24H · MEASURED FROM RAW SAMPLES

— p50‑ ‑ p95
axis 0 – 1000ms
09:00 · 13 AUG10:05 · 13 AUG11:15 · 13 AUG

REST ENDPOINTS · LAST 24H

ENDPOINTP50P95UPTIMESTATUS
REST · ping
1,628 checks · www.bitstamp.net
19ms104ms99.94%OPERATIONAL
REST · ticker
1,628 checks · www.bitstamp.net
8ms34ms100.00%OPERATIONAL
REST · depth
1,628 checks · www.bitstamp.net
15ms170ms100.00%OPERATIONAL

WEBSOCKET STREAMS · LAST 24H

STREAMCONNECTEDDELIVERINGMESSAGESMAX GAPSEQ GAPSRECONNECTSRTTSTATUS
WS · trade
live_trades_btcusd
100.00%100.00%2,34377250ms0011msOPERATIONAL
WS · book
diff_order_book_btcusd
100.00%99.75%24,34215323ms011msOPERATIONAL

INCIDENT HISTORY · 90D

  1. 13 AUG 2026 · 6 min
    Bitstamp WS · book — 33% of windows failing over the last minute (stalled)
    WS · book · stalled

Incidents are opened by up24's own state machine over its own measurements, not by Bitstamp's status page.

BITSTAMP SAID · 90D

up24 opened 1 incident for Bitstamp in the last 90 days. Nothing Bitstamp published lines up with it.

  1. 05 AUG 2026 09:14 UTC · INCIDENT · CRITICAL
    05 AUG 2026 09:14 UTC → 05 AUG 2026 09:53 UTC
  2. 03 AUG 2026 12:07 UTC · INCIDENT · CRITICAL
    03 AUG 2026 12:07 UTC → 03 AUG 2026 12:44 UTC
  3. 28 JUN 2026 10:22 UTC · INCIDENT · CRITICAL
    28 JUN 2026 10:22 UTC → 28 JUN 2026 11:11 UTC
  4. 10 JUN 2026 13:12 UTC · INCIDENT · CRITICAL
    10 JUN 2026 13:12 UTC → 10 JUN 2026 13:19 UTC
  5. 03 JUN 2026 08:09 UTC · INCIDENT · CRITICAL
    03 JUN 2026 08:09 UTC → 03 JUN 2026 09:00 UTC
  6. 29 MAY 2026 13:52 UTC · INCIDENT · CRITICAL
    29 MAY 2026 13:52 UTC → 29 MAY 2026 17:22 UTC

Read from status.bitstamp.net every 5 minutes. Times are the venue’s own.