From servicealerts.blog.ryerson.ca:
The blog.ryerson.ca server became unresponsive on Wednesday, January 18, 2017 at 7:50 PM. The server was restarted and service returned to normal at 8:25 AM on Thursday, January 19, 2017. We are investigating the root cause.
Please accept our apologies for any problems this outage has caused.
-Computing and Communications Services
blog.ryerson.ca will be upgraded to WordPress 4.7 on Friday, January 13, 2017 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.
From servicealerts.blog.ryerson.ca:
The blog.ryerson.ca server became unresponsive on Saturday, Nov. 19, 2016 at 6:40 PM with a database error. The server was restarted and returned to service by 7:51 PM. We are investigating the root cause.
Please accept our apologies for the problems this outage caused.
-Computing and Communications Services
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
blog.ryerson.ca will be upgraded to WordPress 4.6 on Tuesday, August 30, 2016 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.