Private repository lost after transfer – returns 404 for both owners

[jonnieb007]

Select Topic Area

Question

Body

I transferred a private repository from one personal account to another.
The transfer completed, but now the repository returns 404 for the new owner and no longer appears for the old owner.
It is not listed under deleted repositories.
A support ticket is open but there has been no response for over 72 hours.

This looks like an orphaned repository after transfer.
Can a GitHub engineer please reattach the repository or roll back the transfer?

Old owner: jonnieb007
New owner: jamesbond1969
Repository: RiskBlox-Cyber-Suite

[Ashfaqbs]

Hey,
That's definitely concerning - sounds like the repository got stuck in limbo during the transfer. Unfortunately, this isn't something that can be resolved through community discussions since it requires direct database access that only GitHub staff have.
What you should do:

Escalate your support ticket - Since you've already opened one but haven't heard back in 72+ hours, try replying to that ticket to bump it. Sometimes adding "URGENT - Repository inaccessible after transfer" in the subject can help prioritize it.
Contact GitHub Support directly again - If you haven't gotten a response, open a new ticket at https://support.github.com/ and reference your original ticket number. Make sure to select "Account and Billing" or "Critical Issue" as the category if possible.
Try GitHub's premium support - If this is for a business or critical project, you might want to check if you have access to priority support through any paid plans.

Things to try while you wait:

Have both account owners (jonnieb007 and jamesbond1969) check if they can access the repo via direct URL: https://github.com/jamesbond1969/RiskBlox-Cyber-Suite
Check if either account has any pending email notifications about the transfer
Verify both accounts can still log in without issues

Unfortunately, repository orphaning during transfers is a known edge case that only GitHub engineers can fix by directly manipulating the database records. The good news is they can usually restore it once they look into it.
I know 72 hours feels like forever when you can't access your code. If you have a local copy, at least your work is safe. Hang in there - support should get to you soon!
Good luck!

[jonnieb007]

OK thanks for help I have raised another ticket with URGENT in the subject