For a better experience, click the Compatibility Mode icon above to turn off Compatibility Mode, which is only for viewing older websites.

Repair History

Production Windows Server Patching

Tuesday, July 28, 2015 - 10:00 PM

Windows server patching was restored to regular operation for all locations on Wednesday, July 29, 2015 at 11:45:40 AM. Monthly patching all Windows Web Application servers, Management servers, and File servers.

DrexelGuest Wireless Network

Tuesday, July 28, 2015 - 1:40 AM

DrexelGuest Network was restored to regular operation for all locations on Wednesday, July 29, 2015 at 8:30 AM. The Drexel Guess Wireless network may have been intermittently unavailable during this period. DragonFly networks were not impacted.

Bb Learn Outage

Sunday, July 26, 2015 - 6:00 AM

Learn9 was restored to regular operation for all locations on Sunday, July 26, 2015 at 10:26:31 AM. There will be a brief outage for system maintenance which includes implementing a YouTube fix.

Patching Production Windows Servers

Sunday, July 26, 2015 - 6:00 AM

Windows server patching was restored to regular operation for all locations on Tuesday, July 28, 2015 at 8:51:39 AM. Patching Production DCs.

Test Windows Servers Patching

Tuesday, July 21, 2015 - 10:00 PM

Windows server patching was restored to regular operation for all locations on Tuesday, July 28, 2015 at 8:50:43 AM. Monthly patching of Test Windows Servers

Connection string being updated for ServiceStatus

Friday, July 17, 2015 - 11:28 AM

ServiceStatus was restored to regular operation for no specific location on Friday, July 17, 2015 at 11:28 AM.

IRT Data Center Services

Sunday, July 12, 2015 - 5:30 AM

All application services hosted by IRT was restored to regular operation for all locations on Sunday, July 12, 2015 at 8:28:51 AM. Durning the advertised maintenance window all application services hosted by IRT including Email, Drexel Website, Learn, Banner, Banner Web, Drexel One, SharePoint, Paypath, Nolij and others may be intermittently unavailable while network software is upgraded to provide increased security and reliability. Internet, Dragonfly, VPN, telephone and campus network services will NOT be impacted.

Exchange unavailable for some users

Tuesday, July 7, 2015 - 7:45 AM

Exchange Server was restored to regular operation for all locations on Wednesday, July 08, 2015 at 9:48 AM. Update: All mailboxes are back online. Some Exchange users are currently experiencing difficulty getting mail. IRT have identified the problem and are working to correct it.

drexel.edu

Wednesday, July 1, 2015 - 1:45 PM

Sitecore was restored to regular operation for all locations on Wednesday, July 01, 2015 at 5:54:01 PM. Sitecore websites: drexel.edu, ansp.org, etc. are unavailable. Fix is underway as of 2pm; near completion as of 4pm.

Discover outage

Tuesday, June 30, 2015 - 8:40 PM

Discover Drexel was restored to regular operation for no specific location on Wednesday, July 01, 2015 at 12:27:36 AM. 100% CPU utilization on both web nodes From AWS support site: Between 5:25 PM and 6:07 PM PDT we experienced an Internet connectivity issue with a provider outside of our network which affected traffic from some end-user networks. The issue has been resolved and the service is operating normally. The root cause of this issue was an external Internet service provider incorrectly accepting a set of routes for some AWS addresses from a third-party who inadvertently advertised these routes. Providers should normally reject these routes by policy, but in this case the routes were accepted and propagated to other ISPs affecting some end-user’s ability to access AWS resources. Once we identified the provider and third-party network, we took action to route traffic around this incorrect routing configuration. We have worked with this external Internet service provider to ensure that this does not reoccur. Additionally, some customers have reported continued connectivity issues for some of their instances. We have seen with these reported issues that this has been caused by a leap second bug within the instance operating system, which results in 100% CPU utilization. We recommend rebooting the instance via the EC2 Management Console or API, or resetting the operating system time to resolve the issue.