История сбоев Mitist

1. 16 июля 2026 г. в 09:00 UTCinvestigating

   Отключение частичной системы

Автоматический перевод официального обновления инцидента.

1. 1 июля 2026 г. в 02:54 UTCinvestigating

   All circuits connecting OC1 to MITnet are down due to a currently unknown issue affecting the provider's service. A ticket has been opened with the vendor who is currently investigating the issue. Updates will be provided as they are received.

2. 2 июля 2026 г. в 22:32 UTCresolved

   This incident has been resolved.

1. 23 июня 2026 г. в 20:05 UTCinvestigating

   IS&T is investigating an issue affecting outgoing.mit.edu. Applications and services that rely on outgoing.mit.edu for outbound email delivery may be unable to send email at this time. We are actively working to restore service and will post updates as they become available.

2. 23 июня 2026 г. в 21:58 UTCmonitoring

   IS&T has deployed a work-around, and we believe that outgoing.mit.edu is fully functional.

3. 24 июня 2026 г. в 21:20 UTCresolved

   This incident has been resolved.

1. 10 июня 2026 г. в 14:33 UTCinvestigating

   IS&T has received reports that users are unable to successfully place calls to the emergency number 100 from campus phones. If you need emergency assistance, please dial 911 or call MIT Police at 617-253-1212. All other telephone services are operating normally at this time.

2. 10 июня 2026 г. в 15:49 UTCinvestigating

   We are continuing to investigate the issue. At this time, we believe it is also affecting 911 calls placed from campus phones. If you need emergency assistance, please dial 911 from your mobile phone or call MIT Police at 617-253-1212. All other telephone services are operating normally at this time.

3. 11 июня 2026 г. в 00:23 UTCmonitoring

   A fix has been implemented by the vendor handling emergency call routing and we are monitoring the results.

4. 11 июня 2026 г. в 17:43 UTCresolved

   This incident has been resolved.

1. 20 мая 2026 г. в 17:18 UTCinvestigating

   MIT has received reports of some users being unable to connect to the MIT SECURE wireless network. IS&T is currently investigating the issue. We will provide updates as more information becomes available.

2. 21 мая 2026 г. в 00:56 UTCmonitoring

   Connection to the MIT Secure network has been restored. Contact the service desk if you have difficulty connecting to the network.

3. 21 мая 2026 г. в 18:26 UTCresolved

   This incident has been resolved.

1. 6 мая 2026 г. в 12:41 UTCinvestigating

   We are aware of a nationwide security incident involving Canvas and are actively monitoring updates from Instructure while assessing any potential impact to our environment. This incident originates with the vendor and is affecting multiple institutions; it is not the result of an issue within our local systems. Canvas remains available and operational for users. We are continuing to review information from the vendor and will share updates as more details become available, including any recommended actions or guidance.

2. 7 мая 2026 г. в 21:01 UTCinvestigating

   Due to a nationwide security incident involving Canvas that is affecting multiple institutions, Canvas is currently unavailable. The issue originates with the vendor and is not the result of an issue within MIT’s local systems. We are actively monitoring updates and will share additional information as it becomes available.

3. 8 мая 2026 г. в 13:06 UTCmonitoring

   Canvas access has been restored and classes may resume normal use of the platform. We will continue to monitor the situation and coordinate with the vendor regarding the ongoing security incident.

4. 14 мая 2026 г. в 19:00 UTCresolved

   Canvas is operational. We continue to monitor the ongoing security incident involving Canvas and its vendor, Instructure. At this time, we do not have information indicating that MIT data has been publicly released; however, our review and coordination with the vendor remain ongoing. Additional updates can be found at: https://ist.mit.edu/canvasupdate

1. 9 апреля 2026 г. в 04:15 UTCinvestigating

   Partial System Outage

2. 6 мая 2026 г. в 12:37 UTCresolved

   This incident has been resolved.

1. 19 марта 2026 г. в 19:36 UTCinvestigating

   IS&T is currently investigating reports of degraded network performance affecting AFS on Athena and Moira, including the web-based Moira interface. Users may experience slower response times, intermittent delays, or client timeouts. We will provide updates as more information becomes available.

2. 19 марта 2026 г. в 23:05 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 20 марта 2026 г. в 18:26 UTCresolved

   This incident has been resolved.

1. 3 марта 2026 г. в 11:44 UTCinvestigating

   Connectivity between MITnet and Haystack (Buildings OC21, OC24, OC25, OC26) is currently down due to fiber/optical circuit issues. IS&T has engaged MIT-LL to further investigate optical network.

2. 3 марта 2026 г. в 21:00 UTCinvestigating

   Connectivity to the building networks (Wi-Fi, VoIP, Internet) is restored, but full recovery of all Haystack circuits is still in progress.

3. 5 марта 2026 г. в 18:05 UTCresolved

   This incident has been resolved.

1. 23 февраля 2026 г. в 16:18 UTCinvestigating

   Some users may experience problems accessing Microsoft 365 services that require multi-factor authentication. We are investigating and will provide updates as more information becomes available. https://x.com/MSFT365Status

2. 23 февраля 2026 г. в 17:43 UTCmonitoring

   Microsoft 365 MFA services are operating, and authentication attempts should now be successful.

3. 23 февраля 2026 г. в 21:30 UTCresolved

   This incident has been resolved.

1. 23 февраля 2026 г. в 16:16 UTCinvestigating

   Authentication issues with Duo are currently affecting access to Microsoft services such as Outlook. Users may be unable to sign in. Status updates: https://status.duo.com/

2. 23 февраля 2026 г. в 18:06 UTCmonitoring

   The gateway issue with Duo authentication has been resolved and we are monitoring. The phone authentication issue is still being investigated by Duo. https://status.duo.com/

3. 23 февраля 2026 г. в 21:30 UTCresolved

   This incident has been resolved.

1. 19 февраля 2026 г. в 13:53 UTCinvestigating

   The network is down in several FSILG locations. This is due to a cut fiber optic cable in Boston. The fiber vendor is currently working on restoring the circuits. At this time we do not have an ETA on the repair but IS&T will continue to monitor and update as the situation progresses. Affected Houses ET - ZBT - PIKA - CP - XF - PKT - DTD - PLP - ND

2. 20 февраля 2026 г. в 14:12 UTCresolved

   The fiber vendor completed repairs on the damaged cable and network was restored to all effected FSILG locations just before 5:30 am today. If you continue to experience any network related issues in the FSILG locations listed, please contact the Service Desk at 617-253-1101 or [email protected]

1. 2 февраля 2026 г. в 16:42 UTCinvestigating

   We are receiving widespread complaints across campus regarding slow wireless connections. IS&T is investigating and we will provide updates as available.

2. 2 февраля 2026 г. в 22:59 UTCresolved

   IS&T has identified the issue impacting wireless performance and has resolved it.

1. 31 января 2026 г. в 03:24 UTCinvestigating

   IS&T is investigating a cloud hosting outage that is affecting our production server environments. Examples of sites that are affected (student.mit.edu, atlas.mit.edu, rolesapp.mit.edu, ist.mit.edu). As we receive more information on recovery, we will update this incident with appropriate information.

2. 31 января 2026 г. в 05:26 UTCmonitoring

   A fix was implemented for MIT's cloud hosting service. Services are back up and running. IS&T is monitoring the health of all services overnight.

3. 31 января 2026 г. в 22:58 UTCresolved

   This incident has been resolved.

1. 22 января 2026 г. в 20:18 UTCinvestigating

   Microsoft is reporting a degradation in some M365 services, including Exchange Online, Microsoft Purview, and Microsoft Defender. Microsoft will publish updates to X at https://x.com/MSFT365Status/status/2014422298506285161?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Etweet.

2. 22 января 2026 г. в 22:13 UTCidentified

   Microsoft has identified the issue and is applying a fix.

3. 23 января 2026 г. в 16:16 UTCresolved

   Microsoft has resolved the issue.

1. 19 декабря 2025 г. в 21:52 UTCinvestigating

   We are currently experiencing unplanned downtime affecting SAP services. The following systems are impacted: SAPGUI, Atlas, SAP Mobile (Facilities), and NetWeaver. IS&T and SAP are actively investigating and working to restore service.

2. 20 декабря 2025 г. в 15:41 UTCmonitoring

   Full connectivity has been restored; both primary and backup connections have been successfully patched. Users can now access SAP systems without limitation. Batch processes and data warehouse refresh are currently underway. We will update when these activities have concluded.

3. 20 декабря 2025 г. в 19:00 UTCresolved

   This incident is resolved. All systems are online and all data is restored. If you encounter any issues, please contact [email protected]

1. 4 декабря 2025 г. в 13:38 UTCmonitoring

   Last night's Data Warehouse loads did not run as expected. We are refreshing data this morning, and expect completion by early afternoon. At this time the data is static as of yesterday.

2. 4 декабря 2025 г. в 18:36 UTCresolved

   Data Warehouse loads have completed and all tables should be current with expected schedules.

1. 18 ноября 2025 г. в 12:45 UTCinvestigating

   Partial System Outage

2. 18 ноября 2025 г. в 16:02 UTCresolved

   This incident has been resolved.

1. 29 октября 2025 г. в 17:41 UTCmonitoring

   Microsoft is reporting a degradation in some M365 services, including Exchange Online, Microsoft 365 suite, and Microsoft Intune. Microsoft will published updates to X at https://x.com/MSFT365Status.

2. 30 октября 2025 г. в 11:13 UTCresolved

   Microsoft has reported this issue as resolved.

1. 23 октября 2025 г. в 13:45 UTCinvestigating

   Partial System Outage

2. 23 октября 2025 г. в 16:51 UTCresolved

   This incident has been resolved.