# Rskj full node uptime requirement

**URL:** <https://research.rsk.dev/t/rskj-full-node-uptime-requirement/209>\
**Category:** Uncategorized\
**Created:** [July 27, 2021, 6:25pm UTC](https://research.rsk.dev/t/rskj-full-node-uptime-requirement/209 "2021-07-27T18:25:02Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![light](https://yyz2.discourse-cdn.com/flex036/user_avatar/research.rsk.dev/light/32/59_2.png) [@light](https://research.rsk.dev/u/light)\
**Post date:** [July 27, 2021, 6:25pm UTC](https://research.rsk.dev/t/rskj-full-node-uptime-requirement/209/1 "2021-07-27T18:25:02Z")

</div>

If I am running an rskj node does it require 24/7 uptime, or can it handle being turned on and off for periods of time? I ask because my experience running geth for Ethereum is that it does not like to be turned off for more than a few hours, or else it will want to be re-synced when I turn it back on again. Whereas with Bitcoin Core, I can sync it, turn it off for weeks or even months, then turn it back on again and it will continue syncing to the chain tip with no problem. Is rskj more like geth or more like Bitcoin Core in this regard?

---

<div class="post-metadata">

**Author:** ![adrian.eidelman](https://avatars.discourse-cdn.com/v4/letter/a/a9a28c/32.png) [@adrian.eidelman](https://research.rsk.dev/u/adrian.eidelman)\
**Post date:** [July 30, 2021, 1:22pm UTC](https://research.rsk.dev/t/rskj-full-node-uptime-requirement/209/2 "2021-07-30T13:22:13Z")

</div>

Hi John,

RSK node will resume syncing after restart, continuing from the last block it processed before being turned off. We’ve seen some exceptional cases where the database would not shutdown properly, and this causes the node not to be able to continue syncing properly, so we recommend turning nodes off by running ‘service rsk stop’ command.

Hope it helps!