News archive - January 2013

Thursday, January 31, 2013

Message from the Provost regarding LEARN

To: All University of Waterloo students
 
From: Geoff McBoyle, Vice-President, Academic & Provost
 
Date: January 31, 2013
 
Subject: Update on Waterloo LEARN
 
 
Dear Students,
 
As you are painfully aware, our Waterloo LEARN online learning management system has been unusable or unavailable since Tuesday at 3:25 p.m. You may also know that the system is hosted at a facility run by Desire2Learn (D2L).
 
An explanation of the Waterloo LEARN problem
 

Thursday, January 31, 2013

Letter From Desire2Learn

Below is a letter from Desire2Learn's President and CEO, John Baker.

UW Letter Jan 2013 John Baker .docx

Thursday, January 31, 2013

LEARN is unavailable again

[Thu., Jan 31, 12:10pm]

No new news to report in the latest update.  Desire2Learn is still working on the issue.

[Thu., Jan. 31, 10:45am]

The latest news indicates that other clients are also experiencing the slowness, and that specific clients (and we don't yet know if we are one of them) will have data migrated to a different storage device. Again, no new estimated time of recovery has been indicated.

Wednesday, January 30, 2013

LEARN UNAVAILABLE

Update 5:45 PM

The changes anticipated to be complete by 6:00PM are not complete. The revised finish time is estimated for between 10:00PM and midnight, followed by a verification process.

******

Update 12:30 PM.

Revised recovery time is 6:00PM. The issue is at the Desire2Learn hosting site and they are doing everything they can to rectify the issue.

******

We have heard from Desire2Learn (8:07am) and have done some testing of our own. According to D2L, they have "partially implemented" their solution.

Tuesday, January 29, 2013

29th Waterloo LEARN - January

Waterloo LEARN is extremely slow or completely unavailable. The vendor is aware (see message below) but we don't have a timeframe for when this may be resolved.
 

Incident: The D2L Network Operations Center (NOC) advises that an infrastructure event in your SaaS facility may be impacting access for clients.

  1. 2023 (5)
    1. July (1)
    2. June (3)
    3. January (1)
  2. 2020 (1)
  3. 2019 (4)
  4. 2018 (2)
  5. 2017 (10)
  6. 2016 (13)
  7. 2015 (17)
  8. 2014 (16)
  9. 2013 (30)
    1. December (1)
    2. November (4)
    3. October (1)
    4. August (1)
    5. July (1)
    6. May (3)
    7. April (3)
    8. March (4)
    9. February (5)
    10. January (7)
  10. 2012 (8)