<html>
<head>
</head>
<body>
<div style="margin-left: auto; margin-right: auto; width: 50em;">

<div style="font-size: 120%; font-family: sans-serif; border: 1px solid black; background: yellow; margin-bottom: 2em; padding: 1em">

<h1>Sorry :-(</h1>
<h1>We can't provide you this site right now</h1>

<p>This website is unavailable due to emergency maintenance of the Wikidot.com 
service that it runs on. We will be updating this page with technical status 
updates.</p>

<p>Our regrets to all Wikidot users and users of sites running on Wikidot.
Once these problems are resolved we will be looking carefully at our systems
to make better failover, with more redundant servers.</p>
</div>

<hr/>

<div style="font-family: monospace">

<p><i>26 August, 17:33 CET:</i> Welcome back.  You're getting this page instead
of a uselss "500 Internal Server Error" on the Wikidot.com site you're trying to
access.</p>

<p><i>26 August, 17:25 CET:</i> Configuring the Lighttpd server so that the "500"
error message redirects automatically to this page.  Looking at www.lighthttpd.org
and realize it's actually hosted at Wikidot.com!  Oops.  Trying www.lighttpd.org 
instead but that does not respond.  Has the whole Internet died today? Ah, 
Google finds lighttpd.net...</p>

<p><i>26 August, 17:16 CET:</i> "500 - Internal Server Error".  The problem is back.
CPU usage at 100% (on all CPUs and the web service is giving errors).  We're switching
the DNS back to show this page.  No point in delivering tens of thousands of error
messages.</p>

<p><i>26 August, 17:03 CET:</i> When the DNS updates are done, all sites in the
wikidot.com domain should work.  So should all custom domains that resolve to
"wikidot.com".  To test this, try "ping <i>sitename</i>", and if it tells you
"74.86.235.236", then you will be OK (or whatever passes for "OK" right now).</p>

<p><i>26 August, 16:55 CET:</i> To heck with SoftLayer.  We're switching the DNS
back to the main server, using a fixed IP address.  It should take 15 minutes
for the DNS to refresh. Then we'll all be back on the main server and either it
will work, finally, or still crash. We are, incidentally, running a week-old
version of Wikidot.com so some sites may not work perfectly.</p>

<p><i>26 August, 16:52 CET:</i> Still no answer from SoftLayer :-/... but we keep
asking.</p>

<p><i>26 August, 16:27 CET:</i> Waiting for SoftLayer to fix the IP addresses.
Custom domains using the main server will almost work, but won't fetch stylesheets,
and won't load images, nor let you log in.</p>

<p><i>26 August, 16:15 CET:</i> We're talking to SoftLayer, asking why the portable
IPs don't work.  They are looking into it.  Hopefully they're faster than us at 
solving technical issues. :-/</p>

<p><i>26 August, 16:10 CET:</i> We have restarted the Wikidot.com service on the 
main server and some custom domains are now using it.  CPU load looks normal but
accessing web sites is <i>very</i> slow due.  We're not back to normal, yet.</p>

<p><i>26 August, 16:03 CET:</i> SoftLayer offers "portable IP addresses" but they really
do not seem to work.  We may need to move to a different hosting provider.  It is
essential to be able to switch to another box but keep the same IP address.</p>

<p><i>26 August, 15:50 CET:</i> We have spent the last half day testing different parts
of the service.  We can now exclude firewall problems, denial-of-service
attacks, database load, and network traffic.  The remaining culprit is the 
software that runs Wikidot.com.  We are now reverting to older versions to see
if a recent change was responsible. This is a slow process, sorry!</p>

<p><i>26 August, 15:43 CET:</i> This page is at 74.86.234.147, the backup server.  The 
main server is at 67.228.37.26.  We switched the DNS so that if you use 
<i>somename</i>.wikidot.com, you will see this page.  If you use a custom domain
and configured your DNS to use the 67.228.37.26 IP address, you may still be
landing on the main server.</p>

<p><i>26 August, 15:37 CET:</i> Wikidot.com has switched to a backup server but that is 
thrashing (out of memory).  Some people are reporting successful web site loads 
but overall it is not working.  We are taking down the service and replacing it 
with this static HTML page.</p>

<p><i>26 August, 14:00 CET:</i> It's been a frustrating morning of "500 Internal Server
Error" and failed AJAX requests.  Frustrating for us, unable to find the cause of this, 
and frustrating for the thousands of people trying to access their websites.</p>
</div>

</div>
</body>
</html>

