Service Alerts

In the last few weeks, CCS occasionally has been receiving reports of Google Authenticator App on Android phones no longer showing the two-factor codes. This issue seems to be more frequent this past week. The cause has not been identified, and CCS continues to investigate the issue. 

If you currently have issues with your Google Authenticator App, please see below –

• If you can still log in to the my.torontomu.ca portal from a device you have logged on from within the last 30 days or have access to your two-factor backup codes, please log in and navigate to Self Service > Personal Account > Two-Factor Authentication to revoke the mobile device currently registered in your account and set up the device again.

• If you are unable to log in to your account at all, please call the CCS Help Desk to obtain an emergency code. Once you get this emergency code and are able to authenticate again, please follow the same steps above to navigate to the Two-Factor Authentication settings page to redo your two-factor authentication setup. 

Please visit the Two-Factor Authentication page for instructions on setting up your two-factor authentication for Android phone. The CCS Help Desk summer hours of operations can be found on this page.

Please accept our apologies for the problem.

-Computing and Communications Services

On Thursday June 5, 2025 at 12:30 PM, CCS received alerts that the digital certificate used by the VPN gateway device has expired. This prevented any new VPN connections from faculty, staff, students, or vendors. We are working to resolve the issue.

Update at 3:00 PM

The digital certificate has been renewed and services resumed

Please accept our apologies for the problems this outage has caused.

-Computing & Communication Services

Update: The correct time of D2L Brightspace unavailability on March 20, 2025 was from 03:04 AM to 03:10 AM EDT.

CCS received a report from D2L that D2L Brightspace was unavailable in the morning of Thursday, March 20, 2025 from 07:04 AM to 07:10 AM UTC. D2L has resolved the issue and service has been restored.

We apologize for any inconvenience this has caused.

-Computing and Communication Services

The blog.torontomu.ca site was unavailable from about 6:30 PM Thursday, January 23, 2025 until about 7:50 AM Friday, January 24, 2025. The unexpected outage was caused by a plugin and we have remediated the issue.

We apologize for any inconvenience this might have caused.

-Computing and Communications Services

On Monday January 6, 2025 at 8:00 AM, CCS received alerts that 4 out of 6 Bell phone circuits are down. This limited the maximum number of concurrent inbound and outbound calls to and from the university to 46. This caused some users to get a busy tone when trying to dial an outside number. Similarly, outside callers may get a busy signal when dialing any university phone number. A Bell technician is onsite to troubleshoot the problem. We will provide updates as they become available.

Update Jan 9, at 1:30 PM

Bell team is digging a portion of Nelson Mandela way to reach to the affected cable. Unfortunately, they cut one more circuit, so currently we are running with 23 voice channels only

Update Jan 12, at 2:30 PM

Bell team was able to fix 2 more circuits which brought the total working phone channels to 69. Bell will continue to work during the weekend.

Update Jan 14, at 9:30 AM

Bell team was able to fix 2 more circuits which brought the total working phone channels to 115. These are enough for regular operations.

Update Jan 15, at 1:00 PM

Bell team was able to fix all the circuits and services resumed at full capacity.

Please accept our apologies for the problems this outage has caused.

-Computing & Communication Services

On Tuesday December 17, 2024 at 8:00 AM, CCS received alerts that some users were unable to connect to the WiFi network. The Network team removed one of the WiFi clustered controllers to restore the service.

Please accept our apologies for the problems this outage has caused.

-Computing & Communication Services

We were informed by D2L that Brightspace was performing poorly on Tuesday, December 3, 2024 starting at approximately 10:59 a.m. EST. D2L found the issue and was able to recover from it at around 11:16 a.m. EST. During this time, some users may have experienced difficulty accessing Brightspace, but not all users would have been impacted.

We apologize for any inconvenience this has caused.

-Computing and Communication Services