# Google Gemini Rate Limiting - Provider: [Vapi](https://down.guide/vapi) - Level: confirmed - Impact: Partial outage - lasted 13d 1h - started 2026-01-21 19:40 UTC - us - id: DWN-ecd05ebcd4 - Official page: https://status.vapi.ai/incident/809181 ## Updates from Vapi ### 2026-01-21 19:40 UTC: update We are hitting rate limits again with our Google Gemini models. We are working with the vendor to resolve this issue. Please consider using another model at this time or implementing fallbacks. ### 2026-01-21 20:11 UTC: update \*\*Google/Gemini Service Degradation - Immediate Workarounds\*\* We're experiencing intermittent rate limiting from Google affecting several Vapi features. We're working with Google to resolve this. In the meantime, there are immediate workarounds for affected features. - Model (LLM): Gemini models may intermittently fail. - Workaround one - switch to a different model (e.g., GPT 4.1) - Workaround two - \[obtain an API key\](https://aistudio.google.com/app/api-keys) from Google and use that. - Vapi Dashboard → Settings → Integrations → Custom Credentials - Transcriber (STT): Gemini-based transcription may intermittently fail - Two workarounds - switch your primary or fallback transcriber to a different model (e.g., Deepgram Nova 3) or obtain an API key from Google and use that. - \[Voicemail detection\](https://docs.vapi.ai/tools/voicemail-tool): may intermittently fail if "provider" is set to "google" - Two workarounds. Switch to "openai" or "twilio" provider (if using Twilio telephony) or turn off \*\*\`voicemailDetection\`\*\* and switch to Voicemail tool - \[Query tool\](https://docs.vapi.ai/knowledge-base/using-query-tool): may intermittently fail since it relies on Google infrastructure - Two workarounds (both high effort) - switch to a custom knowledgebase or use a function tool to replicate behavior - \[Structured Outputs\](https://docs.vapi.ai/assistants/structured-outputs-quickstart): Gemini models may intermittently fail. - Workaround - switch to a different model provider: OpenAI or Anthropic - \[Speech-to-Speech\](https://docs.vapi.ai/openai-realtime): Gemini models may intermittently fail. - Workaround - switch to a different model provider: OpenAI ### 2026-01-22 07:30 UTC: update We have confirmed with the provider that the issue is from their end. We have implemented fallbacks that should help mitigate this issue going forward. We apologize for any disruption to service as a result of this issue. ### 2026-01-22 18:47 UTC: update Google is again reporting issues with the Vertex AI API that is impacting both our default and fallback Gemini clients. Consider using a different model. We are working with the provider to resolve this and will update here. ### 2026-01-26 04:03 UTC: update Google has not resolved the issue on their side, we have requested an updated timeline. Our team is working on implementing fallbacks for the services impacted by the Google degradation (the query tool). ### 2026-01-27 06:50 UTC: update Google has confirmed the underlying issue is resolved. We’re continuing to deploy a mitigation to ensure this doesn’t impact customers if it recurs. ### 2026-01-27 17:47 UTC: update We are still seeing rate limiting issues for Google LLMs and are looking into another fix we can implement to mitigate it. This is likely caused by regional exhaustion of Google Vertex AI resources rather than us hitting an org-level quota. ### 2026-02-03 21:16 UTC: resolved Google is still resolving capacity issues on their end, but we have put a mitigation in place to resolve this for gemini-2.5-flash. Please switch to this model when using Google, if you require another model reach out to support@vapi.ai. We are continuing to monitor and work with the Google team to resolve. --- down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by Sazabi (https://sazabi.com/?utm_source=down-guide&utm_medium=markdown).