Ollama Cloud streaming timeout after 120-145s on long generation tasks

What this error means

ReadTimeout after 144.6s — ollama-cloud stream drop on long responses with large context is a Ollama failure pattern reported for developers trying to fix ollama cloud streaming requests timing out after ~2 minutes on long generation with large context windows. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

GitHub issue #16108 (created 2026-05-12, very recent). Using ollama.com cloud proxy, streaming requests timeout after ~2 minutes on long generation tasks. Log shows: ‘ollama-cloud stream drop (ReadTimeout) after 144.6s — reconnecting, retry 2/3’. No keepalive during tool composition.

Common causes

• Ollama Cloud (paid Pro plan) streaming requests timeout after ~120-145 seconds even when the model is still processing. No ping/keepalive during tool composition or long generation causes ReadTimeout errors, forcing developers to implement retry logic
• GitHub issue #16108 (created 2026-05-12, very recent). Using ollama.com cloud proxy, streaming requests timeout after ~2 minutes on long generation tasks. Log shows: ‘ollama-cloud stream drop (ReadTimeout) after 144.6s — reconnecting, retry 2/3’. No keepalive during tool composition.

Quick fixes

1. Confirm the exact error signature matches ReadTimeout after 144.6s — ollama-cloud stream drop on long responses with large context.
2. Check the Ollama account, local tool state, and provider configuration involved in the failing workflow.
3. Compare the failing environment with a known working setup, then change one configuration value at a time.

Platform/tool-specific checks

• Verify the command, editor, extension, or API client that produced the error.
• Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
• Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

1. Capture the exact error message and the command, editor action, or request that triggered it.
2. Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
3. Review the source evidence below and compare it with your environment.
4. Apply one change at a time and rerun the smallest failing action.
5. Keep the working fix documented for the team or deployment environment.

How to prevent it

• Keep provider/tool configuration documented.
• Record non-secret diagnostics such as tool version, provider name, model name, and command path.
• Add a lightweight check before CI or production workflows depend on the tool.

Sources checked

• https://github.com/ollama/ollama/issues/16108

Evidence note: GitHub issue #16108 (created 2026-05-12, very recent). Using ollama.com cloud proxy, streaming requests timeout after ~2 minutes on long generation tasks. Log shows: ‘ollama-cloud stream drop (ReadTimeout) after 144.6s — reconnecting, retry 2/3’. No keepalive during tool composition.

Related errors

• Ollama Cloud connection timeout
• Ollama streaming response cut off
• Ollama proxy timeout configuration

FAQ

What should I check first?

Start with the exact ReadTimeout after 144.6s — ollama-cloud stream drop on long responses with large context text and the smallest action that reproduces it.

Can I ignore this error?

No. Treat it as a failed Ollama workflow until the root cause is understood.

Is this guaranteed to have one fix?

No. The imported evidence supports the troubleshooting path above, but tool behavior can vary by account, plan, version, provider, and local configuration.

How do I know the fix worked?

Rerun the same command, editor action, or request. The fix is working when that action completes without ReadTimeout after 144.6s — ollama-cloud stream drop on long responses with large context.