issue with Ultralytics Dedicated Inference API

[KaramRazooq]

Search before asking

• [X] I have searched the HUB issues and found no similar bug report.

HUB Component

No response

Bug

I have recently generated a new endpoint for my project, but whenever I execute it, I receive a “503 Service Unavailable” error. I have attempted to replicate this issue with other models, and the result is consistent. It is uncertain whether this is an ongoing problem. I have taken the following steps to address the issue:

• Restarting the token
• Turning the endpoint on and off
• Waiting for over a day
• Utilizing different networks and implementing various troubleshooting methods, yet the error persists.

Environment

No response

Minimal Reproducible Example

No response

Additional

No response

[UltralyticsAssistant]

👋 Hello @KaramRazooq, thank you for raising an issue about the Ultralytics HUB 🚀! We're sorry to hear you're experiencing issues with the Dedicated Inference API.

For more information and guidance, you can explore our comprehensive HUB Docs to learn more about setting up and using the platform effectively:

• Quickstart: Discover how to launch and use HUB efficiently.
• Inference API: Learn how to set up and troubleshoot the Inference API.

As this is a 🐛 Bug Report, we'd greatly appreciate it if you could provide a minimal reproducible example (MRE). This will help our engineers diagnose and resolve the issue more effectively. Please include any relevant code snippets, configurations, and any steps you took that led to this error. You can learn more about creating an MRE here.

Our dedicated team is here to help, and an Ultralytics engineer will look into your issue shortly. Thank you for your patience and understanding! 😊

[sergiuwaxmann]

@KaramRazooq Apologies for the inconvenience. Can you please share your model ID with us so we can investigate this internally?

CC @yogendrasinghx

[glenn-jocher]

@yogendrasinghx @sergiuwaxmann all tests passing for inference API for me, I don't see any errors.

[glenn-jocher]

@KaramRazooq I'm able to reproduce this. This is our fault for deploying outdated images, we're working on a fix and should have this resolved soon.

[yogendrasinghx]

@KaramRazooq Thank you for your patience. We have fixed the issue. Please try again, and let us know if you encounter any further problems.

[glenn-jocher]

Closing issue as should be resolved now.