Ollama Cloud: Frequent 503 errors making cloud models unreliable
Hey Ollama team, I've been running autonomous agents using Ollama Cloud models and running into frequent 503 Service Unavailable errors. Thought I'd report this since it's making the cloud models pretty unreliable for production use. ## What's happening Requests to cloud models randomly fail with: This happens with: - glm-5:cloud - glm-5.1:cloud - minimax-m2.7:cloud - kimi-k2.5:cloud ## How often Multiple times per hour. Sometimes a single request works, the next one fails with 503, then it works again. It's intermittent but frequent enough to break agent workflows. ## Impact - Agent requests timeout mid-conversation - Cron jobs fail unexpectedly - Users experience broken interactions in Telegram/Discord bots ## What I've tried - Retry logic with exponential backoff - Falling back to different models - None of it really helps when the 503s are this frequent ## Setup - Ollama running in Docker - Using the model suffix to hit ollama.com:443 - Fairly standard setup otherwise ## Would be helpful 1. Some visibility into when/why 503s happen (rate limiting vs capacity issues?) 2. A retry-after header so we can back off properly 3. Maybe a status page for Ollama Cloud uptime? Thanks for the great work on Ollama! Happy to provide more details if needed.
Posted by oggixx on Apr 8, 2026, 11:28 AM
Tags
Related issues
- The issue is really the extreme difficulty of programming them, especially for anything sequential (rather than combinatorial).
- I probably could have beared with it if it was only limited to programming, but it showing up in creative fields has made me feel all sor...
- I hate that I'm in deep enough to know what you mean.
- The biggest problem with “AI” is that big corps are shoving it down our throats.
- in the middel of a coding session with 5.6 sol.
- [Hero Run] 535B-A23B on 18T tokens
Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments
reliability (Other)
The issue is really the extreme difficulty of programming them, especially for anything sequential (rather than combinatorial).
I probably could have beared with it if it was only limited to programming, but it showing up in creative fields has made me feel all sor...
I hate that I'm in deep enough to know what you mean.
The biggest problem with “AI” is that big corps are shoving it down our throats.
in the middel of a coding session with 5.6 sol.
[Hero Run] 535B-A23B on 18T tokens
I hate that this is how AI is being used..
inexperienced protobuf user here -- why do non-googlers generally use protobuf?
Ollama Cloud: Frequent 503 errors making cloud models unreliable
Hey Ollama team, I've been running autonomous agents using Ollama Cloud models and running into frequent 503 Service Unavailable errors. Thought I'd report this since it's making the cloud models pretty unreliable for production use. ## What's happening Requests to cloud models randomly fail with: This happens with: - glm-5:cloud - glm-5.1:cloud - minimax-m2.7:cloud - kimi-k2.5:cloud ## How often Multiple times per hour. Sometimes a single request works, the next one fails with 503, then it works again. It's intermittent but frequent enough to break agent workflows. ## Impact - Agent requests timeout mid-conversation - Cron jobs fail unexpectedly - Users experience broken interactions in Telegram/Discord bots ## What I've tried - Retry logic with exponential backoff - Falling back to different models - None of it really helps when the 503s are this frequent ## Setup - Ollama running in Docker - Using the model suffix to hit ollama.com:443 - Fairly standard setup otherwise ## Would be helpful 1. Some visibility into when/why 503s happen (rate limiting vs capacity issues?) 2. A retry-after header so we can back off properly 3. Maybe a status page for Ollama Cloud uptime? Thanks for the great work on Ollama! Happy to provide more details if needed.
Comments (0)
No comments yet. Start the discussion.