Lumin Outage History

11 incidents recorded over the last 365 days, 11 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 Lumin Incident

Lumin incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 22, 2026Partial outage on Lumin APIs> This incident has been resolved and service is now operating normally. We apologize for any inconvenience this may have caused. This uptime notification was manually recorded.-4772 minResolved
Oct 22, 2026Full outage on Lumin Sign> This incident has been resolved and service is now operating normally. We apologize for any inconvenience this may have caused. This uptime notification was manually recorded.-4767 minResolved
Aug 3, 2026Lumin Statis is downThis incident has been resolved.-2790442 minResolved
Aug 3, 2026Lumin Web Backend is downThis incident has been resolved.-2790442 minResolved
Aug 3, 2026Lumin Web Viewer is downThis incident has been resolved.-2790442 minResolved
Aug 3, 2026This is an example incidentWhen your product or service isn’t functioning as expected, let your customers know by creating an incident. Communicate early, even if you don’t know exactly what’s going on.-2809494 minResolved
Aug 3, 2026Lumin Community is downThis incident has been resolved.-2790442 minResolved
Aug 3, 2026Some customers are experiencing an issue accessing documents stored in Lumin foldersThis incident has been resolved. All systems are operational-1717968 minResolved
Aug 3, 2026Lumin Authentication Systems are downThis incident has been resolved.-924035 minResolved
Aug 3, 2026Customers are experiencing issues with Teams and Sharepoint integrationThis incident was resolved. This incident was caused by a configuration error, which allowed Lumin to become the default file handler for file types other than PDF-940650 minResolved
Aug 3, 2026Lumin Tools is downThis incident has been resolved.-2790442 minResolved

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 Lumin 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 Lumin 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 Lumin 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.