Cronologia delle interruzioni di Lmax

1. 16 ottobre 2026 alle ore 14:53 UTCidentified

   Il sito web LMAX (www.lmax.com) non è attualmente disponibile per alcuni utenti a causa delle modifiche necessarie al motore di hosting. Ci scusiamo per l'inconveniente e stiamo lavorando per ripristinare l'accesso completo. Forniamo un aggiornamento a breve.

2. 16 ottobre 2026 alle ore 15:01 UTCmonitoring

   Una soluzione è stata implementata e stiamo monitorando i risultati.

3. 16 ottobre 2026 alle ore 15:11 UTCresolved

   Questo incidente è stato risolto.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 22 maggio 2026 alle ore 06:49 UTCinvestigating

   We are investigating market data related incident that has started at 06:09 UTC

2. 22 maggio 2026 alle ore 08:11 UTCinvestigating

   We are currently investigating alternative solutions to restore service.

3. 22 maggio 2026 alle ore 09:18 UTCresolved

   Services are now restored.

1. 18 maggio 2026 alle ore 09:07 UTCinvestigating

   We are currently investigating the issue. Front End application is not affected by this incident. More updates to follow shortly.

2. 18 maggio 2026 alle ore 09:51 UTCmonitoring

   A fix has been successfully implemented and service is restored. We are currently monitoring the system.

3. 18 maggio 2026 alle ore 11:16 UTCresolved

   This incident has been resolved.

1. 14 maggio 2026 alle ore 13:14 UTCidentified

   We apologise for the downtime. The cause is unexpectedly prolonged maintenance that involved patching the underlying servers against some of the recent serious vulnerabilities. While we have been solving hiccups and gremlins we discovered during the patching, unfortunately the pre-set maintenance template resolved it automatically. Please accept our apologies. ETA: 1h.

2. 14 maggio 2026 alle ore 15:11 UTCresolved

   The extended UAT maintenance has been completed successfuly. We have released a new version of the software and conducted other urgent maintenance. Please accept our sincere apologies for the delay.

1. 30 aprile 2026 alle ore 03:59 UTCinvestigating

   Please be aware of an ongoing P1 incident affecting PERPS in Demo and Production. This is affecting both revenue and client trading. The issue is being investigated as a priority. More information to follow shortly.

2. 30 aprile 2026 alle ore 05:03 UTCidentified

   Re this ongoing incident, further to investigation, we have now identified a root cause. An emergency change is being prepared to resolve the issue, and we plan to bring PERPS Demo and Production back up shortly.

3. 30 aprile 2026 alle ore 07:23 UTCresolved

   Resolved: Release was pushed to both PERPS Demo and Production and we are back up and running now.

1. 29 aprile 2026 alle ore 13:25 UTCinvestigating

   We are currently investigating the issue where Crypto deposits are not showing full ledger information for Broker Clients.

2. 29 aprile 2026 alle ore 14:23 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 29 aprile 2026 alle ore 14:54 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 29 aprile 2026 alle ore 15:06 UTCresolved

   This incident has been resolved.

1. 5 marzo 2026 alle ore 09:52 UTCinvestigating

   We will be undergoing scheduled maintenance during this time.

2. 5 marzo 2026 alle ore 11:46 UTCresolved

   This incident has been resolved.

1. 20 febbraio 2026 alle ore 18:51 UTCinvestigating

   We are investigating incident related to internet connectivity.

2. 20 febbraio 2026 alle ore 19:17 UTCmonitoring

   We have recorded impact on the internet based services in London between 18:36 and 18:46 DST. We are currently monitoring the situation.

3. 20 febbraio 2026 alle ore 19:47 UTCresolved

   This incident has been resolved.

1. 2 febbraio 2026 alle ore 12:49 UTCinvestigating

   We are investigating an incident impacting emails sent from lmax.com and lmaxdigital.com domains to external contacts.

2. 2 febbraio 2026 alle ore 14:40 UTCmonitoring

   We have implemented a fix earlier this morning and are gradually recovering external outbound email service.

3. 2 febbraio 2026 alle ore 15:53 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 3 febbraio 2026 alle ore 07:58 UTCresolved

   This incident has been resolved.

