# Blueprint: Downtime Disqualification

**URL:** <https://forum.storj.io/t/blueprint-downtime-disqualification/5502>\
**Category:** design draft\
**Tags:** uptime, downtime, storagenode\
**Created:** [March 30, 2020, 1:28pm UTC](https://forum.storj.io/t/blueprint-downtime-disqualification/5502 "2020-03-30T13:28:57Z")\
**Posts on this page:** 1\
**Showing post:** 50

<div class="post-metadata">

**Author:** ![BrightSilence](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/brightsilence/32/6048_2.png) [@BrightSilence](https://forum.storj.io/u/BrightSilence)\
**Post date:** [April 1, 2020, 11:35am UTC](https://forum.storj.io/t/blueprint-downtime-disqualification/5502/50 "2020-04-01T11:35:34Z")

</div>

To be fair, that’s what the whole suspension system is about. Allowing you to recover from such errors.

A similar system is being worked on for audits, which would have helped in your case.

> [@Design Draft: Storage Node "Suspended" State](https://forum.storj.io/t/design-draft-storage-node-suspended-state/4606):
>
> Hi everyone, we are working on designing a plan for how to handle what we call “unknown” audit errors. In the past, we treated them the same way as normal audit failures, which caused a lot of nodes to get disqualified for simple configuration issues, rather than because they were trying to cheat. We have a blueprint for the new feature here, and would appreciate any feedback, big or small: [https://github.com/storj/storj/pull/3778](https://github.com/storj/storj/pull/3778)

---

_[View the full topic](https://forum.storj.io/t/blueprint-downtime-disqualification/5502)._
