Vendor Status Watch

← all vendors

BitMEX status history

Current state: operational — “All Systems Operational” per https://status.bitmex.com (Atlassian Statuspage), checked 2026-09-24 12:28 UTC.

0incidents, last 30 days
1incidents, last 90 days
25incidents on record
Incidents per week, last 12 weeks:

How long do BitMEX incidents last?

2.8 hmedian incident duration5 measured
3.0 days90th percentile1 in 10 ran longer
44 minmedian, major/critical only3 incidents

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)

StartedIncidentStatusImpactDuration
2026-07-13 14:08 UTCDelayed Withdrawalsresolvedmajor44 min
2026-06-13 07:36 UTCIncorrect Account Information in UIresolvedminor2 d 23 h
2026-05-14 09:28 UTCCloudflare bypass connection issuesresolvedminor2 h 49 min
2026-05-12 07:59 UTCWebsite unavailable in certain regionsresolvedmajor—
2026-04-15 12:48 UTCWithdrawals held in processing stateresolvedmajor3 h 34 min
2026-03-28 13:38 UTCTestnet Websocket Instabilityresolvedmajor—
2026-03-24 05:43 UTCAuthentication Error Ratesresolvedcritical26 min
2026-02-26 07:58 UTCREST API Latencyresolvedminor—
2026-02-26 07:58 UTCWebsocket API Service Impairedresolvedcritical—
2026-02-26 07:58 UTCIssue for Accessing BitMEX.com and the BitMEX APIresolvedcritical—
2026-02-26 07:58 UTCTrading Engine Issuesresolvedcritical—
2026-02-26 07:57 UTCSlow BitMEX Rest API Responsesresolvedminor—
2026-02-26 07:57 UTCTestnet Service Interruptionresolvedcritical—
2026-02-26 07:57 UTCTrading Engine Interruptionresolvedminor—
2026-02-26 07:57 UTCWebSocket API Degradationresolvedminor—
2026-02-26 07:57 UTCTrading Engine Interruptionresolvedmajor—
2026-02-26 07:57 UTCAuto-Deleveraging Issueresolvedminor—
2026-02-26 07:57 UTCMinor Outageresolvedmajor—
2026-02-26 07:57 UTCBitMEX Frontend Issueresolvedminor—
2026-02-26 07:57 UTCTrading Engine Interruptionresolvedmajor—
2026-02-26 07:57 UTCWebsocket API Latencyresolvedminor—
2026-02-26 07:57 UTCWebsocket API Interruptionresolvedmajor—
2026-02-26 07:57 UTCWebsocket API Feed Interruptionresolvedmajor—
2026-02-26 07:57 UTCWebsocket API with Incorrect Rate-Limitsresolvedmajor—
2026-02-26 07:57 UTCETHUSD Orderbook Issueresolvedminor—

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
}