All Systems Operational
About This Site
Welcome to Dartmouth College's home for real-time incident and maintenance communications.
Academic Services
Operational
Administrative Services
Operational
Authentication
Operational
Email
Operational
M365 email
Operational
Gmail
Operational
Infrastructure
Operational
Load Balancer
Operational
Containerization
Operational
RDS Services
Operational
Active Directory
Operational
Computing Infrastructure
Operational
Network
Operational
Research Computing
Operational
General Research Services
Operational
AI
Operational
Granite
Operational
HPC
Operational
Rapport
Operational
Storage
Operational
Security
Operational
Telephone
Operational
Web
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Scheduled Maintenance
Dartmouth Chat Maintenance: 6/15 – 6/18 Jun 15, 2026 17:00 - Jun 18, 2026 08:00 EDT
MGHPCC, the data center hosting Dartmouth Chat will be undergoing maintenance from Monday, June 15th at 5pm through Thursday, June 18th at 8am. To minimize disruptions we will be migrating Dartmouth Chat temporarily. back to the Dartmouth campus.
What you need to know:
Dartmouth Chat will be offline on Monday, June 15th from 5 pm to 7pm. and again on Thursday, June 18th from 6 am to 8 am as we migrate Dartmouth Chat to and from its temporary home on the Dartmouth campus. During this window of time, local Gemma and Qwen models will be unavailable. However, the local model GPT-OSS 120b and all Cloud-based models will remain available throughout the process.
Further details are on our blog: https://ai-tools.dartmouth.edu/blog
Posted on Jun 05, 2026 - 08:43 EDT
What you need to know:
Dartmouth Chat will be offline on Monday, June 15th from 5 pm to 7pm. and again on Thursday, June 18th from 6 am to 8 am as we migrate Dartmouth Chat to and from its temporary home on the Dartmouth campus. During this window of time, local Gemma and Qwen models will be unavailable. However, the local model GPT-OSS 120b and all Cloud-based models will remain available throughout the process.
Further details are on our blog: https://ai-tools.dartmouth.edu/blog
Posted on Jun 05, 2026 - 08:43 EDT
RAPPORT COI Update Jun 16, 2026 06:00-06:30 EDT
We will be updating RAPPORT COI at this time. This update will not affect other RAPPORT applications (Grants, IRB, or Agreements).
Posted on Jun 10, 2026 - 09:23 EDT
Posted on Jun 10, 2026 - 09:23 EDT
Research Computing and Data quarterly patching Jun 16, 2026 09:00-13:00 EDT
All Research Computing and Data servers and cluster nodes will be patched and rebooted on June 16th, beginning at 09:00.
Discovery cluster nodes will be reserved from 09:00‐1:00.
No jobs will be accepted for which the requested walltime runs into the reservation window.
Public and private head nodes are included in this (Polaris, Andes, etc.)
Posted on Jun 02, 2026 - 18:07 EDT
Discovery cluster nodes will be reserved from 09:00‐1:00.
No jobs will be accepted for which the requested walltime runs into the reservation window.
Public and private head nodes are included in this (Polaris, Andes, etc.)
Posted on Jun 02, 2026 - 18:07 EDT
Zoom SSO update Jun 16, 2026 16:30-18:00 EDT
On June 16th at 5pm, we will be changing SSO on the Zoom side to facilitate the college wide SSO updates: https://services.dartmouth.edu/TDClient/1806/Portal/KB/Article/169599/Dartmouth-Login-is-Getting-a-New-Look
After making the changes, you may be signed out of your Zoom client and will be prompted to sign in again. If you are in a meeting, you may see a notification of being signed out but you will be able to finish your meeting before needing to sign in again.
Posted on Jun 12, 2026 - 14:08 EDT
After making the changes, you may be signed out of your Zoom client and will be prompted to sign in again. If you are in a meeting, you may see a notification of being signed out but you will be able to finish your meeting before needing to sign in again.
Posted on Jun 12, 2026 - 14:08 EDT
Planon Space updates Jun 16, 2026 19:00-20:00 EDT
We have been working on restructuring the address fields on properties in Planon and are preparing to move these changes up to production early next week.
Currently, the street address of a property is stored on the Street field. We are moving this data to a new field called Street address, and will be using the Street field to store only the street name, and a new field called Building number to store the building number. This change will improve the user experience for sorting and filtering, allowing users to properly search for and sort properties based on Street name. There will be an impact to consumers of the Planon API.
You can preview these changes in our pre-production environment: facilities-pre.dartmouth.edu
If you have any reports that rely on the data from the Street field, please update these reports to use the Street address field.
If you have any questions or concerns, please reach out to CSTS.
Posted on Jun 10, 2026 - 14:24 EDT
Currently, the street address of a property is stored on the Street field. We are moving this data to a new field called Street address, and will be using the Street field to store only the street name, and a new field called Building number to store the building number. This change will improve the user experience for sorting and filtering, allowing users to properly search for and sort properties based on Street name. There will be an impact to consumers of the Planon API.
You can preview these changes in our pre-production environment: facilities-pre.dartmouth.edu
If you have any reports that rely on the data from the Street field, please update these reports to use the Street address field.
If you have any questions or concerns, please reach out to CSTS.
Posted on Jun 10, 2026 - 14:24 EDT
Dell Powerscale Storage (DartFS, ThayerFS,etc.) OneFS Upgrade Jun 24, 2026 10:00-16:00 EDT
Research Computing and Data will be installing routine firmware and software updates on the Dell PowerScale system which provides network file services to the campus. This includes DartFS, ThayerFS, and others.
These reboots are staggered so that the service never goes down, but any clients connected to a node that is in the process of rebooting obviously need to reconnect to a different node.
NFS clients running Linux do this automatically and seamlessly.
Unfortunately, the SMB protocol does not allow for the same kind of seamless transition to a different node. The actual SMB client behavior depends on the operating system (Mac, Windows, or Linux) and the application using the storage.
In general, Windows systems and applications will recognize that the connection was interrupted and automatically reconnect to a different node after just a few seconds.
Mac and Linux SMB clients will keep trying the same node for longer. After a timeout period, they declare a network error. Some applications will try to restart the connection from scratch and that will work. Most commonly, Mac users can simply reconnect from their saved list of favorite servers.
Please note that if you were actively using any of these file servers during the entire maintenance window you would experience at least one such disconnection and probably several as we cycle through the nodes to reboot them all.
We will post an update here when the work is complete.
Posted on Jun 12, 2026 - 13:49 EDT
These reboots are staggered so that the service never goes down, but any clients connected to a node that is in the process of rebooting obviously need to reconnect to a different node.
NFS clients running Linux do this automatically and seamlessly.
Unfortunately, the SMB protocol does not allow for the same kind of seamless transition to a different node. The actual SMB client behavior depends on the operating system (Mac, Windows, or Linux) and the application using the storage.
In general, Windows systems and applications will recognize that the connection was interrupted and automatically reconnect to a different node after just a few seconds.
Mac and Linux SMB clients will keep trying the same node for longer. After a timeout period, they declare a network error. Some applications will try to restart the connection from scratch and that will work. Most commonly, Mac users can simply reconnect from their saved list of favorite servers.
Please note that if you were actively using any of these file servers during the entire maintenance window you would experience at least one such disconnection and probably several as we cycle through the nodes to reboot them all.
We will post an update here when the work is complete.
Posted on Jun 12, 2026 - 13:49 EDT