1. 14 gennaio 2026 alle ore 13:24 UTCinvestigating

   We are currently investigating incident related to Perpetual Futures FIX trading.

2. 14 gennaio 2026 alle ore 14:01 UTCmonitoring

   We are monitoring the incident after applying the fix.

3. 14 gennaio 2026 alle ore 14:10 UTCresolved

   The incident has been resolved.

1. 12 dicembre 2025 alle ore 21:52 UTCidentified

   The issue has been identified and a fix is being implemented.

2. 12 dicembre 2025 alle ore 22:27 UTCresolved

   We are pleased to announce the incident has now been resolved. We investigated the issue, identified a fix, raised a change request for the proposed resolution and actioned the change. This has been tested and confirmed resolved.

1. 8 dicembre 2025 alle ore 10:19 UTCinvestigating

   Some clients reported rejections from https://api.lmaxtrader.com.

2. 8 dicembre 2025 alle ore 10:58 UTCmonitoring

   We have created a workaround for the issue. Some clients confirmed connectivity.

3. 8 dicembre 2025 alle ore 12:00 UTCresolved

   This incident has been resolved.

1. 18 novembre 2025 alle ore 14:12 UTCidentified

   Please note that DFX Trading Portal is currently unavailable. Please contact support if you wish to place a trade.

2. 18 novembre 2025 alle ore 14:55 UTCresolved

   The incident has been resolved as of 14:42 UTC.

1. 18 novembre 2025 alle ore 12:03 UTCinvestigating

   we are currently investigating the issue. Should have you have any issues logging in please do not hesitate to contact our LMAX Client Services team.

2. 18 novembre 2025 alle ore 12:59 UTCresolved

   Please note this incident is now resolved. For further queries, please do hesitate to contact our LMAX Client Services team via [email protected] or via +44 20 3192 2555.

1. 12 novembre 2025 alle ore 09:33 UTCinvestigating

   We are currently investigating this issue.

2. 12 novembre 2025 alle ore 11:08 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 12 novembre 2025 alle ore 11:45 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 12 novembre 2025 alle ore 13:36 UTCresolved

   This incident has been resolved.

1. 18 agosto 2025 alle ore 12:58 UTCresolved

   Trading was briefly suspended on the Production Perpetual Futures Exchange due to an issue connecting to a third-party pricing source. All functionality has now resumed; markets were opened at 13:55 BST.

1. 20 giugno 2025 alle ore 13:41 UTCinvestigating

   We are currently investigating the issue

2. 20 giugno 2025 alle ore 14:35 UTCresolved

   this incident has now been resolved.

1. 19 luglio 2024 alle ore 06:13 UTCinvestigating

   We are currently investigating incident impacting MT4 Retail service.

2. 19 luglio 2024 alle ore 08:12 UTCmonitoring

   We have implemented the workaround and are monitoring the incident

3. 19 luglio 2024 alle ore 09:04 UTCresolved

   The incident has been resolved

1. 8 luglio 2024 alle ore 20:14 UTCinvestigating

   We are currently investigating the issue with Live Chat. For urgent queries, please contact us via phone on + 44 20 3192 2555

2. 8 luglio 2024 alle ore 21:03 UTCresolved

   This incident has now been resolved

1. 20 giugno 2024 alle ore 19:30 UTCidentified

   There is currently an intermittent issue affecting some of services fronted by Cloudflare. Clients who are using impacted services will be getting 502 errors. This issue is logged on Cloudflare status page: https://www.cloudflarestatus.com/incidents/p7l6rrbhysck We are monitoring the issue and are prepared to take mitigation action should the problem worsen.

2. 20 giugno 2024 alle ore 20:05 UTCidentified

   Cloudflare posted updated on their status page: The issue has been identified and a fix is being implemented. Posted at 20:52 BST We are continuing to monitor the situation.

3. 20 giugno 2024 alle ore 20:18 UTCmonitoring

   A fix has been implemented and we are monitoring the situation.

4. 20 giugno 2024 alle ore 20:22 UTCresolved

   This incident has been resolved.