Space stuck at "Starting" / Runtime init failed: curl (6) Could not resolve host: huggingface.co

Spaces
1

Hello,

My Hugging Face Space suddenly stopped working after running normally for about 2 months.

Now it gets stuck at Starting / Restarting, and eventually shows a runtime initialization error.

The key error message is:

Initialization step 'init' failed with exit code: 6

curl: (6) Could not resolve host: huggingface.co
Warning: Problem : timeout. Will retry in 1 seconds.

This suggests a DNS resolution failure inside the Space container.

What I have already tried

I performed several tests to rule out issues with my code:

  1. Factory restart

  2. Restart Space multiple times

  3. Duplicate the Space (new Space shows the same problem)

  4. Downgrade Python version (3.12 → 3.10)

  5. Create a minimal Gradio test Space (no model, just a textbox)

Even the minimal Gradio Space stays stuck at Starting, which suggests the problem is not related to my application code.

Additional symptoms

Before the runtime failure appeared, the Space UI sometimes briefly showed:

Could not get API info. Connection errored out.

Also, API calls to the Space started becoming extremely slow before the Space eventually stopped starting.

Space info

Space configuration:

sdk: gradio
sdk_version: 6.4.0
python_version: 3.10 / 3.12 (both tested)

The Space loads a model from Hugging Face Hub:

Qwen/Qwen3-TTS-12Hz-0.6B-Base

But based on the logs, the failure occurs before the model loading step, during initialization.

Question

Is there currently an issue with Spaces DNS resolution or networking?

Since even a minimal Space fails to start and the error indicates DNS failure for huggingface.co, it seems likely to be a platform-side issue.

Any help or confirmation would be greatly appreciated.

Thanks!

1 Like
Sleeping spaces are not restarting
2

I noticed the same issue with my space four hours ago, and I still can’t restart it.

1 Like
3

im getting same issue since last week, im just trying duplicate and it runs fine, but if u try to restart or rebuild it will facing this issues again

1 Like
4

Hi,

I had the same issue as well, tried to restart but it didn’t work. I tried editing README file and and saved. it built successfully and issue is now resolved. I’m not sure if there is deeper issue but might as well try this to see if you can get your space running.

Cheers,

1 Like
5

@hysts @meganariley Maybe hub-side issue.

1 Like
6

Thanks for reporting. There have been internal reports of issues with Spaces as well, so this could be the same issue. For now, we are awaiting a response from the infra team.

2 Likes
7

Thank you!

8

same issue for me
Space miranda-gv/dashwright is stuck on Starting/Preparing. Build succeeds, but app never reaches running state. Tested commit: 977fb3e (minimal Express health-check). This appears to be runtime allocation/init issue for this Space. Please reset or reassign the runtime node.

1 Like
9

I kept restarting my space after runtime errors, and occasionally it starts running, which is frustrating since I’m still editing.

1 Like
10

Possibly (just possibly) related case: Why there are no output when my space is running