Service Disruption: the EMS room scheduling service was experiencing degraded performance
Investigating - Information Strategy and Services (ISS) is aware of and currently investigating a service disruption.

What service is affected: EMS Room Scheduling via Outlook

What is the issue: Degraded performance between EMS and Outlook Calendars. Users may be unable to use the EMS Outlook plugin or synch reservations from EMS to Outlook. EMS web app room reservations are still functioning normally.

Who is impacted: People using Outlook to reserve rooms via EMS.

Workarounds (if any): None at this time

Thank you for your patience while our team works on identifying the cause and resolving it as quickly as possible.
Oct 01, 2026 - 13:46 MDT

About This Site

Welcome to the CU Anschutz ISS and CU Denver OIT system status page. ISS will provide information about service interruptions here.

Authentication Services Operational
Email Operational
Canvas Operational
Network Services Operational
CU Anschutz Operational
CU Denver Operational
Off-Site Location Operational
Telephone Services Operational
CU Anschutz Operational
CU Denver Operational
Off-Site Location Operational
University Webpages Operational
CU Anschutz Operational
CU Denver Operational
Virtual Private Network (VPN) Operational
Zoom Operational
Other Systems and Services Degraded Performance
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance

Oct 1, 2026

Unresolved incident: Service Disruption: the EMS room scheduling service was experiencing degraded performance.

Sep 30, 2026

No incidents reported.

Sep 29, 2026

No incidents reported.

Sep 28, 2026

No incidents reported.

Sep 27, 2026

No incidents reported.

Sep 26, 2026

No incidents reported.

Sep 25, 2026

No incidents reported.

Sep 24, 2026

No incidents reported.

Sep 23, 2026

No incidents reported.

Sep 22, 2026

No incidents reported.

Sep 21, 2026

No incidents reported.

Sep 20, 2026

No incidents reported.

Sep 19, 2026

No incidents reported.

Sep 18, 2026

No incidents reported.

Sep 17, 2026

Service Disruption: Availability to some CU Denver hosted servers / services
Resolved - Information Strategy and Services (ISS) has determined that service has been fully restored.

What service was affected: Ability of some virtual servers to be reachable / hosted services being functional.

What is the resolution: Impacted virtual servers were identified and network connectivity was restored to each server individually.

If you are still experiencing service degradation after this resolution, please contact the Service Desk at 303-724-4357.

Incident: 3090341
Sep 17, 11:04 MDT
Monitoring - Information Strategy and Services (ISS) has identified the cause of the service disruption.

What service is affected: Ability of some virtual servers to be reachable / hosted services being functional.

What fix has been applied: Impacted virtual servers were identified and network connectivity was restored to each server individually.

Workarounds (if any):

ISS will continue to monitor the service for full stability and service restoration.

Incident: 3090341
Sep 16, 21:02 MDT
Investigating - Information Strategy and Services (ISS) is aware of and currently investigating a service disruption.

What service is affected: Ability of some virtual servers to be reachable / hosted services being functional.

What is the issue: In an attempt to prevent a system outage, a scheduled restart of the virtual server environment was engaged in an effort to mitigate. Upon completion of that restart, a segment of virtual servers did not reestablish connection.

Who is impacted: A small percentage of virtual servers hosted within the CUDenver environment may not be accessible due to the environment reboot.

Workarounds (if any): At this time, the majority of impacted servers have had their connections restored, and efforts to restore the remaining servers are in progress.

Thank you for your patience while our team works on identifying the cause and resolving it as quickly as possible.

Incident: 3090341
Sep 16, 19:55 MDT
Incident History Powered by Atlassian Statuspage