Data for the WormNAT2 traffic graph at the bottom is provided by HostingProxy (the server component of WormNAT2).WormNET activity is measured by channel joins (thus, a player joining a channel represents one activity measurement unit). This is why W:A users represent the majority in the version distribution chart, even though #AnythingGoes is mostly occupied by snooper users. For the same reasons, spikes of snooper activity can be observed on days when the bot collecting the logs was restarted several times (since it counts users already present on WormNET every time it connects). Up until September 14th 2009, WebSnooper was only present in #AnythingGoes, and thus didn't monitor activity in other channels. Logging all WormNET channels caused an increase in measured activity, and thus the long-term statistics have been reset to data collected since this date. The hosted games history is generated by interpolating pairs of WormNET game IDs and timestamps. A game ID is basically an index which is incremented every time a game is hosted. Thus, having two pairs of game ID/timestamps, we know the exact number of games hosted (and can estimate WormNET activity) in that time period. Some events (indicated by a red line), such as game ID counter resets or gamelist flood, are handled specially to not disturb the statistics. Here is a list of major events that had an effect on the displayed statistics (whether directly or indirectly). JHostingBuddy began its sporadic logging of #AnythingGoes activity. March 23–24, 2008 Game list was frozen for some time due to a WormNET problem. AugFirst recorded instance of game list flood. Last recorded instance before a fix was implemented the next day. Febru(marked by a red line) Web Snooper was launched and began logging #AnythingGoes activity. Old W:A versions started getting an error message when connecting to WormNET, due to connecting to WormNET by its IP address which was about to change. The WormNET statistics page was announced. JA memory corruption bug that was causing instability in WormNAT2 was fixed, after a day of intensive on-site debugging. JWormNET server was inaccessible for a few hours due to migration to another ISP. JThe Team17 network was down while Team17 copied a file. AugTeam17 DNS servers were down for more than a few hours. August 10–11, 2009 Planned outage due to network maintenance. August 23–24, 2009 Another DNS outage that lasted a good part of the weekend. The problem causing random DNS outages is believed to have been fixed on the 25th. Septem(marked by a red line) WebSnooper began logging activity in all WormNET channels. SeptemA large number of schemes have been added to HostingBuddy. September 22–23, 2009 WormNAT2 server went down for 16 hours due to broken link dependencies. December 17–18, 2009 Several WormNET outages which left the bots outside the channels for a while. February 9–10, 2010 A WormNET restart left the bots outside the channels for a while. MaThe logging bot failed to rejoin the channels due to an unknown reason. March 17–18, 2010 Bug in bot timeout code caused the logging bot to remain disconnected from WormNET for over a day. Ma(later) Temporary Team17 network outage. April 24–25, 2010 WormNET server was down for the weekend. The server hosting the WormNET bots was down for most of the day. Additionally, a problem in the replacement HostingBuddy instance caused a large number of bogus (unjoinable) games to be hosted. JA problem in HostingBuddy caused a large number of bogus (unjoinable) games to be hosted. October 10–12, 2010 WormNET server nearly unusable due to considerable network lag (caused by problems at Team17's ISP). November 28 – December 5 HostingBuddy maintenance. DecemHostingBuddy began warning 3.6.28.0 users of upcoming end of 3.6.28.0 support. JanuHostingBuddy dropped support for 3.6.28.0 users. FebruHostingBuddy's memory corruption problem was fixed. MaUsers of W:A versions older than 3.6.31.0 start seeing a warning screen when connecting to WormNET. ApW:A versions older than 3.6.31.0 can no longer connect to WormNET. AugTemporary WormNET outage due to problems from Team17's ISP. April 10–11, 2012 WormNET outage due to server failure. April 11–12, 2012 Partial WormNET malfunction due to misconfiguration of new server (W:A failed to host non-passworded games, HostingBuddy failed to host games).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |