{
"vendor": "BitMEX",
"slug": "bitmex",
"platform": "statuspage",
"status_url": "https://status.bitmex.com",
"last_checked": "2026-09-16T12:28:20Z",
"last_state": "ok",
"history_backfilled": true,
"first_watched": "2026-09-04T07:06:16Z",
"incidents": [
{
"body": "The withdrawal backlog has been cleared and systems are operating as expected. ",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-07-13T14:52:35Z",
"resolved_inferred": false,
"started_at": "2026-07-13T14:08:03Z",
"state": "resolved",
"title": "Delayed Withdrawals",
"updated_at": "2026-07-13T14:52:35Z"
},
{
"body": "The incident is now resolved",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-06-16T07:31:58Z",
"resolved_inferred": false,
"started_at": "2026-06-13T07:36:25Z",
"state": "resolved",
"title": "Incorrect Account Information in UI",
"updated_at": "2026-06-16T07:31:58Z"
},
{
"body": "Connections are restored. Monitoring complete",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-05-14T12:18:00Z",
"resolved_inferred": false,
"started_at": "2026-05-14T09:28:24Z",
"state": "resolved",
"title": "Cloudflare bypass connection issues",
"updated_at": "2026-05-15T16:38:48Z"
},
{
"body": "The issue has been resolved, all systems are operating normally",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-05-12T07:39:00Z",
"resolved_inferred": false,
"started_at": "2026-05-12T07:59:34Z",
"state": "resolved",
"title": "Website unavailable in certain regions",
"updated_at": "2026-05-12T07:59:34Z"
},
{
"body": "The fix has been implemented and withdrawals are now flowing as expected. ",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-04-15T16:23:40Z",
"resolved_inferred": false,
"started_at": "2026-04-15T12:48:52Z",
"state": "resolved",
"title": "Withdrawals held in processing state",
"updated_at": "2026-04-15T16:23:40Z"
},
{
"body": "The issue is now resolved",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-03-28T12:25:00Z",
"resolved_inferred": false,
"started_at": "2026-03-28T13:38:51Z",
"state": "resolved",
"title": "Testnet Websocket Instability",
"updated_at": "2026-03-28T13:38:51Z"
},
{
"body": "This issue is now resolved",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "critical",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-03-24T06:09:37Z",
"resolved_inferred": false,
"started_at": "2026-03-24T05:43:14Z",
"state": "resolved",
"title": "Authentication Error Rates",
"updated_at": "2026-03-24T06:09:37Z"
},
{
"body": "REST 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.\n\nThe 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.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2018-12-27T18:36:00Z",
"resolved_inferred": false,
"started_at": "2026-02-26T07:58:00Z",
"state": "resolved",
"title": "REST API Latency",
"updated_at": "2026-03-12T18:30:56Z"
},
{
"body": "From 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. \n\nAs 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. \n\nWe 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 potential issues in a more timely manner.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "critical",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2018-09-03T06:03:00Z",
"resolved_inferred": false,
"started_at": "2026-02-26T07:58:00Z",
"state": "resolved",
"title": "Websocket API Service Impaired",
"updated_at": "2026-03-12T18:30:56Z"
},
{
"body": "From 14:29 to 15:26 UTC today, August 4, 2018, access to [BitMEX.com](http://BitMEX.com) and the BitMEX API was severely impaired. \n\nA 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. \n\nThe 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. \n\nWe 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 cannot occur again.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "critical",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2018-08-04T14:26:00Z",
"resolved_inferred": false,
"started_at": "2026-02-26T07:58:00Z",
"state": "resolved",
"title": "Issue for Accessing BitMEX.com and the BitMEX API",
"updated_at": "2026-03-12T18:30:56Z"
},
{
"body": "Today, May 17, 2018, the BitMEX trading engine encountered several separate and heretofore unpredictable problems, causing feed latency and downtime in spurts throughout the day.  \n  \nDisks 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.  \n  \nBitMEX 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.  \n  \nAt no point was data integrity compromised by this problem, but restoring the machine to a functional state with nominal disk performance took longer than expected to execute and verify.  \n  \nAfter this action was complete, we restarted trading. Unfortunately, another problem was uncovered during the next archive, where a reindex job combined with a previously rare request pattern led to unexpected index regeneration and symbol revalidation on specific tables. This led to another backpressure scenario, with similar symptoms.  \n  \nWe have identified and fixed multiple contributing factors to the above behavior. The trading engine team will be closely monitoring engine performance throughout the day while continuing root cause analysis for the slowdowns.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "critical",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2018-05-17T15:00:00Z",
"resolved_inferred": false,
"started_at": "2026-02-26T07:58:00Z",
"state": "resolved",
"title": "Trading Engine Issues",
"updated_at": "2026-03-12T18:30:56Z"
},
{
"body": "Between 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. \n\nFixes 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.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2019-02-08T07:11:08Z",
"resolved_inferred": false,
"started_at": "2026-02-26T07:57:59Z",
"state": "resolved",
"title": "Slow BitMEX Rest API Responses",
"updated_at": "2026-03-12T18:30:56Z"
},
{
"body": "Earlier 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 caused",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "critical",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2019-01-23T19:57:48Z",
"resolved_inferred": false,
"started_at": "2026-02-26T07:57:59Z",
"state": "resolved",
"title": "Testnet Service Interruption",
"updated_at": "2026-03-12T18:30:56Z"
},
{
"body": "At 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. \n\nThere 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. \n\nOn 15 Jan 2019, we successfully released an enhancement to our internal market data distribution component's re-subscription logic. This addresses the root cause of the previous week's issue and along with the additional safety mechanism to prevent impact to the trading engine deployed at the time, we don't anticipate a reoccurrence of last week's issue.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2019-01-09T06:10:31Z",
"resolved_inferred": false,
"started_at": "2026-02-26T07:57:59Z",
"state": "resolved",
"title": "Trading Engine Interruption",
"updated_at": "2026-03-12T18:30:56Z"
},
{
"body": "At 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. \n\nClients 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.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2019-01-09T02:47:06Z",
"resolved_inferred": false,
"started_at": "2026-02-26T07:57:59Z",
"state": "resolved",
"title": "WebSocket API Degradation",
"updated_at": "2026-03-12T18:30:56Z"
},
{
"body": "On 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. \n\nThe 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.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2018-12-27T18:39:00Z",
"resolved_inferred": false,
"started_at": "2026-02-26T07:57:59Z",
"state": "resolved",
"title": "Trading Engine Interruption",
"updated_at": "2026-03-12T18:30:56Z"
},
{
"body": "On 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.\n\nAt 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 handful of users were auto-deleveraged upon large liquidations within these affected contracts. \n\nBitMEX receives auto-deleveraging reports and was made aware of the unusually high rate of auto-deleveraging events, at which point we investigated the matter. We identified the root cause, corrected the allocation and put further controls in place to ensure that reallocation failures are automatically flagged internally. \n\nFor users that were affected, BitMEX will be reaching out to you personally to explain the situation and document your compensation. We compensated users based on the maximum potential profit that they would have made over the timeframe of these auto-deleveraging events. We exited these users at the best price of each contract: longs at 5,079.5 on XBTU19 and shorts at 0.03103 on ETHM19. BitMEX did not profit from these auto-deleveraged positions.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2019-04-02T04:22:44Z",
"resolved_inferred": false,
"started_at": "2026-02-26T07:57:58Z",
"state": "resolved",
"title": "Auto-Deleveraging Issue",
"updated_at": "2026-03-12T18:30:56Z"
},
{
"body": "On 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.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2019-03-29T23:00:29Z",
"resolved_inferred": false,
"started_at": "2026-02-26T07:57:58Z",
"state": "resolved",
"title": "Minor Outage",
"updated_at": "2026-03-12T18:30:56Z"
},
{
"body": "The 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.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2019-03-29T20:08:15Z",
"resolved_inferred": false,
"started_at": "2026-02-26T07:57:58Z",
"state": "resolved",
"title": "BitMEX Frontend Issue",
"updated_at": "2026-03-12T18:30:56Z"
},
{
"body": "On 19 February at 05:31 UTC, BitMEX experienced a minor outage for approximately 1 minute whereby all trading engine operations were suspended. \n\nThis 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.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2019-02-19T05:32:14Z",
"resolved_inferred": false,
"started_at": "2026-02-26T07:57:58Z",
"state": "resolved",
"title": "Trading Engine Interruption",
"updated_at": "2026-03-12T18:30:56Z"
},
{
"body": "Between 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. \n\nThe 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. \n\nThe 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 the post release checks at the time. The configuration of this service has been corrected and the deployment tested to prevent this from happening again.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2019-11-26T07:05:08Z",
"resolved_inferred": false,
"started_at": "2026-02-26T07:57:57Z",
"state": "resolved",
"title": "Websocket API Latency",
"updated_at": "2026-03-12T18:30:56Z"
},
{
"body": "Between 10:44:13 and 10:52:29 UTC on 24 July 2019, the realtime data on the following websocket API feeds was interrupted: \n\naccount, affiliate, execution, funds, instrument, margin, order, position, trade, transact, wallet \n\nUsers 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. \n\nThe following public feeds were unaffected during this period: \n\nfunding, 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 period can be resolved using the REST API. \n\nDuring this period we continued to process all order instructions and the trading engine was unaffected. The outage was due to a slow consuming internal market data service which became degraded, putting pressure on our market data infrastructure. This internal market data service has been suspended whilst the root cause is being investigated. Additionally, several safety mechanisms are currently being deployed to prevent a potential recurrence from impacting user-facing feeds.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2019-07-27T19:13:22Z",
"resolved_inferred": false,
"started_at": "2026-02-26T07:57:57Z",
"state": "resolved",
"title": "Websocket API Interruption",
"updated_at": "2026-03-12T18:30:56Z"
},
{
"body": "Between 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:\n\nAccount, 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.\n\nThe following public feeds were unaffected during this period:\n\nFunding, 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 instructions and the trading engine was unaffected.\n\nDue to this issue, data in a subset of data mirrors which service user REST API requests was left in an incomplete state. A side-effect of this was that some users observed stale open orders on the BitMEX website for orders which were already cancelled for a period of 90 minutes whilst data was being restored. Any API users that may be missing updates for this period can now backfill data via the REST API.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2019-06-27T06:58:24Z",
"resolved_inferred": false,
"started_at": "2026-02-26T07:57:57Z",
"state": "resolved",
"title": "Websocket API Feed Interruption",
"updated_at": "2026-03-12T18:30:56Z"
},
{
"body": "At 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. \n\nWe 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.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2019-06-26T00:19:23Z",
"resolved_inferred": false,
"started_at": "2026-02-26T07:57:57Z",
"state": "resolved",
"title": "Websocket API with Incorrect Rate-Limits",
"updated_at": "2026-03-12T18:30:56Z"
},
{
"body": "Between 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. \n\nWe 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. \n\nThere was no impact to orders in the trading engine itself \u2013 just the presentation of the calculated orderbook for ETHUSD downstream of the trading engine. \n\nWe have deployed additional automated feed validators to detect potential similar issues in the future and to alert us earlier.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2019-06-24T19:36:17Z",
"resolved_inferred": false,
"started_at": "2026-02-26T07:57:57Z",
"state": "resolved",
"title": "ETHUSD Orderbook Issue",
"updated_at": "2026-03-12T18:30:56Z"
}
]
}