Wormsnet hostbuddy code#
Wormsnet hostbuddy Offline#
Wormsnet hostbuddy plus#

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). April 10–11, 2012 WormNET outage due to server failure. AugTemporary WormNET outage due to problems from Team17's ISP. ApW:A versions older than 3.6.31.0 can no longer connect to WormNET. MaUsers of W:A versions older than 3.6.31.0 start seeing a warning screen when connecting to WormNET. FebruHostingBuddy's memory corruption problem was fixed. JanuHostingBuddy dropped support for 3.6.28.0 users.

DecemHostingBuddy began warning 3.6.28.0 users of upcoming end of 3.6.28.0 support. November 28 – December 5 HostingBuddy maintenance. October 10–12, 2010 WormNET server nearly unusable due to considerable network lag (caused by problems at Team17's ISP). JA problem in HostingBuddy caused a large number of bogus (unjoinable) games to be hosted. Additionally, a problem in the replacement HostingBuddy instance caused a large number of bogus (unjoinable) games to be hosted. The server hosting the WormNET bots was down for most of the day. April 24–25, 2010 WormNET server was down for the weekend. Ma(later) Temporary Team17 network outage.

Wormsnet hostbuddy code#

March 17–18, 2010 Bug in bot timeout code caused the logging bot to remain disconnected from WormNET for over a day. MaThe logging bot failed to rejoin the channels due to an unknown reason. February 9–10, 2010 A WormNET restart left the bots outside the channels for a while. December 17–18, 2009 Several WormNET outages which left the bots outside the channels for a while. September 22–23, 2009 WormNAT2 server went down for 16 hours due to broken link dependencies. SeptemA large number of schemes have been added to HostingBuddy. Septem(marked by a red line) WebSnooper began logging activity in all WormNET channels. The problem causing random DNS outages is believed to have been fixed on the 25th. August 23–24, 2009 Another DNS outage that lasted a good part of the weekend. August 10–11, 2009 Planned outage due to network maintenance. AugTeam17 DNS servers were down for more than a few hours. JThe Team17 network was down while Team17 copied a file. JWormNET server was inaccessible for a few hours due to migration to another ISP. JA memory corruption bug that was causing instability in WormNAT2 was fixed, after a day of intensive on-site debugging. The WormNET statistics page was announced. 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. Febru(marked by a red line) Web Snooper was launched and began logging #AnythingGoes activity. Last recorded instance before a fix was implemented the next day. AugFirst recorded instance of game list flood. March 23–24, 2008 Game list was frozen for some time due to a WormNET problem. JHostingBuddy began its sporadic logging of #AnythingGoes activity.

Here is a list of major events that had an effect on the displayed statistics (whether directly or indirectly). Some events (indicated by a red line), such as game ID counter resets or gamelist flood, are handled specially to not disturb the statistics.

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. A game ID is basically an index which is incremented every time a game is hosted. The hosted games history is generated by interpolating pairs of WormNET game IDs and timestamps. 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. Up until September 14th 2009, WebSnooper was only present in #AnythingGoes, and thus didn't monitor activity in other channels. 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). This is why W:A users represent the majority in the version distribution chart, even though #AnythingGoes is mostly occupied by snooper users. WormNET activity is measured by channel joins (thus, a player joining a channel represents one activity measurement unit). Data for the WormNAT2 traffic graph at the bottom is provided by HostingProxy (the server component of WormNAT2).

Wormsnet hostbuddy plus#

WormNET hosted games history (see below) is provided from the above sources, plus older personal logs.

WormNET data since Februis provided by Web Snooper WormNET logs.

Wormsnet hostbuddy Offline#

Since HostingBuddy wasn't very stable and was occasionally put offline for long periods of time, there are gaps in the data.

WormNET activity before Februcomes from old HostingBuddy logs.

The WormNET statistics page is a collection of statistical information about WormNET activity.