Red Hat Support: Portal, Contact Numbers & Options

Red Hat support is tied to an active subscription — organizations without one rely on Linux server support from an outside provider or on community channels. This page covers how the subscription-attached model works: where cases are opened, which phone numbers Red Hat publishes, how severity levels map to response times, what each subscription tier includes, and what the options are when no subscription is in place.

How Red Hat support works

Support is delivered through the Red Hat Customer Portal (access.redhat.com). Access requires a Red Hat account with an active subscription attached; the subscription determines which support level applies. The standard flow:

• Open a case in the portal. Cases are filed against a specific product and version, with a severity level selected at submission. Log files and diagnostic data (sosreport output) are attached to the case.
• Severity drives routing. The severity selected sets the initial response target under the subscription's service level. Red Hat's severity policy recommends following Severity 1 and 2 submissions with a phone call to expedite handling.
• Chat and phone supplement the portal. Live chat is available from within the Customer Portal for entitled accounts. Phone support routes to regional numbers listed below.

The portal also carries the Knowledgebase, product documentation, and errata (patch) access — these are part of the subscription entitlement at every tier, including self-support.

Red Hat support phone numbers

Red Hat publishes regional technical support numbers on its technical support contact page. Numbers current as of publication (verify against that page before calling):

Phone support verifies the caller's account and subscription before a case is worked. Callers without an active subscription are directed to sales or to the public Knowledgebase.

Severity levels and response times

Red Hat defines four severity levels in its severity definitions:

• Severity 1 (Urgent): a problem actively causing serious interruption to business-critical operations.
• Severity 2 (High): a critical system partially functional, with degradation actively impacting operations.
• Severity 3 (Medium): the product functioning, with recent degradation under observation or indicators of potential functionality loss.
• Severity 4 (Low): a non-urgent query, no interruption to business-critical operations.

Initial response targets per tier, from the production support terms of service:

Standard coverage runs during standard business hours. Premium adds 24x7 coverage for Severity 1 and 2; for Severity 2 the 24x7 handling must be explicitly requested on the case — it is not automatic. Self-support subscriptions have no response targets because they include no engineer-assisted cases.

What each subscription tier includes

Two additions sit on top of these tiers. A Technical Account Manager (TAM) is a paid add-on that assigns a named Red Hat engineer for planning, escalation, and ongoing guidance. Enhanced Solution Support, offered for OpenShift and OpenStack, provides 24x7 access to senior engineers with tighter targets.

The no-cost Red Hat Developer Subscription for Individuals is self-support only. It covers up to 16 physical or virtual systems, includes portal and errata access, and includes no engineer-assisted cases. It is not licensed for production use beyond its own terms. For background on the product itself, see Red Hat Enterprise Linux.

Lifecycle boundaries and ELS

Each RHEL major release carries a ten-year lifecycle (full support, then maintenance support). Beyond that, Extended Life Cycle Support (ELS) is a paid add-on covering selected critical security fixes, selected urgent bug fixes, and troubleshooting.

RHEL 7 reached end of maintenance on June 30, 2024. ELS for RHEL 7.9 runs up to four additional years, to May 31, 2029, per Red Hat's RHEL 7 end-of-maintenance page. Systems on RHEL 7 without an ELS add-on receive no security advisories or bug fixes from Red Hat, regardless of subscription tier. RHEL 6 ELS has ended entirely.

Options without a subscription

Without an active subscription there is no Red Hat case channel, no errata access, and no phone entitlement. The available paths:

• Rebuild distributions. Rocky Linux and AlmaLinux are binary-compatible rebuilds of RHEL. They receive their own security updates and are supported by community channels (forums, mailing lists, chat), not by a vendor SLA.
• Third-party managed support. Independent providers support RHEL, Rocky, and Alma environments under their own contracts — break/fix, patching from the applicable update stream, hardening, and monitoring. Medha Cloud provides this under its managed Linux support service, with 24/7 chat and phone coverage; dial-in details are on the Linux server support number page.
• Developer Subscription for evaluation. For lab and individual development use within its 16-system limit, the no-cost developer subscription restores errata access without engineer support.

Escalation tips

• Set severity accurately at case creation; misclassified Severity 1 cases get downgraded and lose priority.
• Call the regional number after filing a Severity 1 or 2 case. Red Hat's own policy recommends this.
• For Premium Severity 2 cases needing overnight work, request 24x7 handling on the case explicitly.
• Attach sosreport output at case creation; the first engineer response is usually a data request otherwise.
• With a TAM in place, route escalations through the TAM rather than re-filing.

FAQ

What is the Red Hat support phone number in the US?

+1 919 301 3003, as published on the Customer Portal's technical support contact page. Phone support requires an active subscription on the account.

Can I open a Red Hat case without a subscription?

No. Cases require an active Standard or Premium subscription. Self-support and expired subscriptions have portal access at most, with no engineer-assisted cases.

Is the free Developer Subscription supported?

It is self-supported only: portal, Knowledgebase, and errata access for up to 16 systems, with no support cases and no response targets.

Is RHEL 7 still supported?

Only under the paid ELS add-on, which covers selected critical security fixes through May 31, 2029 for RHEL 7.9. Without ELS, RHEL 7 receives no fixes from Red Hat.