Skip to main content
Vapi

Google Gemini Rate Limiting

Partial outage Lasted 13d 1h · started · Vapi's page

Level
confirmed
Worst impact
Partial outage
Regions
us
Down Index
37of 100

What to do

  • Check whether you use Vapi in us. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 13d 1h it lasted.

    Anything that failed between 2026-01-21 19:40 UTC and 2026-02-03 21:16 UTC may need a replay.
  • Subscribe to Vapi's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=vapi works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Vapi 8

  1. 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.

    provider

  2. 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

    provider

  3. 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.

    provider

  4. 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.

    provider

  5. 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).

    provider

  6. 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.

    provider

  7. 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.

    provider

  8. 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.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-ecd05ebcd4

Is Vapi still down?

No, this incident was resolved 2026-02-03 21:16 UTC. For Vapi's live state, see https://down.guide/vapi.

How long did it last?

13d 1h, from 2026-01-21 19:40 UTC to 2026-02-03 21:16 UTC, by the times Vapi posted.

What was affected?

Vapi named in us.

What caused it?

Vapi hasn't published a root cause. If it does, it shows here.

Where does this come from?

Vapi's official status page, https://status.vapi.ai, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.