503 Service Unavailable hitting multiple major Image-to-3D Spaces (TripoSR, InstantMesh, LGM) via Gradio Client

I’ve reviewed the Spaces code history both manually and using AI, and it seems that for quite some time now, the code has been written in a way that no longer works when rebuilt in the “current” HF Spaces environment.
This is partly due to changes on the HF Spaces runtime side, and as you mentioned, external dependencies—such as the libraries used by Spaces—also play a significant role.

Therefore, I believe modifying the code itself is necessary regardless of the cause of the sudden reboots.

Aside from your hypothesis, here’s what I can think of as a cause for the sudden forced restarts of multiple Spaces: [Bug] Space stuck in 503 loop after waking from pause — cannot restart
From the serious HF Spaces-related issue (Stuck at space problem - #3 by hysts
) two weeks ago up to now, various Spaces-related problems have been occurring one after another, and this could be considered part of that…:downcast_face_with_sweat: