Luzmo Outage History
3 incidents recorded over the last 365 days, 3 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 Luzmo Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 23, 2026 | Security update: Luzmo not affected by PHP2Shell; patched for Node.js Brotli and eMudhra issues | 311h 46m | Resolved |
| Oct 2, 2026 | Issue with Snowflake connector | 808h 45m | Resolved |
| Jun 1, 2026 | Higher latency and error rate on Warp | 2194h 27m | 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 Luzmo 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 Luzmo 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 Luzmo 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 Luzmo outage in this window ran 91d 10h, against a mean recovery of 46d. If you depend on Luzmo 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.