An operation that commits to a cube-based ASRS is concentrating its fulfillment into one machine, so the reliability question deserves a specific answer, not a brochure adjective. The good news for buyers: cube storage is the ASRS category where reliability is easiest to engineer, because a fleet of interchangeable robots has no equivalent of the crane that blocks an entire aisle when it fails. The vendors know it, and the leading cube systems all publish reliability claims worth examining closely.
This guide compares how the cube-based systems achieve uptime, what each vendor actually publishes, and how a high-uptime operation should verify the claims before signing.
Why Cube Architecture Starts Ahead on Reliability
Traditional crane-based ASRS designs concentrate risk: one crane serves an entire aisle, so one failure takes every location in that aisle offline. Industry maintenance literature calls an ASRS without redundant design "a multi-million-dollar single point of failure," with automated warehouse downtime benchmarked at $5,000 to $50,000+ per hour.
Cube systems distribute that risk across a robot fleet. Any robot can retrieve any bin and deliver to any workstation, so a single robot failure removes a slice of capacity instead of stopping the operation. That's the architectural baseline for the whole category. The differences between cube systems live one level down: where robots operate, how they charge, where maintenance happens, and what degrades when things go wrong.
The Cube Systems, Compared on Reliability
Attabotics — Full 3D Movement, Ground-Level Everything
Attabotics' reliability case is architectural, per the company's published specs:
- No single point of failure. The system keeps working if an Attabot™ robot goes down. Robots are interchangeable fleet members with direct access to any storage location, so remaining robots absorb the work without a zone going dark.
- Ground-level maintenance bays. All robot maintenance happens at ground level. Nobody works on top of the structure, no maintenance platform is required up high, and servicing a robot doesn't idle the cube.
- No battery infrastructure. Robots recharge on supercapacitors while working inside the structure. That removes battery swaps, charging bays, battery lifecycle management, and charging downtime as failure and maintenance categories entirely.
- Degradation stays graceful under load. Because robots travel in three dimensions with direct access to every bin, there's no bin-digging workload to reroute when capacity drops. Fewer robots means proportionally slower, not structurally different.
- Replacement without interruption. New robots and workstations install while the operation runs, so lost capacity is restored without a shutdown window.
- Purpose-built software. The control software operates this one system and nothing else, handling sequencing, sortation, and conveyance, with optional continuous 5G communication to the robots.
Attabotics states the result as the highest uptime of any cube-based ASRS. The company doesn't publish a percentage behind that claim, which cuts both ways: treat it as a design argument to verify against the architecture above and against reference deployments. The longest-running public proof is Gordon Food Service's Calgary distribution center, in continuous operation since 2018 through food-distribution peak seasons, with a 2X throughput efficiency improvement over the partnership.
AutoStore — Grid Design With a Published Track Record
AutoStore publishes the most complete reliability numbers in the category: 99.7% uptime measured across hundreds of installed systems, customer-achieved mean time between failures over 3,000 hours, and no single point of failure, with any robot able to collect any bin for any port. Self-diagnostic and AI-driven preventative maintenance reduce intervention needs.
The grid design's reliability considerations sit in its mechanics: robots operate on top of the stacked-bin grid, so robot recovery and servicing involve the grid's top surface, and buried bins require digging even in normal operation. When fleet capacity drops, the digging workload concentrates on fewer robots, which shapes how performance degrades at the margin. Robots are battery-powered, making charging infrastructure part of the maintenance surface.
None of that undercuts a strong published record. It defines what to ask about: how service reaches a robot mid-grid, what happens to bin-dig latency during partial outages, and how charging cycles are scheduled against peak windows.
Ocado's OSRS — The Third Cube Player
Ocado's Storage and Retrieval System brings grid-based cube storage to the market through Ocado Intelligent Automation, primarily in grocery. Ocado publishes far less system-level reliability data than the other two, so evaluations should request uptime and MTBF figures directly and weigh the answer against the published benchmarks above.
Reliability Scorecard at a Glance
| Factor | Attabotics (full 3D) | AutoStore (grid) |
|---|---|---|
| Published uptime | "Highest of any cube-based ASRS" (no % published) | 99.7% across installed base |
| MTBF | Not published | 3,000+ hours (customer-reported) |
| Single point of failure | None (vendor claim) | None (vendor claim) |
| Robot access model | 3D travel, direct to any bin | Top of grid, dig to buried bins |
| Maintenance location | Ground-level bays | Grid top surface |
| Charging | Supercapacitors, charge while working | Battery, scheduled charging |
| Capacity restoration | Add robots without stopping | Add robots to grid |
Both vendors' figures are their own published claims, presented for comparison rather than adjudicated. The architecture rows are where an evaluation can verify independently.
How High-Uptime Operations Should Verify
Uptime claims are hypotheses; deployments are evidence. Four checks separate the two:
- Walk the failure scenarios. One robot down, one workstation down, control software restart, power interruption. Ask each vendor what keeps running, what degrades, and by how much.
- Ask where the wrench goes. Have the vendor physically show where a failed robot is recovered and serviced, and what that does to live operations while it happens.
- Interrogate the charging model. Scheduled charging is a capacity tax and a failure surface; charge-while-working designs remove both. Ask how each system behaves when peak volume and charging windows collide.
- Call the longest-tenured reference. Ask their operations team, not the vendor: worst downtime event, cause, recovery time, and what planned maintenance actually costs in hours per month. A system running continuously in one building since 2018 tells you more than any percentage.
FAQ
What is the most reliable cube-based ASRS?
Both leading cube systems claim no single point of failure. AutoStore publishes the strongest numbers: 99.7% uptime and 3,000+ hour MTBF across its installed base. Attabotics claims the highest uptime of any cube-based ASRS on architectural grounds: full 3D robot access with no digging, ground-level maintenance, supercapacitor charging with no downtime, and robot replacement without stopping the system. High-uptime operations should verify both claims against failure scenarios and reference deployments.
Why is cube storage more reliable than crane-based ASRS?
Crane systems concentrate risk: one crane serves an entire aisle, so one failure blocks every location in it. Cube systems distribute work across a fleet of interchangeable robots, so a single failure removes a small slice of capacity instead of stopping the operation.
Do cube storage robots need charging downtime?
It varies by design. AutoStore robots run on batteries with scheduled charging. Attabotics robots recharge on supercapacitors while working inside the structure, so there is no charging downtime, battery swap labor, or battery infrastructure to maintain.
How is a failed robot serviced in a cube system?
In Attabotics' design, all maintenance happens at ground-level bays, and the cube keeps operating during service. In grid designs, robots operate on the grid's top surface, so recovery and servicing involve that surface. Ask every vendor to demonstrate the recovery procedure live.
What downtime costs should high-uptime operations plan around?
Industry benchmarks put automated warehouse downtime at $5,000 to $50,000+ per hour depending on throughput. That range is the reason failure behavior, not headline uptime percentage, should drive the evaluation: the same 99.7% means something different if the remaining 0.3% arrives as one long stoppage versus brief, partial slowdowns.
Conclusion
Cube-based ASRS is the right category for high-uptime operations, and the reliability choice within it comes down to architecture you can verify. AutoStore brings the category's best published track record. Attabotics removes entire failure categories by design: no digging, no batteries, no top-of-structure maintenance, no shutdown to restore capacity. Since both claim no single point of failure, make the vendors prove the claim your way: walk the failure scenarios, watch a robot recovery, and call the reference that's been running longest. Uptime isn't a number on a spec sheet; it's how the system behaves on its worst day, and you can find that out before you buy.
