AutoStore Outage History

18 incidents recorded over the last 365 days, 8 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 AutoStore status99.90% uptime history

Every Recorded AutoStore Incident

AutoStore incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Dec 9, 2026Routine MaintenanceWe will be doing routine maintenance on the Qubit application from 05:00-06:00 UTC on 2026-12-09, a small window of downtime may occur.1h 0mScheduled
Nov 11, 2026Routine MaintenanceWe will be doing routine maintenance on the Qubit application from 05:00-06:00 UTC on 2026-11-11, a small window of downtime may occur.1h 0mScheduled
Oct 22, 2026Short email notification internmittentEmail notifications for live events did not work between 09:51 and 10:02 UTC+2. Users with email alerts enabled did not receive notifications during this brief period. The impact was minimal, and most users were…-24 minResolved
Oct 13, 2026Routine MaintenanceThe scheduled maintenance has been completed.1h 0mScheduled
Sep 8, 2026Routine MaintenanceThe scheduled maintenance has been completed.1h 0mScheduled
Sep 2, 2026Release Rollout - Production OutageThis incident has been resolved.2h 30mResolved
Aug 11, 2026Routine MaintenanceThe scheduled maintenance has been completed.1h 0mScheduled
Jul 14, 2026Routine MaintenanceThe scheduled maintenance has been completed.1h 0mScheduled
Jun 24, 2026Reports of Transient LatencyThis incident has been resolved. Investigates continue, as no root cause is immediately obvious. However, latency across sites has been reported as all clear.214h 45mResolved
Jun 10, 2026Potential Product Update LatencyFix has been deployed and team has monitored over the last hour. Setting to resolve.4h 34mResolved
Jun 10, 2026Routine MaintenanceThe scheduled maintenance has been completed.1h 0mScheduled
May 13, 2026Unsuccessful LogoutThis incident has been resolved.1h 24mResolved
Apr 15, 2026Qubit Network Maintenance WindowThe scheduled maintenance has been completed.1h 0mScheduled
Apr 8, 2026Potential Task Latency ExperiencedAfter continued monitoring for the past hour we have decided to resolve this incident. If you still experience post incident symptoms, please submit a case outlining details of the incident and we will investigate…2h 10mResolved
Mar 11, 2026Qubit Network MaintenanceThe scheduled maintenance has been completed.1h 0mScheduled
Feb 11, 2026Azure Key Vault MaintenanceThe scheduled maintenance has been completed.1h 0mScheduled
Feb 2, 2026Simulator Web App not loadingThis incident has been resolved.2h 50mResolved
Dec 10, 2025Label Printing at select sitesIncident has been resolved. Confirmation from impacted sites that label printing is working as expected.1h 17mResolved

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 AutoStore 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 AutoStore 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 AutoStore 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 AutoStore outage in this window ran 8d 22h, against a mean recovery of 14h 5m. If you depend on AutoStore 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.