BitMEX Outage History
27 incidents recorded over the last 365 days, 27 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded BitMEX Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Nov 3, 2026 | Scheduled MaintenanceMaintenance has started | 2h 4m | Resolved |
| Oct 12, 2026 | Scheduled System Upgrade on 12 October 2026Maintenance is continuing | 50h 49m | Resolved |
| Jul 13, 2026 | Delayed WithdrawalsThe withdrawal backlog has been cleared and systems are operating as expected. | 44 min | Resolved |
| Jun 13, 2026 | Incorrect Account Information in UIThe incident is now resolved | 71h 55m | Resolved |
| May 14, 2026 | Cloudflare bypass connection issuesConnections are restored. Monitoring complete | 2h 49m | Resolved |
| May 12, 2026 | Website unavailable in certain regionsThe issue has been resolved, all systems are operating normally | -20 min | Resolved |
| Apr 15, 2026 | Withdrawals held in processing stateThe fix has been implemented and withdrawals are now flowing as expected. | 3h 34m | Resolved |
| Mar 28, 2026 | Testnet Websocket InstabilityThe issue is now resolved | -73 min | Resolved |
| Mar 24, 2026 | Authentication Error RatesThis issue is now resolved | 26 min | Resolved |
| Feb 26, 2026 | Trading Engine IssuesToday, May 17, 2018, the BitMEX trading engine encountered several separate and heretofore unpredictable problems, causing feed latency and downtime in spurts throughout the day. Disks mounted to the main trading… | -4092058 min | Resolved |
| Feb 26, 2026 | Issue for Accessing BitMEX.com and the BitMEX APIFrom 14:29 to 15:26 UTC today, August 4, 2018, access to [BitMEX.com](http://BitMEX.com) and the BitMEX API was severely impaired. A large spike in load caused an overload in a critical internal system used for rate… | -3978332 min | Resolved |
| Feb 26, 2026 | Websocket API Service ImpairedFrom 06:53 to 07:03 UTC today, September 3rd, 2018, the service of our websocket API was impaired, which impacted the live data updates on the [bitmex.com](http://bitmex.com) website as well as clients connected… | -3935635 min | Resolved |
| Feb 26, 2026 | REST API LatencyREST API queries for trading related data (read-only HTTP GET requests, not order management requests) took longer to return than usual over a period of 23 minutes from 18:13 UTC to 18:36 UTC. The root causes of both… | -3769282 min | Resolved |
| Feb 26, 2026 | Trading Engine InterruptionOn 27 December at 18:38 UTC, BitMEX experienced a minor outage for approximately 1 minute whereby the trading engine was unavailable. During this time, market data updates were not published over the Websocket API… | -3769278 min | Resolved |
| Feb 26, 2026 | WebSocket API DegradationAt 02:44:10 UTC the WebSocket API saw a degradation in performance for a minute where 7% of commands sent by clients failed. Connections continued undergoing a 1% failure rate of commands until servers recovered at… | -3751510 min | Resolved |
| Feb 26, 2026 | Trading Engine InterruptionAt 05:48:10 UTC and 06:10:10 UTC, BitMEX experienced minor outages for approximately 30 seconds whereby requests to the trading engine were load-shed as the engine was busy. During these times, clients would have… | -3751307 min | Resolved |
| Feb 26, 2026 | Testnet Service InterruptionEarlier today, the [testnet.bitmex.com](http://testnet.bitmex.com) website and the API were not available for approximately 16 minutes from 19:42 to 19:57 UTC. We identified the cause, made adjustments and service has… | -3730320 min | Resolved |
| Feb 26, 2026 | Slow BitMEX Rest API ResponsesBetween 05:40 and 07:11 UTC today, a subset of the requests to the BitMEX REST API experienced slow API responses and eventual API timeouts due to resource contention at the API layer. Upon detection via our internal… | -3708046 min | Resolved |
| Feb 26, 2026 | Trading Engine InterruptionOn 19 February at 05:31 UTC, BitMEX experienced a minor outage for approximately 1 minute whereby all trading engine operations were suspended. This issue occurred due to a sustained period of data transfers between… | -3692305 min | Resolved |
| Feb 26, 2026 | Minor OutageOn 29 March at 12:00 UTC, BitMEX experienced a minor outage for approximately 15 seconds whereby all requests would have been load shed as the engine was blocked during settlement operations. The platform was back to… | -3636537 min | Resolved |
| Feb 26, 2026 | Auto-Deleveraging IssueOn 2 April 2019 between 04:44:34 UTC and 05:22:08 UTC, less than 200 positions were auto-deleveraged due to the sharp price movements of the underlying mark price on XBTU19 and ETHM19. At the time of these… | -3631895 min | Resolved |
| Feb 26, 2026 | BitMEX Frontend IssueThe issue has been resolved. We apologise for any inconvenience this may be causing. If you have any further questions, please contact us via https://www.bitmex.com/app/support/contact. | -3636709 min | Resolved |
| Feb 26, 2026 | Websocket API Feed InterruptionBetween 07:50 and 07:58 UTC on 27 June 2019, the following websocket API feeds were interrupted due to a complication during a planned upgrade of our market data distribution services: Account, affiliate, execution… | -3507899 min | Resolved |
| Feb 26, 2026 | ETHUSD Orderbook IssueBetween 09:25:54 UTC and 09:44:30 UTC 24 June 2019 the orderBookL2, orderBookL2\_25, orderBook10, and quote realtime websocket feeds for ETHUSD were in a degraded state. During this period, the state of the ETHUSD… | -3511461 min | Resolved |
| Feb 26, 2026 | Websocket API with Incorrect Rate-LimitsAt 21:09:00 UTC 25 June, we released an update to our API layer that inadvertently started to count WebSocket subscriptions to certain tables against the request rate limit that had otherwise been exempt. This update… | -3509738 min | Resolved |
| Feb 26, 2026 | Websocket API InterruptionBetween 10:44:13 and 10:52:29 UTC on 24 July 2019, the realtime data on the following websocket API feeds was interrupted: account, affiliate, execution, funds, instrument, margin, order, position, trade, transact… | -3463964 min | Resolved |
| Feb 26, 2026 | Websocket API LatencyBetween 21:30 UTC 25 November 2019 and 07:05 UTC 26 November 2019 the Websocket API was running with degraded capacity. This resulted in slightly more latent feeds during this time and some isolated occurrences of… | -3289012 min | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next BitMEX incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This BitMEX Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before BitMEX acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single BitMEX outage in this window ran 2d 23h, against a mean recovery of 18h 54m. If you depend on BitMEX in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.