From servicealerts.blog.ryerson.ca:
Ryerson’s Blog system, blog.ryerson.ca, experienced a system outage from Monday, Nov. 7, 2016 5:50 PM to Tuesday, Nov. 8, 2016 7:40 AM.
We are investigating the cause of the problem.
Please accept our apologies for any inconvenience this may cause.
-Computing and Communications Services
From servicealerts.blog.ryerson.ca:
Ryerson’s Blog system, blog.ryerson.ca experienced a system outage today, Monday October 17, 2016
The issue started about 11:45 AM with intermittent errors and was fixed at about 1:55 PM.
We are continuing to investigate the problem.
Please accept our apologies for any inconvenience this may cause.
-Computing and Communications Services
From servicealerts.blog.ryerson.ca:
This morning, Tuesday, September 27 [sic] 2016, we received reports that due to an unusually high load the Ryerson’s blog system (blog.ryerson.ca) was down. Computing and Communications Services implemented a fix and the blog was back up at 11:07 AM.
Please accept our apologies for any inconvenience this may cause.
-Computing and Communications Services
UPDATE: This issue was resolved by around 12:00 noon on Monday, September 26, and was posted on servicealerts.blog.ryerson.ca for the broader Ryerson community.
It is believed that this issue began on the morning of Friday, September 23, 2016. Our technicians continue to investigate the root cause of this issue.
—
We are currently looking into an issue that is currently preventing off-campus visitors from commenting on blogs hosted on blog.ryerson.ca.
Users commenting from on-campus do not appear to be impacted.
This post will be updated as new details are known.
Thank you for your patience while we work to resolve this issue.
blog.ryerson.ca Support
Due to emergency Network maintenance on Sunday, blog.ryerson.ca was unavailable for a couple of hours.
Originally posted on http://servicealerts.blog.ryerson.ca/, in the post Network outage on Sunday 11, 2016 from 8:00 to 9:00 AM:
On Sunday September 11, 2016, at 8:00 AM an emergency network maintenance took place. This caused access interruption to and from the Internet. The maintenance work was completed and services resumed at 9:00 AM.
We apologize for any inconvenience.
-Computing and Communications Services
From http://servicealerts.blog.ryerson.ca/:
The Ryerson blog site became unavailable on Friday, Sept. 9, starting around 11:45 AM. Partial services were restored around 2:45 PM. We’ll provide an update (on http://servicealerts.blog.ryerson.ca/) after full services are restored.
We apologize for any inconvenience.
-Computing and Communications Services
Now that the term is over, please be sure to back up any data from your course blogs, take screenshots if you want to capture the look & feel of your blog for your CV, etc.
Winter 2016 course blogs will be archived starting in June, and you will no longer have access.
If you have any questions, please use our Contact Form to get in touch. Please be sure to include your blog address.
Blogs that are used for other purposes, and not for a current term course, will not be archived at this time.
Please see this page for details on blog archiving, and the schedule for archiving courses by term.
blog.ryerson.ca will be upgraded to WordPress 4.1 on Friday, February, 2015 between 6:00am and 8:00am.
blog.ryerson.ca users and visitors to your sites may experience a brief outage during this time.
This upgrade includes some feature changes, security fixes and performance updates.
Details can be found here.
Please report any problems you may experience post-upgrade via the form linked on our Contact Us page.
The blog.ryerson.ca network will be unavailable on Friday, October 25, 2013, from 7:00am – 8:00am.
None of the blogs hosted on the network will be available during this time.
This outage is needed in order to add more disk space.
We apologize for any inconvenience this may cause.
~ The blog.ryerson.ca Team
This summer, the Twitter plugins on blog.ryerson.ca blogs (WordTwit and Tweet Blender) stopped functioning, as they had not been updated by their developers to work with a new Twitter API. We first reported this problem back in June, and have been working to resolve the issue since then.
We are happy to report that both of the plugins we were using have now been updated. If you were using either plugin previously, please see the details below to find out what you need to do in order to re-establish them on your site. Neither plugin will automatically start working again without your intervention.
We apologize for the time it has taken to get everything working again, and are thankful for your ongoing patience.
We’re *finally* back up and running with both of our Twitter plugins.
WordTwit, the plugin used to send a tweet when a new post is published on your blog, has now been updated. If you were using WordTwit previously, you will need to reconfigure the plugin – it will not automatically work. The new Twitter API has some new requirements, so the setup is a little bit more complicated. Instructions are available in the plugin’s own pages – please read them carefully.
Tweet Blender, the plugin we use to display tweets on our blogs, has also been updated. If you were using TweetBlender previously, you will need to go to the “Status” tab in the plugin and re-authenticate Twitter (by entering your username and password).