New node will take about 20-24 GB every day untill it is vetted by europe north ( takes ~10 days) - my secondary node finished vetting yesterday.
Then it will split traffic 50-50.
there is some sort of 4 hour counter for if nodes are online or offline… this might do so that your new node didn’t register for 4 hours… 4 is 1/6th of a day…
we got 140ingress divided by 6 gives us 23gb extra because of the delay from your new node going online until the network adjusts for you having two nodes…
and then ofc reality isn’t always the same as theory… so your new node got just a bit above 20gb
now you will get the same ingress as the rest of us tomorrow…
it is an interesting thing tho… one could in theory make use of that 4hour delay… spin up 1000 nodes and gain 4000 hours of extra node ingress, ofc the overhead with doing that might not be worth the advantage gained…
but atleast in theory it works lol
1 Like
it’s only a delay if a node goes offline, not if a 2nd node comes online… If a 2nd node comes online, the ingress traffic will be split immediately.
Some stats from my nodes this month. All numbers are averages.
Nodes are almost exactly the same, but first two got full earlier.
stored: 7.040
repair: 0.00170
repairM: 0.05113
usage: 0.00325
usageM: 0.09755
stored: 7.040
repair: 0.00173
repairM: 0.05203
usage: 0.00320
usageM: 0.09603
stored: 6.784
repair: 0.00142
repairM: 0.04257
usage: 0.00544
usageM: 0.16318
stored: 6.904
repair: 0.00159
repairM: 0.04756
usage: 0.00556
usageM: 0.16669
Just for fun, here are stats from nodes I started yesterday, they’re not even a full day old. Daily usage on the fresh data here is higher than projected monthly usage on old data.
stored: 0.001
repair: 0.00000
repairM: 0.00000
usage: 0.28468
usageM: 8.54040
stored: 0.002
repair: 0.00000
repairM: 0.00000
usage: 0.23890
usageM: 7.16700
stored: 0.002
repair: 0.00000
repairM: 0.00000
usage: 0.18941
usageM: 5.68230
stored: 0.002
repair: 0.00000
repairM: 0.00000
usage: 0.20381
usageM: 6.11430then how do you explain why themightygeek’s new node made him go beyond what has been the only rule we have observed while doing this…
and it fits almost exactly with 4 hours of ingress extra… sure i made the assumption that it is the system that monitors which nodes are on the system that uses a 4 hour counter…
but in over 14 days now… nobody has ever gone beyond the max ingress of the day… and this happened on just the same day he made a new node… sorry i know this is just a hypothesis of mine, but imo it is the only thing that makes sense… and no matter we can easily test it… and i will one day when ingress goes back to 5mb/s lol
I think I found a way to cheat the held back system by spinning up a second node but I don’t know if it’s a good idea to post it on the forum…
you cannot count on the numbers the estimated payout gives you…it’s been wildly inaccurate until just recently… so will still be full of errors for atleast 6month still untill most of the common errors have been reported and fixed…
Well ingress on my big node did still increase by approximately 20GB.
Looks like inbound traffic spiked up when I added the second node but it’s still higher than the average traffic over the last few weeks.
how are we suppose to read that again?
a bit more detail about what the numbers mean… is it all in TB?
i also got 140gb ingress yesterday… just like you did and just like basically everybody else did… if their nodes didn’t have some sort of limitations.
i just think your new node took 4hours to be included in the count and thus it gets a slight start boost which made your ingress seems 1/6th higher than would usually be possible.
Maybe Mighty Greek showed his might ! he spun a node and everyone got the increase in traffic 
Sorry 
Stored is in TB, other numbers are ratios.
usage: 0.20381
means that on average egress usage on this node was 20.38% of data it has stored, per day
usageM: 6.11430
is the previous number multiplied by 30 to estimate total usage per month
repair numbers are similar, they represent repair upload.
there is no such rule… and I got 130GB ingress yesterday.
Also as you know I have 3 nodes and never did I encounter an increase of ingress. It’s technically impossible! The satellite has a list of nodes that are selected for upload and if your node goes offline, it’ll stay in that list for 4 hours. But if a new node comes online, it’ll be added to that list immediately (otherwise it would not receive data) and therefore the traffic gets split. It’s impossible that you suddenly get more ingress.
1 Like
yeah, first day is waaaay above average on my node too. But it quickly goes down as more data is collected.
I think what he means by rule it the fact that since the start of this thread no one reported an ingress of more than 130GB but again everyone seems to have had an increase in ingress yesterday.
thats funny because thats what the data has been saying for the last 14 days…
there was a max daily ingress which all nodes without limitation or issues would run into…
ofc it’s not a max in the sense of it being a set quantity, but as in nobody would be faster than that… even if they had multiple nodes, singular nodes, or super internet… all of the nodes would reach the exact same peak within 1% or a few % each day…
the data is pretty clear about that…
July 3rd
dragonhogan - ingress 17.75 - egress 19,58 = 1,89 ‰ of stored 10,31 TB
Mark - ingress 18.17 - egress 3,14 = unknown
SGC - ingress 17.40 - egress 19,34 = 1,77 ‰ of stored 10,9 TB
striker43 - ingress 25,2 - egress 36,93 = 3,62 ‰ of stored 10,2 TB
(had to extrapolate here so striker numbers are highly inaccurate)
4th July
Mark - ingress 57,97 - egress 3,14 = ‰ of stored
SGC - ingress 55,32 - egress 23,58 = 2,16 ‰ of stored 10,9 TB - (still with stability issues)
kevink - ingress 48.05 - egress 9,73 = 2.86 ‰ of stored - 3,4 TB approx
(seems slightly off, but have been changing/tinker numbers of nodes)
striker43 - ingress 57,75 (i will assume mark and striker are the two accurate numbers here)
dragonhogan - ingress 57,03 - egress 22,63 = 2,20 ‰ of stored 10,31 TB approx
July 5th
striker43 - ingress 105,81
SGC - ingress 104,20 - egress 32,39 = 2,97 ‰ of stored 10,9 TB
Kevink - ingress 106,07 - egress 17,61 = 5,18 ‰ of stored 3,4 TB approx
Krystof - ingress 106,15 - egress 38,24 = 3,55 ‰ of stored 11,85 TB
dragonhogan - ingress 101,62 - egress 34,74 = 3,37 ‰ of stored 10,31 TB approx
the mighty geek - ingress 105,45 - egress 6,27 = 5,22 ‰ of stored 1,2 TB
6th july
striker43 - ingress 112,83 - (missing egress)
dragonhogan - ingress 108,38 - egress 34,33 = 3,32 ‰ of stored 10,31 TB
TheMightyGeek - ingress 113,09 - egress 6,87 = 5,72 ‰ of stored 1,2
SCG - ingress 108,71 - egress 32,64 = 2,93 ‰ of stored 11,11TB
zagg - ingress 108,77 - egress 6,52 = 4,93 ‰ of stored 1,32 TB
7th july
TheMightyGeek - ingress 109,30 - egress 6,06 = 5.0 ‰ of stored - 1,3 TB
SGC - ingress 109,96 - egress 29,61 = 2.6 ‰ of stored - 11,21 TB
kevink - ingress 109,60 - egress 15,69 = 4.6 ‰ of stored - 3.4 TB approx
dragonhogan - ingress 104,21 - egress 29,11 = 2,8 ‰ of stored - 10,31TB
striker43 - ingress 109,76 - egress 25,58 = 2.5 ‰ of stored - 10,2TB
July 8th
TheMightyGeek - ingress 113,82 - egress 7,13 = 5.50 ‰ of stored 1,4 TB
SGC - ingress 114,14 - egress 36,49 = 3.20 ‰ of stored 11,33 TB
Dragonhogan - ingress 108,71 - egress 41,79 = 4,03 ‰ of stored 10,35 TB
striker43 - ingress 114,25 - egress 36,31 = 3,52 ‰ of stored 10,31 TB
9 July
Dragonhogan - ingress 98,57 - egress 67,20 = 6,41 ‰ of stored 10,48 TB
SGC - ingress 103,8 - egress 42,75 = 3.75 ‰ of stored 11,39 TB
TheMightyGeek - ingress 102,65 - egress 7,13 = 6,89 ‰ of stored 1,49 TB
kevink - ingress 102,73 - egress 45,78 = 12,71 ‰ of stored 3,60 TB
(exceeded 1% congratz - i kinda feel a bit left out egress wise lol)
JoshGarza - data inconclusive
10 july
Dragonhogan - ingress 107,53 - egress 67,20 = 6,75 ‰ of stored 10,47 TB
TheMightyGeek - ingress 105,78 - egress 7,13 = 6,81 ‰ of stored 1,6 TB
kevink - ingress 109,26 - egress 47,75 = 12,76 ‰ of stored 3,74 TB
SGC - ingress 109,89 - egress 47,02 = 4,07 ‰ of stored 11,54 TB
11 July
SGC - ingress 118,39 - egress 59,78 = 5,13 ‰ of stored 11,64 TB
TheMightyGeek - ingress 117,14 - egress 11,09 = 6,41 ‰ of stored 1,73 TB
kevink - ingress 117,66 - egress 44,19 = 11,5 ‰ of stored 3,84 TB
dragonhogan - ingress 115,75 - egress 73,64 = 6,97 ‰ of stored 10,56 TB
12 july
SGC - ingress 114,58 - egress 71,56 = 6,09 ‰ of stored 11,75 TB
TheMightyGeek - ingress 113,97 - egress 11,2 = 6,15 ‰ of stored 1,82 TB
kevink - ingress 113,68 - egress 37,18 = 9,40 ‰ of stored 3,95 TB
dragonhogan - ingress 111,00 - egress 68,49 = 6,41 ‰ of stored 10,68 TBI guess they started a new project/test on europe-north and uploaded more data, we’ll see if it keeps going like this or if it settles back down.
anyone else get this spike today…
@TheMightyGreek
see why one cannot use that graph for much…
from 250 to 375 in a day and then tomorrow it will most likely do a deep dive…
it’s numbers are so unreliable it’s ridiculous…
I actually had a slight dip compared to the day before yesterday even with the 120GB of ingress…
Yep, I saw it too. Looking at the “All Satellite” Graph and then drilling down to the individual satellite graphs, it appears that it’s the Saltlake satellite that has the most variation from day to day, and specifically had the big spike up yesterday. That satellite has always had some issues with reporting consistent space used data on a day-to-day basis.
1 Like