# Ping satellite: check-in ratelimit: node rate limited by id, errorVerbose": "ping satellite: check-in ratelimit: node rate limited **URL:** \ **Category:** troubleshooting\ **Tags:** authorization-token, identity, offline\ **Created:** [July 11, 2021, 8:16am UTC](https://forum.storj.io/t/ping-satellite-check-in-ratelimit-node-rate-limited-by-id-errorverbose-ping-satellite-check-in-ratelimit-node-rate-limited/14556 "2021-07-11T08:16:35Z")\ **Posts on this page:** 1\ **Showing post:** 18
**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\ **Post date:** [September 28, 2021, 7:03am UTC](https://forum.storj.io/t/ping-satellite-check-in-ratelimit-node-rate-limited-by-id-errorverbose-ping-satellite-check-in-ratelimit-node-rate-limited/14556/18 "2021-09-28T07:03:46Z")
> [@Sleepy\_PIP](#): > > significant delays on WiFi The WiFi is the reason. The storagenode is a server, it must have a stable connection. otherwise it would have a low reputation (and you just prove that). > [@Sleepy\_PIP](#): > > why the following may happen - `2021-09-27T07:17:30.556+0300 INFO pieces to reupload canceled ` This is variation on subject [Error piercestore protocol: rpc error: code = canceled desc = context canceled](https://forum.storj.io/t/error-piercestore-protocol-rpc-error-code-canceled-desc-context-canceled/970), your node were too slow to receive a piece and loosed the race. > [@Sleepy\_PIP](#): > > I disabled all firewalls and antiviruses Please, enable them back and configure to allow traffic to/from the node. Please, consider to switch to a wire connection instead of WiFi. I’m not sure that powerline would be significant better, I’m more confident in twisted pair so I would recommend to use this method instead, if possible. --- _[View the full topic](https://forum.storj.io/t/ping-satellite-check-in-ratelimit-node-rate-limited-by-id-errorverbose-ping-satellite-check-in-ratelimit-node-rate-limited/14556)._