LMAX status history
Current state: operational — “All Systems Operational” per https://status.lmax.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do LMAX incidents last?
From 15 incidents with a vendor-posted start and resolve time. Longest on record: Delays in external emails sent from lmax.com and lmaxdigital.com — 19.1 h (2026-02-02 12:49 UTC). Excluded, never estimated: 3 scheduled maintenance. 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 (18)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-09-12 09:00 UTC | Exchange Maintenance | maintenance | maintenance | 27 h 30 min (approx.) |
| 2026-09-10 11:48 UTC | Digital UAT Maintenance | maintenance | maintenance | 24 h 41 min (approx.) |
| 2026-09-05 09:00 UTC | Exchange Maintenance | maintenance | maintenance | 27 h 28 min (approx.) |
| 2026-05-22 06:49 UTC | LMAX Perpetual Futures - Pricing Incident | resolved | major | 2 h 28 min |
| 2026-05-18 09:07 UTC | LMAX SWAPS X-Bridge Related incident | resolved | none | 2 h 08 min |
| 2026-05-14 13:14 UTC | Prematurely closed UAT Maintenance | resolved | major | 1 h 57 min |
| 2026-04-30 03:59 UTC | P1 - INC0024145 - PERPS issue in Prod and Demo | resolved | none | 3 h 24 min |
| 2026-04-29 13:25 UTC | LMAX Global: Crypto Deposits in Broker | resolved | minor | 1 h 41 min |
| 2026-03-05 09:52 UTC | UAT Maintenance | resolved | none | 1 h 53 min |
| 2026-02-20 18:51 UTC | Internet Connectivity problem | resolved | none | 56 min |
| 2026-02-02 12:49 UTC | Delays in external emails sent from lmax.com and lmaxdigital.com | resolved | minor | 19 h 09 min |
| 2026-01-14 13:24 UTC | Perpetual Futures FIX Trading | resolved | none | 46 min |
| 2025-12-12 21:52 UTC | PD #1525: Digital broker's custodian 2 integration has stopped detecting deposits after kit44 patch release. | resolved | none | 35 min |
| 2025-12-08 10:19 UTC | Java API rejections in London Professional | resolved | minor | 1 h 40 min |
| 2025-11-18 14:12 UTC | DFX Trading Portal is unavailable | resolved | none | 42 min |
| 2025-11-18 12:03 UTC | LMAX Global Trading platform down | resolved | minor | 56 min |
| 2025-11-12 09:33 UTC | Perpetual Futures Order Entry UAT Outage | resolved | critical | 4 h 03 min |
| 2025-08-18 12:30 UTC | Pyth price not updating in Perpetual Futures | resolved | none | 0 min |
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 LMAX with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"lmax"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}