The terms of GitHub Premium Support are subject to change without notice and are effective as of November 2021.
When you use GitHub's support offerings, the terms of your Agreement, the GitHub Privacy Statement, and the GitHub Data Protection Agreement apply. By Agreement, we mean your main agreement with us — i.e. the GitHub Corporate Terms of Service, the GitHub Customer Agreement, or your Microsoft volume licensing agreement.
In addition to all of the benefits of GitHub Enterprise Support, GitHub Enterprise customers can purchase GitHub Premium Support, which offers:
- Written support, in English, through our support portal 24 hours per day, 7 days per week
- Phone support via callback request, in English, through our support portal 24 hours per day, 7 days per week
- A Service Level Agreement (SLA) with guaranteed initial response times
- Escalation and incident management
- Support Engineers, for Premium customers, and Customer Reliability Engineers (CREs), for Premium Pus customers, have direct access to escalation engineering resources, if needed to expedite case resolution
- Available incident coordinator to manage technical resources within GitHub until underlying issue is mitigated or fully resolved
- Access to premium content
- Health Checks
- Application upgrade assistance: Before you upgrade GitHub Enterprise Server, we review your upgrade plans, playbooks, and other documentation and answer questions specific to your environment (Premium Plus plan / GitHub Engineering Direct only)
- Technical advisory hours (Premium Plus plan / GitHub Engineering Direct only)
There are two GitHub Premium Support plans: Premium and Premium Plus / GitHub Engineering Direct.
|Premium plan||Premium Plus plan / GitHub Engineering Direct|
|Hours of operation||24 x 7||24 x 7|
|Initial response time|
|Training||Access to premium content|
|Members with support entitlements||20||20|
|Resources||Priority ticket handling|
|Escalation management||For High and Urgent priority tickets||For High and Urgent priority tickets|
|Incident management||None||For Urgent priority tickets, as needed|
|Health Checks||Unlimited automated Health Check reports (see "Generating a Health Check for your enterprise")|
|Technical advisory hours||None||4 hours per month|
|Application upgrade assistance||None||By request|
|Cloud planning||None||By request|
Enterprise owners and billing managers automatically have a support entitlement. Enterprise owners can add support entitlements to members of organizations owned by their enterprise account. For more information, see "Managing support entitlements for your enterprise."
For the Premium Plus plan / GitHub Engineering Direct, 50% of unused Managed Services hours roll over to the next month and expire at the end of the quarter.
If your support request is outside of the scope of what our team can help you with, we may recommend next steps to resolve your issue outside of GitHub Support. Your support request is possibly out of GitHub Support's scope if the request is primarily about:
- Third party integrations, such as Jira
- Hardware setup
- CI/CD, such as Jenkins
- Writing scripts
- Configuration of external authentication systems, such as SAML identity providers
- Open source projects
- Writing or debugging new queries for CodeQL
If you're uncertain if the issue is out of scope, open a ticket and we're happy to help you determine the best way to proceed.
GitHub Premium Support customers can use the GitHub Support portal to report issues in writing, in English.
GitHub Premium Support is available 24 hours a day, 7 days per week. If you purchased GitHub Premium Support prior to September 17, 2018, support is limited during holidays. For more information on holidays GitHub Premium Support observes, see the holiday schedule at "About GitHub Support."
For tickets you submit, support is available 24 hours a day, 7 days per week. The initial response time guaranteed by the SLA is dependent on the priority level of the ticket. Response time begins when GitHub Premium Support sets the priority level of the ticket. A response does not mean the issue has been resolved.
|Ticket priority level||Initial response time|
During the initial response time for Urgent priority tickets, you can expect us to do the following:
- The paged Support Engineer or CRE assigns and carefully reviews your ticket. The goal is to understand the issue, start troubleshooting, and identify next steps.
- In the initial response, the assigned Support Engineer or CRE will acknowledge ticket receipt and assignment as well as provide next steps to clarify and troubleshoot the situation. To assist with resolving your issue, the Support Engineer or CRE may ask for additional information such as screenshots, error messages, log files, diagnostics files, support bundles, or the output of specific console commands.
- Depending on the issue, the assigned Support Engineer or CRE may collaborate with others in Support, Engineering, or the regional incident commander.
- If a callback was requested upon opening the Urgent ticket, the assigned Support Engineer or CRE will determine if, at the current time, screen sharing is the most efficient way of driving the ticket towards resolution. If so, they will extend an offer to you to join a screen sharing session.
To ensure that your GitHub Enterprise Server instance is stable, you must install and implement GitHub Enterprise Server releases. Installing GitHub Enterprise Server releases ensures that you have the latest features, modifications, and enhancements as well as any updates to features, code corrections, patches or other general updates and fixes to GitHub Enterprise Server.
You must install the minimum supported version of GitHub Enterprise Server pursuant to the Supported Releases section of your applicable license agreement within 90 days of placing an order for GitHub Premium Support.
When you contact GitHub Premium Support, you can choose one of four priorities for the ticket: Urgent, High, Normal, or Low.
|Urgent||Production workflows for your organization or enterprise on GitHub Enterprise Cloud are failing due to critical service errors or outages, and the failure directly impacts the operation of your business.|
|High||Account or security issues with your organization or enterprise on GitHub Enterprise Cloud are causing limited impact to your business.|
|Normal||Members of your organization or enterprise on GitHub Enterprise Cloud are experiencing limited or moderate issues with GitHub.com, or you have general concerns or questions about your organization or enterprise.|
|Low||You have a question or suggestion about your organization or enterprise on GitHub Enterprise Cloud that is not time-sensitive, or does not otherwise block the productivity of your team.|
|Urgent||GitHub Enterprise Server is failing in a production environment, and the failure directly impacts the operation of your business.|
Support for tickets with Urgent priority is only available in the English language.
|High||GitHub Enterprise Server is failing in a production environment, but impact on your business is limited.|
|Normal||You're experiencing limited or moderate issues with GitHub Enterprise Server, or you have general concerns or questions about the operation of your instance.|
|Low||You have a question or suggestion about GitHub Enterprise Server that is not time-sensitive, or does not otherwise block the productivity of your team.|
GitHub Premium Support may consider a ticket solved after providing an explanation, recommendation, usage instructions, workaround instructions, or by advising you of an available GitHub Enterprise Server release that addresses the issue.
If you use a custom or unsupported plug-in, module, or custom code, GitHub Premium Support may ask you to remove the unsupported plug-in, module, or code while attempting to resolve the issue. If the problem is fixed when the unsupported plug-in, module, or custom code is removed, GitHub Premium Support may consider the ticket solved.
GitHub Premium Support may close a ticket if the ticket is outside the scope of support or if multiple attempts to contact you have gone unanswered. If GitHub Premium Support closes a ticket due to lack of response, you can request that GitHub Premium Support reopen the ticket.
If you don't receive an initial response within the guaranteed response time to more than four tickets in a given quarter based on GitHub's fiscal year, you're eligible for a credit. To honor the SLA, GitHub will refund 20% of the quarterly GitHub Premium Support fee in cash. To receive the refund, you must submit a credit request.
The credit request must be made within 30 days of the end of the quarter during which GitHub Premium Support did not respond to your tickets within the designated response time. Credit requests will not be honored if the respective deadline has passed. Once the respective deadline passes, you have waived the ability to claim a refund for the qualified credit.
To receive a refund, you must submit a completed credit request to firstname.lastname@example.org. To be eligible, the credit request must:
- Be sent from an email address associated with your account on your GitHub Enterprise Server instance
- Be received by GitHub by the end of the 30th day after the quarter in which the four qualifying credits occurred
- Include "Credit Request" in the subject line
The following information must be included in your credit request:
- Date (The date must be within 30 days after the quarter based on GitHub’s fiscal year end in which the claims occurred [January 31, April 30, July 31, or October 31].)
- Customer contact (You must specify both name and email address.)
- Customer address
- Qualifying credits (You must provide the date of each qualifying credit and the associated ticket number.)
- Ticket numbers
You can access premium content by signing in to the GitHub Support portal.