Webserver Status

Scheduled Maintenance And Other Outages.

If there is nothing marked as unresolved in the section below, Quillcards should be running OK.

All times are Coordinated Universal Time (UTC), which is for all practical purposes the same as Greenwich Mean Time or London Time. You can read more about Universal Time here.

Scroll down for the latest updates.

History

1.30 a.m UTC., Tuesday, September 30, 2008 : Hardware swap in progress – site may be unobtainable for a couple of hours.

1.47a.m UTC., Tuesday, September 30, 2008 : Site back up.
———

9.00p.m UTC., Sunday, July 26, 2009 to 1a.m Monday July 27, 2009 : Scheduled maintenance will take place over a period of 3 to 4 hours. There are expected to be several short outages (1-3 minutes) during this period.

11.58 p.m UTC., Sunday, July 26, 2009 : Maintenance completed.
———

8.35 a.m UTC., Wednesday, October 29, 2009 : Scheduled maintenance is taking place to upgrade the blog. An outage of one hour is expected. This should only affect the blog, and the main part of the site should be unaffected.

9.25 a.m UTC., Wednesday, October 29, 2009 : Upgrade completed. There will be another short maintenance update in the next day or two – details to follow.
———

00.30 a.m UTC., Monday, December 07, 2009 : Server hardware swap in progress – the site is down and should be back up by 2a.m. UTC.

01.40 a.m UTC., Monday, December 07, 2009 : Site back up.
———

7.50 p.m UTC., Thursday, August 19, 2010 : The server has been behaving erratically and is being looked at- the site is down with the first unexpected outage in more than a year.

7.07 p.m UTC., Thursday, August 19, 2010 : The cause of the issue appears to be a failed drive, which will be replaced as soon as possible. The site was back up at 7.57p.m. and then down again. It is now up again.

00.01 a.m. UTC Friday August 20, 2010 : Update: Server offline to swap out a bad drive – 0000UTC.”

01.40 a.m UTC., Friday, August 20, 2010 : Site back up.
———

12.34 p.m. UTC Wednesday, August 25, 2010 : There was an unexpected outage for several hours beginning in the early hours of this morning. The site came back up at 7.24 a.m. and is running now. Our web host is investigating the cause of the outage.
———

11.30 p.m. UTC Sunday, August 29, 2010 : There were two short network outages at the Dallas datacenter affecting more than a hundred hosts, including Quillcards. The site was down from about ten minutes from 6.00 p.m. and then again for a couple of minutes starting at about 6.20 p.m. The outages are attributed to a denial of service attack affecting the host’s network. The site is up and running normally now.
———

01.00a.m. UTC Monday, April 4, 2011 Advance Notice of Scheduled Maintenance. Our web host will be upgrading the server. We expect a few minutes down-time. Update: After a few minutes downtime for scheduled maintenance, the site is up and running normally.
———

Advance Notice of Scheduled Maintenance – posted June 25, 2011
03.00a.m. UTC Monday, June 29, 2011 Our web host will be performing firmware upgrade. We expect a short period of downtime. Update – all work completed with just a couple of minutes downtime.
———

10.45 p.m. UTC Wednesday, August 10, 2011
Our web host’s data center for Quillcards is situated in Dallas in Texas. There has been a major outage affecting many web hosts and their websites – incuding ours. We shall update you as soon as we learn more.

00.45 p.m. UTC Wednesday, August 11, 2011
Engineers are working on the issue and expect it to be resolved shortly.

10.05 a.m. UTC Wednesday, August 11, 2011
Issue resolved early this morning. Site back on line.
———-

10.39 p.m. UTC Wednesday, February 8, 2012
Advance Notice Of Maintenance at the data center on Saturday, 11 February 2012 beginning at 07.00am UTC with expected downtime of 15 to 20 minutes some time between 07.00am and 11.00am.
Feb 11: Marked Resolved
———

06.48 a.m. UTC Thurssday, March 15, 2012
Our web host has reported that a drive will need to be replaced.
The work has been scheduled for 0000 UTC 16th March, and we have been advised that this is estimated to involve 30-60 minutes of downtime.