# Spaces are down

**URL:** </static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fspaces-are-down%2F139562%3E%5C
**Category:** Spaces\
**Created:** [February 7, 2025, 6:43pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fspaces-are-down%2F139562 "2025-02-07T18:43:16Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![John6666](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/john6666/32/27664_2.png) [@John6666](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FJohn6666)%5C
**Post date:** [February 7, 2025, 8:55pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fspaces-are-down%2F139562%2F2 "2025-02-07T20:55:36Z")

</div>

Same there.

> [@Scheduling failure error in HF](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fscheduling-failure-error-in-hf%2F139173)%3A
>
> I’m unable to restart a private Space which used to run before for the past several days. During starting, it errors out (after a long time) with a message “Scheduling failure: Unable to schedule” without any additional logs. I tried Factory Reboot, but didn’t help. How can I debug this ?

---

_[View the full topic](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fspaces-are-down%2F139562)._