iLOQ Outage History

26 incidents recorded over the last 365 days, 17 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.

Live iLOQ status98.43% uptime history

Every Recorded iLOQ Incident

iLOQ incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Sep 23, 2026Major Incident: Service Outage Impacting iLOQ S10 in AWS SwedenThis incident has been resolved.3h 12mResolved
Sep 22, 2026Scheduled maintenance pre-notice - Server maintenance AWS GBR / SWE / GER / CHEThe scheduled maintenance has been completed.0 minScheduled
Sep 22, 2026Scheduled maintenance pre-notice - Server maintenance AWS AUSThe scheduled maintenance has been completed.2h 0mScheduled
Sep 22, 2026Scheduled maintenance pre-notice - Server maintenance AWS USA / CanadaThe scheduled maintenance has been completed.2h 0mScheduled
Sep 18, 2026Major Incident: Multi-Region Outage Impacting 5 Series+This incident has been resolved.3h 50mResolved
Jul 15, 2026KeyScheduler issues in AWS Germany–based 5 Series locking systemsThis incident has been resolved.7h 43mResolved
Jun 10, 2026Degraded performance in AWS StockholmThis incident has been resolved.41 minResolved
Jun 7, 2026Degraded performance in AWS StockholmThis incident has been resolved.12h 15mResolved
Jun 6, 2026Degraded performance in AWS StockholmThis incident has been resolved.4h 39mResolved
Jun 6, 2026Degraded performance in AWS StockholmThis incident has been resolved.4h 12mResolved
May 8, 2026Degraded performance in Telia datacenterThis incident has been resolved.17h 21mResolved
Apr 22, 2026Degraded performance in 5 Series on AWS StockholmThis incident has been resolved.1h 21mResolved
Apr 22, 2026Degraded performance in 5 Series on AWS StockholmThis incident has been resolved.9 minResolved
Apr 21, 2026Scheduled maintenance pre-notice - Fujitsu FinlandThe scheduled maintenance has been completed.6h 0mScheduled
Apr 10, 2026iLOQ 5 Series+ phone keys stop functioningThis incident has been resolved.5h 59mResolved
Apr 10, 2026N501 device performance problemsThis incident has been resolved.10h 54mResolved
Jan 21, 2026Degraded performance in 5 Series on AWS GermanyThis incident has been resolved.49 minResolved
Jan 1, 2026Problems with email registration impacting iLOQ S50 and HOME applicationsThis incident has been resolved.13h 52mResolved
Dec 15, 2025Scheduled maintenance pre-notice - Server maintenance AWS Frankfurt / StockholmThe scheduled maintenance has been completed.3h 0mScheduled
Dec 15, 2025Scheduled maintenance pre-notice - Server maintenance AWS SydneyThe scheduled maintenance has been completed.2h 0mScheduled
Dec 15, 2025Scheduled maintenance pre-notice - Server maintenance AWS USA / CanadaThe scheduled maintenance has been completed.1h 0mScheduled
Nov 26, 2025Service interruption affecting Alerta clients on the Fujitsu platformThis incident has been resolved.5h 16mResolved
Nov 17, 2025Degraded performance in 5 Series on AWS StockholmThis incident has been resolved.61h 34mResolved
Nov 13, 2025Issue related to iLOQ HOME functionalityThis incident has been resolved.2h 19mResolved
Nov 12, 2025Scheduled maintenance pre-notice - Server maintenance AWS Frankfurt / StockholmThe scheduled maintenance has been completed.3h 0mScheduled
Nov 9, 2025Scheduled maintenance Fujitsu FINThe scheduled maintenance has been completed.1h 15mScheduled

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 iLOQ 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 iLOQ 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 iLOQ 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 iLOQ outage in this window ran 2d 13h, against a mean recovery of 6h 47m. If you depend on iLOQ 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.