This is the status page archive for tapestryjournal.com.
You can see more recent issues on our main page.
Tapestry underwent maintenance at 10PM BST
Planned maintenance was completed
Our server upgrades took longer than expected meaning we were down from 11pm-2am. Sorry for the inconvenience.
Over a few days leading up to the 29th September, a small percentage of users saw an error message when trying to upload media. This was caused by strain on the database from our background workers. We were able to alleviate that and successfully requeue the media from the 29th. To avoid surprising any users with media suddenly appearing, we did not requeue any from before the 29th.
Apologies to those of you who experienced some errors this morning. They were due to some of our web servers running out of disk space. The issue has now been resolved.
The first week of September our phone provider experienced a DDoS attack that affected our ability to make and receive phone calls.
There was also a problem with securresuite.co.uk that card issuers (e.g. banks in the uk) use to verify that your card is secure. This meant that the card transactions processed through this company failed.
Scheduled maintenance: Tapestry was offline between 6 and 7 am GMT on Saturday 13 March for upgrades.
From January 5th-11th we saw an increased rate of errors on Tapestry. These were the result of a chain reaction triggered by an exceptionally high load. We experienced some issues with background tasks in the week that followed, see below for details. You can also see our information page about it for FAQs.
We saw a few bursts of errors on Tuesday 19th at 8:35am, 8:43am and 11:20am. These quickly subsided and we believe we have found the cause.
Since 5:19pm iOS app users were emailed any notifications that should have been push notifications. Any iOS users who were affected should start receiving push notifications the next time they open the app (which triggers it to re-register with us). Any iOS users who didn't receive a notification overnight should now be getting them as normal.
Some users were not receiving email notifications. We made sure any missed email notifications went out, but they may have been delayed.
Tapestry remained stable all day. Media did take slightly longer to process than usual and some document uploads and scheduled observations stalled after background processes resumed the day before, though. Our developers identified and fixed the issue. Stalled tasks were all restarted with the scheduled observations backlog clearing by about 7pm and the antivirus checks for documents finishing early Wednesday morning.