LiteLLM Timeout Silently Ignored for Bedrock and Vertex AI Deployments

What this error means

litellm.Timeout: Connection timed out. Timeout passed=Timeout(timeout=0.1), time taken=0.101 seconds is a LiteLLM failure pattern reported for developers trying to fix litellm silently ignoring configured timeout values when proxying requests to aws bedrock and google vertex ai, causing unpredictable request latency. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

GitHub issue #23375 (Mar 2026): LiteLLM’s timeout parameter is silently ignored for Bedrock and Vertex AI model groups. Despite setting timeout=0.1s, actual request takes 0.101s and gets terminated — behavior inconsistent with expected semantics. Additionally, issue #25080 (Apr 2026) discusses lack of automatic fallback configuration when rate limits are exceeded. This affects production deployments relying on LiteLLM proxy for cost management. Maps to LiteLLM category.

Common causes

• GitHub issue #23375 (Mar 2026): LiteLLM’s timeout parameter is silently ignored for Bedrock and Vertex AI model groups. Despite setting timeout=0.1s, actual request takes 0.101s and gets terminated — behavior inconsistent with expected semantics. Additionally, issue #25080 (Apr 2026) discusses lack of automatic fallback configuration when rate limits are exceeded. This affects production deployments relying on LiteLLM proxy for cost management. Maps to LiteLLM category.

Quick fixes

1. Confirm the exact error signature matches litellm.Timeout: Connection timed out. Timeout passed=Timeout(timeout=0.1), time taken=0.101 seconds.
2. Check the LiteLLM account, local tool state, and provider configuration involved in the failing workflow.
3. Check the build output, project root, and deployment platform configuration before redeploying.

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/BerriAI/litellm/issues/23375
• https://github.com/BerriAI/litellm/issues/25080

Evidence note: GitHub issue #23375 (Mar 2026): LiteLLM’s timeout parameter is silently ignored for Bedrock and Vertex AI model groups. Despite setting timeout=0.1s, actual request takes 0.101s and gets terminated — behavior inconsistent with expected semantics. Additionally, issue #25080 (Apr 2026) discusses lack of automatic fallback configuration when rate limits are exceeded. This affects production deployments relying on LiteLLM proxy for cost management. Maps to LiteLLM category.

Related errors

• LiteLLM

FAQ

What should I check first?

Start with the exact litellm.Timeout: Connection timed out. Timeout passed=Timeout(timeout=0.1), time taken=0.101 seconds text and the smallest action that reproduces it.

Can I ignore this error?

No. Treat it as a failed LiteLLM 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 litellm.Timeout: Connection timed out. Timeout passed=Timeout(timeout=0.1), time taken=0.101 seconds.