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.
Saturday 15 August 2026
-
+2,419Rizon channels back to normal, 4,201 to 6,620
-
+2,298WixChat users back to normal, 4,328 to 6,626; channels back to normal, 86 to 171
-
-2,796WixChat users dipped from 6,626 to 3,830 for 4 hours, then recovered at 6,631; channels dipped from 171 to 82 for 4 hours, then recovered at 173
-
-3,867FlexChat users dipped from 3,902 to 35 for 2 hours, then recovered at 4,306
-
-2,418Rizon channels dipped from 6,619 to 4,201 for 30 minutes, then recovered at 6,611
-
-2,419Rizon channels dipped from 6,619 to 4,200 for 30 minutes, then recovered at 6,617
-
-2,418Rizon channels dipped from 6,653 to 4,235 for 30 minutes, then recovered at 6,659
-
-2,416Rizon channels dipped from 6,673 to 4,257 for 30 minutes, then recovered at 6,626
-
+77
LibraIRC users spiked from 199 to 276 for 2 hours, then settled at 213
-
-2,268WixChat users fell from 6,625 to 4,357 (-34%); channels fell from 170 to 86 (-49%)
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.