https://approjects-vendor-status-watch.static.hf.space/v/bitmex.htmlIncidents from BitMEX's public status page, polled daily.Wed, 16 Sep 2026 12:28:20 +0000https://status.bitmex.combitmex:2026-07-13T14:08:03ZMon, 13 Jul 2026 14:08:03 +0000The withdrawal backlog has been cleared and systems are operating as expected. https://status.bitmex.combitmex:2026-06-13T07:36:25ZSat, 13 Jun 2026 07:36:25 +0000The incident is now resolvedhttps://status.bitmex.combitmex:2026-05-14T09:28:24ZThu, 14 May 2026 09:28:24 +0000Connections are restored. Monitoring completehttps://status.bitmex.combitmex:2026-05-12T07:59:34ZTue, 12 May 2026 07:59:34 +0000The issue has been resolved, all systems are operating normallyhttps://status.bitmex.combitmex:2026-04-15T12:48:52ZWed, 15 Apr 2026 12:48:52 +0000The fix has been implemented and withdrawals are now flowing as expected. https://status.bitmex.combitmex:2026-03-28T13:38:51ZSat, 28 Mar 2026 13:38:51 +0000The issue is now resolvedhttps://status.bitmex.combitmex:2026-03-24T05:43:14ZTue, 24 Mar 2026 05:43:14 +0000This issue is now resolvedhttps://status.bitmex.combitmex:2026-02-26T07:58:00ZThu, 26 Feb 2026 07:58:00 +0000REST 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 issues have been identified and we are working on permanent fixes to prevent a recurrence. 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.https://status.bitmex.combitmex:2026-02-26T07:58:00ZThu, 26 Feb 2026 07:58:00 +0000From 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 directly to our websocket API. As part of a scheduled software release on the trading engine, our market data distribution component became saturated with a cascade of updates during the restart process which temporarily prevented downstream data distribution on the websocket API. We apologise for the disruption. The root cause has been identified and mitigated in the production environment. BitMEX engineers have already deployed a fix for the underlying issue to prevent a re-occurrence. We are also improving a number of alerting mechanisms to enable us to recover from potentiahttps://status.bitmex.combitmex:2026-02-26T07:58:00ZThu, 26 Feb 2026 07:58:00 +0000From 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 limiting and sessions, creating a feedback loop in that system where data was recalculated more often than usual, exacerbating the load. The feedback loop has been fixed and systems have returned back to normal. BitMEX engineers are working to separate these systems entirely, so that these particular non-critical operations cannot affect processing time of critical trade requests and logins. We apologise for the disruption. BitMEX engineers have disabled the cause of the feedback loop and are working the weekend to separate these critical systems so that such an event canhttps://status.bitmex.combitmex:2026-02-26T07:58:00ZThu, 26 Feb 2026 07:58:00 +0000Today, 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 engine hardware degraded sharply in performance at roughly 10:00 UTC. This degradation caused feed latency during scheduled archive and reindex jobs, which caused significant backpressure. Disk I/O operations were running at roughly 1/20 of their expected rate. BitMEX runs redundant drives, but in this case, both drives were simultaneously exhibiting this degraded behavior. We had no choice but to schedule a maintenance downtime to replace them. Unfortunately, backpressure reached critical levels faster than we expected and we moved up our timetable. At no point washttps://status.bitmex.combitmex:2026-02-26T07:57:59ZThu, 26 Feb 2026 07:57:59 +0000Between 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 alerting mechanisms we identified the cause and mitigated the immediate impact within a few minutes. There is currently no ongoing issue and there was no impact to the trading engine or user data during this time. Fixes for the underlying root cause of the issue have been identified and are being worked on as a priority. We will follow up with another announcement once these are live. We have also increased the sensitivity of our system monitoring to detect and resolve potential similar issues much sooner. We apologise for any inconvenience this may have caused.https://status.bitmex.combitmex:2026-02-26T07:57:59ZThu, 26 Feb 2026 07:57:59 +0000Earlier 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 resumed immediately. We apologise for any inconvenience this may have causedhttps://status.bitmex.combitmex:2026-02-26T07:57:59ZThu, 26 Feb 2026 07:57:59 +0000At 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 observed a lack of updates over the WebSocket API for the same reason. The outages were due to data replay complications during a regularly scheduled market data distribution component restart. There was no data loss during these events and an additional safety mechanism to prevent a similar situation from impacting the trading engine has already been deployed. The root causes have also been identified and we are currently working on permanent fixes to prevent a recurrence. Updates will follow in the future. On 15 Jan 2019, we successfully released an enhancement to our internhttps://status.bitmex.combitmex:2026-02-26T07:57:59ZThu, 26 Feb 2026 07:57:59 +0000At 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 02:47:00 UTC. Clients may have also seen an increase in response times for some market data REST endpoints up during this period. This was due to a rolling restart of the API servers that occurred in too tight of a timeframe.https://status.bitmex.combitmex:2026-02-26T07:57:59ZThu, 26 Feb 2026 07:57:59 +0000On 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. The root causes of both issues have been identified and we are working on permanent fixes to prevent a recurrence. Updates will follow in the future.https://status.bitmex.combitmex:2026-02-26T07:57:58ZThu, 26 Feb 2026 07:57:58 +0000On 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 auto-deleveraging events, the Insurance Fund allocated to these contracts was minimal. The Insurance Fund is allocated individually to each contract according to how many liquidations contribute to that specific contract \(System Gains and Losses\). In the case of expired contracts, BitMEX has a process in place to roll over the Insurance Fund allocated to these contracts into the next front month contract. With the recent expiry on the 29th March 2019, this process failed and front month contracts did not receive their reallocation, and the funds remained unallocated. As a result, a hahttps://status.bitmex.combitmex:2026-02-26T07:57:58ZThu, 26 Feb 2026 07:57:58 +0000On 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 normal after the 15 second outage.https://status.bitmex.combitmex:2026-02-26T07:57:58ZThu, 26 Feb 2026 07:57:58 +0000The 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.https://status.bitmex.combitmex:2026-02-26T07:57:58ZThu, 26 Feb 2026 07:57:58 +0000On 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 the internal market data distribution components. This was part of a regularly scheduled update to improve the overall resiliency of the platform. The root cause has been identified and a fix via internal processes has been put in place to prevent a recurrence. Additionally, we are continuing to re-work our market data distribution architecture to eliminate any potential impact to the trading engine in such a scenario.https://status.bitmex.combitmex:2026-02-26T07:57:57ZThu, 26 Feb 2026 07:57:57 +0000Between 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 substantial lag during traffic spikes correlated with large market moves. The issue was identified when latency thresholds were breached in our automated monitoring systems around 06:55 UTC. From 07:05 the issue was resolved and full capacity was restored. We continue to monitor the impacted services closely. The issue was caused by incorrect CPU pinning following a release of a market data distribution component at 21:30 UTC 25 November 2019. The impact of this was only observed during large traffic spikes which occurred several hours later and so was not identified during thttps://status.bitmex.combitmex:2026-02-26T07:57:57ZThu, 26 Feb 2026 07:57:57 +0000Between 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, wallet Users of the BitMEX website may have noticed that some data was not updating during this period; e.g. in the Recent Trades panel, Open Orders panel, Fills panel, and Position panel. The following public feeds were unaffected during this period: funding, insurance, liquidation, settlement, impactQuote, impactQuoteBin1m, quote, quoteBin1m, quoteBin5m, quoteBin1h, quoteBin1d, tradeBin1m, tradeBin5m, tradeBin1h, tradeBin1d, orderBookL2\_25, orderBook10, orderBookL2 The REST API was also unaffected and client-side data loss due to missed feed updates during this periodhttps://status.bitmex.combitmex:2026-02-26T07:57:57ZThu, 26 Feb 2026 07:57:57 +0000Between 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, funds, instrument, margin, order, position, trade, transact, wallet Users of the BitMEX website may have noticed some data not updating during this period e.g. in the Recent Trades panel, Open Orders panel, Fills panel, and Position panel. The following public feeds were unaffected during this period: Funding, insurance, liquidation, settlement, impactQuote, impactQuoteBin1m, quote, quoteBin1m, quoteBin5m, quoteBin1h, quoteBin1d, tradeBin1m, tradeBin5m, tradeBin1h, tradeBin1d, orderBookL2\_25, orderBook10, orderBookL2 During this period we continued to process order instructhttps://status.bitmex.combitmex:2026-02-26T07:57:57ZThu, 26 Feb 2026 07:57:57 +0000At 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 may have impacted customers who heavily utilise the WebSocket API. Once the issue was identified at 00:19 UTC 26 June, we immediately rolled back the update to bring systems back to normal. We apologise for any inconvenience this may have caused. To read more about which subscriptions are exempt from the request rate limiter, see our previous blog post \[[https://blog.bitmex.com/update-to-our-realtime-apis-image-delivery/](https://blog.bitmex.com/update-to-our-realtime-apis-image-delivery/)\] for details.https://status.bitmex.combitmex:2026-02-26T07:57:57ZThu, 26 Feb 2026 07:57:57 +0000Between 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 orderbook on these feeds was incorrect. We were able to identify and resolve the root cause of the issue within a minute of detection. The issue was caused by a rare sequence of order events that triggered a bug in an optimisation of the orderBookL2 calculation which had been deployed to the production environment several hours earlier. This change has since been reverted. There was no impact to orders in the trading engine itself – just the presentation of the calculated orderbook for ETHUSD downstream of the trading engine. We have deployed additional automated feed valid