That is a CDN customer that is using the storj network to deliver software updates. Should be fine. Hopefully that customer is happy with the service and will keep doing it.
It is not the first time. In the first 24 hours they downloaded about 200 TB (reading from yesterday. Today it might be 400). In the last 30 days it was 600 TB. So they have been active all the time. We have seen these spiks previously. What has changed is the duration. I now get these spiks for hours. For the past 2 days now. I believe that is new. I hope that CDN customer is happy with our service.
(I wonder if they might be doing it on purpose. Like a business decision on their end. Old plan might be to slowly migrate data over to us, chapter 11 hits us, they decided lets risk it and hope it makes both sides more successful in the long run)
Later today I have to run the numbers for my nodes to see if it makes sense to upgrade my internet connection. This amount of paid egress traffic should allow me that. (Except that I have agreed to a $0 payout rate. I might upgrade the internet connection anyway to increase the chances)
That is more of a visual glitch. One of the satellites has not completed a full tally run and that means your node gets no datapoint to display. For the final payout it doesn’t matter because the next day will include that missing tally. Reason for all this is that we cut the infrastructore costs down a lot. All of our services have been moved to self hosted. And there are still some side effect.
You might also notice a high amount of trash. In your case 7.something TB / 10.83 TB. Same reason. No bloomfilter for US1 for a month. That was fixed yesterday. Your node should have received that bloomfilter already and over the next days your node should mark a lot of pieces as trash. Nothing scary. Just another aftermatch of the infrastructure cost saving. Should get more stable over time.
It wasn’t dropped, it’s missing datapoints. This graph is used only for the dashboard and payout estimation on the same dashboard (which is wrong due to missing datapoints), the real payout is calculated based on the orders sent by your node.
However, this visual issue should be fixed in the next release, thanks to @Aleksman4o for their PR.