BitMEX status history
Current state: operational — “All Systems Operational” per https://status.bitmex.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do BitMEX incidents last?
From 5 incidents with a vendor-posted start and resolve time. Longest on record: Incorrect Account Information in UI — 3.0 days (2026-06-13 07:36 UTC). Excluded, never estimated: 20 resolved before started (vendor data error). Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.
Incidents on record (25)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-07-13 14:08 UTC | Delayed Withdrawals | resolved | major | 44 min |
| 2026-06-13 07:36 UTC | Incorrect Account Information in UI | resolved | minor | 2 d 23 h |
| 2026-05-14 09:28 UTC | Cloudflare bypass connection issues | resolved | minor | 2 h 49 min |
| 2026-05-12 07:59 UTC | Website unavailable in certain regions | resolved | major | — |
| 2026-04-15 12:48 UTC | Withdrawals held in processing state | resolved | major | 3 h 34 min |
| 2026-03-28 13:38 UTC | Testnet Websocket Instability | resolved | major | — |
| 2026-03-24 05:43 UTC | Authentication Error Rates | resolved | critical | 26 min |
| 2026-02-26 07:58 UTC | REST API Latency | resolved | minor | — |
| 2026-02-26 07:58 UTC | Websocket API Service Impaired | resolved | critical | — |
| 2026-02-26 07:58 UTC | Issue for Accessing BitMEX.com and the BitMEX API | resolved | critical | — |
| 2026-02-26 07:58 UTC | Trading Engine Issues | resolved | critical | — |
| 2026-02-26 07:57 UTC | Slow BitMEX Rest API Responses | resolved | minor | — |
| 2026-02-26 07:57 UTC | Testnet Service Interruption | resolved | critical | — |
| 2026-02-26 07:57 UTC | Trading Engine Interruption | resolved | minor | — |
| 2026-02-26 07:57 UTC | WebSocket API Degradation | resolved | minor | — |
| 2026-02-26 07:57 UTC | Trading Engine Interruption | resolved | major | — |
| 2026-02-26 07:57 UTC | Auto-Deleveraging Issue | resolved | minor | — |
| 2026-02-26 07:57 UTC | Minor Outage | resolved | major | — |
| 2026-02-26 07:57 UTC | BitMEX Frontend Issue | resolved | minor | — |
| 2026-02-26 07:57 UTC | Trading Engine Interruption | resolved | major | — |
| 2026-02-26 07:57 UTC | Websocket API Latency | resolved | minor | — |
| 2026-02-26 07:57 UTC | Websocket API Interruption | resolved | major | — |
| 2026-02-26 07:57 UTC | Websocket API Feed Interruption | resolved | major | — |
| 2026-02-26 07:57 UTC | Websocket API with Incorrect Rate-Limits | resolved | major | — |
| 2026-02-26 07:57 UTC | ETHUSD Orderbook Issue | resolved | minor | — |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch BitMEX with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"bitmex"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}