My Space has been stuck on “Starting on T4” for several hours and it doesn’t move forward or enter the “Running” state. I’ve tried restarting it, but the issue persists.
Can I have a look on the code of app.py?
the same problem
===== Application Startup at 2025-07-13 14:45:16 =====
Nvidia T4 small
- 4 vCPU
- ·
- 15 GB RAM
- ·
- 16 GB VRAM
I though it my problem but seems hf has problems again
Maybe +1 Space cannot start and keeps getting stuck at "starting on l4"
Server issue? @meganariley
I met the same problem.
same problem
Space-related issues, including this one, have very few solutions that users can resolve on their own.
One workaround is to create a completely new Space and re-upload the same source code, but this will result in the loss of commit history, community posts, and likes.
Therefore, if you encounter an issue that appears to be related to Hugging Face’s servers with a Space you have been using for an extended period, it is recommended to send an email to Hugging Face with your account name and a detailed description of the situation. website@huggingface.co
Same issue but with A10G
I tried emailing website@huggingface.co and an automated message basically told me it’s my fault and to post on the forums.
okay this is weird? The app only started if I switch to CPU but if I change to GPU, it the same problem?
I contacted support and their solution is to upgrade to a PRO account and use ZeroGPU. It’s disappointing they won’t even acknowledge the problem but want me to buy a PRO account all of a sudden
okay this is weird?
It’s been happening very rarely for a long time, but it’s DEFINITELY WEIRD that it is happening so frequently now.
ZeroGPU is convenient, but it’s an extremely specialized GPU sharing flat-rate service, and its usability is fundamentally different from PAYG services such as T4 and L4… I can’t seem to figure it out. @meganariley @lunarflu
I have the solution!
Switch to vast
From Hugging Face Discord (“specific case” refers it):
Adam
In this specific case I’m asking in the thread to verify, but generally, if a space is building for days etc then it’s been disabled by admins for various reasons (abuse, etc). Good idea to make it more transparent though, we do already show when repos are disabled such as datasets