What is the waiting time for a response from Github Support?

[Bluesuma]

Select Topic Area

Question

Body

Hello everyone, and today I'm going to tell you about how I was literally dumped on Github, a long time ago I was in places where global sanctions are in effect, and when I logged on to my Github, I got a regional lock tag, which means I don't have access to my private repositories anymore, but thank God I do. git, where you can clone them, but I can't view them from the Web version of Github, and they also disabled the ability to create Private repositories and view private repositories in organizations in general. I went to explore how to remove this restriction on my account, you need to contact Github Support, made the first ticket, 2 months pass without an answer, recreated the ticket with a link to the last one, 2 months pass without an answer, and created 1 more ticket, and now I hope that a miracle will happen and an active employee will appear in Github Support and can get things off the ground, I also wanted to ask how were you with Github Support on your Free account?

[AnilaAnilaN]

https://docs.github.com/en/enterprise-cloud@latest/support/learning-about-github-support/about-github-support

[aryannten]

Response times from GitHub Support can vary a lot, especially depending on account type and the nature of the issue.

For free accounts, responses are typically not guaranteed within a fixed timeframe. In practice, it can range from a few days to several weeks, and in complex or policy-related cases (like regional restrictions or sanctions), it can take significantly longer because those tickets often require legal and compliance review.

For paid plans (Pro, Team, Enterprise), tickets are usually prioritized and answered much faster—often within a few business days, sometimes sooner.

A few important points in your situation:

Sanctions and regional lock issues are handled by a specialized team, which explains the long delays.

Creating multiple tickets for the same issue can sometimes slow things down, as they may be merged or deprioritized.

The best approach is usually to keep a single ticket updated with any new information rather than opening new ones.

Unfortunately, there’s no public SLA for free accounts, and long wait times—especially for sanctions-related cases—are not uncommon.

[roshanthm]

The response time from GitHub Support can vary based on the volume of requests and the nature of the issue:

General support requests: ~24 to 72 hours

Account or security issues: Often faster, sometimes within a few hours

Complex technical problems: May take several days

GitHub Support prioritizes security and account-related requests, so critical issues are handled sooner. If you haven’t heard back in a few days, you can reply to your support ticket to follow up.

[abhinav25232354]

I would say you should wait for at least 24 hours after request.

[AdminKawldron]

They are terrible. I've raised a chargeback via my bank for the Pro cost.

[A-Hassan-Dev]

How can we permanently switch to the old view? please accpet this question