June 18 is a university holiday (Juneteenth). July 2 & 5 are university holidays (Independence Day)
Next monthly maintenance July 12th 7am-11am - [Details]
Annual MGHPCC Power Shutdown Aug 9-12 [Details and Schedule]
STATUS PAGE Some systems are experiencing issues.

Search Docs by Keyword


Need help? The information below will help you decide how best to find the help you need.



  • Self-Help Documentation: Our documentation covers everything from basic How-Tos up to more advanced concepts such as running MPI jobs or installing software. https://docs.rc.fas.harvard.edu/
  • Status Page: Check for know issues or maintenance windows here: https://status.rc.fas.harvard.edu/
  • Accounts: Access to many RC and Informatics resources can be requested through the RC Portal account request tool. Additional information on signing up and qualifications can be found here.
  • Password Reset: Reset your password with our password reset tool by entering the email address associated with your account. Password resets are a common request and a special purpose tool has been setup to assist with this.
  • Instruments/SPINAL: For information on how to use and access SPINAL, see documentation here.
  • Office Hours
    We hold office hours once a week on the main campus. The location and schedule can be found on our Office Hours page.
  • Create a Help Ticket:
    If our documentation does not cover your question or issue, please send us a help ticket and we’ll do our best to respond as quickly as possible.

    • Portal: Submit a ticket via the RC Ticket page (login required) for other cluster-related issues not covered by the above. Comments and attachments can be submitted from the web page and outstanding tickets can be reviewed.
    • Email: Alternately, you can submit a ticket by sending an email to rchelp@rc.fas.harvard.edu
    • Phone: If you have a voicemail number purporting to belong to us, this is incorrect. We do not offer phone support.

To help RC better help you, when submitting a ticket, be specific about the system and/or resource you’re having trouble with. A good guideline for your ticket description is to consider the who, what, where, when, and why of your problem. The more targeted your description, the faster RC can diagnose and resolve the issue.

Was this article helpful?
1.6 out Of 5 Stars
5 Stars 13%
4 Stars 13%
3 Stars 0%
2 Stars 0%
1 Stars 75%
How can we improve this article?
Need help?
© The President and Fellows of Harvard College
Except where otherwise noted, this content is licensed under Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International license.