Events
Why the numbers changed. Each entry explains a change you can see in our data: a network joining or leaving the totals, or a sudden jump or drop in its users or channels. It is dated when our data changed, which can be later than what happened on the network itself. Where we know more, we add our own commentary.
Monday 17 August 2026
-
-2,418Rizon channels dipped from 6,610 to 4,192 for 30 minutes, then recovered at 6,608
-
-2,420Rizon channels dipped from 6,612 to 4,192 for 30 minutes, then recovered at 6,561
-
-2,419Rizon channels dipped from 6,616 to 4,197 for 30 minutes, then recovered at 6,614
-
-2,415Rizon channels dipped from 6,632 to 4,217 for 30 minutes, then recovered at 6,638
Sunday 16 August 2026
-
-2,417Rizon channels dipped from 6,615 to 4,198 for 30 minutes, then recovered at 6,616
-
-2,417Rizon channels dipped from 6,607 to 4,190 for 30 minutes, then recovered at 6,611
-
-2,420Rizon channels dipped from 6,640 to 4,220 for 30 minutes, then recovered at 6,643
-
-2,417Rizon channels dipped from 6,641 to 4,224 for 30 minutes, then recovered at 6,641
How this works
Every figure on erkstats comes from our collectors polling each network. A network that doesn't answer keeps its last reading for 36 hours, so a short outage doesn't move the totals; after that it drops out until it answers again. A sudden change is noted when a network moves more than 25% outside its normal range over the previous 24 hours, and only for networks with at least 200 users (or 100 channels), so the daily ebb and flow isn't listed.
We can only see what our data shows. We don't know why a network changed, and a drop on our side can mean the network had trouble or that our collectors couldn't reach it.